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 Carol, re: > I've copied the ABITRUCOL.MCB file to /home/mcidas/workdata and > /home/mcidas/data. I can get the 'help.k ABITRUCOL' to print the help page, > but I can't get the abitrucol command to work. > > [mcidas@typhoon workdata]$ abitrucol.k NPGOESR/CONUS 'DAY=221 TIME=21:16' > 'MAG=-2' > -bash: abitrucol.k: command not found ABITRUCOL is a McBASI script, not a binary executable, so you can not execute it outside of a McIDAS session by specifying the name of the script without the .MCB extension. Instead, you have to use the RUN command (run.k) to run the McBASI script: run.k NPGOESS/FD 1 'DAY=216 TIME=21:30:31' 'LAT=0 137 MAG=-2' FILE=ABITRUCOL.MCB re: > What's weird is that if I actually load the McIDAS interface and run > ABITRUCOL NPGOESR/CONUS 'DAY=221 TIME=21:16' 'MAG=-2' it all works. Yes, that is because the McIDAS command interpreter knows how to run McBASI scripts directly. re: > Any thoughts why the ABITRUCOL command isn't working in the terminal? Please try using RUN (run.k) and let me know if you still have problems. 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.