Inputs - Revision history

Seltz: /* Multiple Inlet */

2021-05-26T07:13:18Z

‎Multiple Inlet

Seltz: /* QSS and optimisation key words */

2019-02-01T13:31:41Z

‎QSS and optimisation key words

Seltz: /* Multiple Inlet */

2019-02-01T13:28:32Z

‎Multiple Inlet

Seltz: /* Premixed flame */

2019-02-01T13:25:17Z

‎Premixed flame

Seltz: /* General keywords */

2019-02-01T13:21:26Z

‎General keywords

Seltz at 13:14, 2 January 2018

2018-01-02T13:14:33Z

Seltz at 17:55, 11 December 2017

2017-12-11T17:55:29Z

Seltz at 16:36, 19 September 2017

2017-09-19T16:36:38Z

Seltz: /* Multiple Inlet */

2017-09-19T16:21:06Z

‎Multiple Inlet

Seltz at 16:10, 19 September 2017

2017-09-19T16:10:20Z

@@ Line 80: / Line 80: @@
-Some last parameters are necessary :
+Other parameters are necessary :
@@ Line 86: / Line 86: @@
 which determine if the mixing of the fluid particles is new or set from a previous mixing. 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.
    MixingTime =
    TimeStep =
    IterationNumber =
 === QSS and optimisation key words ===

@@ Line 94: / Line 94: @@
-Concerning the QSS part, the user have to fill a vector with the species put in QSS assumption. The user can test several scenarios (definition of multiple vectors)
+Concerning the QSS part, the user have to indicate the species put in QSS assumption.
     //------QSS Scenarios------//
-    string array1[17] {"species1", "species2"};
+   QSS =
-    vector<string> vec(array1, array1 + sizeof(array1) /sizeof(array1[0]));
+   QSS =
-    listQSSscenarios.push_back(new QSSscenario(vec));
-−
      ...
@@ Line 109: / Line 107: @@
      //------Optimisation------//
-    //MAKE SURE THE "listQSSscenarios" THAT IS PUSHED FIRST, IS THE SCENARIO YOU WANT TO OPTIMISE
-     int PopSize = 22;
+  CrossoverRate = 0.75
-     int MaxAllowableGenerations = 10;
+  MutationRate = 0.02
-     int NbElitism = 1;
-     double CrossoverRate = 0.75;
+We recommend to keep the mutation and crossover rates by default.
-     double MutationRate = 0.02;
-     double AllowedVariation_A = 0.005;
+  AllowedVariation_A =
-     double AllowedVariation_b = 0;
+  AllowedVariation_b =
-     double AllowedVariation_E = 0;
+  AllowedVariation_E =
-−
-     listOptimScenarios = new OptimScenario(PopSize, MaxAllowableGenerations, NbElitism, CrossoverRate, MutationRate, AllowedVariation_A, AllowedVariation_b, AllowedVariation_E);

@@ Line 65: / Line 65: @@
-   //Inlet i
+  //Inlet i
-   listInlets.push_back(new MultipleInlet(
+  new Inlet i
-                "Temperature",
+  T =
-                "Pressure",
+  Pressure =
-                "Mass flow rate",
+  MassFlowRate =
-                "Xk",
+  Xk =
-                "Yk",
+  EvaporationModel = false or true (0 or 1)
-                /*evaporationModel*/ true or false,
+  DropletDiameter =
-                /*DropletDiameter*/,
+  EvaporationTime =
-                /*Tau_vj (characteristic time of evaporation)*/,
+  liquidDensity =
-                /*liquidDensity*/,
+  EvaporationLatentHeat =
-                /*EvaporationlatentHeat*/));
+ //EndInlet
- new_mixing = "true or false"
+which determine if the mixing of the fluid particles is new or set from a previous mixing. 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.
+  MixingTime =
-which determine if the mixing of the fluid particles is new or set from a previous mixing. 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.
+  TimeStep =
 === QSS and optimisation key words ===

@@ Line 30: / Line 30: @@
-  configuration = "PremixedFlames";
+  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));
+  //Flame 0
+ Tf =    //fuel temperature
@@ Line 43: / Line 50: @@
-  listFlames.push_back(...)
+  //Flame 0
- listFlames.push_back(...)
   ...
