-
Notifications
You must be signed in to change notification settings - Fork 55
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
make skip_t0_output true by default #3006
Comments
This would have the side effect of changing the first output file name. E.g., if the run starts at 2000-01-01-00000, and output is INSTANT every 5 min, the first file will have timestamp 2000-01-01-00600. I assume that's acceptable? |
Yeah, that's fine. The "conventional" (e.g., EAM) behavior is exactly this:
So, if someone wants something different, they should toggle the flag... Do you remember if people specifically requested something different back in the day? We could probably review when support for this was added and see what the thinking was at the time? |
I don't think anybody requested anything different. I think that's always been the behavior. From a recent message (maybe on slack? by Rob maybe?) I found out EAM puts t0 output in its own file. In EAMxx, we just stuffed it in the same output as following instants. Maybe that generated some discrepancy and confusion. As for the file name, users can also ask for 1 file per month (if that's not too big). We could even introduce "1 file per day", for high frequency output, if that helped. This would take away the annoyint "-00600" part from the filename. |
Hmmm. I don't think this is the default behavior... I've never seen it! |
I thought Rob said something like that, but it's quite possible I misread/misinterpreted. |
We currently special-case this to be true for ERS/ERP tests, but we really oughta make it true by default
The text was updated successfully, but these errors were encountered: