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.
Hi HP- > Institution: EUMETSAT > Package Version: 2.4a1 build date:@DATE@ > Operating System: Linux > Hardware Information: Java: home: /home/user/IDV_2.4a1/jre version: 1.5.0_11 > j3d:1.3.1 > Inquiry: Hi > > There is an inconsistency btw parameter names given when choosing a single > channel > (e.g. .*10.8....) and when choosing it among All Bands. In this case the 10.8 > channel is > called Temperature wich is not specific to the channel. It would be useful if > both unit and > channel designators would appear in the parameter name. For the time being I > tried to > define a default for Temperature but it does not work. Is the paramter name > really justTemperature or > are there some hidden characters? See attached parameter plugin For the single Band (single calibration), I default to the old style of parameter naming and did this so old bundles/formulas wouldn't break. But you are correct that this is problematic. I this case the parameter name is actually "M9 (10.8 um IR Surface/Cloud-top Temp)", the same as the Data Source description. The description is 10.8 um IR Surface/Cloud-top Temp and what you see in the list. In the new version (when you select multiple bands or a single band with multiple calibrations), the parameter name is not Temperature, but 52_Band9_BRIT using the convention we decided on. Temperature is just the description that gets listed in the selector. I decided not to put in the band information to the description since you would end up with something like this in the Field Selector: 0.6 um VIS Cloud and Surface Features 0.6 um VIS Cloud and Surface Features - Raw 0.6 um VIS Cloud and Surface Features - Radiance 0.6 um VIS Cloud and Surface Features - Reflectivity 0.6 um VIS Cloud and Surface Features - Brightness 0.8 um VIS Aerosols over Water, Veg 0.8 um VIS Aerosols over Water, Veg - Raw 0.8 um VIS Aerosols over Water, Veg - Radiance 0.8 um VIS Aerosols over Water, Veg - Reflectivity 0.8 um VIS Aerosols over Water, Veg - Brightness if you select all units and/or all bands/all units. It seemed that would be overkill in the selection list. Right now a Data Choice has a name (e.g. 52_Band9_BRIT) which is the key used for derived parameters and is the default name used in display labels and a a description (e.g. Brightness) which is used in the Field Selector or as the long name in display labels. Jeff and I talked about having a "label" which could be used in various places (labels, etc). In tomorrow's build, there will no longer be a composite choice shown as "0.6 um VIS Cloud and Surface Features" with sub choices of times when you select one band and one unit. Instead, there will be a single choice with a description "0.6 um VIS Cloud and Surface Features" with a name of 52_Band9_BRIT. That way it will be consistent with the multiple band/multiple unit selection. There will also no longer be a choice for the Image Sequence Display since this was tied to the composite choice. > Further on the paramter issue, I have a wild card entry in the parameter > defaults starting > with .*10.8. This resisted so far to be taken into a plugin. However, just > now when creating > the attachment it did not bark at me anymore. Was this mended and do you see > the wild card entry? I don't see any changes that should have fixed this so I don't know what's going on here. You shouldn't need that parameter any more with the new naming scheme, though. Let me know if this still causes problems. Don Ticket Details =================== Ticket ID: KUX-993952 Department: Support IDV Priority: Normal Status: Open