Welcome, Guest
Username: Password: Remember me
Forgot your password? Forgot your username? Create an account
Forum
System Modules
TOMAWAC
Continued computation error in coupled mode
Flat Threaded

TOPIC: Continued computation error in coupled mode

Continued computation error in coupled mode 10 years 3 months ago #13937

  • cyamin
  • cyamin's Avatar
  • OFFLINE
  • openTELEMAC Guru
  • Posts: 997
  • Thank you received: 234
Hello,

I am trying to continue a computation in TOMAWAC-TELEMAC2D-SISYPHE coupled mode. Telemac2D and Sisyphe are able to read their respective from previous results. Tomawac on the other hand, presents an error while trying to read from the previous Global results file.

Although my previous computation ends at
TIME: 4 H 32 MIN 10.0000 S ( 16330.0000 S)

LECSUI subroutine prints that
- COMPUTATIONAL RESUMPTION AT TIME 1.0000000000000000

The computation stops after INITAB is completed and subroutine IMPR tries to print information.

Here is the complete computation listing:

File Attachment:

File Name: coupled_yfist_05-06_cont.txt
File Size: 9 KB


Any ideas why this is happening?

Best Regards,
Costas
The administrator has disabled public write access.

Continued computation error in coupled mode 10 years 3 months ago #13938

  • Elodie
  • Elodie's Avatar
Hi,

did you try to run the Tomawac calculation only (from the previous global result file), without coupling, to see what happens?

Regards,

Elodie
The administrator has disabled public write access.

Continued computation error in coupled mode 10 years 3 months ago #13941

  • cyamin
  • cyamin's Avatar
  • OFFLINE
  • openTELEMAC Guru
  • Posts: 997
  • Thank you received: 234
Hi,

With coupling disabled, Tomawac passes the IMPR subroutine and then fails at the LIMWAC subroutine, where I have defined a time-varying wave spectrum (type 6).

The time read from the Global results file is still the same. Here is the listing of interest:
**** FOLLOWING COMPUTATION ****

 TITLE OF THE PREVIOUS COMPUTATION :Waves
 - COMPUTATIONAL RESUMPTION AT TIME    1.0000000000000000
 RETOUR DE LECSUI
 APPEL DE USTAR1
 RETOUR DE USTAR1
 APPEL DE INITAB
 RETOUR DE INITAB
 APPEL DE IMPR

================================================================================
       TEMPS :       1.0000 SECONDES                            0IEME  ITERATION
--------------------------------------------------------------------------------
 RETOUR DE IMPR
 APPEL DE LIMWAC

 LIMWAC
 ERROR IN THE WAVE FILE

 PLANTE: PROGRAM STOPPED AFTER AN ERROR

The error in LIMWAC is something I want to troubleshoot after the problem with the time read from the Global results file, because wrong restart time maybe the cause.

Costas
The administrator has disabled public write access.

Continued computation error in coupled mode 10 years 3 months ago #13965

  • cyamin
  • cyamin's Avatar
  • OFFLINE
  • openTELEMAC Guru
  • Posts: 997
  • Thank you received: 234
Hello,

It appears that the Computational resumption time in the global results file of TOMAWAC is always 1, if the file is output from a COUPLED computation. The Global results file from a standalone TOMAWAC computation retains the actual time that the previous computation has ended.

Am I missing something or this is a bug in the Telemac2D-Tomawac coupling?

Any help would be appreciated.
Costas
The administrator has disabled public write access.

Continued computation error in coupled mode 10 years 3 months ago #13969

  • cyamin
  • cyamin's Avatar
  • OFFLINE
  • openTELEMAC Guru
  • Posts: 997
  • Thank you received: 234
OK, I found what was wrong. The TOMAWAC cas files I had set up were meant to be used in coupling with TELEMAC2D and therefore I had not explicitly defined a value for 'TIME STEPS'. I had defined time steps in the TELEMAC2D cas file.

I studied the wac.f subroutine (I wish it had comments in English as well!) and just before the bor3D.f subroutine, it sets the computation time to the time steps defined in the TOMAWAC cas file.
!COUPLAGE TELEMAC-TOMAWAC : reset de la variable NIT (nombre
!         de pas de temps de TOMAWAC indique dans la fichier .cas)
      IF(PART.EQ.1) NIT=DUMMY
If the timesteps are not defined, the default value is 1.

The question is why is the end time defined from the time steps in the TOMAWAC cas file (which is not read in coupled mode) and not the actual duration of the coupled computation? It is a bit confusing... :unsure:

Costas
The administrator has disabled public write access.

Continued computation error in coupled mode 10 years 3 months ago #13970

  • jmhervouet
  • jmhervouet's Avatar
Hello Costas,

Sorry for this somewhat late answer. You are right, the coupling with Tomawac is different from what is done with Sisyphe, it offers more possibilities (of errors...) and the time step given for Tomawac is still used. We are working on this problem and prepare an improved version. Please note that we suspect problems in the following situations:
COUPLING PERIOD=1 and Telemac time step < Tomawac time step
COUPLING PERIOD>1 and Telemac time step = or > Tomawac time step
This is under investigation and we'll issue a correction as soon as possible.

With best regards,

Jean-Michel Hervouet
The administrator has disabled public write access.

Continued computation error in coupled mode 10 years 3 months ago #13986

  • cyamin
  • cyamin's Avatar
  • OFFLINE
  • openTELEMAC Guru
  • Posts: 997
  • Thank you received: 234
Hello,

I have resolved the previous issues and managed to run TOMAWAC with computation continued from a previous global results file. However, when I try to do the same in coupled mode, TOMAWAC stops in subroutine INITAB for no apparent reason.

Here is the listing output:

File Attachment:

File Name: coupled_ergo_05-06_2014-08-11.txt
File Size: 10 KB

And TOMAWAC cas file:

File Attachment:

File Name: twac_ergo_05-06.cas
File Size: 4 KB


Any help would be appreciated.

Regards,
Costas
The administrator has disabled public write access.

Continued computation error in coupled mode 10 years 3 months ago #13988

  • jmhervouet
  • jmhervouet's Avatar
Hello,

There are parallel communications in INITAB but nothing special, so a priori no mistake in INITAB, but maybe it is the first call to mpi in the run. A thorough debugging would be necessary with all the files to find what happens.

Regards,

JMH
The administrator has disabled public write access.
Flat Threaded
Moderators: tfouquet
Forum
System Modules
TOMAWAC
Continued computation error in coupled mode

The open TELEMAC-MASCARET template for Joomla!2.5, the HTML 4 version.