Problem with ck2cti - Githubissues

jcaiuwyo / cantera

Automatically exported from code.google.com/p/cantera

0 stars 0 forks source link

Problem with ck2cti #99

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1.ck2cti -i mech.dat -t therm.dat -id prf.cti
2.
3.

What is the expected output? What do you see instead?
Expected cti file.
Instead I get an error saying ck2cti.exe has stopped working.  

What version of the product are you using? On what operating system?
Cantera-2.0.0-x64.msi
numpy-MKL-1.6.2.win-amd64-py3.2.‌exe
Python 2.7.3 Windows X86-64 Installer

Please provide any additional information below.
Would really appreciate any help.

Original issue reported on code.google.com by kish...@gmail.com on 23 Jul 2012 at 9:05

Attachments:

ck2cti.exe

GoogleCodeExporter commented 9 years ago

Please attach the mech.dat and therm.dat files you are using as inputs.

Original comment by yarmond on 23 Jul 2012 at 10:21

GoogleCodeExporter commented 9 years ago

Original comment by yarmond on 12 Aug 2012 at 10:06

Changed state: Feedback

GoogleCodeExporter commented 9 years ago

Original comment by yarmond on 23 Aug 2012 at 3:06

Changed state: Invalid

GoogleCodeExporter commented 9 years ago

I was able to get it to work.  It turned out that the mechanism had some 
reversible reactions and cantera was identifying those as duplicate reactions.  
If I got rid of the information for reverse equation then ct2cxi worked fine.  
Is there a format I could use which would allow cantera to use the information 
for the reversible reaction as well?
Thanks!

Original comment by kish...@gmail.com on 23 Aug 2012 at 3:12

GoogleCodeExporter commented 9 years ago

Please attach the mech.dat and therm.dat files you are using as inputs that 
don't work with ck2cti.

Original comment by yarmond on 24 Aug 2012 at 2:42

GoogleCodeExporter commented 9 years ago

Original comment by kish...@gmail.com on 24 Aug 2012 at 2:51

Attachments:

GoogleCodeExporter commented 9 years ago

The reason those reactions are being flagged as duplicate is because they *are* 
duplicate reactions. The Chemkin preprocessor also identifies those reactions 
as duplicate. Either remove the duplicate reaction or mark both reactions as 
duplicate using the 'DUP' keyword.

Original comment by yarmond on 27 Aug 2012 at 6:10