Bibliographic record
Abstract
5.9.0 (2024-09-12) Changes: Add CWL schema definitions with weaver namespace (see weaver/schemas/cwl) that provide explicit requirement classes for weaver:BuiltinRequirement, weaver:WPS1Requirement, weaver:OGCAPIRequirement and weaver:ESGF-CWTRequirement to avoid missing reference warnings that were previously raised by cwltool due to Application Packages using their non-weaver namespaced classes in hints. These new CWL definitions can be reported directly in the requirements section, better describing the required dependencies of the referenced Process and/or Provider in the workflow steps. Add hosted CWL schema definitions for weaver accessible at the https://schemas.crim.ca/cwl/weaver# endpoint. Add support of weaver namespaced requirements to the cwltool runner. Add better validation off well-known CWL $namespaces as reserved keywords when deploying a Process to ensure better interoperability between implementations and adequate metadata resolution (relates to #463). Add documentation about Jupyter Notebook to CWL conversion utility ipython2cwl and a sample crim-ca/ncml2stac repository making use of it with the Weaver CLI to generate a deployed OGC API - Processes definition (fixes #63). Add parsing of additional metadata from schema.org in CWL document to convert into process fields (fixes #463). Add more metadata mapping details in documentation (fixes #613). Fixes: Fix VariableSchemaNode resolution of child nodes with complex mixture of StrictMappingSchema or when using the equivalent unknown = "raise" parameter for a colander.Mapping schema type to disallow additionalProperties that cannot be mapped to a particular child JSON schema definition. Fix VariableSchemaNode resolution to allow mapping against multiple variable sub-nodes representing different nested JSON schema nodes permitted under the additionalProperties mapping. Fix GET /jobs endpoint failing to return the rendered HTML listing when detail=true was omitted or set to any non-detailed value. The detail query parameter is ignored for HTML since details are always required to populate the Job table. Pin pymongo>=4.3 and remove celery[mongodb] extra requirement to avoid incompatible resolution of pymongo[srv]>=4.8.0 (relates to celery/celery#9254 and MongoDB PYTHON-4756).
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 imitationNot 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.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.004 | 0.014 |
| Meta-epidemiology (narrow) | 0.003 | 0.003 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.003 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.006 | 0.007 |
| Open science | 0.007 | 0.005 |
| Research integrity | 0.003 | 0.005 |
| Insufficient payload (model declined to judge) | 0.403 | 0.518 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; the direct Gemma label and the distilled Codex classifier agree on what is shown here.
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".