Error reporting for NETcdf files needs improvement
Bug #920944 reported by
Jon Hill
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fluidity |
Fix Released
|
Undecided
|
Adam Candy | ||
Bug Description
See Yi HanSoo email on 23/01/12.
A scenario with two or more netcdf files (e.g. bathymetry, forcing, initial conditions, or NEMO data) are produce similar error messages: "Point not found in netcdf file". However, it's doesn't say which netcdf file. Error messages need updating to at least print out the filename, but the variable being searched would also be useful.
Related branches
lp:~fluidity-core/fluidity/netcdferrorreporting
- Jon Hill: Approve
- Fluidity Core Team: Pending requested
-
Diff: 19 lines (+2/-2)1 file modifiedbathymetry/read_netcdf_interface.cpp (+2/-2)
| Changed in fluidity: | |
| status: | New → Triaged |
| Changed in fluidity: | |
| assignee: | nobody → Jon Hill (jon-hill) |
Revision history for this message
| Adam Candy (asc) wrote | #1 |
Download full text (4.9 KiB)
| Changed in fluidity: | |
| milestone: | none → 4.1.4 |
| Changed in fluidity: | |
| assignee: | Jon Hill (jon-hill) → Adam Candy (asc) |
| status: | Triaged → Fix Committed |
| Changed in fluidity: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
As well as pointing to the relevant CF conventions, the error could suggest interrogating the netCDF header using 'ncdump -h'. This was demonstrated in my recent email to Lee, to extract the range of the field values. In this case the coordinate fields are defined in a Cartesian coordinate system, not geographic. It also lists the CF convention used. This is one way we could suggest the user can check the file is formatted correctly.
# ncdump -h initSWL.grd
netcdf initSWL {
dimensions:
x = 2161 ;
y = 1321 ;
variables:
double x(x) ;
double y(y) ;
float z(y, x) ;