Copy a FITS image to a local working directory or local archival directory.
Usage: mli_copy_markII RAW ../S/20170420T101656.1_acm_sci.fits N arg1 = name of subdirectory in archival directory (can be none) arg2 = image to be copied arg3 = run in debug/verbose mode (Y/N) For a more detiled description of mli_copy_markII use: % mli_copy_markII --helpThe reasons for a routine like this may not be obvious. In short, it provides a way of handling images located in readonly locations, and a way to handle the processing of images with extremely long fullpath names (many of my image processing codes require image names of less that 120 characters). A short example is given below:
A good image for demonstracting processing of HET acm images is located in my critical files diretory. The full path to this image can often be well over 120 characters. Grabing a local copy could be done with:
The file I want: $critfils/tdat/acm/20190401T115437.0_acm_sci.fits % mli_copy_markII RAW $critfils/tdat/acm/20190401T115437.0_acm_sci.fits N This givesm a copy of the image in: % ls -lt ./local_red/RAW total 2352 -rw-r--r-- 1 sco sco 2407680 Apr 16 13:43 20190401T115437.0_acm_sci.fits % cat LIST.OUT ./local_red/RAW/20190401T115437.0_acm_sci.fitsThe local image address is deposited in the file LIST.OUTT and can be easily accessed by downstream processing scripts.