-
Notifications
You must be signed in to change notification settings - Fork 0
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
Monthly NRT #168
Monthly NRT #168
Conversation
This may belong better in the VM repo, where specifics about how the environment are setup could be included...
This does not update any attrs to reflect the NRT nature of this product. Need to update the title/version/summary/metadata_link attrs similar to how the daily nrt code does it. |
daily-nrt --last-n-days 5 --hemisphere both | ||
``` | ||
|
||
Note that the `--overwrite` flag can be used to re-create NRT data if e.g., a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you want to explicitly give the command to use the overwrite flag?
eg
daily-nrt --last-n-days 5 --hemisphere both --overwrite
...in this README.md ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, always good to see the single-use kwarg is_nrt go away.
And good to see the NRT output file directory structure mirror that of the "final" processing.
Improves readability. Originally thought I'd break this down so that I could separately create a monthly ds so that the monthly nrt cli could override global attrs. But this code is already nrt-aware (`is_nrt`) and so can handle the overrides itself.
This ensures if we decide to change the NRT platform id later, that we update the summary.
Override G10016-specific attrs in monthly NRT files
Adds a CLI for monthly NRT processing.