inert passive tracer boundary not being read
inert passive tracer boundary not being read
Hi all,
I'm having some trouble getting the boundaries for an inert passive tracer to work. I defined T_PASSIVE and ANA_BPFLUX, and changed NPT = 1 in the .in file. I provided initial conditions, dye_01_sflux and boundary conditions for the tracer. The initial condition and boundary are included in in the ic and bry netcdfs with all the other variables, and the surface flux is in a file of its own.
However, on a test I did with ANA_SPFLUX undefined, the dye is all gone within a few months. I can't get the model to even begin reading my boundary conditions for dye. Has anyone encountered this problem before? Am I missing something?
Thanks!
I'm having some trouble getting the boundaries for an inert passive tracer to work. I defined T_PASSIVE and ANA_BPFLUX, and changed NPT = 1 in the .in file. I provided initial conditions, dye_01_sflux and boundary conditions for the tracer. The initial condition and boundary are included in in the ic and bry netcdfs with all the other variables, and the surface flux is in a file of its own.
However, on a test I did with ANA_SPFLUX undefined, the dye is all gone within a few months. I can't get the model to even begin reading my boundary conditions for dye. Has anyone encountered this problem before? Am I missing something?
Thanks!
Re: inert passive tracer boundary not being read
What are the LBC values for your tracers? Four dye tracers with no boundary conditions would look like:
It seems you want RadNud instead of Clo.
As for the surface forcing, is that being read?
Code: Select all
LBC(isTvar) == RadNud RadNud RadNud RadNud \ ! temperature
RadNud RadNud RadNud RadNud \ ! salinity
Clo Clo Clo Clo \ ! inert(1)
Clo Clo Clo Clo \ ! inert(2)
Clo Clo Clo Clo \ ! inert(3)
Clo Clo Clo Clo ! inert(4)
As for the surface forcing, is that being read?
Re: inert passive tracer boundary not being read
Hi Kate,
I fixed my .in and the dye data is read, both at the boundary and at the surface. However, in both experiments (I ran boundary input and surface input separately), the concentrations get really unreasonable really fast. I am posting the average dye concentration at 5 and 300m for the 7th month of my simulation, with dye initialized with 0 concentration on the domain, and a boundary input of 0.1 at the bottom layer. I am running this simulation with ice, and the only passive tracer option activated is T_PASSIVE. How can I stop the values from going negative? The 2 open boundaries were both defined with RadNud for dye.
Thank you!
I fixed my .in and the dye data is read, both at the boundary and at the surface. However, in both experiments (I ran boundary input and surface input separately), the concentrations get really unreasonable really fast. I am posting the average dye concentration at 5 and 300m for the 7th month of my simulation, with dye initialized with 0 concentration on the domain, and a boundary input of 0.1 at the bottom layer. I am running this simulation with ice, and the only passive tracer option activated is T_PASSIVE. How can I stop the values from going negative? The 2 open boundaries were both defined with RadNud for dye.
Thank you!
Re: inert passive tracer boundary not being read
Have you tried clamped dye boundary conditions? It looks like something is really wrong. If the dye BC is 0.1 at the bottom, is it 0.0 for the rest? I'd look much closer to the beginning time to try to figure it out.
- arango
- Site Admin
- Posts: 1367
- Joined: Wed Feb 26, 2003 4:41 pm
- Location: DMCS, Rutgers University
- Contact:
Re: inert passive tracer boundary not being read
Yes, I know. I has an update for it. Mark Hadfield put a post about this and the solution.
Re: inert passive tracer boundary not being read
Thanks for the reply. I can't find the post with the solution, though, can anyone send me the link? Thanks again!
- arango
- Site Admin
- Posts: 1367
- Joined: Wed Feb 26, 2003 4:41 pm
- Location: DMCS, Rutgers University
- Contact:
Re: inert passive tracer boundary not being read
Please update your codes. I corrected this bug in the repository. See following trac ticket for details.
Re: inert passive tracer boundary not being read
Thank you for the help, really appreciate it!