| | 91 | == Other projects to consider == |
| | 92 | * Ask Steve O if he has seasonal/historic data on sky transparency from 30-inch observations |
| | 93 | * Work with Greg Z to run LRS2raw reductions in real-time while observing |
| | 94 | * Refine our pointing model/layers to do a better job for Az=0 and Az=180 - those have the largest scatter in our pointing corrections |
| | 95 | * Update statistics on sky surface brightness, transparency, and IQ from typical observations at each priority, and provide that documentation to users |
| | 96 | * use Goldilocks to determine how much sky brightness is "too bright", consider making sky-subtracted S/N measurement in our real-time data reduction |
| | 97 | * revisit discussion of "throughput drop" from April 2023, investigate causes and possible explanations |
| | 98 | * monitor total azimuth rotation throughout a whole year - calculate statistics on a nightly or RA-ly basis to see if anybody has a good strategy for managing Az moves |
| | 99 | * quantify FWHM/IQ between both guiders and WFS PSFs to see what is most reliable |
| | 100 | * prepare documentation/planning tools to start using Collecting Efficiency |
| | 101 | * update shuffle to check for proper motion of blind offset starts (has led to bad setups in the past) |
| | 102 | * write small DIMM data monitoring program, and send audio/visual alert if we go >5min without DIMM data while still getting Guider/etc data |
| | 103 | * make cronjob status-checker for VIRUS/LRS2 pivot and other data transfer scripts, just to make sure it doesn't die during the night and end up crashing the instrument servers |
| | 104 | * make monthly probe health check images with cleaned data, to show when flat fields are not working very well |
| | 105 | * discontinue/remove "rasession" on hpf, if it causes more trouble than it is worth? |
| | 106 | * add moon/sky brightness to object observability tool, give brightness at start/mid/end of each track. |
| | 107 | * use ACQ camera photometry to measure photometric zeropoints over many years (requires ACQ data to be processed first - talk to Steve O about his pipeline for doing that) |
| | 108 | * consider documenting our practice of avoiding observations within 15-deg of the moon, inform PIs about the same, and include this in the planning tools |
| | 109 | * consider expanding definition of science time to be 12-deg twilights instead of 18-deg as it is now - with HPF (and soon HRS-2) it is possible to observe to -6 or -8 deg twilight. |
| | 110 | * consider "charging" the -000 engineering program for spectrophotometric standards and telluric standards - right now those are not charged to any partner and are not being consistently handled in our time accounting system |
| | 111 | * once we are using CE, scan the queue submissions to make sure no targets are requesting impossible/unreasonable CE values given their declinations and exposure times. |
| | 112 | * someday expand "checkcals" and "plotcals" from only LRS2 to include VIRUS and HPF cals as well |
| | 113 | * do dark dome testing with GTAG lights on and off some time while closed for weather |
| | 114 | * add another raspberry PI screen for currently loaded shuffle finding chart |
| | 115 | * add another raspberry PI screen to show "rasession" on HPF |
| | 116 | * consider whether this sky model would be useful for us: https://rtn-012.lsst.io/ |
| | 117 | * consider adding email confirmation when new users create accounts on hydra - would require legit emails and prevent spam user accounts |
| | 118 | * transition stability_test to Python3 (requires fixing weird issues with errors in the matching code that I didn't write) |
| | 119 | * consider adding morning Hg+Cd VIRUS cals into an overall morning cal script that will also run HPF morning cals (and any other morning cals needed) in an efficient way |
| | 120 | * resolve systematic discrepancy between IQ estimates from WFS1 and WFS2 |
| | 121 | * Someday, include reports from: https://trac.het.astronomy.utexas.edu:8001/trac/WFUCommissioning/wiki/HetDescription/spie and https://www.het.astronomy.utexas.edu/HET/TechReports/techreports.htm intp our document management system: https://edocuments.utexas.edu/D2/#d2 |
| | 122 | * ask Sergey about adding "-ev" argument for L/V cals, to just run a bunch of things together, V, L, PB, PD. since we do that usually |
| | 123 | * ask Sergey about adding self-timing feature to "cal" so that it can report how long each calibration set takes; get those numbers and monitor/report/udpate as needed |
| | 124 | * monitor and update GC1/GC2 positional zeropoints based on Amy W's data |
| | 125 | * analyze GC2 alignment data from 2022-07-30 UT, see RAlog txt file for details; we moved GC2 across its range, with rich star field throughout. plate-solve and check alignment. it's a very cool dataset!!! |
| | 126 | * automatically cycle the filter on the inactive guider every ~5min? useful data for sky brightness modeling |
| | 127 | * consider loading trajectory before cancelling - could speed up the setup commands from target_setup if we run it a little earlier |
| | 128 | * analyze 2021-11-15 UT data: we intentionally moved a mirror segment out and took a VIRUS SPC observation, trying with multiple segments, using PV camera to verify segment is un-obscured. This would allow a direct measurement of that segment's absolute reflectivity |
| | 129 | * periodically review HPF evening/morning cals to assess whether anything can be removed or shortened based on what we know now |
| | 130 | * do another review of HET Queue Operations to publish perhaps in SPIE's JATIS? Similar to this one: https://ui.adsabs.harvard.edu/abs/2007PASP..119..556S/abstract possibly starting from July 2016 when full science operations began. Maybe target July 2026 for 10-year review? |
| | 131 | * add longcals to highpri, to help remind us when longcals are needed? |
| | 132 | * update hetsky page, migrate off that computer, improve maps/links/etc |
| | 133 | * periodically verify probe positions using VIRUS + ACQ + Guider1 + Guider2 data in rich field - plate solve everything and map it all together |
| | 134 | * data mine historical weather data, how does the temp change before sunset, seasonally/weather; use that to inform operational decisions |
| | 135 | * |
