From 24280e3b4ba4ed5f38f58d46662e5a7daead9bb6 Mon Sep 17 00:00:00 2001
From: mattijs <mattijs>
Date: Fri, 18 Mar 2011 14:43:26 +0000
Subject: [PATCH] ENH: ReleaseNotes-dev: updated for codedFixedValue
---
ReleaseNotes-dev | 2 +-
doc/changes/dynamicCode.org | 26 ++++++++++++++------------
2 files changed, 15 insertions(+), 13 deletions(-)
diff --git a/ReleaseNotes-dev b/ReleaseNotes-dev
index 2e9a025ec81..687dda9a452 100644
--- a/ReleaseNotes-dev
+++ b/ReleaseNotes-dev
@@ -196,7 +196,7 @@
#+BEGIN_SRC c++
outlet
{
- type codedFixedValue<scalar>;
+ type codedFixedValue;
value uniform 0;
redirectType fixedValue10;
diff --git a/doc/changes/dynamicCode.org b/doc/changes/dynamicCode.org
index beae07b217d..cb3a83df091 100644
--- a/doc/changes/dynamicCode.org
+++ b/doc/changes/dynamicCode.org
@@ -36,9 +36,8 @@
scalar start = readScalar(dict["startTime"]);
scalar end = readScalar(dict["endTime"]);
label nDumps = 5;
- label interval = end-start
- os << ((start-end)/nDumps)
- #}
+ os << ((end-start)/nDumps);
+ #};
};
#+END_SRC
@@ -65,7 +64,7 @@
#+BEGIN_SRC c++
outlet
{
- type codedFixedValue<scalar>;
+ type codedFixedValue;
value uniform 0;
redirectType fixedValue10;
@@ -132,6 +131,10 @@
};
#+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
The syntax of =#codeStream= can be quite hard to get right. These are some
common pitfalls:
@@ -146,19 +149,18 @@
+ the =#codeStream= entry (itself a dictionary) has to end in a ';'
* 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=:
- =foamFormatConvert=
- =changeDictionaryDict=
- =foamUpgradeCyclics=
- These applications will usually switch off all '#' processing.
-
-
- 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.
+ These applications will usually switch off all '#' processing which
+ just preserves the entries as strings (including all formatting).
* Other
- - the implementation is still changing though the syntax is fixed
- parallel running not tested a lot. What about distributed data
(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.
--
GitLab