[Go-essp-tech] who owns the version difference information, and where do we collect it?

[Sébastien Denvil]

Hi all,

my feeling is that the ESG publisher will be the best "how" in this
case. The person in charge of the concerned simulation will unpublished
the dataset and thus will be the most appropriate person to justify it.
The same apply when the corrected dataset will be republish.

May be a short to long comment associated with the unpublished/republish
process will be enough, may be not.

I see three cases that could make me unpublished and republish when
possible my dataset. From soft to critical importance. I do not pretend
it's exhaustive :

A- a bug in the diagnostics codes of the model (Can affect a category of
variables)
  * can be in the diagnostic part (sign error, CfMIP package ...)
B- a bug/problem in the post-processing workflow (Can affect a broader
category of variables)
  * calendar and time axis issue, corruption of data compared to the
original, offline diagnostics errors, ...
  * a bug in the CMOR2 handling due to the the user

C- a bug in the experimental settings of the simulation (affect the
whole simulation)
  * wrong forcing files (due to many potential reasons)
  * wrong starting files (due to many potential reasons)
  * major bug in the I/O module of the model ... very bad
  * an unacceptable and lately discover biases/bug/issues in the model
(the very very bad case)

Regards.
Sébastien

Bryan Lawrence a écrit :
> Hi Folks
> 
> Stephen's email prompted me to think about something else.
> 
> When a new version of a (CMIP5) dataset is produced, there will be a reason for making that new version.
> Who is collecting that reason, and how, and where do we put that information?
> 
> Bryan


-- 
Sébastien Denvil
IPSL, Pôle de modélisation du climat
UPMC, Case 101, 4 place Jussieu,
75252 Paris Cedex 5

Tour 45-55 3ème étage Bureau 303A
Tel: 33 1 44 27 21 10
Fax: 33 1 44 27 61 71

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4091 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mailman.ucar.edu/pipermail/go-essp-tech/attachments/20100114/63a33785/attachment.bin