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 Jeff, > > it works well. > > The tree-view interaction would indeed complement things. Further to this, I > was wondering if the selection could also be done semi-automatically by > matching the param-names used in a Formula against the names of fields > available in the Field Selector. > > This would work analog to the "Search for a field by name" (as attached), > except we have to consider the fact that some field %longname%s have spaces > _and_ formulas would grow quite lengthy with many params. So a wildcards like > * or ? would be helpful here: > > test(Retrieved?Temperature*[multiple=true]) > > would auto-select all "Retrieved Temperature - Level x" fields, skipping the > "Retrieved Moisture - Level x" fields. > That already exists. See the formula docs: http://www.unidata.ucar.edu/software/idv/docs/userguide/tools/Formulas.html You can also specify a regular expression pattern that is used to pre-select the first data choice whose description matches the pattern. someProcedure(someValue[pattern=some_pattern]) Right now we only select one thing but I will look into it. -Jeff Ticket Details =================== Ticket ID: HIE-550438 Department: Support IDV Priority: Normal Status: Open