search

jimfrimel / jfHWRF

My HWRF repository for tracking issues and tasks.
0 stars 0 forks source link

Testing the 2 and 3 hourly cycling #2

Open evankalina opened 5 years ago

evankalina commented 5 years ago

What are all the configurations we want to test?

evankalina commented 5 years ago

Testing the 2- and 3-hourly cycling, and then performing a CC with trunk (verifying that we can run the trunk configuration with the hwrf_intercycle_DA branch) should be highest priority.

jimfrimel commented 5 years ago

Regarding the 2 Hourly Inter Cycles test, w/ 12 hour forecast 201810090000,201810090200,201810090400,201810090600 Reviewed the output from Rocotostat, The workflow, all Tasks were run and completed successfully.

Regarding the 3 Hourly Inter Cycles test, w/ 12 hour forecast 201810090000,201810090300,201810090600 Reviewed the output from Rocotostat, The workflow, all Tasks were run and completed successfully.

jimfrimel commented 5 years ago

Side Note: Regarding 2 hourly and 3 hourly cycling ... we did notice that the runwrf directory for the intercycles does generate hourly wrfout files up to the next cycle. Instead of just the wrfout files for the current cycle and the next cycle. (which is all that is really needed). So for example for 2 hourly cycling, The 2018100902 cycle, also generates the "03" hour wrfout and the 2018100904 cycle generates the "05" hour wrfout, which are not needed for 2 hourly cycling ... etc ...

ie. pytmp/hwrf_icda_2hour_cycles/2018100902/14L/runwrf wrfout_d03_2018-10-09_02_00_00 wrfout_d03_2018-10-09_03_00_00 wrfout_d03_2018-10-09_04_00_00

We deem this behavior acceptable, and recall that some issue may arise if we linked the wrfout interval to the cycling interval ?

jimfrimel commented 5 years ago

@evankalina Regarding running hwrf_intercycle_DA branch with default trunk settings .. Discuss merge job is failing Jet:/lfs1/.../pytmp/hwrf_icda_default_trunk/2018100900/14L/hwrf_merge.log