Cantera/Debugging Cantera from Python - Revision history

Admin: /* (Cantera 2.0) Step 4: Run Python Driver */

2017-04-17T07:46:00Z

(Cantera 2.0) Step 4: Run Python Driver

← Older revision		Revision as of 07:46, 17 April 2017
Line 266:		Line 266:


			=Flags=

			{{CanteraFlag}}

	~~[[Category:Cantera]]~~

Admin at 04:09, 19 September 2014

2014-09-19T04:09:09Z

← Older revision		Revision as of 04:09, 19 September 2014
Line 1:		Line 1:
	This page explains how to run [[Cantera]] in debug mode via [[Python]]. Note ~~that,~~ thanks to Apple's continually-changing compiler toolchain, these instructions no longer work on OS X~~. To do this, you'll need to be running on Linux~~. I have not figured out how to debug C++ code called from Python using lldb, which has replaced gdb in the latest version of Mac OS X.		This page explains how to run [[Cantera]] in debug mode via [[Python]].

			'''Note:''' thanks to Apple's continually-changing compiler toolchain, and their irritating obsession with abandoning standard tools, these instructions no longer work on OS X. I have not figured out how to debug C++ code called from Python using lldb, which has replaced gdb in the latest version of Mac OS X. To do this, you'll need to be running on Linux.

	=Creating a Cantera Debug Build=		=Creating a Cantera Debug Build=

Admin at 04:07, 19 September 2014

2014-09-19T04:07:36Z

← Older revision		Revision as of 04:07, 19 September 2014
Line 1:		Line 1:
	This page explains how to run [[Cantera]] in debug mode via [[Python]].		This page explains how to run [[Cantera]] in debug mode via [[Python]]. Note that, thanks to Apple's continually-changing compiler toolchain, these instructions no longer work on OS X. To do this, you'll need to be running on Linux. I have not figured out how to debug C++ code called from Python using lldb, which has replaced gdb in the latest version of Mac OS X.

	=Creating a Cantera Debug Build=		=Creating a Cantera Debug Build=

Admin: moved Debugging Cantera from Python to Cantera/Debugging Cantera from Python

2014-01-28T20:34:37Z

moved Debugging Cantera from Python to Cantera/Debugging Cantera from Python

← Older revision	Revision as of 20:34, 28 January 2014
(No difference)

Admin at 01:01, 11 January 2014

2014-01-11T01:01:41Z

← Older revision		Revision as of 01:01, 11 January 2014
Line 21:		Line 21:
	For this example, I'll use the following simple sequence of Python commands:		For this example, I'll use the following simple sequence of Python commands:

	<~~pre~~>		<source lang="python">
	>>> from Cantera import *		>>> from Cantera import *
	>>> from Cantera.Reactor import *		>>> from Cantera.Reactor import *
Line 27:		Line 27:
	>>> r = Reactor(gas)		>>> r = Reactor(gas)
	>>> n = ReactorNet([r])		>>> n = ReactorNet([r])
	</~~pre~~>		</source>

	We will jump into the C++ core of Cantera, at the equilibrate() function, using gdb.		We will jump into the C++ core of Cantera, at the equilibrate() function, using gdb.
Line 39:		Line 39:
	The first step is to run		The first step is to run

	<~~pre~~>		<source lang="python">
	>>> from Cantera import *		>>> from Cantera import *
	>>> from Cantera.Reactor import *		>>> from Cantera.Reactor import *
	</~~pre~~>		</source>

	This will load all of the Cantera libraries and hook them into Python.		This will load all of the Cantera libraries and hook them into Python.
Line 131:		Line 131:
	Next step is to run the Python driver (the short set of commands listed above, which create a reactor network).		Next step is to run the Python driver (the short set of commands listed above, which create a reactor network).

	<~~pre~~>		<source lang="python">
	>>> gas = GRI30()		>>> gas = GRI30()
	>>> r = Reactor(gas)		>>> r = Reactor(gas)
	>>> n = ReactorNet([r])		>>> n = ReactorNet([r])
	</~~pre~~>		</source>

	The Python process should hang, and when you switch over to gdb, you should see a message about the breakpoint you have reached:		The Python process should hang, and when you switch over to gdb, you should see a message about the breakpoint you have reached:
