You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Need config.nml control of minimum neutral input altitude #136
Currently the neutral perturbation data objects assume their grid starts at 0 km -- this should be a user-provided input in the appropriate namelist that then gets passed into the object so it can flexibly set the bottom boundary.
Currently, I manually set it here:
self%zn=[ (70000 + (real(izn, wp)-1)*cfg%dzn, izn=1,self%lzn) ]
minzn=minval(self%zn)
and then use minzn in:
self%extents(0,1:6)=[minzn,maxzn,xnrange(1),xnrange(2),ynrange(1),ynrange(2)]
self%extents(iid,1:6)=[minzn,maxzn,xnrange(1),xnrange(2),ynrange(1),ynrange(2)]
Activity
mattzett commentedon Nov 25, 2025
@paulinchin -- which is the source file you have to manually edit to adjust min altitude for input files?
paulinchin commentedon Nov 25, 2025
It is neutraldata3Dobj_mpi.f90.
Currently, I manually set it here:
self%zn=[ (70000 + (real(izn, wp)-1)*cfg%dzn, izn=1,self%lzn) ]
minzn=minval(self%zn)
and then use minzn in:
self%extents(0,1:6)=[minzn,maxzn,xnrange(1),xnrange(2),ynrange(1),ynrange(2)]
self%extents(iid,1:6)=[minzn,maxzn,xnrange(1),xnrange(2),ynrange(1),ynrange(2)]
mattzett commentedon Nov 25, 2025
Perfect I'll get some more general code in to have this be specified in the config.nml file.