open TELEMAC-MASCARET The mathematically superior suite of solvers

There is a very different way of defining source tracers (define all sources for each tracer) and liquid boundary (define all tracers for each boundary) tracers in the control file. (Basically the inputs are transposed in a matrix sense).

The method for liquid boundaries is better as it (indirectly) allows a default value to be defined (where last values are kept for the following undefined ones). For simple freshwater flow sources and boundaries, simple constant tracers for temperature and salinity would be normal with other possibly tracers defined through a timeseries file where needed.

I realise you can use a separate text file definition (and this would be used the most) - but the control file should use a consistent approach.

Please consider this.

Regards
John

Hi John
You're right, the question of tracers is problematic.
Few years ago I introduced the separation of index in the source and boundary file but this was not possible in the steering file...
As we're more and more working with GUI, it becomes easier to automatically build dedicated files. So maybe we could imagine to only use dedicated files and forgot some keywords...
And in order to manage constant values, we just add a flag in the file...

The consortium is open to all suggestions which can improve the use of codes and also to code contribution if you want add a new way of working with tracers. In the second case, the development should be validate by the scientific committee.

Best regards