NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Hi Mary Ellen, I have been meaning to send you a follow-up email regarding the change in the maximum size of an ADDE image dataset, but one thing after another has made me put it off... sorry. Before I was going to open a ticket with SSEC/MUG, I decided to take a closer look at the server code that is now limiting the maximum size of an ADDE dataset to 9999 elements. What I found convinced me that the changes that would be needed to get rid of the limitation are more than what SSEC/MUG are likely to want to take on. The major issue comes down to using the maximum number of dataset elements to dimension an array of strings that represent the fully qualified pathnames to the elements of the prospective dataset. If this code were written in C, then one could realloc the space allotted as needed, but for some reason the code was written Fortran, so the allocation is static. One could increase the number of elements allowed, but that would do nothing more than make the limit a bigger number; it would not get rid of the fundamental limitation of there being a maximum number. It is because of this that I don't think that the MUG folks will be interested in/excited about/willing to make the code change. I will informally bounce the notion off of Becky to see if there was a general consensus that the number of image elements in a dataset should be limited, or if this was simply something that was never tested because nobody in SSEC, including the Data Center, has tried to define datasets with more than 9999 elements. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: ZAJ-781418 Department: Support McIDAS Priority: Normal Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.