Hi Jennifer,<br><br><div class="gmail_quote"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style=""><div><div>Did you build GrADS from source on this machine? </div>
</div></div></blockquote><div><br>Yes <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style=""><div><div></div><div><div class="Ih2E3d">
<br></div>Looks like you have converted grib2 into netcdf -- one file per forecast time. Is that right? </div></div></div></blockquote><div><br>Yes, I created one netcdf file per grib2 forecast run (ie <a href="http://01.nc">01.nc</a> would contain all 61 time periods from the 12z WW3 run); see more thorough description below.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style=""><div><div></div><div><div class="Ih2E3d"><br></div>There are some bugs in the gancgrid() routine in 2.0.a1 that I believe have been fixed for the next release. The gancgrid() routine is designed for speeding up the I/O from OPeNDAP servers, but it can work for non-pdef non-templated local netcdf files too. The non-templated condition for calling gancgrid() is what's missing in 2.0.a1 plus some other bug fixes in the subroutine itself. </div>
<div><br></div><div>You can bypass the gancgrid() routine by changing one line of code in gaio.c (lines 212-216) and re-compiling:</div><div><br></div><div><div> /* if (!strncmp(pgrid->pfile->name,"http://",7)) { */</div>
<div> if ((!strncmp(pgrid->pfile->name,"http://",7)) || ((pfi->ncflg==1) && (pfi->ppflag==0))) {</div><div> rc = gancgrid(gr,gru,id,jd,d,dx);</div><div> return (rc);</div><div> }</div>
<div><br></div><div>If you un-comment out the first line and comment out the second -- i.e., call gancgrid only for opendap data sets -- then the I/O should work. </div><div><br></div><div>However, it sounds like you are also making a mistake in the way you are templating your netcdf files. If you have one file per forecast time, you can aggregate them into one data set (with XDFOPEN and OPTIONS TEMPLATE) so there's no need to have each time step be in a separate data set. Also, when you call the smth9() function, which dimensions are varying? </div>
</div></div></div></blockquote><div><br>I will modify the src accordingly and see if that helps. <br><br>I think I may have misspoke initially when describing the setup of the various files or perhaps I am just misunderstanding. As I attempted to clarify above each netcdf file has the exact same contents as the original grib2 file on NCEP's FTP site (<a href="ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/wave/prod/wave.20080317">ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/wave/prod/wave.20080317</a>). <br>
<br>I want to show how the model is trending by using an "ensemble" of the previous 7 runs. When my script is executed it inserts the newest runs data into <a href="http://00.nc">00.nc</a> and "bumps" the previous runs down. If the newest run is the 12Z run for today (20080317) the netcdf files would contain the data for the various runs as follows:<br>
<br><a href="http://00.nc">00.nc</a> -> 12Z 20080317<br><a href="http://01.nc">01.nc</a> -> 06Z 20080317<br><a href="http://02.nc">02.nc</a> -> 00Z 20080317<br><a href="http://03.nc">03.nc</a> -> 18Z 20080316<br>
...<br><br>And so on until there are 8 netcdf files. Would your templating example still apply and help me display data in the manner I describe above? I attached a sample image which is being generated by this same script but is running in GrADS 1.8S11.<br>
<br>Thanks as always.<br><br>Cheers,<br>Matt<br> </div></div><br>