CAM icon indicating copy to clipboard operation
CAM copied to clipboard

Add TUV-x to CAM

Open mattldawson opened this issue 1 year ago • 3 comments

This PR contributes to #757 by including TUV-x in the CAM build and introducing a TUV-x wrapper to allow CAM-Chem photolysis rates to be calculated in-line by TUV-x. @stacywalters @tilmes @lkemmons @dkinnison

Using TUV-x for photolysis rate calculations in CAM runs is disabled pending science evaluation/implementation of:

  • cross section and quantum yield data sets
  • aerosol optical inputs to TUV-x
  • cloud optical inputs to TUV-x
  • heating rate calculations

This is my first CAM PR and I have some remaining questions about the correct way to do some things (which I will add as comments on this PR), so I'm leaving it in draft mode for now.

mattldawson avatar Apr 04 '23 22:04 mattldawson

Are there plans to bring biological effects in to this PR? @coupewx has coupled a version of WACCM4 with TUV (from @cbardeen) to POP in CESM2 to compute UV inhibition in ocean plankton groups; we would like to bring this work into CESM3 (with MOM6 instead of POP), and are trying to scope out what would be involved. If this update to CAM provides fields like UV index and phytoplankton damage per Cullen et al (see this block of code from the version of CAM he is currently using), that would reduce the workload on our end. We skimmed through the changes in this PR and didn't see anything - if we missed something, could you please point us to it?

mnlevy1981 avatar Jul 03 '24 20:07 mnlevy1981

Are there plans to bring biological effects in to this PR? @coupewx has coupled a version of WACCM4 with TUV (from @cbardeen) to POP in CESM2 to compute UV inhibition in ocean plankton groups; we would like to bring this work into CESM3 (with MOM6 instead of POP), and are trying to scope out what would be involved. If this update to CAM provides fields like UV index and phytoplankton damage per Cullen et al (see this block of code from the version of CAM he is currently using), that would reduce the workload on our end. We skimmed through the changes in this PR and didn't see anything - if we missed something, could you please point us to it?

@dkinnison should weigh in on this

fvitt avatar Jul 03 '24 21:07 fvitt

@mattldawson Is the version of TUVx used in your branch near the head of NCAR/tuv-x? Do you have a test case for WACCM including the json file needed for Js and chemical heating?

fvitt avatar Sep 09 '24 21:09 fvitt