The bash script, named gcpic_draw, uses many different routines. It is patterned after het_acam. The difference is I DO NOT input a WCS-calibrated ACAM image. Instead I just feed the RA,DEC of the IHMP center and plot things up on a DSS image. Just like het_acam, we used the bash script gcpic to actually retrieve the DSS image and prepare a few files. IMPORTANT: If a DSS image named dss.fits already resides in the local working directory, then gcpic_draw uses THAT image and does not gather a new FITS image for display!
gcpic_draw 21:53:53.89 +62:36:52.6 15.0 342.0 -0.031 -0.134 gc1 Y Usage: gcpic_draw 21:53:53.89 +62:36:52.6 15.0 342.0 -0.031 -0.134 gc1 Y arg1 - RA (sexigecimal) arg2 - DEC (sexigecimal) arg3 - faintest USNO RED magnitude arg4 - Azimuth of HET structure (degrees) arg5 - x_ang of probe (degrees) arg6 - y_ang of probe (degrees) arg7 - probe name arg8 - open a ds9 window (Y/N)It may be helpful to see a full run:
* In an empty subdirectory I run my gcpic_praw command:
% pwd
/home/sco/tmp
% ls
% gcpic_draw 21:53:53.89 +62:36:52.6 15.0 342.0 -0.031 -0.134 gc1
*** I answer the "hit any key" queries with a Return.
*** I see my image pop up and then:
Clean working directory? (Y/n):Y
Close the ds9 window? (Y/n):Y
Deleting the ds9 window. Goodbye.
*** The ds9 GUI disapears, and in my working directory I
now see:
% ls
circle_trans.header dss.fits gc.reg STARS.cdfp
c.pix dss.ps_data gprobes.circles STARS.cdfp.reg
If I wanted to run gcpic_draw again using the same field, but
changing the probe positions, I would just make that run now.
However, I wanted to do a completely NEW field, I would (at least)
have to eliminate the file "dss.fits". In general, I would just
(carefully) executed a "\rm -r *" in my working directory and
go again with a new gcpic_draw run.
HISTORICAL CONTEXT: Why do I have 3 different routines that really should be one? Early on I was using gcpic to get a DSS image and draw the probe positions. Then the IHMP was covered (in late Aug2015) with dsi and dwfs cameras and the guide probes were turned off. In order to proceed with the dsi image analysis I developed het_acam, which does use gcpic (before the guide probe painting was intsalled). This work was objected to, so I stopped, but in Nov2015, these routines were desired, so I had to kluge something up. Becasue het_acam has been developed and tested, I did not want to alter it's usage by horsing around with gcpic. Hence, this routine (gcpic_draw) will perform much of the work of het_acam. However, I'll add a few tasks that enable us to overplot the position of a guide probe camera on the DSS image.
DSS Image Size: The size of the DSS image pulled for use by gcpic_draw is hardcoded. In the mid-Nov2015 versions of gcpic and gcpic_draw I was pulling very large dss.fits images. Here is a table of sizes I commented into gcpic:
# The size of the image is hard-coded # Here are some radmin vaues (radius of image in ARCMIN) # and the reulting image (dss.fits) sizes # radmin Xsize Ysize # 27 3208 3214 # 22 2614 2619 # 20 2376 2381 # 20 2376 2381 # 17 2020 2024 radmin="17"In late Nov (Nov22,2015) I changed the size to radmin="17". This makes the image retrieval time much shorter, but more importantly to me now, it builds a dss.fits file that all of my codes can read (i.e. a size less than 204x2048 pixels). I guess if folks want larger images, than can write their own versions of this.
In Jan2017 I began to upgrade gcpic_draw. Basically I wanted it to also draw in things like the BIB, HRS, etc... I just added these positions to the vir_ifu_pat.ifu_names file that is made by the call to the vir_ifu_pat.sh script (an OTW code). The names are plotted just like with the IFU positions, however the actual cyan boxes for these special positions are not drawn in. Here are some notes:
1) The script that draws in the IFUs and other features is virus_mark_all. It is called about half down in gcpic_draw. 2) Routine that virus_mark_all uses: mark_ifu_boxes == draws and labels IFU boxes mark_ihmp == draws IHMP center mark_ifu_fibers == paints fibers in each IGU