Difference between revisions of "Inputs"

From orch
Jump to: navigation, search
Line 13: Line 13:
 
</code>
 
</code>
  
The detailed chemical scheme contained in mechanisms/
+
The reference chemical scheme  
  
 
<code>
 
<code>
mech_ref = "mechanims/detailed scheme in xml";
+
mech_ref = "mechanims/reference scheme in xml";
 
</code>
 
</code>
  
Finally the reference scheme of the current step, also found in the repertory mechanism, depends on the step, and the mechanism description (doesn't change through the ORCh steps) :
+
The reference scheme of the current step, and the mechanism description (doesn't change through the ORCh steps) :
  
 
<code>
 
<code>
Line 25: Line 25:
 
mech_desc = "mechanism description";
 
mech_desc = "mechanism description";
 
</code>   
 
</code>   
 +
 +
The level of debug wanted (generally 1)
 +
 +
<code>
 +
debug = 1;
 +
</code>
 +
 +
The species trajectories and/or the temperature and the flame speed (in Premixed configuration) the user wants to vizualise during the step :
 +
 +
speciesToPlot.push_back("O2") ;
 +
speciesToPlot.push_back("CO2") ;
 +
etc ..
 +
 +
plot_T = true or false; //temperature plot
 +
plot_U = true or false; //flame speed plot
 +
 +
  
 
=== Premixed flame ===
 
=== Premixed flame ===

Revision as of 17:10, 19 September 2017

Every key words are contained in the file "condition.cpp", this is where you specify the characteristics of your flame and the ORCh step you want to run.

First, you choose the studied combustion regime (premixed flame, auto-ignition ou multiple Inlet regime)

configuration = "studied regime";

Then, the ORCh step you want to perform (DRGEP_species, DRGEP_reactions, ComputeTrajectories, computeQSSCriteria, getQSSfile, getQSSfileFORTRAN, Optimisation, or Lumping)

step = "chosen step";

The reference chemical scheme

mech_ref = "mechanims/reference scheme in xml";

The reference scheme of the current step, and the mechanism description (doesn't change through the ORCh steps) :

mech = "mechanims/current chemical scheme in xml"; mech_desc = "mechanism description";

The level of debug wanted (generally 1)

debug = 1;

The species trajectories and/or the temperature and the flame speed (in Premixed configuration) the user wants to vizualise during the step :

speciesToPlot.push_back("O2") ;
speciesToPlot.push_back("CO2") ;
etc ..

plot_T = true or false; //temperature plot
plot_U = true or false; //flame speed plot 


Premixed flame

If you want to reduce schemes for premix flames, firstly you will run a flame with the following inputs :


configuration = "PremixedFlames";


listFlames.push_back(new PremixedFlames( fuel temperature, oxider temperature, pressure, ratio, Yf, Xf, Yo, Xo, path of the reference flame, path of the new flame));


In order to converge faster, you have to indicate a reference flame with characteristics close to the ones you want to run


Then you define your target species :


listTargets.push_back("species 1"); 
listTargets.push_back("species 2");
listTargets.push_back("species 3");
...


and so on.

Concerning the QSS part, you have to fill a vector with


string array1[] = {}

Multiple Inlet

Concerning this regime, as many inlets as needed can be added with the following characteristics :


  //Inlet i
  listInlets.push_back(new MultipleInlet(
               "Temperature",
               "Pressure",
               "Mass flow rate",
               "Xk",
               "Yk",
               /**/,
               /**/,
               /**/,
               /**/,
               /**/));

Also, target species must be specified :


  listTargets.push_back("species 1"); 
  listTargets.push_back("species 2");
  listTargets.push_back("species 3"); 


One last parameter is necessary :


new_mixing = "true or false"


which determine if all the fluid particles are mixed or not. For the first step of the analysis, this parameter is set to true, and false for all the other steps of the study, so the random mixing of the first step is re-used for the other ones.

Auto ignition