Hi,
I'm very new to Saturne and trying to get it work on one basic case but it's still a challenge to me. Here's my problem:
I'm using Saturne 4 (the version you gave me in your last conference) coupling with Salome platform
For the calculation, I modified 4 cs_user files: boundary_conditions_base, initialization_base, parameters, physical_properties.
I need to run the calculation based on enthalpy equations
For some last results, I always get signal SIGSEGV error:
Signal SIGSEGV (accès à une zone mémoire interdite) intercepté !
Pile d'appels :
1: 0x7fa381c49aea <strlen+0x2a> (libc.so.6)
2: 0x7fa382a172b4 <cs_field_set_key_str+0x94> (libsaturne.so.0)
3: 0x7fa382e335ee <uithsc_+0x24e> (libsaturne.so.0)
4: 0x7fa382a98726 <fldvar_+0x94f> (libsaturne.so.0)
5: 0x7fa382aa4976 <iniusi_+0x2d6> (libsaturne.so.0)
6: 0x7fa382aa4102 <initi1_+0x62> (libsaturne.so.0)
7: 0x7fa3829a33cf <cs_run+0x39f> (libsaturne.so.0)
8: 0x7fa3829a3565 <main+0x115> (libsaturne.so.0)
9: 0x7fa381be2ec5 <__libc_start_main+0xf5> (libc.so.6)
10: 0x402fb9 <> (cs_solver)
Fin de la pile
Can someone please help me to surpass this please?
Enthalpy model
Forum rules
Please read the forum usage recommendations before posting.
Please read the forum usage recommendations before posting.
-
- Posts: 4208
- Joined: Mon Feb 20, 2012 3:25 pm
Re: Enthalpy model
Hello,
Could you post the setup files recommended in the forum usage guidelines ?
(the backtrace alone is not enough to guess what is causing the issue).
Regards,
Yvan
Could you post the setup files recommended in the forum usage guidelines ?
(the backtrace alone is not enough to guess what is causing the issue).
Regards,
Yvan
Re: Enthalpy model
Here is the check files and the .xml (which I changed to .log because your messenger didn't accept)
- Attachments
-
- castest.log
- (9.56 KiB) Downloaded 385 times
-
- preprocessor.log
- (5.07 KiB) Downloaded 251 times
-
- compile.log
- (12.97 KiB) Downloaded 254 times
Re: Enthalpy model
Personally, I guess the error is in the way I declared variables in cs_user_initialization.f90. There is the only place I used the command "cs_field_set_key_str" which appeared in the error list.
- Attachments
-
- cs_user_boundary_conditions.f90
- (8.14 KiB) Downloaded 264 times
-
- cs_user_parameters.f90
- (70.27 KiB) Downloaded 251 times
-
- cs_user_initialization.f90
- (5.6 KiB) Downloaded 249 times
-
- Posts: 4208
- Joined: Mon Feb 20, 2012 3:25 pm
Re: Enthalpy model
Hello,
field_set_key_str is not used in your user files, as it is in a "if .false." block.
But it may be used indirectly by the code. uithsc appears in your backtrace, and is related to the GUI, so please follow the full forum usage recommendations, and also post your XML file.
I won't need a mesh to reproduce your issue, as the crash occurs before the mesh is read, but I do need both the user subroutines (at least those called upon initialization) and the XML file.
Regards,
Yvan
field_set_key_str is not used in your user files, as it is in a "if .false." block.
But it may be used indirectly by the code. uithsc appears in your backtrace, and is related to the GUI, so please follow the full forum usage recommendations, and also post your XML file.
I won't need a mesh to reproduce your issue, as the crash occurs before the mesh is read, but I do need both the user subroutines (at least those called upon initialization) and the XML file.
Regards,
Yvan
Re: Enthalpy model
I attached the xml in the previous post, under the name castest.log, because I couldn't attach directly the xml.
About the subroutines, I'm very sorry but which another files you needed?
About the subroutines, I'm very sorry but which another files you needed?
-
- Posts: 4208
- Joined: Mon Feb 20, 2012 3:25 pm
Re: Enthalpy model
Hello,
Sorry, I did not see the file before.
I just tested tour case, and the issue is due to the XML file:
line 20, the file contains:
<scalar label="Enthalpy" name="enthalpy" type="thermal"/>
where it should contain:
<variable label="Enthalpy" name="enthalpy" type="thermal"/>
Fixing it by hand seems to solve the issue, though it should not occur in the first place.
I suspect this is a bug in the XML automatic update feature (I assume your XML file was initially generated with an older version, as when creating a new case, the matching line is OK).
I'll try to see with Cyril later this week if a fix can be done in time for rc3 (or 4), but in the meantime, I would recommend simply rebuilding a new XML case, using the first as a model.
Best regards,
Yvan
Sorry, I did not see the file before.
I just tested tour case, and the issue is due to the XML file:
line 20, the file contains:
<scalar label="Enthalpy" name="enthalpy" type="thermal"/>
where it should contain:
<variable label="Enthalpy" name="enthalpy" type="thermal"/>
Fixing it by hand seems to solve the issue, though it should not occur in the first place.
I suspect this is a bug in the XML automatic update feature (I assume your XML file was initially generated with an older version, as when creating a new case, the matching line is OK).
I'll try to see with Cyril later this week if a fix can be done in time for rc3 (or 4), but in the meantime, I would recommend simply rebuilding a new XML case, using the first as a model.
Best regards,
Yvan