Opened 8 years ago
Last modified 4 years ago
#1579 assigned Request
Assumption initial conditions are on z-levels when ln_sco = .true.
Reported by: | jamesharle | Owned by: | jamesharle |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | OCE | Version: | trunk |
Severity: | minor | Keywords: | |
Cc: |
Description
The initial conditions for runs ln_sco = .true. are assumed to be on z-levels based on gdept_1d. This is not immediately apparent from reading the manual.
A few options would be to either:
- modify code such that depth information is required in the initial condition file. This would allow an initial condition file, comprising a different number of levels and/or gird type, to be read in and interpolated onto gdept_0.
- remove the interpolation loop completely (bearing in mind the on-going simplification process) and impose that the initial conditions read in have to be on gdept_0, requiring a pre-processing step.
Commit History (0)
(No commits)
Change History (9)
comment:1 Changed 8 years ago by jamesharle
comment:2 Changed 6 years ago by nicolasmartin
- Owner nemo deleted
- Status changed from new to assigned
comment:3 Changed 6 years ago by nicolasmartin
- Severity set to minor
- Type changed from Task to Enhancement
comment:4 Changed 6 years ago by jamesharle
I'm currently writing this code into my copy of the trunk. I was also thinking of removing this loop and putting it into domain_cfg TOOLS so the initial conditions are mapped onto the native vertical grid and written out when domain_cfg is used. That way they can be read in a runtime without the need for on-the-fly interpolation.
comment:5 Changed 6 years ago by nicolasmartin
- Owner set to jamesharle
comment:6 Changed 4 years ago by smasson
- Owner changed from jamesharle to mathiot
comment:7 Changed 4 years ago by mathiot
- Owner changed from mathiot to jamesharle
James, one other solution could be to clarify the documentation and if you really want to to implement the capability and an action in the proposal for 2020 WP.
comment:8 Changed 4 years ago by jamesharle
- Version changed from v3.6 to trunk
OK - I have an updated changeset for v4.0 that I've been using for ORCHESTRA, so won't be too much effort to add. I'll look over the documentation and discuss with Andrew.
comment:9 Changed 4 years ago by clevy
- Type changed from Enhancement to Feature request
A fix I used a while back to get me going - could be tidied:
dtatsd.F90