Changes between Initial Version and Version 1 of Ticket #476
- Timestamp:
- 01/04/11 21:58:23 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #476
- Property Resolution → Fixed
- Property Status new → closed
- Property Summary point source values replaced by fillvalue → point source values replaced by FillValue
- Property Type bug → defect
-
Ticket #476 – Description
initial v1 1 Another reason why the fillvalues give me a headache: Most users place point sources at locations where the u- or v- mask is zero (ie land). During the simulation the model will acuatlly compute a source value at that 'land' location and those transports are used in the simulation. However, when writing his or other output files, the u- or v- values at the psource locations will be repalced with fillvalues. This does not allow the user to check if the correct transport is being introduced into the model. Please negate the fillvalue at locations of the point sources. suggested fix: make up a temporary u/vmask that does not mask the point sources in wrt_his send that temporary mask to nf_fwite3d instead of Grid(ng)%umask. 1 Another reason why the !FillValues give me a headache: Most users place point sources at locations where the u- or v-mask is zero (i.e. land). During the simulation the model will actually compute a source value at that 'land' location and those transports are used in the simulation. However, when writing history or other output files, the u- or v-values at the ppoint source locations will be replaced with !FillValues. 2 3 This does not allow the user to check if the correct transport is being introduced into the model. Please negate the !FillValue at locations of the point sources. Suggested fix: make up a temporary u/vmask that does not mask the point sources in '''wrt_his.F''' send that temporary mask to '''nf_fwite3d''' instead of '''GRID(ng)%umask'''.