Use ymd instead of uninitialized date in timeInit for (unused?) optDate in alarmInit#1423
Conversation
|
@NickSzapiro-NOAA these changes look very straightforward and I saw the comments from @DeniseWorthen suggesting this fix in the other thread. I'm assuming the UFS regression tests are sufficient for these changes? We don't need any workflow tests or things like that? The standalone WW3 tests are not applicable here so I will not run them. |
|
The UFS regression tests don't use this option, so I'm not sure they're applicable either |
|
Is there any testing we need to do? If so, let me know. Otherwise I'm okay w/approving this PR - but if there's tests we should run or whatever I'm happy to help. |
|
We'll need to run the UWM RTs when this comes in (here and in CICE), but I see no reason to run any standalone RTs prior to that. |
|
I don't know if we should check that the alarm has the proper effect for optDate. For me, idea is to fix compiler warning |
|
Thanks @DeniseWorthen |
JessicaMeixner-NOAA
left a comment
There was a problem hiding this comment.
Approve assuming all the UFS tests pass.
|
@NickSzapiro-NOAA Thanks for making this fix. I'm concerned about the one in fld1md that is using |
|
I can do that one next...I assume **1 vs **1.5 has to change answers. |
f9af832
into
NOAA-EMC:dev/ufs-weather-model
Pull Request Summary
Address compiler warning and bug that
Warning: 'date' is used uninitialized [-Wuninitialized]Description
This impacts alarmInit when using optDate. I don't know that anyone does that, especially as it's not working properly.
labels: bug
Issue(s) addressed
Part of ufs-community/ufs-weather-model#2703
Commit Message
Use ymd instead of uninitialized date in timeInit for (unused?) optDate in alarmInit
Solution by @DeniseWorthen
Check list
Testing