zhyang-dev/openfoam
1
0
Fork 0
mirror of https://develop.openfoam.com/Development/openfoam.git synced 2025-11-28 03:28:01 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

ENH: ReleaseNotes-dev: updated for codedFixedValue

Browse Source
This commit is contained in:
mattijs
2011-03-18 14:43:26 +00:00
parent d60378e4af
commit 24280e3b4b
2 changed files with 15 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
ReleaseNotes-dev
View File

@ -196,7 +196,7 @@
#+BEGIN_SRC c++ #+BEGIN_SRC c++
outlet outlet
{ {
type codedFixedValue<scalar>; type codedFixedValue;
value uniform 0; value uniform 0;
redirectType fixedValue10; redirectType fixedValue10;

26
doc/changes/dynamicCode.org
View File

@ -36,9 +36,8 @@
scalar start = readScalar(dict["startTime"]); scalar start = readScalar(dict["startTime"]);
scalar end = readScalar(dict["endTime"]); scalar end = readScalar(dict["endTime"]);
label nDumps = 5; label nDumps = 5;
label interval = end-start os << ((end-start)/nDumps);
os << ((start-end)/nDumps) #};
#}
}; };
#+END_SRC #+END_SRC
@ -65,7 +64,7 @@
#+BEGIN_SRC c++ #+BEGIN_SRC c++
outlet outlet
{ {
type codedFixedValue<scalar>; type codedFixedValue;
value uniform 0; value uniform 0;
redirectType fixedValue10; redirectType fixedValue10;
@ -132,6 +131,10 @@
}; };
#+END_SRC #+END_SRC
Note: above field initialisation has the problem that the boundary conditions
are not evaluated so e.g. processor boundaries will not hold the opposite cell
value.
* Pitfalls * Pitfalls
The syntax of =#codeStream= can be quite hard to get right. These are some The syntax of =#codeStream= can be quite hard to get right. These are some
common pitfalls: common pitfalls:
@ -146,19 +149,18 @@
+ the =#codeStream= entry (itself a dictionary) has to end in a ';' + the =#codeStream= entry (itself a dictionary) has to end in a ';'
* Exceptions * Exceptions
There are unfortunately some exceptions. Following applications read There are unfortunately some exceptions to above field massaging.
Following applications read
the field as a dictionary, not as an =IOdictionary=: the field as a dictionary, not as an =IOdictionary=:
- =foamFormatConvert= - =foamFormatConvert=
- =changeDictionaryDict= - =changeDictionaryDict=
- =foamUpgradeCyclics= - =foamUpgradeCyclics=
These applications will usually switch off all '#' processing. These applications will usually switch off all '#' processing which
just preserves the entries as strings (including all formatting).
Note: above field initialisation has the problem that the boundary conditions
are not evaluated so e.g. processor boundaries will not hold the opposite cell
value.
* Other * Other
- the implementation is still changing though the syntax is fixed
- parallel running not tested a lot. What about distributed data - parallel running not tested a lot. What about distributed data
(i.e. non-=NFS=) parallel? (i.e. non-=NFS=) parallel?
- paraview has been patched so it will pass in RTLD_GLOBAL when loading
the OpenFOAM reader module. This is necessary for above dictionary
processing to work.