<p>The <code>miptable</code> <code>Emon</code> is the extended variable list, which is basically there to stop the large number of more niche, rarely-used variables from cluttering the core monthly tables like <code>Amon</code>, <code>Omon</code>, <code>Lmon</code>, etc.  See the comment in the <a href="https://clipc-services.ceda.ac.uk/dreq/u/MIPtable::Emon.html" rel="nofollow noreferrer">Data Request Record</a>:</p>
<blockquote>
<p>Data in the 'E...' tables is requested by specific endorsed MIPs, and is generally more specialised than other tables.</p>
</blockquote>
<p>The variables in <code>Emon</code> tend to have priorities 2 and 3, whereas those in the core monthly lists tend to have priority 1.</p>
<p>I can't see any difference in the definitions of <code>Amon.ta</code> and <code>Emon.ta</code> other than the pressure levels, e.g., they are both monthly time means.  As always, check the metadata for the files you're using in case a modelling center has done something different from the Data Request.</p>

CC BY-SA 4.0
2023-10-13T09:57:56.697Z
2023-10-13T09:57:56.697Z
Deditos
<p>While looking for atmospheric data in CMIP6, I came across two Table entries: <code>Amon</code> and <code>Emon</code>, both seem to contain monthly-mean atmospheric data. For Example, the following two datasets are the same except for the Table ID:</p>
<ol>
<li><code>CMIP6.HighResMIP.EC-Earth-Consortium.EC-Earth3P-HR.hist-1950.r1i1p2f1.Amon.ta.gr</code></li>
<li><code>CMIP6.HighResMIP.EC-Earth-Consortium.EC-Earth3P-HR.hist-1950.r1i1p2f1.Emon.ta.gr</code></li>
</ol>
<p>The documentation doesn't mention much about the differences between those two Table IDs except that <code>Amon</code> is <em>Monthly atmospheric data</em> and that <code>Emon</code> is <em>Monthly (time mean, extension)</em>. After some searching, it seems that <code>Emon</code> has more vertical levels (27 as opposed to 19 in <code>Amon</code>).
I would like to if there are any other differences between these to Table IDs other than the difference the number of vertical levels?</p>

<climate-models><climate-data>
What are the differences between 'Amon' and 'Emon' Table IDs in CMIP6?
RogUE
# What are the differences between 'Amon' and 'Emon' Table IDs in CMIP6?

(Asked by: username_0 on 2023-10-04)

While looking for atmospheric data in CMIP6, I came across two Table entries: `Amon` and `Emon`, both seem to contain monthly-mean atmospheric data. For Example, the following two datasets are the same except for the Table ID:

1. `CMIP6.HighResMIP.EC-Earth-Consortium.EC-Earth3P-HR.hist-1950.r1i1p2f1.Amon.ta.gr`
2. `CMIP6.HighResMIP.EC-Earth-Consortium.EC-Earth3P-HR.hist-1950.r1i1p2f1.Emon.ta.gr`

The documentation doesn't mention much about the differences between those two Table IDs except that `Amon` is *Monthly atmospheric data* and that `Emon` is *Monthly (time mean, extension)*. After some searching, it seems that `Emon` has more vertical levels (27 as opposed to 19 in `Amon`).
I would like to if there are any other differences between these to Table IDs other than the difference the number of vertical levels?

**Tags:** climate-models, climate-data


---

## 1 answers

### Answer by username_1 on 2023-10-13. Score: 2

The `miptable` `Emon` is the extended variable list, which is basically there to stop the large number of more niche, rarely-used variables from cluttering the core monthly tables like `Amon`, `Omon`, `Lmon`, etc. See the comment in the [Data Request Record](https://clipc-services.ceda.ac.uk/dreq/u/MIPtable::Emon.html):

> Data in the 'E...' tables is requested by specific endorsed MIPs, and is generally more specialised than other tables.

The variables in `Emon` tend to have priorities 2 and 3, whereas those in the core monthly lists tend to have priority 1.

I can't see any difference in the definitions of `Amon.ta` and `Emon.ta` other than the pressure levels, e.g., they are both monthly time means. As always, check the metadata for the files you're using in case a modelling center has done something different from the Data Request.


---

