Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standard names: Add two variables of MODIS output from COSP simulator #209

Closed
LisaBock opened this issue Aug 12, 2024 · 3 comments
Closed
Labels
add to cfeditor (added by template) Moderators are requested to add this proposal to the CF editor standard name (added by template) Requests and discussions for standard names and other controlled vocabulary

Comments

@LisaBock
Copy link

We (@axel-lauer and me) would like to propose two more new standard names for MODIS output from the COSP satellite simulator package (see Table 1 in the description of COSP), including the ice and liquid water path.

To evaluate clouds in climate model by comparing with satellite observations the output of satellite simulators allows for a more quantitative comparison of model and satellite data. Until now only cloud coverage is part of the physical variables in the CMOR tables. Additional insight into the models’ performance in reproducing observed cloud properties is expected from using additional output from the COSP satellite simulator package, in particular ice and liquid water path resembling MODIS measurements.
For this, we suggest to also include the parameters ‘clivimodis’ and ‘clwvimodis’ alongside with ‘cltmodis’. We use already existing CF standard names.

Proposer's name: Lisa Bock and Axel Lauer
Date: 24-08-12

The two variable are:
(Term: Long Name, CF Standard Name [Units])

  • clivimodis: MODIS Ice Water Path, atmosphere_mass_content_of_cloud_ice [kg m-2]
    Ice water path, as seen by the MODIS simulator.
  • clwvimodis: MODIS Condensed Water Path, atmosphere_mass_content_of_cloud_condensed_water [kg m-2]
    Liquid water path, as seen by the MODIS simulator.

Thank you!

@LisaBock LisaBock added add to cfeditor (added by template) Moderators are requested to add this proposal to the CF editor standard name (added by template) Requests and discussions for standard names and other controlled vocabulary labels Aug 12, 2024
Copy link

Thank you for your proposal. These terms will be added to the cfeditor (http://cfeditor.ceda.ac.uk/proposals/1) shortly. Your proposal will then be reviewed and commented on by the community and Standard Names moderator.

@taylor13
Copy link

It appears that you are content with the existing standard names, but would like to propose two standardized variable names. CF does not specify what the names of variables should be, so you're free to use clivimodis and clwvimodis.

As you point out, these variables may be of interest to some MIPs which often require approval of your preferred variable names. It looks like you've chosen names that would be consistent with the naming of other CMIP variables (and with the CMOR tables), but they have not been included in past standard output tables or the CMIP6 "data request".

@LisaBock
Copy link
Author

It appears that you are content with the existing standard names, but would like to propose two standardized variable names. CF does not specify what the names of variables should be, so you're free to use clivimodis and clwvimodis.

As you point out, these variables may be of interest to some MIPs which often require approval of your preferred variable names. It looks like you've chosen names that would be consistent with the naming of other CMIP variables (and with the CMOR tables), but they have not been included in past standard output tables or the CMIP6 "data request".

Thanks, I think I understood now. I close this issue and propose directly new physical variables.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
add to cfeditor (added by template) Moderators are requested to add this proposal to the CF editor standard name (added by template) Requests and discussions for standard names and other controlled vocabulary
Projects
None yet
Development

No branches or pull requests

2 participants