`overwrite` and `redo` options are underperforming
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 50
- Forks
- 48
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
ADF run type
Model vs. Model
What happened?
There seem to be a number of times with overwrite = false or redo = false seems to be ignored (or not used efficiently) in the clm_diags branch. Is this something that's been fixed on main, or can they be used more effectively to speed up debugging?
ADF Hash you are using
v0.11-576-gb46ed6f2
What machine were you running the ADF on?
CGD machine, CISL machine
What python environment were you using?
ADF-provided Conda env
Extra info
I'll fill out more when I'm less frusterated. Namely it seems like time series are always being overwritten, even when they already exist, but plotting features take longer than expected with they already exist?
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.
Research direction
The issue names the clm_diags branch and the overwrite and redo options, but no source file or test. Reproduce the behavior with the reported ADF hash and existing time-series and plotting outputs, then trace how those options are handled. Done means existing results are reused when the options are false, without preventing required updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-visualization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100