orch:Usage - Revision history

Barnaudc: /* Common Errors */

2020-07-02T19:17:54Z

‎Common Errors

2020-07-02T19:17:20Z

‎Common Errors

2020-07-02T19:16:26Z

‎Common Errors

2018-12-19T14:57:26Z

‎Common Errors

2018-12-19T14:51:32Z

2018-12-19T14:35:21Z

adding common errors and ways to avoid them

2018-02-15T09:28:56Z

‎Reduce chemistry

2017-12-11T18:00:51Z

‎Reduce chemistry

2017-12-11T17:59:36Z

‎Reduce chemistry

2017-12-11T17:58:55Z

‎Reduce chemistry

@@ Line 209: / Line 209: @@
   <code> Cantera Error </code>
 or
-  <code>...terminate called after throwing an instance of 'Cantera::CanteraError'
+  <code>...terminate called after throwing an instance of 'Cantera::CanteraError'  what():  </code>
-  what():  </code>
   <code>***********************************************************************</code>
-CanteraError thrown by ct2ctml_string:
+ <code>CanteraError thrown by ct2ctml_string:</code>
-Error converting input file "./" to CTML.
+ <code>Error converting input file "./" to CTML.</code>
-Python command was: 'python'
+ <code>Python command was: 'python'</code>
-The exit code was: 1</code>
+ <code>The exit code was: 1</code>
 Usually, it's due to the input_ini file : Cantera isn't able to find and read your scheme.

@@ Line 210: / Line 210: @@
 or
   <code>...terminate called after throwing an instance of 'Cantera::CanteraError'
-   what():
+   what():  </code>
-***********************************************************************
+ <code>***********************************************************************</code>
 CanteraError thrown by ct2ctml_string:
 Error converting input file "./" to CTML.

@@ Line 206: / Line 206: @@
 == Common Errors ==
-Usually, you will make mistakes and get on your screen a pretty beautiful :
+If you get on your screen this kind of error :
   <code> Cantera Error </code>
-There are many ways to get it BUT main of the time it's your fault, not your scheme or Cantera one's. Often, Cantera isn't able to find and read your scheme.
+or
-*To be sure of your error, check this points first :
+ <code>...terminate called after throwing an instance of 'Cantera::CanteraError'
-# Check every path in condition.cpp and in your Makefile, never let a wrong path somewhere even if you "just want to test something"
+  what():
 # Check and spell every name of folder/files you entered in the program (condition.cpp).

@@ Line 210: / Line 210: @@
 There are many ways to get it BUT main of the time it's your fault, not your scheme or Cantera one's. Often, Cantera isn't able to find and read your scheme.
 *To be sure of your error, check this points first :
-# Check every path in condition.cpp and in you Makefile, never let a wrong path even if you "just want to test something"
+# Check every path in condition.cpp and in your Makefile, never let a wrong path somewhere even if you "just want to test something"
 # Check and spell every name of folder/files you entered in the program (condition.cpp).

@@ Line 206: / Line 206: @@
 == Common Errors ==
-Usually, you will make mistake and get on your screen a beautiful :
+Usually, you will make mistakes and get on your screen a pretty beautiful :
   <code> Cantera Error </code>
 There are many ways to get it BUT main of the time it's your fault, not your scheme or Cantera one's. Often, Cantera isn't able to find and read your scheme.

← Older revision		Revision as of 14:35, 19 December 2018
Line 203:		Line 203:

	: in 'outputs/Premixed' or 'outputs/Stochastic' the name of the file is either Premixed_.dat or Trajectory_i, i : number of the inlet for the stochastic configuration.		: in 'outputs/Premixed' or 'outputs/Stochastic' the name of the file is either Premixed_.dat or Trajectory_i, i : number of the inlet for the stochastic configuration.
		+
		+	== Common Errors ==
		+
		+	Usually, you will make mistake and get on your screen a beautiful :
		+	<code> Cantera Error </code>
		+	There are many ways to get it BUT main of the time it's your fault, not your scheme or Cantera one's. Often, Cantera isn't able to find and read your scheme.
		+	*To be sure of your error, check this points first :
		+	# Check every path in condition.cpp and in you Makefile, never let a wrong path even if you "just want to test something"
		+	# Check and spell every name of folder/files you entered in the program (condition.cpp).

← Older revision		Revision as of 09:28, 15 February 2018
Line 202:		Line 202:
	and provides the computation of the mechanism defined in 'mech =' in 'conditions.cpp' in the current configuration. This is not a part of the reduction process.		and provides the computation of the mechanism defined in 'mech =' in 'conditions.cpp' in the current configuration. This is not a part of the reduction process.

−	: in 'outputs' the name of the file is :	+	: in 'outputs/Premixed' or 'outputs/Stochastic' the name of the file is either Premixed_.dat or Trajectory_i, i : number of the inlet for the stochastic configuration.

@@ Line 35: / Line 35: @@
 These target species will have the highest DRGEP coefficient (=1) and the hight weight during optimisation
-(note that for the DRGEP steps the species into reactant are automatically preserved i.e. their DRGEP coefficient also set to 1 and can't be suppressed)
+(note that for the DRGEP steps the species into reactant are automatically preserved, i.e. their DRGEP coefficient is also set to 1 so they can't be suppressed)
 * Inlet of composition space trajectories

@@ Line 28: / Line 28: @@
   <code> listTargets.push_back("H2");
    listTargets.push_back("O2");
    listTargets.push_back("H2O");
    listTargets.push_back("CH4");
    listTargets.push_back("CO");
    listTargets.push_back("CO2"); </code>
 * Inlet of composition space trajectories