Problems with mech.dat in Converge 2.3.16
 

Hi everyone,
I had some cases running succesfully on Converge 2.3.10, involving combustion reactions. Then I updated Converge to the 2.3.16 version and tried to run the same cases, but I've had some problems:
1) if I include the mech.dat, but not the species.in file (which worked with Converge 2.3.10), I get the following error

*** Process received signal ***
Signal: Segmentation fault (11)
Signal code: Address not mapped (1)
Failing at address: (nil)
[ 0] /lib64/libpthread.so.0() [0x3da6a0f710]
[ 1] converge-2.3.16-openmpi(write_check_mech+0x108a) [0x7c68fa]
[ 2] converge-2.3.16-openmpi(setup+0x7545) [0x71e835]
[ 3] converge-2.3.16-openmpi(main+0x1e2) [0x638d12]
[ 4] /lib64/libc.so.6(__libc_start_main+0xfd) [0x3da621ed5d]
[ 5] converge-2.3.16-openmpi(realloc+0x229) [0x4a2a19]
*** End of error message ***

2) if I include the species.in file, but not the mech.dat, the simulation starts without problems but, of course, no reactions take place

3) if I include both mech.dat and species.in, I get the following error

JOB ABORT invoked by rank 0:
ERROR: there is no thermodynamic data for species O2

Have you got any idea of what the problem could be? I'm rather sure that it is a bug, because as I said before I had no problems with the 2.3.10 version.

Hi,

If all species are included in mech.dat, then species.in is not needed. Otherwise, you have to explicitly declare those not listed in mech.dat in species.in and give their thermaldynamics in therm.dat. Also, if you were using some physical models that requires some specific species, such as some emission or soot models, then you have to define them in species.in. Have you checked that all species required are properly defined?

It appears to me that your third problem is because you defined O2 in species.in but not in therm.dat (are you using the default therm.dat from STUDIO?). You can open therm.dat to see if O2 is there.

After the check and if the problem is still there, then we have to take a look at your setup files. Please forward them to support@convergecfd.com in that case.

Thank you.