Hi Thiery
sorry for very late reply, this issue got more and more complicated. now i have few clues. I did investigate this case further and found out some issue concerning shperical/mercator and coupling.
As the grid file i use both for telemac as well as tomawac is presented in spherical coordinates,
at the beginning of the run, telemac switches the grid to mercator (in subroutine readgeo3) because of the switch "SPATIAL PROJECTION TYPE : 3". The results of telemac however are written in spherical because of user defined subroutine write_mesh. what i get out of this makes sense.
when it comes to tomawac, i use the same grid which is in spherical coord. but i can make the choice to run (more precise to solve the equation) in mercator or spherical.
If i run tomawac in mercator, with the switch "SPHERICAL COORDINATES = NO", Tomawac uses user_defined subroutine corrxy to switch the grid to mercator, and uses write_mesh to write results in spherical coord.
Here appears the first problem. as sub readgeo3 calls corrxy, if corrxy is defined (to be used by tomawac) inside telemac_user_fortran_file, the grid will be converted to mercator two times which results in nonsense . I think i bypassed this issue in readgeo3.
I can get the same result from tomawac running in mercator in online and offline coupled case. that makes sense.
but what stays a problem is that for the same case,
for running tomawac in spherical, i get offline coupled results which are different from Mercator run. I do not manage to get online coupling working if tomawac is running in spherical. I get NaN.
does this problem sound like familiar a bug? anyone has had that? or is this what i can hope will be different in next version or do you think i have some errors in my settings?
I add the latest files as attachment. this run results in NaN which i can not trace if it starts in telemac or tomawac. dt and other settings can not be influential i guess as they have worked in offline case.
thank you again
Homayoon