I created ini, bry and frc files, using use_calendar=True in tides.ini configuration file.
In cppdefs.h, I also activate USE_CALENDAR and compile fine.
However, we launching croco, I get this error:
At line 55 of file tooldecompdat_.f90
Fortran runtime error: Bad value during integer read
Error termination. Backtrace: #0 0x7f7f81c232ba in ??? #1 0x7f7f81c23db9 in ??? #2 0x7f7f81e96254 in ??? #3 0x7f7f81e9a99f in ??? #4 0x7f7f81e9bca5 in ??? #5 0x55b65644e242 in tool_decompdate_ #6 0x55b65644dc19 in tool_datosec_ #7 0x55b65644e5f5 in tool_origindate_ #8 0x55b6564ab0c6 in get_initial_ #9 0x55b65645d303 in MAIN__ #10 0x55b65644d5de in main
It seems that dates are not well formated somewhere, but don’t where it comes from.
Could you please share your full log file , as well as your croco.in and cppdefs.h files?
This error usually suggests that there might be an incorrect time unit or date format in one of your input files. The full log should help us identify which one.
I don’t see the log file, but after checking your ini and bry NetCDF files, it appears that the time unit is missing a zero in the hours field. It currently shows 0:00:00, whereas it should be 00:00:00
double scrum_time(time) ;
scrum_time:long_name = "time since initialization" ;
scrum_time:units = "seconds since 1970-01-01 0:00:00" ;
This suggests there may have been a mismatch somewhere, as this is not the standard output from make_ini or make_bry in croco_pytools. I also noticed that your bry file is named croco_bry_mercator_.nc, with no character after the underscore, which is not expected behavior either.
I suspect the issue may come from the [Times] section of your .ini file.
Which version of croco_pytools are you using, and what values did you set in your .ini file?
As a temporary workaround, you can manually correct the time unit attribute in your files; however, this will not resolve the underlying issue. I recommend fixing your .ini file instead.