Hello Mathilde,
Which release do you use?
Can you provide your steering file?
Looking at the tide example, running t3d_tide-jmj_real.cas where the keyword ORIGINAL DATE OF TIME is used, I can see that this date is written in both 3D RESULT FILE and 2D RESULT FILE, see the beginning of the listing when running run_telfile.py scan r3d_tide-jmj_real_gen.slf :
Interpreting command line options
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~> Generic info
- Title: TELEMAC 3D: tide
- Date: 2011-10-22 00:00:00
- Format: SERAFIN
- Endianess: BIG_ENDIAN
- Precision: Single precision
~> Mesh info
- Number of dimensions: 3
- Element type: prism
- Number of points: 26246
- Number of elements: 43850
- Number of points per element: 6
- Number of planes: 11
- Number of points: 2386
- Number of elements: 4385
- Number of points per element: 3
+> Coordinates
- X offset, Y offset = 0, 0
- X range [184123.40625, 206226.0]
- Y range [136035.5, 160011.0]
- Z range [-67.40676879882812, 10.710958480834961]
~> Parallel info
- No parallel information
~> Boundary info
- No boundary file given
~> Data info
- Number of records: 51
- Time range: [0.0, 45000.0]
- Number of variables: 4
- Name: ELEVATION Z Unit: M
- Name: VELOCITY U Unit: M/S
- Name: VELOCITY V Unit: M/S
- Name: VELOCITY W Unit: M/S
My work is done
I cannot use Blue Kenue, I am not able to say if it may come from this tool or not. Please use another post-processing tool like Paraview to see if you get the same behaviour.
Chi-Tuan