Line 185:		Line 185:
	The following is an example that works for Cantera 1.8 (but not for Cantera 2.0...):		The following is an example that works for Cantera 1.8 (but not for Cantera 2.0...):

	<~~pre~~>		<source lang="python">
	>>> from Cantera import *		>>> from Cantera import *
	>>> gas = GRI30()		>>> gas = GRI30()
	>>> gas.set(T=320.0, P=OneAtm, X='CH4:1,O2:2,N2:7.52')		>>> gas.set(T=320.0, P=OneAtm, X='CH4:1,O2:2,N2:7.52')
	>>> gas.equilibrate('HP')		>>> gas.equilibrate('HP')
	</~~pre~~>		</source>

	===(Cantera 1.8) Step 1: Import Python Module===		===(Cantera 1.8) Step 1: Import Python Module===
Line 196:		Line 196:
	From Python, import the Cantera module:		From Python, import the Cantera module:

	<~~pre~~>		<source lang="python">
	>>> from Cantera import *		>>> from Cantera import *
	>>> from Cantera.Reactor import *		>>> from Cantera.Reactor import *
	</~~pre~~>		</source>

	===(Cantera 1.8) Step 2: Determine Python PID, Attach GDB===		===(Cantera 1.8) Step 2: Determine Python PID, Attach GDB===
Line 243:		Line 243:
	Now run the remainder of the Python driver:		Now run the remainder of the Python driver:

	<~~pre~~>		<source lang="python">
	>>> gas = GRI30()		>>> gas = GRI30()
	>>> gas.set(T=320.0, P=OneAtm, X='CH4:1,O2:2,N2:7.52')		>>> gas.set(T=320.0, P=OneAtm, X='CH4:1,O2:2,N2:7.52')
	>>> gas.equilibrate('HP')		>>> gas.equilibrate('HP')
	</~~pre~~>		</source>

	Python should hang on the last command, and when you switch to the gdb window, you should see this:		Python should hang on the last command, and when you switch to the gdb window, you should see this:

Admin at 16:25, 13 June 2013

2013-06-13T16:25:41Z

← Older revision		Revision as of 16:25, 13 June 2013
Line 1:		Line 1:
	This page explains how to run Cantera in debug mode via Python.		This page explains how to run [[Cantera]] in debug mode via [[Python]].

	=Creating a Cantera Debug Build=		=Creating a Cantera Debug Build=

Admin: /* Cantera 1.8 Example */

2013-06-13T16:23:37Z

Cantera 1.8 Example

← Older revision		Revision as of 16:23, 13 June 2013
Line 181:		Line 181:
	You can see how Cantera's Python wrapper works: Python calls a binding function py_reactornet_new in ctreactor_methods.cpp, which in turn calls a C binding for creating a new reactor, which calls the actual C++ core of Cantera.		You can see how Cantera's Python wrapper works: Python calls a binding function py_reactornet_new in ctreactor_methods.cpp, which in turn calls a C binding for creating a new reactor, which calls the actual C++ core of Cantera.

	==Cantera 1.8 ~~Example~~==		==Debugging Cantera 1.8==

	The following is an example that works for Cantera 1.8 (but not for Cantera 2.0...):		The following is an example that works for Cantera 1.8 (but not for Cantera 2.0...):

Admin: /* Using Cantera 2.0 */

2013-06-13T16:23:21Z

Using Cantera 2.0

← Older revision		Revision as of 16:23, 13 June 2013
Line 33:		Line 33:
	I'll need to attach GDB to the Python process in the midst of these commands. Order is very important here.		I'll need to attach GDB to the Python process in the midst of these commands. Order is very important here.

	==~~Using~~ Cantera 2.0==		==Debugging Cantera 2.0==

	===Step 1: Import Python Module===		===Step 1: Import Python Module===

Admin: /* Cantera 1.8 Example */

2013-06-07T05:44:43Z

Cantera 1.8 Example

← Older revision		Revision as of 05:44, 7 June 2013
Line 183:		Line 183:
	==Cantera 1.8 Example==		==Cantera 1.8 Example==

	~~Another driver~~ that works for Cantera 1.8 is:		The following is an example that works for Cantera 1.8 (but not for Cantera 2.0...):

	<pre>		<pre>

Admin: /* Step 4: Run Python Driver */

2013-06-07T05:44:15Z

Step 4: Run Python Driver

← Older revision		Revision as of 05:44, 7 June 2013
Line 129:		Line 129:
	===Step 4: Run Python Driver===		===Step 4: Run Python Driver===

	Next step is to run the Python driver (the short set of commands listed above, which create a ~~gas and equilibrate it~~).		Next step is to run the Python driver (the short set of commands listed above, which create a reactor network).

	<pre>		<pre>