Replaces the dictionary access functionality of foamInfoExec and
provides additional options to edit individual entries.
Contributed by Mattijs Janssens
reactionSensitivityAnalysis FO
This function object creates four data files named:
"consumption" : consumption rate
"production" : destruction rate
"productionInt" : integral between dumps of the production rate
"consumptionInt" : integral between dumps of the consumption rate
The function object indicates reaction rates of creation or destruction of species in each reaction.
code:
src/postProcessing/functionObjects/utilities/reactionSensitivityAnalysis/
tutorial:
/tutorials/combustion/chemFoam/gri
The output format file is (consumption.dat):
time : 1e-2
dellat T: 1e-5
Reaction specie1 specie2 ....
1 RR11 RR12
2 RR21 RR22
.
.
See merge request !44
Feature lagrangian
Minor adjustments to static information attached to lagrangian parcels/particles.
Fixes#108 (duplicate of http://www.openfoam.org/mantisbt/view.php?id=1990), #109, #110, #111.
Future reworking would require a better mechanism to also deal with dynamic information such as particle collisions etc.
See merge request !34
ENH: Update tutorial for features directionalPressureGradient, Global file handling
- Activate directionalPressureGradient source
- Check for Global/Share file handling
See merge request !45
- The only reasonable means of mirroring the data layout.
The '{}' delimiters mark the extent of the binary writes.
The primitives 'label' and 'scalar' are directly supported and correspond
to known byte widths.
Using "List<scalar>" was a bad choice, since this triggers unpleasant
tokenizing behaviour. Instead use 'scalars' as a provisional placeholder
to indicates a list of scalar values. However, there is currently no
support for actually handling lists of scalars, for several reasons:
* The information is not available at compile-time.
The cloud or parcel must be queried. And it must be guaranteed
that this value is consistent for the entire cloud.
* Binary output of lists is currently not great for determining the
the encoded width:
- A zero-size list is a single '0'.
- The leading size is a non-constant number of digits.
- There are prefix/suffix newlines need to be tagged and
skipped.
The special '*' (glob) token indicates that the remaining content
has a dynamic variable length and nothing reasonable can be known
about their sizes. This is exemplified by the collision records.
- only affects transfer of C-style string with a single character
remaining after whitespace stripping. Test added into Test-parallel.
- Note some idiosyncrasies in the behaviour:
send | receives
-------------------------+-------------------------
string("a b c") | string "a b c"
string("a") | string "a"
"a b c" | word "abc"
'd' | char 'd'
"d" | char 'd'
"d " | char 'd'
e.g.
functions
{
#includeFunc mag(U)
}
executes 'mag' on the field 'U' writing the field 'mag(U)'.
The equivalent post-processing command is
postProcess -func 'mag(U)'
