The MDOR/PDOR on-line module for MISO, the planning software of Solar Orbiter instruments
Bibliographic record
Abstract
Solar Orbiter is a solar mission that will approach the Sun down to a minimum perihelion of 0.28 AU and will increase its orbit inclination with respect to the ecliptic up to a maximum angle of 34 deg. For imagers aboard Solar Orbiter there will be three 10-days remote sensing windows per orbit. Observations shall be carefully planned at least 6 months in advance. The Multi Instrument Sequence Organizer (MISO) is a web based platform developed by the SPICE group and made available to support Solar Orbiter instruments teams in planning observations by assembling Mission Database sequences. Metis is the UV and visible light coronagraph aboard Solar Orbiter. Metis is a complex instrument characterized by a rich variety of observing modes, which required a careful commissioning activity and will need support for potential maintenance operations throughout the mission. In order to support commissioning and maintenance activities, the Metis team developed a PDOR (Payload Direct Operation Request) and MDOR (Memory Direct Operation Request) module integrated in MISO and made available to all Solar Orbiter instruments. An effort was made in order to interpret the coding philosophy of the main project and to make the additional module as homogeneous as possible both to the web interface and to the algorithm logic, while integrating characteristics which are peculiar to PDORs and MDORs. An user friendly web based interface allows the operator to build the operation request and to successively modify or integrate it with further or alternative information. In the present work we describe the PDOR/MDOR module for MISO by addressing its logic and main characteristics.
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.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.049 | 0.023 |
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; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
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".