Ver 1.1 Bugs & issues
Posted: Wed Oct 20, 2004 7:27 pm
Some of the things I've found with 1.1:
-NGRD2PCG32 has problems with NOGAPS grib files. For some reason after it builds the grid file and places it in GRIDDATA directory, even if the /NWS directory is empty, it still checks all the fields from the earlier version of the file in the GRIDDATA directory.
-PCGRIDDS32 has several issues with the ANIM command. First, if it builds a loop based on 3 hour interval data and loops that data, a switch to a different GRIB file with different forecast hour intervals results in the ANIM command still looking for 3 hourly interval data. The way to get around this is to exit PCGRIDDS32 and delete all the BMP files in the ANIMATE directory. A good fix would be to have PCGRIDDS32 reset the animation parameters when a new GRIB file is loaded.
Another issue with the ANIM command is the lack of an abort option when ANIM is loading parameters that are not found. For example if you run the command "bknt 105m clr1&anim" because there is no 105m wind, the ANIM command will keep looking throughout the whole forecast interval time series with no way to stop the process. This is not the case when data is found, the "S" key stops the loading.
-NGRB2PCG32, GFDL nested grib files create a unique grid project and file for each forecast interval. Because NGRB2PCG32 processes the grib files in the order they were saved on the computer, it's possible the 36 hour forecast and the 12 hour forecast be labled in or out of sequential order. This makes it quite challanging to load a GFDL file and find the forecast hour for that specific file. Also, this prevents the use of macros because the labeling is not time specific.
-NGRB2PCG32, the change to the naming of the files now overwrites the date digit. For example, if NGRB2PCG32 creates a file called OCT200412.AVN211 and then different data for the same model is processed, it gets the name OCT2A0412.AVN211 but you can't see if it's October 20th or 21st or 22nd, etc.
All this being said, this is a great program and I look forward to using it well into the future. Thanks Jeff for the hard work.
Craig Setzer
-NGRD2PCG32 has problems with NOGAPS grib files. For some reason after it builds the grid file and places it in GRIDDATA directory, even if the /NWS directory is empty, it still checks all the fields from the earlier version of the file in the GRIDDATA directory.
-PCGRIDDS32 has several issues with the ANIM command. First, if it builds a loop based on 3 hour interval data and loops that data, a switch to a different GRIB file with different forecast hour intervals results in the ANIM command still looking for 3 hourly interval data. The way to get around this is to exit PCGRIDDS32 and delete all the BMP files in the ANIMATE directory. A good fix would be to have PCGRIDDS32 reset the animation parameters when a new GRIB file is loaded.
Another issue with the ANIM command is the lack of an abort option when ANIM is loading parameters that are not found. For example if you run the command "bknt 105m clr1&anim" because there is no 105m wind, the ANIM command will keep looking throughout the whole forecast interval time series with no way to stop the process. This is not the case when data is found, the "S" key stops the loading.
-NGRB2PCG32, GFDL nested grib files create a unique grid project and file for each forecast interval. Because NGRB2PCG32 processes the grib files in the order they were saved on the computer, it's possible the 36 hour forecast and the 12 hour forecast be labled in or out of sequential order. This makes it quite challanging to load a GFDL file and find the forecast hour for that specific file. Also, this prevents the use of macros because the labeling is not time specific.
-NGRB2PCG32, the change to the naming of the files now overwrites the date digit. For example, if NGRB2PCG32 creates a file called OCT200412.AVN211 and then different data for the same model is processed, it gets the name OCT2A0412.AVN211 but you can't see if it's October 20th or 21st or 22nd, etc.
All this being said, this is a great program and I look forward to using it well into the future. Thanks Jeff for the hard work.
Craig Setzer