jshaw35
jshaw35
Hi @brian-eaton, I don't have much familiarity with CAM outside of the COSP code so I can't comment on everything. The changes in COSP look good to me though!
@cacraigucar - The changes to COSP that add RTTOV are still pulled in via the COSP external library (I am also working with the COSP team to official pull that...
@cacraigucar - This is a really good question. To clarify re: the COSP-RTTOV integration, COSP users will still need to register as RTTOV users if they wish to access the...
@cacraigucar - Yes, I don't think there is another way to access the RTTOV source code. I asked the NWP-SAF developers about distributing RTTOV with COSP a few years ago...
@cacraigucar - I just submitted a ticket to NWP-SAF with that request! 🤞 Thank you for raising this with the CESM SEs and let me know if I can be...
@cacraigucar another update from the RTTOV developers at EUMETSAT: "We have heard back that this exception would require approval (not guaranteed!) by EUMETSAT council. The next council meeting is in...
Hi Cameron, thanks for the heads up on the GenTS implementation! Being able to specify history files and variables is definitely helpful for time and storage use in my applications....
@mnlevy1981 thanks for the update! I have added handling of multiple streams and some simplistic output chunking for my own use. My changes are on this fork: https://github.com/jshaw35/CUPiD feel free...
@cacraigucar I have now ported the COSP-RTTOV interface code to the cam_development branch. These changes make CAM compatible with the COSP-RTTOV branch that @dustinswales and I are currently reviewing before...
As a note, I have made some additional changes to allow for the output of the clear-sky spectral flux fields from RRTMG as well as all-sky. This requires modifications to...