Replies: 8 comments
-
@JessicaMeixner-NOAA please help ! |
Beta Was this translation helpful? Give feedback.
-
@Rafikow It seems the time format/reference are not compatible with ww3 in ayoub.nc. |
Beta Was this translation helpful? Give feedback.
-
@aliabdolali i'm using cdo what command line do i use to convert it to a compatible time for WW3 ??? |
Beta Was this translation helpful? Give feedback.
-
please check cdo manual |
Beta Was this translation helpful? Give feedback.
-
@aliabdolali thank u sir i'll try this and tell you what i will get |
Beta Was this translation helpful? Give feedback.
-
once it's solved, it should be added to the FAQ if it's just the attributes which are missing or misspelling, it can be done with nco :
|
Beta Was this translation helpful? Give feedback.
-
@Rafikow can we close this issue? |
Beta Was this translation helpful? Give feedback.
-
There is a problem in model/ftn/w3timemd.ftn subroutine U2D Please use the standard time format: XXX since YYYY-MM-DD hh:mm:ss XXX since YYYY-M-D hh:mm:ss, XXX since YYYY-MM-D hh:mm:ss or XXX since YYYY-M-DD hh:mm:ss will make mistake It is because of the criteria_:[INDEX('XXX since YYYY-MM-DD hh:mm:ss', "-", .TRUE.).EQ.19] |
Beta Was this translation helpful? Give feedback.
-
hello i found this problem !! how can i solve it ..
thank you
./ww3_prnc | tee ww3_prnc.out
Grid name : Lake Victoria (large)
Description of inputs
*** WAVEWATCH III ERROR IN W3TIMEMD :
PREMATURE END OF TIME ATTRIBUTE
hours since 2022-3-20 00:00:00
DIFFERS FROM CONVENTIONS ISO8601
XXX since YYYY-MM-DD hh:mm:ss
XXX since YYYY-M-D h:m:s
XXX since YYYY-M-D hh:mm:ss
Beta Was this translation helpful? Give feedback.
All reactions