hkmoffat / cantera

Automatically exported from code.google.com/p/cantera
0 stars 0 forks source link

Cython/Python Cantera solution files incompatible with C++ Cantera #164

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Calculate a counterflow flame with the cython or python interface
2. Save the solution as .xml file 
3. Try to load the solution with a C++ counterflow flame Cantera program 

What is the expected output? What do you see instead?
The solution should be loaded correctly but Cantera writes: No data for domain 
0 no data for stagnation flow no data for domain 2

What version of the product are you using? On what operating system?
Cantera development version (from Center) Revision r2205
on Linux openSuSe 12.1

Please provide any additional information below.
I have allready worked out the problem: A solution file which the cython/python 
interface creates has outher ids for the domains, than a C++ solution file.
In C++ the three domains of a counterflow flame are called: "domain 0", 
"stagnation flow", and "domain 2". In cython/python the three domains are 
called: "fuel_inlet", "flame", and "oxidizer_inlet". When I put the C++ names 
in the cython/python solution everything works.

Original issue reported on code.google.com by andi.rue...@gmx.at on 22 May 2013 at 4:34

GoogleCodeExporter commented 9 years ago
I also found an inconsistency between the Python/Cython module: The old 
interface labeled the inlets 'fuel inlet' and 'oxidizer inlet', whereas the new 
interface uses underscores instead of blanks.

Original comment by thetruet...@googlemail.com on 23 May 2013 at 7:06

GoogleCodeExporter commented 9 years ago
I think the solution to this is for the Sim1D.restore method to not require 
matching the "id" attribute of the domain, but rather to require that the 
domains appear in the XML file in order from left to right, and to simply check 
that they have the correct "type" attribute. The "id" should be irrelevant.

Original comment by yarmond on 23 May 2013 at 5:17

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r2425.

Original comment by yarmond on 26 Jun 2013 at 12:23