Database of Nightside, High-latitude Ionosphere Meso-scale Flow Characteristics
Bibliographic record
Abstract
This database is a compilation of nightside, high-latitude ionosphere meso-scale flow characteristics built on those used in Gabrielse et al. [2018] (https://doi.org/10.1029/2018JA025440). It is the most complete version. If you would like to use the database, please contact Christine Gabrielse (cgabrielse@ucla.edu, cgabrielse@gmail.com, and/or christine.gabrielse@aero.org). Depending on how the results are used, the main authors request co-authorship on publications that utilize this database. The methodology and selection criteria can be found in Gabrielse et al. [2018] (https://doi.org/10.1029/2018JA025440). The following list describes the columns in each data file labeled, ***_FLOW-DATA-PCvsAO_YYYY.txt The first three letters (RNK or SAS) designate the station used (Rankin Inlet or Saskatoon). Files named ***_FLOW-DATA-PCvsAO_poleward_YYYY.txt are for poleward-directed flows. Each text file is for a different year (YYYY). AO=Auroral Oval for Rankin Inlet; equatorward of the auroral oval for Saskatoon (not used) PC=Polar Cap for Rankin Inlet; Auroral Oval for Saskatoon (Note: the data files for RNK and SAS have the same format, so the PC designator means flows above the pertinent boundary (polar cap boundary for RNK, auroral oval equatorward boundary at SAS) and the AO designator means flows below the pertinent boundary.) time [YYYYMMDDhhmmss] flagAO [-1=flow could not be observed. 0=flow could be observed, but was not. 1=flow was observed] flagPC [-1=flow could not be observed. 0=flow could be observed, but was not. 1=flow was observed] FWHMavg_AO [degrees] FWHMkmavg_AO=[km] longtestranges=[ignore] Velmaxavg_AO=[m/s, actual average of max V in each range gate used] VelmaxFITavg_AO=[m/s, determined from the Gaussian fits] FWHMavg_PC=[degrees] FWHMkmavg_PC=[km] Velmaxavg_PC=[m/s, actual average of max V in each range gate used] VelmaxFITavg_PC=[m/s, determined from the Gaussian fits] ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; For the bearings/orientation, see the orientation text files. The following four variables were calculated in a first step but are not those used in the paper. They were not found with the strict selection criteria. **Please do not use.** mbearingAO=[degrees in magnetic coordinates, a negative value is South of East (clockwise from East), a positive value is North of East (CC)] mbearingPC=[degrees in magnetic coordinates, a negative value is South of East (clockwise from East), a positive value is North of East (CC)] gbearingAO=[degrees in geographic coordinates, a negative value is South of East (clockwise from East), a positive value is North of East (CC)] gbearingPC=[degrees in geographic coordinates, a negative value is South of East (clockwise from East), a positive value is North of East (CC)] ;;;;;;;;;;;;;;; minlatAO=[degrees, min geographic latitude of the flow] maxlatAO=[degrees, max geographic latitude of the flow] minlatPC=[degrees, min geographic latitude of the flow] maxlatPC=[degrees, max geographic latitude of the flow] mltAO=[degrees (MLT)] mltPC=[degrees (MLT)] AE=[nT] AL=[nT] SYMH=[nT] IMFBy=[nT] IMFBz=[nT] F107=[sfu] The following list describes the columns in each data file labeled, ***_orientation_YYYY.txt Files named ***_orientation_poleward_YYYY.txt are for poleward-directed flows. Each text file is for a different year (YYYY). The orientation was determined when enough bearings between RGs were available. See Gabrielse et al. [2018] for description. https://doi.org/10.1029/2018JA025440 AO=auroral oval PC=polar cap time [YYYYMMDDhhmmss] mbearingAO [degrees clockwise from magnetic North] gbearingAO [degrees clockwise from geographic North] mbearingPC [degrees clockwise from magnetic North] gbearingPC [degrees clockwise from geographic North] The following list describes the columns in each data file labeled, ***_SPEC_TEST_***_noRG1-2.txt time [YYYYMMDDhhmmss] RG [the range gate number at which the polar cap boundary was determined at RNK, or the auroral oval's equatorial boundary at SAS]
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.004 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.005 | 0.007 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.042 | 0.039 |
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".