Shared Software Environments for Heliophysics.
Bibliographic record
Abstract
Making software work across platforms is currently a challenging engineering task but modern approaches to software engineering and development are making it attainable. In the past decades shared software environments have come into a mature state. It is possible to create and use these shared software environments on different platforms. This greatly facilitates sharing and using software between computers. The premise of these shared software environments is that they ‘just work’, regardless of the platform, and decrease user time spent resolving dependencies and related software installation challenges. Furthermore, we believe that open science, which has the goal of creating transparent and reproducible results, will require such solutions since much of our research today relies on creating and/or repurposing existing software to do science. In this paper we describe the efforts of the IHDEA Science Platforms group to engineer a small set of basic shared environments for doing heliophysics research using Python software. These software environments include a range of implementations ranging from virtual environments to containerized environments as well as container-backed platforms, like JupyterLab, which may be hosted remotely in the cloud or institutional compute environments. We present use cases, our work to identify key software in use by the community, our analysis to understand the types of shared software environments that would be of the most use to the community
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 distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.003 | 0.006 |
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; both teacher heads 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".