Number of probes

[vshinde]

Dear Yvan,

I am not able to define the 'porbes' in my calculations. I have ALE activated for fluid structure interactions. Here is the error message.

-----------------------------------------------------------
System error: File exists

/home/projets/saturne/Code_Saturne/2.2/src/code_saturne-2.2.4/src/base/cs_time_plot.c:637: Fatal error.

Plot number 10 is already defined.


Call stack:
1: 0x2b5636ab6f44 <bft_error+0x94> (libbft.so.0)
2: 0x2b56352a3fc6 <tpsini_+0x286> (libsaturne.so.0)
3: 0x2b563535f07f <strhis_+0x61f> (libsaturne.so.0)
4: 0x2b5635239773 <caltri_+0x5843> (libsaturne.so.0)
5: 0x2b563520da0a <cs_run+0x7da> (libsaturne.so.0)
6: 0x2b563520d213 <main+0x193> (libsaturne.so.0)
7: 0x2b563caa9c4d <__libc_start_main+0xfd> (libc.so.6)
8: 0x401309 <> (cs_solver)
End of stack
---------------------------------------------------------------------------------

Please find the listing file attached.

I am using Code Saturne V 2.2.4. But problem persists for V 3.0 too.

Thanks in advance for your time.

Vilas SHINDE
EDF Clamart

[Yvan Fournier]

Hello,

Could you post your setup so we can reproduce this (if the mesh is too big, we can do without, but we need at least the xml and user subroutines, preferably for version 3.0) ?

Regards,

Yvan

[vshinde]

Hello Yvan,

First, sorry for late reply.

Please find the param.xml, error, and listing files attached.
FYI, There is no error when I run the calculation without ALE (fluid structure interaction module) selected.
Please let me know if you need further information.

Thanks a ton.

Vilas

[Yvan Fournier]

Hello,

I do not reproduce the error with Code_Saturne 3.0.1.

Do you have any user subroutines you did not post here ? I don't remember any specific fix betwen 3.0.0 and 3.0-rc1 that would xplain the difference (though I may have forgotten some details).

Regards,

Yvan

[vshinde]

Hello Yvan,

I am sorry. I did not share user subroutines.
I observe the error without these subroutines with 'param.xml' file attached with this message.
I suspect if it has to do with the activation of structural history output.

Thanks for the concern.

--
Vilas

[Yvan Fournier]

Hello,

I just fixed this bug. The fix will be in versions 3.2 (october), 3.1.1, and 3.0.2 (soon).

In the meantime, you can add the attached file to your user subroutines (for version 3.0).

Regards,

Yvan

[vshinde]

Many thanks.

-
Vilas