open TELEMAC-MASCARET The mathematically superior suite of solvers

Hello,

I'm trying to model sediment transport in an TELEMAC-2D model. I wanted to use 'internal coupling with SISYPHE' but I failed at the phase of initialization of SISYPHE. I had an error like "forrtl: severe (257): formatted I/O to unit open for unformatted transfers, unit 7, file E:\Scheldt_Model_BQL\SteeringFile_Scheldt_Telemac2D_Coupled_Sisyphe_BQL.txt2284_tmp\T2DRES"



How to solve this problem and make it work?
Thanks!

Sorry, my mistake!
Problem solved by adding keywords

STEERING FILE
BOUNDARY CONDITIONS FILE
GEOMETRY FILE
RESULTS FILE

to the SISYPHE steering file. Hope this could help someone else...

Hello,

That's exactly what I was about to say. Anyway we have a way at the level of the dictionaries, to stop when a file is missing, and we'll do it in version 6.2.

With best regards,

Jean-Michel Hervouet

Hi,

Thanks for the reply. I have another question. If I have two user-defined FORTRAN files for TELEMAC and SISYPHE respectively, let's call them usrtelemac.f and usrsisyphe.f, should I give the keyword 'FORTRAN FILE' in the Telemac2D steering file the value of usrtelemac.f and the keyword 'FORTRAN FILE' in the SISYPHE steering file the value of usrsisyphe.f? Is it the right way to use two customized FORTRAN files?

Hello,

No, you can keep both. However if you put a Sisyphe subroutine in the telemac2d Fortran file it will work also, the two files are merged.

JMH

Thanks JMH!

So TELEMAC and SISYPHE also share the boundary conditions file, do they?
And since the SISYPHE has been already internal coupled with TELEMAC, I guess it's not necessary to define tracers in TELEMAC, is it?

Qilong

Hello,

Actually the boundary conditions file is not shared, but should be basically the same (Sisyphe will look at the tracer values). The sediment is defined in Sisyphe and is not a tracer in Telemac-2D.

JMH