-  trajectory_ref.push_back("");
+  //Flame 1
- trajectory_ref.push_back("");
   ...
 === Multiple Inlet ===

@@ Line 1: / Line 1: @@
 === General keywords ===
-All the necessary key words are contained in the file "conditions.cpp", this is where you specify the characteristics of your flame and the ORCh step you want to run.
+All the necessary key words are contained in the file "input_file.ini", 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)
+First, you choose the studied combustion regime (premixed flame, auto-ignition ou multiple Inlet regime) with the key word "configuration".
-<code>
+Then, the ORCh step you want to perform ([[DRGEP|DRGEP_species]], DRGEP_reactions, ComputeTrajectories, computeQSSCriteria, getQSSfile, getQSSfileFORTRAN, Optimisation, or Lumping) with the key word "step".
-configuration = "studied regime";
-</code>
-<code>
+The reference chemical scheme (key word mech_ref) (by default it is the scheme "mech" from which the user begins the step) and his associated trajectory file  (key word : trajectory_ref) are optional.
-step = "chosen step";
-</code>
-The reference chemical scheme (by default it is the scheme "mech" from which the user begins the step)
+Note that mech_ref and trajectory_ref are optional and useful only if the user wants to plot and calculate the fitness with other reference schemes than the default one. To use the default one, put "mech_ref = None"
-<code>
+The reference scheme (mech) of the current step, and the mechanism description (mech_desc) (the mech_desc doesn't change through the ORCh steps and corresponds to the id of the mechanism) :
-mech_ref = "mechanims/reference scheme in xml";
-</code>
-−
-and his associated trajectory file
-−
-<code>
-trajectory_ref.push_back("");
-</code>
-−
-Note that mech_ref and trajectory_ref are optional and useful only if the user wants to plot and calculate the fitness with other reference schemes than the default one.
-−
-The reference scheme of the current step, and the mechanism description (the mech_desc doesn't change through the ORCh steps and corresponds to the id of the mechanism) :
-−
-<code>
-mech = "mechanims/current chemical scheme in xml";
-mech_desc = "mechanism description";
-</code>
 The level of debug wanted (generally 1)
- speciesToPlot.push_back("O2") ;
+The species trajectories and/or the temperature and the flame speed (in Premixed configuration) the user wants to vizualise during the step (key word speciesToPlot).
- speciesToPlot.push_back("CO2") ;
- etc ..
-−
- plot_T = true or false; //temperature plot
- plot_U = true or false; //flame speed plot
-Then you define your target species  :
+Also if you want to plot the temperature and the flame velocity :
- listTargets.push_back("species 1");
+Then you define your target species  with the key word "Target".
-  listTargets.push_back("species 2");
- listTargets.push_back("species 3");
- ...
 === Premixed flame ===

@@ Line 1: / Line 1: @@
 === General keywords ===
-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.
+All the necessary key words are contained in the file "conditions.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)
@@ Line 24: / Line 24: @@
 <code>
-trajectory_ref = "";
+trajectory_ref.push_back("");
 </code>
 Note that mech_ref and trajectory_ref are optional and useful only if the user wants to plot and calculate the fitness with other reference schemes than the default one.
-The reference scheme of the current step, and the mechanism description (the mech_desc doesn't change through the ORCh steps) :
+The reference scheme of the current step, and the mechanism description (the mech_desc doesn't change through the ORCh steps and corresponds to the id of the mechanism) :
 <code>
@@ Line 60: / Line 60: @@
 === Premixed flame ===
-If you want to reduce schemes for premix flames, firstly you will run a flame with the following inputs :
+If you want to reduce schemes for premixed flames, firstly you will run a flame with the following inputs :
@@ Line 71: / Line 71: @@
-In order to converge faster, you have to indicate a reference flame with characteristics close to the ones you want to run
+In order to converge faster, you have to indicate a reference flame with characteristics close to the ones you want to run.

@@ Line 13: / Line 13: @@
 </code>
-The detailed chemical scheme contained in mechanisms/
+The reference chemical scheme
 <code>
-mech_ref = "mechanims/detailed scheme in xml";
+mech_ref = "mechanims/reference scheme in xml";
 </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>
@@ Line 25: / Line 25: @@
 mech_desc = "mechanism description";
 </code>
 === Premixed flame ===