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 Trung, re: > Here is the output of dataloc command: > > [~] $ dataloc.k LIST LOC > > Group Name Server IP Address > -------------------- ---------------------------------------- > LOC <LOCAL-DATA> Hmm... > What directory into which the copied images were to be written? This depends on how you set things up. > Can you give me the path? Thanks. If you are doing the IMGCOPYs from a McIDAS session, you can list the working directory by running: !pwd into the McIDAS Text and Command window. If you are doing the IMGCOPYs in some sort of a shell script, then you should be specifying which directory you want to be in before running the McIDAS commands. The example scripts included in the Unidata McIDAS distribution, mcrun.sh and mcscour.sh, put one into the user's $MCDATA directory before running McIDAS commands. Again if you setup your user(s) as per the instructions in the Unidata McIDAS-X Users Guide, this directory will be: ~/mcidas/data -> all users except for 'mcidas' ~/workdata -> for the user 'mcidas' 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: QNX-338397 Department: Support McIDAS Priority: Normal Status: Closed