<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi all,<br>
<br>
My understanding is that "classic" format since release of NetCDF
3.6 includes support of "large files" (>2.2 Gbytes) using "64-bit
offset". Although we recommend against files larger than 2.2 Gbytes
for CMIP5 we don't absolutely forbid it. We certainly don't forbid
specifying "64-bit offset". I think we should recommend use of
3.6.3 or higher to users, and encourage them to install even more
recent versions.<br>
<br>
I agree with Martin on this. Perhaps we can post (when time
permits) a FAQ indicating that 3.6.3 or higher should be used in
reading CMIP5 data.<br>
<br>
Best regards,<br>
Karl<br>
<br>
<br>
On 1/19/12 4:03 AM, <a class="moz-txt-link-abbreviated" href="mailto:martin.juckes@stfc.ac.uk">martin.juckes@stfc.ac.uk</a> wrote:
<blockquote
cite="mid:E21FBC3F00D7304687CB46529F9676D71C8511E6@EXCHMBX01.fed.cclrc.ac.uk"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 12 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Hello All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’ve just noticed, following a user query,
that GFDL data is in NetCDF “64-bit offset” format, rather
than “classic”. “64-bit offset” mode requires NetCDF 3.6 or
later, hence causing at least one user a problem (because of
an old IDL installation using an even older netcdf library). I
believe that most of the archive is in “classic” mode and that
this was, strictly speaking, requested. However, as I have
just copied 40 thousand files from GFDL to BADC, I’m not keen
on having the GFDL data changed – rather, I think we should
advise users to update their software. NetCDF 3.6.0 was
released in Feb. 2007, so we are not exactly forcing the pace
as far as software upgrades go,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Cheers,<o:p></o:p></p>
<p class="MsoNormal">Martin<o:p></o:p></p>
</div>
<br>
<p>-- <br>
Scanned by iCritical.
</p>
<br>
</blockquote>
</body>
</html>