open TELEMAC-MASCARET The mathematically superior suite of solvers

Hello all,

I am having difficulty for the original date of time in my CAS file using the latest version V8P2r0.

I used BINARY BOUNDARY DATA FILE which is time variable. I set original date of time exactly the same as the boundary data file (2012-05-04). However, it is giving the following error regarding the TIME,

TIME: 3902145282.0000000 IS NOT WITHIN THE RANGE OF THE FILE I.E.

But when I define the original date of time as ORIGINAL DATE OF TIME = 1982- 07- 13 it works without any error. However, the model stops exactly as the same time as the last time step of binary boundary data file.

Surprisingly, this error does not happen if I use the previous version of telemac.
I am just wondering if it is the bug in the latest version and is there any way to fix it? Please see the attached file that shows the error.


Thanks in advance,
Sanaz

Hello Sanaz,

Can you upload your steering file and also run the run_selafin.py script with option scan for this BINARY BOUNDARY DATA FILE and copy+paste the listing here please:

run_selafin.py scan name_boundary_data_file.slf

Chi-Tuan

Thanks Chi_Tuan, please see the listing, yes it seems the original date is set to be 13-7-1972 17:24:27. and this is exactly the date which is working without error (I made a typo in my first post and ORIGINAL DATE OF TIME which was working is 1972- 07- 13.
Thanks for your help on this.
Just wondering why the previous version works perfectly and why the model stops when it reaches to the last time step of Binary boundary file.

I also attached my steering file.




This file appears to be coded in "big endian"
and the floats are assumed to be SINGLE PRECISION

title : < >
Date / Time : 13-7-1972 17:24:27
Variables :
- ELEVATION Z M
- VELOCITY U M/S
- VELOCITY V M/S
NUMBERs :
- nplan* = 5
- nptfr* = 0
- iface* = 0
- nelem3 = 1712
- npoin3 = 2150
- ndp3 = 4
- nplan = 5
- x_orig/y_orig = 0, 0
- nelem2 = 428
- npoin2 = 430
- ndp2 = 2
MESH : / min: [ 84185.0234375;79665.5703125 ] / max: [ 97845.140625;87412.3828125 ]
ARRAYs :
- ikle : / min: [ 1 ] / max: [ 2150 ] [[ 1 2 431 432]
[ 2 3 432 433]
[ 3 4 433 434]
...
[1718 1717 2148 2147]
[1720 1719 2150 2149]
[1719 1718 2149 2148]]
- ipobo : / min: [ 828 ] / max: [ 66037 ] [ 828 924 1023 ... 64941 64936 64932]
Number of times : 481
First time step : 0.0
Last time step : 172800.0
Time step : 360.0


My work is done

Hello again,

Since v8p2, there is a new feature for files dealing with time. See for example the TELEMAC-2D user manual subsection 4.2.5:
"Since release 8.2, a time reference can be given: If a #REFDATE with a date + hour in YYYY-
MM-DD HH:MM:SS in year, month, day, hour, minute, second format is written in the file
(after first # line) the date+hour will be added to the times in these ASCII files."

The ASCII equivalent date after #REFDATE is stored in the binary files in the item "Date / Time" you get with the run_selafin.py script.
It enables to start a computation at a specific date and hour (with keywords ORIGINAL DATE/HOUR OF TIME) with a binary file that may use other dates and/or hours as reference. You can have a binary file starting at a time different from the starting time of your simulation, and then TELEMAC will do the conversion for you.

In your case, as the time for your data starts at 0., if using ORIGINAL DATE OF TIME and ORIGINAL HOUR OF TIME, their value should be between the bounds of time of your binary file, but also every time step of your simulation. Otherwise you get the first error message.

For your second issue, it may be due to a rounding of the computation of time for the new feature (it adds the time with an offset). My advice is to use an input file with time at least greater than (not equal to) the final time you want to model.

Anyway, can you give the error message you get when the model stops when it reaches the last time step of Binary boundary file please?

Hope this helps,

Chi-Tuan