This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Pat, It could be that you have some files in the directory named YYMMDD and some named YYYYMMDD. In particular, if you were running nsat_links before to create the links to the AREAxxxx files in the mcidas directory, and now you are naming the files with 4 digit years, then if you have both types in the data directories- one of those will get things confused. To see all of the files under $SAT, cd $SAT ls -R That wills how all the files under the sat directory. If you have a mix of naming conventions, change them all to YYYY. Steve Chiswell >From: Local Data Manager <address@hidden> >Organization: UCAR/Unidata >Keywords: 200008102309.e7AN9MT28496 >Steve: > >Thank you for your quick reply (and thanks also for your help with snrawd---I >can remember if I said so before, but if I did, then thanks again!) > >I made the changes to Garp_defaults; the satT was set to YY. I also changed >the sat: also to reduce the non-existant labels. In addition, I commented >nsat_links out of the ldm crontab and added an extra line to the scour.conf >file. > >However, GARP still does not display satellite imagery. A clue comes with thi > s >also, several actually. First, the error message is now: > > Invoke ... /asp/met/nawips/bin/sol/garp >G A R P - v2.1 starting... >!!!!!Whoa!!!!!! Free() got a 0x0 >ch_to_int_time: Invalid year, 8 > > >*and* when I try to display GOES-8 or -10 IR or VIS imagery, the correct numbe > r of >file times somes up, but they all display the same date and time stamp. This > also >happens for the Floater imagery. > >I won't be in much tomorrow, but my assistant, Stacy will be. She should be a > ble to >continue this dialogue with you. If not, I'll be back on Monday. > >Thanks again, Steve. > >Pat >