open TELEMAC-MASCARET The mathematically superior suite of solvers

I am working on the transport of algae within a canal. My simulation goes very well until a certain time when it stops with this error message.

Can you tell me how to solve it?

Kind regards,

Mathys

Hello Mathys,

Which release do you use?

As you run the computation in parallel, you should have a look in the temporary folder to the output listing for every domain (you may only have read the master one), they are called PEXXXXX-YYYYY.LOG with XXXXX the number of subdomains you have run the computation (in your case, it should be 00004 and YYYYY the number of subdomain (in your case from 00000 to 00003 as you seem to have run on 4 cores).
You may have a better error message in one of them.

Have you tried to run your computation in serial (1 core) or less than 4 cores (e.g. 2 or 3?)? Still have the same error?

What about running the computation without algae feature? Do you reach final time?

Hope this helps,

Chi-Tuan

Hello,

I am on the V8P4 version. I looked at the log files, I didn't find anything wrong except in the third log where I have :
ILL-POSED PROBLEM, ENTERING FREE VELOCITY
FOR EXAMPLE AT BOUNDARY POINT NUMBER 323

However, with each simulation the point number changes.

I get the same error, but later, when I run the simulation on one, 2 or 3 processors. Without the algae function, the simulations went very well.
Please find attached the LOG files.

Thanks for your support.

Regards

Mathys

Your latest remark indicate a problem with the algae...
Did you use user fortran?
If yes, the problem is probably in one of the modified subroutine...

Yes I use user fortran.

You will find it attached

Some subroutine are tagged with v6p3... Should maybe be updated to be consistend with latest version...

Hello Mathys,

As .log extension is not allowed, please send a .zip e.g. with the 4 files of the computation which has failed.

From what files have you started to implement the Fortran file. As Christophe has written, what you have sent is suspicious and should be investigated.

Chi-Tuan

Hello everyone,

The problem is now solved, the error came from one of the user files.
Thanks for your help.

Regards

Mathys

Hello Mathys,

Can you tell what the error was please? It may help other users not to reproduce the same.

Thanks,

Chi-Tuan