-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
have QC setup as part of default configuration for all runs? #109
Comments
A big piece of the "necessary files" is 5 years of daily output. We wouldn't generate that for every run, certainly, but if we were generating it anyhow... maybe a different way to ask this question is this: is there a relatively painless way to retroactively set up what's needed for the qc tests, if we happen to have the output already? |
If I understand correctly, you are asking about how easy it might be to use the QC script on runs that already generated 5 years worth of daily output? The script should already be setup to properly run with those inputs. The problem would be that the QC tests (as far as I understand them) require instantaneous output, not averaged output. So, while the script should run with the inputs from any 5 years of daily output, the tests might not be 100% appropriate due to the fact that the default namelist has |
These are runs that I created for Andrew to analyze, and we kept the aisnap and hisnap fields, which are always instantaneous even when everything else is averaged. I tried running the script on them and I get this error:
The script works when I use directories that were generated with -s qc. |
The script looks for files in the |
I see. We'll need to think about this. Options could be to allow hisnap to be read from any file name, or either hi or hisnap from iceh_inst. |
What is the overhead for doing the things needed for the quality control comparisons ("-s qc" to generate and position necessary files) for all simulations? I've done a bunch of simulations without it, and now it would be nice to go back and check the qc output without having to re-run the simulations.
The text was updated successfully, but these errors were encountered: