Dear Douglas,

Thank you for the answer.

Best regards,
Oliviu


On Wednesday, February 7, 2018, 9:09:26 PM GMT, Douglas Serson <d.serson@gmail.com> wrote:


Hi Oliviu,

In the xml format, an element is generally defined as
    <NAME Attribute1="Value1" Attribute2="Value2" > Content </NAME>
(where we can have any number of attributes, including zero).
When Content is empty, we can use
    <NAME Attribute1="Value1" Attribute2="Value2" />
as a shorter version for
     <NAME Attribute1="Value1" Attribute2="Value2" ></NAME>

Therefore, </Foo> marks the end of an element which was previously opened by <Foo>,
while <Foo /> represents a complete element by itself (an empty one in this case).
This second notation is used for entries consisting only of attributes, but without any content (e.g. each entry in solver info).

Cheers,
Douglas

2018-02-07 15:10 GMT-02:00 Oliviu Sugar <oliviu_sugar@yahoo.com>:
Thank you, now it works.
Could you please explain what would be the difference between < Foo /> and </ Foo > termination?
Looking over the xml file, it would seem that the </ Foo > ending is used for sub-sections (like BC, Params, Solver Info, etc.) and functions (Initial values, etc.), while the < Foo /> ending is for scalar parameters.
The fact that the Body forcing uses the </ Foo > ending may not be surprising, since BodyForce is itself another function, however for the Noise forcing, it is only a simple scalar value that is being provided.

Thank you,
Oliviu


On Wednesday, February 7, 2018, 2:09:48 PM GMT, Douglas Serson <d.serson@gmail.com> wrote:


Hi Oliviu,

There is a typo in your noise forcing. Instead of <WHITENOISE/> it should be </WHITENOISE>.
Also, at the moment this setting for white noise does not evaluate the parameters (or any expression, unfortunately). Therefore, you will have to replace it by
    <WHITENOISE> 0.001 </WHITENOISE>


Cheers,
Douglas


2018-02-07 10:56 GMT-02:00 Oliviu Sugar <oliviu_sugar@yahoo.com>:
Dear all,

The problem I'm facing is probably trivial, but I just cannot figure it out.
The simulation is simply a test case for an under-resolved DNS of a flow at Re=3000 inside a circular pipe, with 1D homogeneity along the flow direction, a body force to drive the flow and some white noise to stimulate transition to turbulence.
The problem is that the IncNS solver throws the following error: Cannot find element 'GEOMETRY'.
The config file is attached here.
Any advice would be much appreciated.

Cheers,
Oliviu

______________________________ _________________
Nektar-users mailing list
Nektar-users@imperial.ac.uk
https://mailman.ic.ac.uk/ mailman/listinfo/nektar-users