open TELEMAC-MASCARET The mathematically superior suite of solvers

Hi,

Typically when using a binary atmospheric file, I set the initial timestep of the file to match that of the simulation. Although I've never tried it I suspect that the binary atmospheric file could cover any duration as long as it contains dated records over the simulation period of the model.

The issue that I'm running into is that when trying to carry out a Computation Continued simulation where the binary atmospheric file covers both the initial and subsequent simulation periods, the model crashes throwing an error:

"TIME: 4680064912.0000000 IS NOT WITHIN THE RANGE OF THE FILE I.E.[ 4676659200.0000000 - 4679510400.0000000 ]"

The strange this is that this timstamp is huge and well well out of my simulation period. The original date and time of the continued computation has been set to be the last time step of the previous file so I would expect the model to simply loop through the binary atmospheric file to the correct timestep. Does the binary atmospheric file have to have an initial timestep conciding with the start of the simulation. How does telemac even treat the start of the simulation. Does AT start from the start of the initial simulation or is AT reset to 0 for the continued computation?

Any idea? Am i setting this up wrong or is there potentially a bug?

Regards,
Toby

Hello Toby,

Can you upload your steering file + potential Fortran files a,d run the following commands:
run_telfile.py scan name_of_previous_computation_file (if using a PREVIOUS COMPUTATION FILE)
run_telfile.py scan name_of_binary_atmospheric_file

and upload the output listing of both please?

Chi-Tuan