Initialization from a 3D post-processing output using MEDCoupling: issue in iteration index

Questions and remarks about code_saturne usage
Forum rules
Please read the forum usage recommendations before posting.
Post Reply
fracenvi
Posts: 38
Joined: Wed Jun 19, 2024 9:58 am

Initialization from a 3D post-processing output using MEDCoupling: issue in iteration index

Post by fracenvi »

Hello everyone,

I'm trying to start a simulation using custom thermochemical fields, making use of the MEDCoupling tool but i have one major issue. I did manage to compile the cs_user_initialization.c file successfully as well as to convert all of my fields to med format but during run phase it keeps giving me that message:

terminate called after throwing an instance of 'INTERP_KERNEL::Exception'
what(): No such iteration (0,0) in existing field 'Temperature' in file '/home/cenvinzf@coria.fr/workdir/cavity_ann_init/nn_couple/3D_import/restart_ann_prova.med' ! Available iterations are : (1,1),
terminate called after throwing an instance of 'INTERP_KERNEL::Exception'


I already checked that changing the iteration index no field get passed to the initialization. Also, i only have one time step iteration to retrieve data from, and i don't get why it keeps saying that the only available iteration is (1,1) despite having clearly stated in the guide that it needs to be (0,0) if only one iteration exists.

I attached the files useful to reproduce the error.

Thanks to everyone that can help,
Francesco
Attachments
setup.xml
(9.42 KiB) Downloaded 754 times
cs_user_initialization-base.c
(7.69 KiB) Downloaded 764 times
restart_ann_prova.med
(7.55 MiB) Downloaded 750 times
Yvan Fournier
Posts: 4231
Joined: Mon Feb 20, 2012 3:25 pm

Re: Initialization from a 3D post-processing output using MEDCoupling: issue in iteration index

Post by Yvan Fournier »

Hello,

The iteration number and order (i.e. sub-iteration) in the MED file may depend on how that file was written, so using 1,1 might be the solution. If no field gets updated after that, there may be another issue, such as a mismatch in field names, shifter coordinates, ...

Best regards,

Yvan
Post Reply