[Go-essp-tech] CMIP5 parameter versions
mark collier
Mark.Collier at csiro.au
Mon Sep 5 19:30:13 MDT 2011
Hi,
just a general question about versions of parameters.
As we identify problems our list of new versions is growing, however,
still manageable.
What concerns us more is the possibility of outdated versions which
may still be accessed. In terms of reconciling file (differences) it
can be good to have all versions available, however, nightmarish if
the wrong files get into analysts repositories and accidently (or
unknowingly used if they aren't aware of them being outdated) used.
I would like to know:
1) if the ESG system is designed to always supply the latest version
(and hide away old versions)?
2) as the filesystem that is scanned by the ESG system is shared by
our analysts, as it stands old versions can still be seen and copied
and potentially end up in local archives, especially when distributed
by 3rd parties. We would like to try and avoid this from happening
_without_ messing up the ESG metadata.
One solution for 2) is to ("in-situ") change the variable name from
say pr to pr_error in the wrong/outdated file versions - the DRS
structure (including filename) will stay the same but anyone trying to
read the file will instantly be alerted to the problem.
This is probably our biggest concern at the moment in terms of making
data available to the CMIP5 community.
Regards,
Mark Collier.
More information about the GO-ESSP-TECH
mailing list