Welcome, Guest
Username: Password: Remember me
Forgot your password? Forgot your username? Create an account
Forum
System Modules
TELEMAC-2D
Fail to run after allocating memory
Flat Threaded
  • Page:
  • 1
  • 2

TOPIC: Fail to run after allocating memory

Fail to run after allocating memory 12 years 1 day ago #6482

  • Nardini26
  • Nardini26's Avatar
Hi all,

I'm confused about the reason of the run failure:
Running your simulation :
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


C:\TELEMAC\Modelisation_Saubens\Saubens_module\Saubens_remodule\Saubens.cas_2012
-11-23-11h06min09s\out_telemac2dv6p2.exe

 LISTING DE TELEMAC-2D ---------------------------------------------------------
---------------------

                 TTTTT  EEEEE  L      EEEEE  M   M  AAAAA  CCCCC
                   T    E      L      E      MM MM  A   A  C
                   T    EEE    L      EEE    M M M  AAAAA  C
                   T    E      L      E      M   M  A   A  C
                   T    EEEEE  LLLLL  EEEEE  M   M  A   A  CCCCC

                         2D    VERSION 6.2    FORTRAN 90
                               WITH SEVERAL TRACERS
                         COUPLED WITH SISYPHE AND TOMAWAC

                   ********************************************
                   *               LECDON:                    *
                   *        APRES APPEL DE DAMOCLES           *
                   *     VERIFICATION DES DONNEES LUES        *
                   *     SUR LE FICHIER DES PARAMETRES        *
                   ********************************************

 SORTIE DE LECDON. TITRE DE L'ETUDE :

 OUVERTURE DES FICHIERS POUR TELEMAC2D

                          *****************************
                          * ALLOCATION DE LA MEMOIRE  *
                          *****************************

 READGEO1 : TITRE= maillage

 NOMBRE D'ELEMENTS:   139914
 NOMBRE REEL DE POINTS:    70277
 MXPTEL (BIEF) : NOMBRE MAXIMUM D'ELEMENTS VOISINS D'
                                  UN POINT :  12
                 NOMBRE MAXIMUM DE POINTS VOISINS D'UN
                                   POINT :  12
 CORRXY (BIEF) : PAS DE MODIFICATION DES COORDONNEES

 MAILLAGE : MESH   ALLOUE

                     ****************************************
                     * FIN DE L'ALLOCATION DE LA MEMOIRE  : *
                     ****************************************

_____________
runcode::main:
      C:\TELEMAC\Modelisation_Saubens\Saubens_module\Saubens_remodule:
   |runCAS: fail to run
   |      C:\TELEMAC\Modelisation_Saubens\Saubens_module\Saubens_remodule\Sauben
s.cas_2012-11-23-11h06min09s\out_telemac2dv6p2.exe

Does it mean that my machine is lacking memory to run the model?
Please find attached my cas file.
Thank you in advance.


File Attachment:

File Name: Saubens.txt
File Size: 2 KB
The administrator has disabled public write access.

Fail to run after allocating memory 12 years 1 day ago #6484

  • riadh
  • riadh's Avatar
Hello,

It could be a problem of lack of memory. Also, maybe the problem is that Telemac was not well installed; otherwise, there is a problem in your model and in such case, we need the full model with all necessary files to check up the problem.
For me, a model with 70277 nodes is big for a 1proc simulation. However, it can run easily without any problem of memory. Try to run it in parallel (maybe on an other platform with more memory), this will permit to see if it is a problem of memory. If it is not possible, send us your model and I will try to run it on my machine.

With my best regards.

Riadh
The administrator has disabled public write access.

Fail to run after allocating memory 11 years 11 months ago #6494

  • pham
  • pham's Avatar
  • OFFLINE
  • Administrator
  • Posts: 1559
  • Thank you received: 602
Hello,

Your attached file is called Saubens.txt whereas the keyword for STEERING FILE ('FICHIER DES PARAMETRES' in French) is filled in with Saubens.cas. It is strongly recommended not to use different names and strongly advised not to use in 'STEERING FILE' keyword in the steering file (please comment it or delete it). That may lead to errors that are difficult to solve.

Anyway, Riadh is right, it will be difficult to give correct advice without the whole input files.

I only have one first comment on your mesh without seeing it: in my opinion, 12 neighbours for one single node is quite big!

Regards,

Chi-Tuan
The administrator has disabled public write access.

Fail to run after allocating memory 11 years 11 months ago #6500

  • Nardini26
  • Nardini26's Avatar
