• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

Ouranosinc / xscen / 14232203331
90%

Build:
DEFAULT BRANCH: main
Ran 03 Apr 2025 12:28AM UTC
Jobs 6
Files 18
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

03 Apr 2025 12:24AM UTC coverage: 87.902% (-0.04%) from 87.944%
14232203331

push

github

web-flow
New column : "driving_member" (#559)

<!-- Please ensure the PR fulfills the following requirements! -->
<!-- If this is your first PR, make sure to add your details to the
AUTHORS.rst! -->
### Pull Request Checklist:
- [ ] This PR addresses an already opened issue (for bug fixes /
features)
    - This PR fixes #xyz
- [x] (If applicable) Documentation has been added / updated (for bug
fixes / features).
- [ ] (If applicable) Tests have been added.
- [x] This PR does not seem to break the templates.
- [x] CHANGELOG.rst has been updated (with summary of main changes).
- [x] Link to issue (:issue:`number`) and pull request (:pull:`number`)
has been added.

### What kind of change does this PR introduce?
Ajout d'une colonne "driving_member" dans le schéma et les colonnes
officielles. Pour les RCM, cette colonne contient le nom de réalisation
de la simulation pilote. Auparavant, l'information était dans `member`,
mais avec CORDEX-CMIP6, une nouvelle specification existe.

Dans [CORDEX-CMIP6](https://zenodo.org/records/15047096), le champ
`version_realization`, construit comme "vX-rY" contient :
> i) versions of CORDEX datasets (simulations) related to technical,
configuration, or postprocessing errors and ii) realizations with
different initial conditions for RCMs.

Dans la structure interne, il n'y a pas place à différentes versions
d'une même simulation. Ainsi, le "vX" n'apparait pas dans le path (mais
il est dans le nom de fichier). Donc, pour un RCM dans un catalogue
xscen, le champ `member` est composé de la partie "rY".

Même si la spécification CORDEX ne mentionne que les conditions
initiales, il est probable que des simulations du MRCC6 utilisant
différentes configurations et physiques (mais ayant les mêmes GES et
pilote) soient identifiées avec des r1, r2, r3, etc. Pour le moment,
MRCC5-CMIP6 contient deux simulations pilotées par ERA5 (cap et caq) qui
sont différenciées par cette nouvelle utilisation du champ.

### Does this PR introduce a breaki... (continued)

9 of 12 new or added lines in 1 file covered. (75.0%)

3967 of 4513 relevant lines covered (87.9%)

5.21 hits per line

New Missed Lines in Diff

Lines Coverage ∆ File
3
87.76
-0.33% src/xscen/extract.py
Jobs
ID Job ID Ran Files Coverage
1 run-Python3.12-conda - 14232203331.1 03 Apr 2025 12:28AM UTC 17
87.79
GitHub Action Run
2 run-Python3.11-conda - 14232203331.2 03 Apr 2025 12:28AM UTC 17
87.79
GitHub Action Run
3 run-Python3.12 - 14232203331.3 03 Apr 2025 12:29AM UTC 18
87.79
GitHub Action Run
4 run-Python3.11 - 14232203331.4 03 Apr 2025 12:29AM UTC 18
85.11
GitHub Action Run
5 run-Python3.10-conda - 14232203331.5 03 Apr 2025 12:28AM UTC 17
87.79
GitHub Action Run
6 run-Python3.10 - 14232203331.6 03 Apr 2025 12:29AM UTC 18
85.11
GitHub Action Run
Source Files on build 14232203331
  • Tree
  • List 18
  • Changed 4
  • Source Changed 4
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • e3f24201 on github
  • Prev Build on main (#14229327751)
  • Next Build on main (#14244214258)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc