Deep time unrealistic salinity trend, likely due to ocean to runoff mapping errors

[nick]

Hi, I've run a hundred or so years of my deep time CESM2 configuration and noticed an unrealistically large (increasing) global salinity trend. This is often due to mapping errors between e.g. the ocean and runoff models. In previous versions of the CESM setup tools there was an IDL script used to find and correct mapping errors, but I don't see it in the current paleotoolkit. Have any deep time users run into salinity trend issues and if so how have you fixed it? I'm running CESM version cesm2.1.3-rc.01-0-g0596a97 on a non-NCAR machine, but I suspect this question applies to any version since CCSM3 running on any machine.

 

[nick]

Solved. I have a 2x2 degree river transport model and I hadn't made all of the necessary adjustments in the code for the tool that creates the ROFF->OCN mapping to handle the lower resolution. After fixing that and restarting, 50 years of salinity data seems to look decent.

 

[jiangzhu]

Hi Nick,

Thanks for reporting. Yes, there are hardwired code in runoff_map, which is the reason map_mod_0.5deg.F90.save and map_mod_1deg.F90.save are provided. paleoToolkit/cesm1_2/rof/runoff_map_src/src at master · CESM-Development/paleoToolkit

 

[yongsheng zheng]

Hi Nick,

Thanks for reporting. Yes, there are hardwired code in runoff_map, which is the reason map_mod_0.5deg.F90.save and map_mod_1deg.F90.save are provided. paleoToolkit/cesm1_2/rof/runoff_map_src/src at master · CESM-Development/paleoToolkit

Hi jiangzhu,

An error occurred when I was using 0.5deg runoff file to create runoff to ocean mapping file, which was run by map_mod_0.5deg.F90.save you mentioned. The following error occurred, do you know what the problem is?

 

[jiangzhu]

Hi Yongsheng,

I am not sure. Perhaps, check your memory allocation? You may need to increase the memory.

Jiang

 

[yongsheng zheng]

Hi jiangzhu,

This is my map_mod.F90 execution file, can you help me to see what the problem is?

Yongsheng