Bibliographic record
Abstract
Aims and ScopeSoftware: Practice and Experience is an internationally respected and rigorously refereed vehicle for the dissemination and discussion of practical experience with new and established software for both systems and applications.Articles published in the journal must be directly relevant to the design and implementation of software at all levels, from a useful programming technique all the way up to a large scale software system.As the journal's name suggests, the focus is on practice and experience with software itself.The journal cannot and does not attempt to cover all aspects of software engineering.The key criterion for publication of a paper is that it makes a contribution from which other persons engaged in software design and implementation might benefi t.Originality is also important.Exceptions can be made, however, for cases where apparently well-known techniques do not appear in the readily available literature. Contributions regularly:• Provide detailed accounts of completed software-system projects which can serve as 'how-to-do-it' models for future work in the same fi eld;• Present short reports on programming techniques that can be used in a wide variety of areas;• Document new techniques and tools that aid in solving software construction problems;• Explain methods/techniques that cope with the special demands of large-scale software projects.However, software process and management of software projects are topics deemed to be outside the journal's scope.The emphasis is always on practical experience; articles with theoretical or mathematical content are included only in cases where an understanding of the theory will lead to better practical systems.If it is unclear whether a manuscript is appropriate for publication in this journal, the list of referenced publications will usually provide a strong indication.When there are no references to Software: Practice and Experience papers (or to papers in a journal with a similar scope such as JSS), it is quite likely that the manuscript is not suited for this journal.Additionally, one of the journal's editors can be contacted for advice on the suitability of a particular topic.
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.001 | 0.008 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.007 | 0.007 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.008 | 0.004 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.003 | 0.002 |
| Insufficient payload (model declined to judge) | 0.935 | 0.897 |
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".