search

ACCESS-Community-Hub / ACCESS-MOPPeR

A tool to post-process ACCESS Model output using CMOR, based on APP4, work in progress!
https://access-mopper.readthedocs.io/en/latest/
Apache License 2.0
0 stars 0 forks source link

be specific in pressure levels mapping #170

Open paolap opened 2 weeks ago

paolap commented 2 weeks ago

As the definition for a variable on pressure levels needs to be specific in terms of how may and what levels are used, it is possible that the incorrect mapping is selected if more than one exists. This is because there's no way to know how many pressure levels the variable is using and if these are comparable when matching variables. This is not an issue when we use a list of tables and variables we want, but it can be an issue when we use "all" tables, even if limiting the tables to the ones present in the mapping files.

There could be a few ways to tackle this, maybe the easiest is to extend labelling like ta19 (meaning ta on plev19) to all pressure variables (with the exception of CMIP6 as we can't change these). Then there's no (less?) risk of confusion.

On the plus side while the tool will try to build all available combinations the ones which are incorrect will fail.

paolap commented 2 weeks ago

Fixed this for AM3 but still need to go back and check how other versions are affected