- Log in to post comments
I'm running into reproducibility issues on Orion when using HWRF-B. I've tested this issue by running 1 cycle twice (run "a" and run "b") under multiple configurations. The cycle I'm using is 2018083006.
- Only allowing 1 storm in the parent domain produces identical atcf files between runs "a" and "b". I tested this with just 90L (Invest) and then just 15E (Miriam).
- Only allowing 2 storms in the parent domain produces identical fhr=0 files between runs "a" and "b", but different fhr>0. I tested this with just 90L (Invest) and 15E (Miriam).
- Allowing all triggered storms in the parent domain produces identical fhr=0 files between runs "a" and "b" for 2/3 storms triggered, and different fhr>0. The three storms that were triggered were 90L (Invest), 15E (Miriam), and 16E (Norman).
Based on feedback from the HAFS/HWRF Developers Meeting on 6/7/21, I am running some additional tests and will report the results on this thread.
- Only allowing 1 storm in the parent domain - running with 16E (Norman).
- Only allowing 2 storms in the parent domain - running with 90L (Invest) and 16E (Norman) as well as running with 15E (Miriam) and 16E (Norman)
- I'm also rerunning all of the above tests to create a run "c".
In May 2020, I ran into a reproducibility issue using HWRF-B on Hera. By reducing the number of processors for the coupler to 4 processors, bitwise reproducibility was achieved on Hera. Can you point me to where I can check the number of processors used by the coupler on Orion? If it's not 4, I'll change it to 4 and run a test with that change. The path to the model directory is: /work/noaa/aoml-osse/sditchek/HB20_ALL/
Thanks for the help!
Best,
Sarah