Database of Nightside, High-latitude Ionosphere Meso-scale Flow Characteristics
Notice bibliographique
Résumé
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]
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Comment cette classification a été obtenuedéplier
Prédiction machine sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Le volet Gemma est une étiquette directe du modèle pour chaque travail de la base, lue sur la notice réduite au titre. Le volet Codex est un classifieur appris des 10 348 étiquettes directes de Codex et calibré sur les taux pondérés de l'échantillon; les champs sans appui suffisant ne portent aucun appel Codex. Le mode candidate est l'union des deux volets; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont pas des étiquettes humaines.
Scores du classifieur distillé par catégorie (deux têtes)
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,001 | 0,004 |
| Méta-épidémiologie (sens strict) | 0,001 | 0,000 |
| Méta-épidémiologie (sens large) | 0,001 | 0,001 |
| Bibliométrie | 0,005 | 0,007 |
| Études des sciences et des technologies | 0,000 | 0,000 |
| Communication savante | 0,002 | 0,001 |
| Science ouverte | 0,001 | 0,001 |
| Intégrité de la recherche | 0,001 | 0,001 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,042 | 0,039 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découleClassification
machine, non validéePrédiction automatique; un appel candidat d’une seule source (Gemma direct ou Codex distillé), pas un consensus.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».