supporting specifying times for consistent budget obs setup #191
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.
Recently noticed that if a timestep fails, MODFLOW-NWT writes the budget info for the failed step to mflistfile. Which is then harvested by the
flopy.utils.MfListBudget().get_dataframes()methods. This could cause misalignment of model output and instruction files if no output was expected for that kstp (which might be the case is only printing budget infor at the end of stress periods).Have added a quick work-around to the setup and apply methods to allow user to specify the times of interest. Currently not very flexible about the format of the requested
timesarray -- onus on the user to make sure that it matches the index of the dataframes that flopy returns when parsing the budget files (array of datetimes should work most of the time I think).N.B. this does not affect the automatic setup in
PstFromFlopyModel().