open TELEMAC-MASCARET The mathematically superior suite of solvers

Hi all,

I'm having some issues regarding the salinity tracer resetting to the original initial conditions after a restart (COMPUTATION CONTINUED=TRUE). This only happens to the salinity tracer (TR1) and not the temperature tracer (TR2). I'm using the latest version (v8p1r0) TELEMAC2D.

After the restart, there is a RESCUE done automatically:
RESCUE: PREVIOUS CALCULATION WITHOUT TRACER, WE FIX TO TRAC0.

In the rescue, the salinity values reset to the INITIAL VALUES OF TRACERS in the CAS file (aka original initial conditions). I checked the restart file (J1.SLF aka previous results file) and the salinity tracer is saved. J2.SLF shows the salinity at the first timestep is reset.

After browsing the forum, I found this was an issue with previous versions (7 years back), so I checked if my v8p1r0 had those changes (opentelemac.com/index.php/assistance/for...values-after-restart). Which it did. The only difference is S and T is my Liquid Boundary Conditions file has Q and T values only, while S is set in CAS (via PRESCRIBED TRACER VALUES).

So I'm a bit lost as to what the issue might be (why telemac doesn't see Salinity in the restart file). I was wondering if someone has come across this in the current version.

I have attached my CAS file in case it is an issue of missing KEYWORDS but temperature works after reset.

I'd appreciate any help in this.

Cheers,
Shiv

Ad hoc resolved.

Found a earlier topic that resolved this.
www.opentelemac.co.uk/index.php/assistan...ued-multiple-tracers

Looks like you add a dummy tracer as the first tracer and do the simulations.
It works for me, since the dummy tracer gets reset each time.
Though I guess it may be slowing the simulation dow a tid bit.

Hello,

This is a bug. It was solved in the trunk version (r15086).
In sources/telemac2d/rescue.f subroutine, can you change the hard coded value 34 to 35? It should then work.

In details for the lines:
Change
IF(TROUVE(34+ITRAC).EQ.0) THEN
to
IF(TROUVE(35+ITRAC).EQ.0) THEN

Anyway, to be sure that you do not miss any latest fixes for the official release, please use the latest release (currently v8p1r1, but this bug was not solved at that time).

Hope this helps,

Chi-Tuan