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.
Gilbert, > Oh, I hate to do this to you, but a colleague has found what appears to be > a bug that I now notice on my machine as well. > > When I installed 6.6.1, my GFS model data started splitting into multiple > files. Like so: > > % ls -al *.gm0 > > -rw-rw-r-- 1 ldm ldm 6.2M Mar 18 23:40 00021907.gm0 > -rw-rw-r-- 1 ldm ldm 6.9M Mar 19 23:41 00022007.gm0 > -rw-rw-r-- 1 ldm ldm 44M Mar 18 23:40 00031907.gm0 > -rw-rw-r-- 1 ldm ldm 43M Mar 19 23:40 00032007.gm0 > -rw-rw-r-- 1 ldm ldm 50M Mar 19 05:40 06031907.gm0 > -rw-rw-r-- 1 ldm ldm 50M Mar 19 11:41 12031907.gm0 > -rw-rw-r-- 1 ldm ldm 50M Mar 19 17:41 18031907.gm0 > > Looking inside the 6.2 and 6.9 MB files, I see that they should be a part > of the March 19 and 20th 0Z files. Of course, when you do the math, they > add up to 50 MB, so this makes sense. > > This just started happening on March 8 with the 0Z run, according to my > 30 day file list, precisely when I installed LDM-6.6.0. Any ideas? What LDM version were you running before 6.6.0? Regards, Steve Emmerson Ticket Details =================== Ticket ID: MDG-898989 Department: Support LDM Priority: Normal Status: Closed