@graybeal , @taylor13 : thank you for those comments. The idea of the
"immediately prior source" certainly makes sense, but it may be undesirable if
taken literally. For instance, global climate simulations which are distributed
for global data exchange will, before being distributed, we rewritten using the
CMOR package. CMOR provides a library of routines, which will are designed to
be integrated into the workflows of the various modeling centres, so that the
software producing the data files is generally some internal software package
with a name that means nothing to people outside the institution. We take the
"immediate prior source" suggested by Jim to refer to the generation of
information content in the data by the global climate model, but this approach
runs into ambiguity when the whole range of post-processing options is
considered. Hence, I can also see some benefits from the more flexible approach
suggested by Karl.
Could we encourage flexibility by allowing multiple source elements, e.g.
`MOHC-HadGEM2-ES WRF MyCropModel` ?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/341*issuecomment-940031779__;Iw!!G2kpM7uM-TzIFchu!m2xqI5SBee9B-vPxqEsBmkhn5Eq98x-_SPmiT172l3qqxuOTrtBa2BpS6CTtKTovbkhUSLglmUE$
This list forwards relevant notifications from Github. It is distinct from
[email protected], although if you do nothing, a subscription to the
UCAR list will result in a subscription to this list.
To unsubscribe from this list only, send a message to
[email protected].