You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
WW3 can be run using a 360 day (climate) calendar where each month has an equal number of days (30).
However, the WW3_PRNC program does not have this functionaliry meaning it is not possible to pre-process input files from netCDF files, even if calendar type is set to 360day in the mod_def file.
To Reproduce
Generate mod_def with 360day calendar. Try running ww3_prnc on a input file with 30 day months for February.
The last day that will be processed for February is the 28th (or 29th on a leap year).
Expected behavior
Missing forcing data.
Additional context
We need to handle other calendar types when decoding dates in ww3_prnc, here:
Describe the bug
WW3 can be run using a 360 day (climate) calendar where each month has an equal number of days (30).
However, the WW3_PRNC program does not have this functionaliry meaning it is not possible to pre-process input files from netCDF files, even if calendar type is set to
360day
in themod_def
file.To Reproduce
Generate mod_def with 360day calendar. Try running ww3_prnc on a input file with 30 day months for February.
The last day that will be processed for February is the 28th (or 29th on a leap year).
Expected behavior
Missing forcing data.
Additional context
We need to handle other calendar types when decoding dates in ww3_prnc, here:
WW3/model/src/ww3_prnc.F90
Lines 798 to 808 in 3952826
The text was updated successfully, but these errors were encountered: