MétaCan
Menu
Back to cohort
Record W2065656952 · doi:10.1145/2037826.2037846

Processing.js

2011· article· en· W2065656952 on OpenAlexafffund
Andor Salga, Daniel Hodgin, Anna Sobiepanek, Scott Downe, Mickael Medel, Catherine Leung

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicComputational Physics and Python Applications
Canadian institutionsSeneca Polytechnic
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsComputer scienceJavaScriptUnobtrusive JavaScriptJavaPlug-inParsingRendering (computer graphics)Web applicationSketchVisualizationWorld Wide WebProgramming languageRich Internet applicationComputer graphics (images)Artificial intelligence

Abstract

fetched live from OpenAlex

The Processing language [Casey Reas 2007], first introduced by Ben Fry and Casey Reas in 2001, is a simple, elegant language for data visualization that is already being used by artists, educators and commercial media groups to produce rich graphical content called sketches. Because Processing is implemented in Java, delivering Processing sketches via a web page requires the user to install a Java plug-in. Processing.js, in comparison, is an open source, cross browser JavaScript port of the Processing language; it translate Processing sketches into JavaScript using the <canvas> element for rendering. No additional plug-ins are required to view a Processing sketch delivered with Processing.js. Furthermore, Processing.js is much more than just a Processing parser written in JavaScript: it enables the embedding of other web technologies into Processing sketches and vice versa. Processing.js seamlessly integrates web technologies with the Processing language to provide an excellent framework for rich multimedia web applications.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.006
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Software · Consensus signal: Software
Teacher disagreement score0.236
Threshold uncertainty score0.789

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0020.006
Meta-epidemiology (narrow)0.0030.002
Meta-epidemiology (broad)0.0020.003
Bibliometrics0.0030.002
Science and technology studies0.0010.001
Scholarly communication0.0060.007
Open science0.0050.005
Research integrity0.0020.003
Insufficient payload (model declined to judge)0.2360.304

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.041
GPT teacher head0.257
Teacher spread0.216 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreSoftware

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations3
Published2011
Admission routes2
Has abstractyes

Explore more

Same topicComputational Physics and Python ApplicationsFrench-language works237,207