make clear obs_window_seconds and obs_window_days are unsupported #525
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
both filter and perfect_model_obs have obs_window_days and obs_window_seconds in their namelists. these are for future use and are currently unsupported. update the docs to be more clear about this and update the code to print out a warning message if they are changed to be >= 0.
also check both the days and seconds values for obs_window_xxx and also init_time_xxx. if either are >= 0, call set_time(). that will catch and print a fatal error if one is set and the other is left at -1. the old code only tested days, so if someone set seconds >= 0 but left days negative the init time would have been set to 0, 0 and the namelist values wouldn't have been used without any message.
Fixes issue
#520
Types of changes
Documentation changes needed?
Tests
I ran Lorenz 96 pmo and filter with various combinations of values in the namelist for both init_time_xxx and obs_window_xxx and it gave me the results i expected.
Checklist for merging
Checklist for release
Testing Datasets