Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

CESM with active carbon cycle and ecosystems.

pdn@hawaii_edu

New Member
Dear CESM users,Here I have a question regarding running CESM with active BGC and ecosystems on a modified KMT.

I would like to use a slightly modified bathymetry around the Maritime Continent. I have extensive experience changing the coupler files, the domain files, and landsea masks. I am also very familiar with the changes to the initial conditions to run POP (without BGC).Here is what I did: I modified the KMT so that new ocean ocean grid points are created (I essentially need to open the Karimata passage, which is closed in the standard KMT). I have the correct ocean initial conditions, which I got from a previous simulation with the same modified KMT.CESM crashes during the initialization of POP. I get the following error:

(co2calc.F90:drtsafe_row)    x2,f =   2.630275536330801E-007 734496747443.228
(shr_sys_abort) ERROR: bounding bracket for pH solution not found

This error makes total sense, because it happens on the grid points that I converted from land to ocean. These grid points do not have BGC initial conditions.

What should I do to avoid this error? Should I modify the ecosystem initial condition files?

 

klindsay

CSEG and Liaisons
Staff member
Hi,I think you're on the right track with your last question, creating a modified ecosystem initial condition file and setting init_ecosys_init_file in user_nl_pop2 to the filename of the newly created file. I expect that something as simple as a iterative nearest neighbor fill should suffice to create values at the new ocean grid points.Please note that you will want to include init_ecosys_init_file in user_nl_pop2 only in your first run. After that, on continuation runs, you should comment that line out. Putting a '!' in the first column suffices. This is necessary because otherwise POP will blindly use the init_ecosys_init_file setting from user_nl_pop2, even on continuation runs.Hope this helps, Keith
 
Top