Delete Configuration
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
Research direction
Start with the wrfcloud.config.delete_config_from_system method and trace how namelists and cached geo_em files are stored for a configuration name. Update the deletion behavior so those artifacts are removed, then verify that deleting and recreating a configuration with the same name does not reuse the old cached file or namelists.
Written by the indexing model from the issue text.
Description
The geo_em file is cached after we run geogrid for the domain once. This way, we avoid running geogrid on the same data multiple times.
However, if a user deletes a model configuration and then creates a new model configuration with the same name, the cached geo_em file is used, but the grid definition has possibly and likely changed.
This causes the system to crash on the real step with mismatched domain grid sizes.
To fix this issue, add code in the wrfcloud.config.delete_config_from_system method to additionally delete namelists and the cached geo_em file.
A better long-term fix would be to generate a configuration ID along with each configuration, then use that ID to store files in S3, rather than the name.
- Dominant language
- Python
- Stars
- 18
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NCAR/wrfcloud
-
component: NWP components component: web ui priority: high type: bug
-
alert: NEED MORE DEFINITION type: bug
-
v1.1.1 release Openpriority: high type: task
-
component: API component: NWP components component: web ui
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
alert: NEED MORE DEFINITION type: bug
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100