Comparison branch for single vs multi chrtout files #486
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.
I just wanted to put this someplace. This converts the chrtout write-outs to doing one at a time instead of loading multiple files. I have some initial results as well, but it looks like the files are too small or we don't have enough to make a huge difference in timing. Will try to run more tests at CONUS scale in order to really observe computation time modifications. This also contains the command for running multiple iterations and checking the average compute time.
time for i in {1..10}; do python3 -m nwm_routing -V3 -f "/glade/work/halgren/longterm_test_files/Florence/Tar_River_test_MC_V3_implicit.yaml"; done
implicit regular - process complete
real 1m4.099s
user 0m58.139s
sys 0m5.503s
5.2945966720581055 seconds.
real 1m4.279s
user 0m57.993s
sys 0m5.621s
implicit single chrt - process complete
5.174154043197632 seconds.
real 1m5.039s
user 0m57.340s
sys 0m5.182s
process complete
5.019704341888428 seconds.
real 1m4.581s
user 0m56.585s
sys 0m5.712s