= Setting up on targets = Apart from our tools, it may be useful to know that when PIs submit finding charts they end up in: {{{ /data1/mcs/hydra/docs/}}}program ID. These can be useful sometimes. == Using {{{target_setup}}} == #target_setup This is current practice as of July 2019, a simpler wrapper for do_shuffle * run target_setup as : {{{ target_setup <-to> <-log> }}} (check other arguments as {{{target_setup -h}}}) [[br]]Example: {{{target_setup 435 E -to}}}. [[br]] Argument "-to" tell script to create TO web page with finding chart * target_setup runs do_shuffle in background if target data is missing * to use target_setup for catalogs use format: {{{target_setup 10 E -cat spc}}} this will calculate data for target #10 from Spectroscopic Standards catalog == [wiki:Shuffle#deleting_data Deleting and re-calculating shuffle data] == It is rare, but sometimes you may need to update the shuffle data for a target, first use [wiki:Shuffle#shdata_clean shdata_clean] and then {{{target_setup}}} If you have run this clean up procedure, it is presumably because you wish to re-run shuffle. We sometimes do this to get fainter stars labeled in the ACQ camera finder chart. Here are some examples: {{{ target_setup 2547 E -shargs "--catalog GAIA" or target_setup 2547 E -shargs "--allcams_magadd 3" }}} The argument passed to "-shargs" will be sent as an argument to the {{{do_shuffle}}} command run by {{{target_setup}}}. The above examples specify to use the GAIA catalog and to find fainter stars by 3 magnitudes, respectively. == Using {{{find_jumps}}} (must be run on Zeus, not astronomer@vdas) == #find_jumps SVN Location in hetdex-pr: /trunk/scripting/raScripts/find_jumps.py [[br]] **Note that this script is not in regular use as of 2022, but may still be useful [[br]]** {{{find_jumps}}} considers 1, 2, or 3 targets and finds stars for each probe (wavefront sensors and guiders) which can be reached from each, and also generates the setup and {{{iexp}}} commands necessary for these observations. It can be run for only those targets which have already had their shuffle data calculated (either via {{{target_setup}}} or {{{do_shuffle}}} directly), and will give an error message if the shuffle data are not present. * run find_jumps as : {{{ find_jumps () }}} (check other arguments as {{{find_jumps -h}}}) [[br]] B+R science target: {{{find_jumps E 2544 2545}}} [[br]] L+V+V target: {{{find_jumps E 1550 1551 1552}}} [[br]] * Can also use this for LRS2-B+R spectrophotometric standards with:[[br]] B to R jump: {{{find_jumps E 12 --spcBR}}} or the R to B jump: {{{find_jumps E 12 --spcRB}}} * Can also use this for VIRUS 047+057 spectrophotometric standards with:[[br]] 047 to 057 jump: {{{find_jumps W 55 --spcV}}} * Can specify a different catalog with {{{--cat}}} or {{{-c}}} argument:[[br]] Examples of running it are:[[br]] * {{{find_jumps E 24 --spcBR}}} #use 056/066 * {{{find_jumps W 44 --spcV }}} #use 047/057 * {{{find_jumps E 27 28 29 }}} #assumes current trimester * {{{find_jumps W 30 31 }}} #assumes current trimester * {{{find_jumps E 25 26 --cat 19-2}}} #specifies 19-2 trimester Examples of the setup commands it produces are given below, for a target (LRS2B + two amps of a VIRUS IFU) from the main queue and for an SPC observation (LRS2-B+R): {{{ [stevenj@zeus ~]$ find_jumps E 400 401 402 .... target_setup 400 E -to >/dev/null syscmd -T 'cancel_trajectory()' > /dev/null cp /data1/mcs/shuffle_data/19-3/400/E/ACAMimages/VLSPC_G19374A_B_056_E.jpg /data1/nossy/www/html/noss/htopx/acam_dss.jpg syscmd -T 'load_trajectory(ra=7.895662, dec=52.493629, equinox=2000.0, dir="EAST", object="triple_jump")' >/dev/null syscmd -T 'Guider1_set_position(ra=7.898899599999999, dec=52.324485, trajectory="next")' >/dev/null syscmd -T 'Guider2_set_position(ra=7.884303266666667, dec=52.597103, trajectory="next")' >/dev/null syscmd -T 'WFS1_set_position(ra=7.911996933333333, dec=52.565909, trajectory="next")' >/dev/null syscmd -T 'WFS2_set_position(ra=7.878961866666667, dec=52.422996, trajectory="next")' >/dev/null syscmd -T "go_next(move_structure='true',move_dome='true',move_probes='true')" > /dev/null syscmd -p 'WFS1_SetExposureTime(time=5)' >/dev/null syscmd -p 'WFS2_SetExposureTime(time=5)' >/dev/null syscmd -p 'Guider1_SetObjectAndMagnitudes(**{"g`": 15.2, "r`": 14.78, "i`": 14.63, "object": "PANSTARRS:170791184834840071"})' >/dev/null syscmd -p 'Guider2_SetObjectAndMagnitudes(**{"g`": 16.21, "r`": 15.74, "i`": 15.55, "object": "PANSTARRS:171111182645257220"})' >/dev/null syscmd -p 'WFS1_SetObjectAndMagnitudes(**{"object": "PANSTARRS:171071186797429885"})' >/dev/null syscmd -p 'WFS2_SetObjectAndMagnitudes(**{"object": "PANSTARRS:170901181843738275"})' >/dev/null iexp 400 E syscmd -T 'offset_trajectory(dra=45.198, ddec=-86.0904, adjust_probes="true")' iexp 401 E syscmd -T 'offset_trajectory(dra=21.276, ddec=5.31359999999, adjust_probes="true")' iexp 402 E # GC1set:True GC2set:True WFS1set:True WFS2set:True }}} {{{ [stevenj@zeus ~]$ find_jumps W 25 --spcBR .... #here are the setup commands: target_setup 25 W -cat spc -ifu 056 -to >/dev/null syscmd -T 'cancel_trajectory()' > /dev/null cp /data1/mcs/shuffle_data/spc/25/W/ACAMimages/GRW+70_5824_056_W.jpg /data1/nossy/www/html/noss/htopx/acam_dss.jpg syscmd -T 'load_trajectory(ra=13.650243, dec=70.326735, equinox=2000.0, dir="WEST", object="triple_jump")' >/dev/null syscmd -T 'Guider1_set_position(ra=13.650619933333333, dec=70.164666, trajectory="next")' >/dev/null syscmd -T 'Guider2_set_position(ra=13.6290654, dec=70.19542, trajectory="next")' >/dev/null syscmd -T 'WFS1_set_position(ra=13.6312956, dec=70.458621, trajectory="next")' >/dev/null syscmd -T 'WFS2_set_position(ra=13.648520516049382, dec=70.15766611111111, trajectory="next")' >/dev/null syscmd -T "go_next(move_structure='true',move_dome='true',move_probes='true')" > /dev/null mgp -traj current -u wf2 syscmd -p 'WFS1_SetExposureTime(time=5)' >/dev/null syscmd -p 'WFS2_SetExposureTime(time=5)' >/dev/null syscmd -p 'Guider1_SetObjectAndMagnitudes(**{"g`": 17.17, "r`": 16.81, "i`": 16.67, "object": "PANSTARRS:192192047593118410"})' >/dev/null syscmd -p 'Guider2_SetObjectAndMagnitudes(**{"g`": 16.86, "r`": 15.83, "i`": 15.36, "object": "PANSTARRS:192232044359325271"})' >/dev/null syscmd -p 'WFS1_SetObjectAndMagnitudes(**{"object": "PANSTARRS:192552044693961125"})' >/dev/null syscmd -p 'WFS2_SetObjectAndMagnitudes(**{"object": "PANSTARRS:0"})' >/dev/null iexp 25 W -cat spc -ifu 056 mgp -toff=BR iexp 25 W -cat spc -ifu 066 # GC1set:True GC2set:True WFS1set:True WFS2set:False # shdata_clean -cat spc -idx 25 target_setup 25 W -cat spc -ifu 056 -shargs "--allcams_magadd 3" target_setup 25 W -cat spc -ifu 066 -shargs "--allcams_magadd 3" }}} Note that if the code is unable to find probe stars which survive the jumps, it will suggest some options for you to try. The previous example shows a setup without a WFS2 star, and suggests that you could re-run shuffle allowing fainter stars (and provides those commands for you, but does not run them automatically). You don't have to re-run shuffle, though, if you're OK with setting up without a WFS2 star. Make sure not to use that probe for setting up, as it is "unset" and will not do the offset(s)/jump(s). The next example shows a setup which completely fails, and requires the user to re-run shuffle with fainter probe stars if you want to try again. {{{ [stevenj@zeus ~]$ find_jumps E 468 469 setup failed - no safe spot for WFS2. I recommend running: shdata_clean -idx 468 shdata_clean -idx 469 target_setup 468 E -shargs "--allcams_magadd 3" target_setup 469 E -shargs "--allcams_magadd 3" }}} After running those commands (on vdas), the setup works! Hooray. Other options you may consider trying * {{{--gc1ccw}}} This selects the star for GC1 as the most-counter-clockwise available, rather than brightest * {{{--allccw}}} This selects all probe stars based only on their angles, not brightnesses * {{{--showplot}}} This will display a plot of the candidate stars and selected positions for each probe. If you find bugs or unusual errors with this code, please send them to Steven J for trouble-shooting and improvements. == Using {{{fgstar}}} == #fgstar The fgstar routine is an alternative to shuffle for visualizing the IHMP projected on a sky position. For a detailed explanation of this routine use the help flag (see example below). {{{ [astronomer@mcs ~]$ fgstar --help Usage: fgstar 06:15:20.46 +39:51:50.6 304.0 gc1 N arg1 - RA of IHMP center (sexigecimal) arg2 - DEC of IHMP center (sexigecimal) arg3 - Azimuth of HET structure (degrees) arg4 - probe name (valid names = gc1,gc2,wf1,wf2) arg5 - run in verbose/debug mode (Y/N) }}} }}} Be sure to use the arguments formatted in the same way they are in the example. The Ra,Dec parsing routines in this code are not very flexible. Direct questions to Steve O. More details and examples of fgstar-generated figures can be viewed at [http://www.as.utexas.edu/~sco/fgstar//index.html]. == [wiki:Shuffle#shuffle.cfg Making changes to shuffle's shuffle.cfg] == #config Talk to Steven J or Sergey if you need to do this. == [wiki:Shuffle#update_shuffle updating shuffle] == Talk to Steven J or Sergey if you need to do this. == Setup on targets from the new queue == #newqueue Set up the HTOPX filter to the new queue first. "Queue filters" > "Queue" > "New" and then click Update button. Make sure that the new queue's targets are shown. Because of the browser's cache or cookies, nothing might have shown up. In this case heck to see if all of the "Queue filters" are set properly. Also, make sure that all of the new programs are selected. Hit the Update button once more. Now, use the "-queue new" arguments when running target_setup to make it work with the new queue targets. iexp should be used with "-queue new" as well