geoarc very slow for h8 data
Posted: Tue Mar 01, 2016 3:54 pm
Hi,
I was helping a co-worker display H8 data as an rgb in McIDAS-V. He had a machine with 25 GB of memory and we could not display a H8image, even at reduced size from the geoarc server. First, the data selection was painfully slow, then the actual image creation failed. It seems that data from the real-time H8 data server is slightly faster. I wrote a script for him so that he could at least get an image created, at the same size we were requesting through the GUI. He had NPOT checked in the Advanced Preferences. This will be a big problem when GOES-R is launched if the speed of data access is the same.
Second, the weighted average as default confused again. It might be a good idea to create a checkbox for some of these features at install so the user knows that default is "Weighted Average." I am not sure if NPOT is still by default "off", but a prompt at install might be appropriate for this as well if it is still default "off."
Joleen
I was helping a co-worker display H8 data as an rgb in McIDAS-V. He had a machine with 25 GB of memory and we could not display a H8image, even at reduced size from the geoarc server. First, the data selection was painfully slow, then the actual image creation failed. It seems that data from the real-time H8 data server is slightly faster. I wrote a script for him so that he could at least get an image created, at the same size we were requesting through the GUI. He had NPOT checked in the Advanced Preferences. This will be a big problem when GOES-R is launched if the speed of data access is the same.
Second, the weighted average as default confused again. It might be a good idea to create a checkbox for some of these features at install so the user knows that default is "Weighted Average." I am not sure if NPOT is still by default "off", but a prompt at install might be appropriate for this as well if it is still default "off."
Joleen