E3SM-Project / E3SM-Project/simboard
[DevOps]: Resolve excluded E3SM v3 HPSS entries
- Dominant language
- Python
- Stars
- 1
- Forks
- 2
- Avg merge
- 25m
- Merged PRs (30d)
- 14
Description
### Task Details
Resolve the [E3SM v3 docs entries](https://docs.e3sm.org/e3sm_data_docs/_build/html/v3/CoupledSystem/simulation_data/simulation_table.html) still absent from the Chrysalis v3 archive backfill dry run. These also do not appear in the [V3 Simulation Planning](https://e3sm.atlassian.net/wiki/spaces/ED/pages/4282679297/V3+Simulation+Planning) Confluence page.
- `LR_ensemble`
- `RRM_ensemble`
### Steps to Complete
- Confirm whether each ensemble entry should exist as a Chrysalis performance-archive case.
- Ingest it when available, or document and retain its absence/exclusion.
- Re-run the Chrysalis v3 ingestion and HPSS-linker dry runs.
Contributor guide
Research direction
Start by running the Chrysalis v3 ingestion and HPSS-linker dry runs and inspect how the LR_ensemble and RRM_ensemble entries are classified. Confirm their expected status against the E3SM v3 docs and V3 Simulation Planning page, then ingest each available case or document and retain its exclusion before rerunning both dry runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100