Open loeiten opened 9 years ago
This is because ixseps1 and ixseps2 are read from a GridDataSource, which can be either a grid file or the options tree. SymmetricGlobal* and similar Mesh switches are always read from the options file.
Agree this should be documented somewhere (sorry)
Is a solution to always allow options in [mesh] to override variables in a grid file, or would that get too confusing?
On 16 March 2015 at 10:00, loeiten notifications@github.com wrote:
ixseps1 and ixseps2 are not read from [mesh] in BOUT.inp when using a grid file.
However, variables like symmetricglobal@ are read from [mesh] even when a grid file is specified. If this is intentional, it could maybe be mentioned explicitly in the manual?
— Reply to this email directly or view it on GitHub https://github.com/boutproject/BOUT-dev/issues/40.
In my opinion it would be a good idea to allow for override or precedence. In worst case, a warning could be printed that a specific option is found in both the grid file and the BOUT.inp file, and that the option from BOUT.inp will be used
ixseps1 and ixseps2 are not read from [mesh] in BOUT.inp when using a grid file.
However, variables like symmetricglobal@ are read from [mesh] even when a grid file is specified. If this is intentional, it could maybe be mentioned explicitly in the manual?