On 8/19/2011 8:02 AM, Jonathan Gregory wrote:
> Dear John
>
>> Im not sure I can actually implement prefixes for calendar fields,
>> since in general that would violate the need for integers.
>> millisecond makes sense, but millihour doesnt.
> Yes, I see. Could we include ms then, and also a, ka and Ma for a year,
> 1000 years and a million years, used in paleoclimate?
i will add ms.
im not familiar with a, ka, and Ma. what are those?
>
> Regarding paleoclimate, a point I forgot is that some modellers may wish to
> have years which are very large negative numbers (many more than four digits)
> if they set up the model with the "true" date for the run. Although for
> geological timescales you might say that this isn't necessary and you might
> as well choose an arbitrary year, there is a good reason for it in Pleistocene
> when you might be using the dates to relate to orbital forcing or atmospheric
> composition.
so the idea is that you are simulating some year, so you really need
time down to the hour or second. but the climate is from 5 million years
ago, so you need the year field to be able to handle that?
>
> Thanks for your other replies as well.
>
> Best wishes
>
> Jonathan
> _______________________________________________
> CF-metadata mailing list
> CF-metadata at cgd.ucar.edu
> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
Received on Fri Aug 19 2011 - 10:32:22 BST
