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 again Carol, So, the problem is in the McIDAS command line parser. This will take more than a few minutes to completely diagnose and fix. In the meantime, I have figured out a way to get things to work. At least this works for me: mcrun ABITRUCOL INPUT/MULTIBAND 1 \'DAY=222 TIME=19:00 19:20\' \'LAT=0 75\' 'mcrun' is Unidata addition to McIDAS that we wrote a LONG time ago. It is built and and installed with the standard SSEC applications, so it is available immediately. Please update your Perl script and change it to run the 'mcrun' invocation like the example above. Of course, you will not be hardwiring the DAY, TIME and LATLON values like this example. Let me know what your results are! 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: YAX-451139 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.