Hi Pham and Riadh,

thank you both for your answers.

Concerning the .txt, i just changed it just before to attach the file in order to insert it in the text. Well, i reduced the number of elements to 81290 but it still doesn't work, the same message appears.

I try to adjust the mesh to avoid the number of neighbours. I used the mesh treatment tool in Fudaa, manually in Blue Kenue also but still 11 neighbours for one node and i don't know how to locate it and ajust it efficiently. Is there a different way to detect and correct these type of nodes?

I attached the whole input files to you. As a self taught-user and my first project with Telemac, i'll appreciate all your relevant comments.
Thank you very much.
Attachments:
The administrator has disabled public write access.

Fail to run after allocating memory 11 years 11 months ago #6501

  • riadh
  • riadh's Avatar
Hello,

I tried your case on my local station and it seems that you have a problem with your CLI file. Maybe you did not update your cli file when you have modified the geometry file.
The error is "end-of-file during reading, unit 7, file = .../T2DCLI"

Try to reload the geometry file and to generate a new boundary condition file.

I hope that this helps.

Riadh
The administrator has disabled public write access.

Fail to run after allocating memory 11 years 11 months ago #6502

  • Nardini26
  • Nardini26's Avatar
Hello Riadh,

This error didn't appeared to me while running the model but nevertheless, i updated the project as you suggested. I forgot sometimes to change the path of the input files before running.

The error pops up again... While loading the mesh, a message tell me that the cartesian mesh is not acceped, are you familiar with this?
Please find attached the new project.

Thank you in advance.
Max
Attachments:
The administrator has disabled public write access.

Fail to run after allocating memory 11 years 11 months ago #6507

  • riadh
  • riadh's Avatar
Dear Max,

The error indicating that your CLI file is bad, hides the real problem which is your geometry file. I have reloaded your geo file in BK and I saved it in a new Selafin geo file (riadh.slf) and I generated the new cli file (which is exactly identical to yours) and Telemac works well.
I have changed some keywords to be more coherent with your medel. it will be a first step to start with Telemac.
The new files are attached hereafter.

With my best regards.
Riadh
Attachments:
The administrator has disabled public write access.

Fail to run after allocating memory 11 years 11 months ago #6510

  • Nardini26
  • Nardini26's Avatar
Hello Riadh,

well, it's good to see that running the model is not an utopy, you give me hope with this ^^. I'm still concerned about "what am i doing wrong" in the process. I'm curious about your method to generate the selafin file. I saw you didn't affect friction coefficient, maybe the problem come from it.

I use for the bottom friction the "FROTTEMENT" variable, are "BOTTOM" or "BOTTOM FRICTION" more appropriated? I try to run a model without any friction coefficient but it doesn't work as well...

Concerning the mesh, once i create the selafin file in BK, i load it in Fudaa to use the mesh treatment tool, save it as a serafin file, and reload it again in BK to auto adjust nodes and generate finally the CLI file. Is this method coherent for you?

Thank you Riadh.
Max
The administrator has disabled public write access.

Fail to run after allocating memory 11 years 11 months ago #6512

  • riadh
  • riadh's Avatar
Hi Max,

You're problably right, the problem can come from the friction layer in the mesh, I did not investigate that point.
For friction, the variable is BOTTOM FRICTION.
For your last question, Yes it seems coeherent, however, I think that you can do everything in BK without FUDAA. Take a glance on the user manual of BK to see how to proceed with an optimal way.

Good luck!

My best regards
Riadh
The administrator has disabled public write access.

Fail to run after allocating memory 11 years 11 months ago #6521

  • Nardini26
  • Nardini26's Avatar
Hello Riadh,

i finally discover the real problem which is the coordinate system Lambert 93 i'm using. The solution is well covered and explained thank to Serrer in the topic #5626.

To paraphrase him, Fudaa and Blue Kenue imply the use of different floating point numbers. Fudaa and Telemac (selafin files) use a 4 byte float which has approximately 7 significant digits (decimal). On an other hand, BK uses double precision. So, working on BK with a Lambert93 coordinate system that contains already 7 values for the Y (6000000 for example) doesn't allow any "sub meters" once the mesh is exported within Fudaa.

Therewith, i wish u a good day!
Max.
The administrator has disabled public write access.
Flat Threaded
  • Page:
  • 1
  • 2
Moderators: pham
Forum
System Modules
TELEMAC-2D
Fail to run after allocating memory

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