Documentation regarding free surface pressure initialisation is unclear
Bug #922025 reported by
Jon Hill
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fluidity |
Fix Released
|
Low
|
Adam Candy |
Bug Description
As reported on the Fluidity mailing list:
"When reading in a netcdf file for initial condition of free surface,
I found that the values after reading in become one order larger than the original values.
For example,
-2 < Free Surface (in my netcdf file) < 4
in xxx_0_0.vtu file, it is
-20 < FreeSurface < 40
Anyway, I am testing with a manipulation of the netcdf file.
Is it a bug or just my simple mistake somewhere."
The documentation in the schema and the manual needs to tell the user that the initial pressure is formed by:
free surface * gravity magnitude * density
and that they should scale their input appropriately.
Related branches
lp:~fluidity-core/fluidity/freesurfacefromnetcdffix
- Jon Hill: Pending requested
- Fluidity Core Team: Pending requested
-
Diff: 1259 lines (+1052/-37)15 files modifiedmanual/configuring_fluidity.tex (+15/-3)
ocean_forcing/load_netcdf.F90 (+20/-12)
preprocessor/Initialise_Fields.F90 (+2/-0)
schemas/input_output.rnc (+13/-7)
schemas/input_output.rng (+15/-15)
tests/netcdf_read_errors/Makefile (+18/-0)
tests/netcdf_read_errors/createnetcdf.py (+86/-0)
tests/netcdf_read_errors/missingdata.err.sample (+44/-0)
tests/netcdf_read_errors/netcdf_read_errors.xml (+130/-0)
tests/netcdf_read_errors/valid.flml (+292/-0)
tests/netcdf_read_free_surface/Makefile (+13/-0)
tests/netcdf_read_free_surface/createnetcdf.py (+33/-0)
tests/netcdf_read_free_surface/height.py (+13/-0)
tests/netcdf_read_free_surface/netcdf_read_free_surface.flml (+309/-0)
tests/netcdf_read_free_surface/netcdf_read_free_surface.xml (+49/-0)
Changed in fluidity: | |
assignee: | nobody → Jon Hill (jon-hill) |
status: | New → Confirmed |
status: | Confirmed → Triaged |
importance: | Undecided → Low |
Changed in fluidity: | |
assignee: | Jon Hill (jon-hill) → Adam Candy (asc) |
Changed in fluidity: | |
milestone: | none → 4.1.4 |
Changed in fluidity: | |
status: | In Progress → Fix Committed |
Changed in fluidity: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The files relating to this bug are up on scratch at:
/scratch/asc/seto/
Lee recently sent initSWL.grd and seto_0_0.vtu, and there's also the seto.flml from a previous mail. The other files have been generated by me. We don't have everything to run the case - we need the mesh file, so I've asked Lee to send this also. I'll look at the code in more detail to try and identify the issue - this will be easier once we have the mesh information.