open TELEMAC-MASCARET The mathematically superior suite of solvers

Hi,

I am trying to couple Telemac2D with Sisyphe for a simple case. For some reasons, the coupled program only generated Telemac2D result file but did not generate the result file for Sisyphe. Based on the BOTTOM variable from the Telemac2D result file, I know that the coupled program is working properly. When I ran Sisyphe alone, the program did generate the result file. This should be something very basic that I overlooked. Any one had the similar program before?

Thanks.

EW

Hi EW,
did you check the output name of your simulation in the Sisyphe cas file?

all the best,
pablo

Hi Pablo,

When I ran sisyphe using the sisyphe steering file, the model did generate the result file.

When I ran telemac2d coupling with sisyphe, the model only generated the result file stated in the telemac2d steering file but not the result file stated in the sisyphe steering file.

Edwin

Hi Edwin,
just to check: do you assign different names to the T2D and Sisyphe res files?
best,
pablo

Yes. The names are different.

Edwin

Hello,

In coupling, number of parallel processors, time step, number of iterations and period for graphic outputs are monitored by Telemac-2D, and the corresponding values in Sisyphe steering file are discarded, could that be a hint ? You can also check in the temporary folder if a file SISRES is generated.

With best regards,

Jean-Michel Hervouet

Hi,

I do have SISRES file in the temporary folder. The file is not being converted to the name that I gave it in the steering file.

Edwin

Hello,

If the file SISRES is correct, the problem must be only:

* In the Python or Perl scripts (which one do you use ?)
* In your steering file. Check that lines do not exceed 72 characters,
also check that there is no mismatch between the steering files names. For example if in a telemac-2D steering file my_case.txt you have a line:

STEERING FILE : my_other_case.txt

it is very misleading and can drive you mad (same thing within the sisyphe steering file). Such autoreferences in steering files must be cancelled, the scripts do not need them. Check also that SISRES is not so big that it cannot be copied.

Regards,

Jean-Michel Hervouet

Thanks. I think the problem is with the Pyhton scripts. I can get by for now with the SISRES file.

Edwin

I think I've found the problem. It is now copying SISRES file properly after I changed the default value for sortieFile in runcode.py from False to True.

Edwin