2016B Release Notes

Critical Update: 2016B v1.4 will cease to produce scripts on February 10, 2017. Please download the newest version of the OT from our installation page.

Version 1.4: January 18, 2017

Listed below are known issues and bugs. This is not a comprehensive list and only addresses the modes released for BETA. Improvements to this software will be on-going and rapid. Bugs are likely not all known or characterized. If you find a bug, please contact the Q-Dev team.

Release Notes

• V1.4 (01/18/17):
  • Set position angle for LUCI target when reading from a LUCI mask file.
  • Change OT memory requirements from 8GB to 6GB.
• V1.3 (11/14/16): Added the 0.75″ Longslit to and removed the 1.5″ Longslit from LUCI1 after the most recent LUCI mask exchange.

• V1.2 (11/10/16): Fixed a MOS bug that caused MOS masks to fail to load after the “cancel” button was pressed.

• V1.2 (11/9/16): Initial release of BETA OT

Known Issues

• Position angle is not correctly set for LUCI targets when reading from an lms mask file (Issue in V1.3; fixed in V1.4)

• The V1.3 OT requires install/runtime memory of 8GB.
• Blind offsets do not have an special observing element to identify them. Thus the instrument must take a short exposure after making blind offset.
• Telluric Star Acquisition: Script should command the cross-filters to move into the filter wheel immediately after previous exposure while the acquisition takes place to avoid saturation. Currently, the mechanism only moves right before the exposure, potentially exposing the detector to persistence effects.

• Acquisition and spectroscopy blocks are not properly connected to lock Target coordinates, PA, or GS coordinates so that they must be identical. The same is true for LBCR and LBCB blocks which MUST have the same offsets.

• LUCI Guide Probe geometries are not high fidelity (missing fold mirror shadow). Additional geometry will be added in the future.

• On Windows 10, no desktop icon appears after install. The icon does appear in the start menu.

• Screen painting issues with Windows 10. If you are currently magnifying your desktop using the display settings under Windows 10 you may see cut off text on some OT screen. The ‘Observation’ / script creation panel, and the ‘Random‘ and ‘Grid‘ dialog boxes in the ‘Offset Sequence Component’ panel are known examples of where this may be seen. To correct this right click on your desktop and select ‘Display Settings’ from the menu. Set the ‘Change the size of text, apps, and other items’ slider to 100% and click on ‘Apply’. You may need to log out of your current Windows session and log back in again to have this correctly applied o the OT. If you find this makes the text on your screen too small to read then you might consider reducing your screen resolution under ‘Display Settings’, or using the ‘Magnifier’ desktop application.

• It is currently impossible to enter 0s as an Exposure Time for either MODS or LBC. Although it is common practice to do so for biases, it is not necessary in the OT. The scripts will simply ignore whatever exposure time you choose.

Known Bugs

• Error messages may appear inappropriately in MODS and LUCI sequence tabs even when no offset iterator is present: “You are offsetting along the dispersion direction and may be dithering outside the slit.” In these instances, please simply ignore this warning

• In LUCI, the OH1060 is not correctly identified as a cross-filter in the error handling software. You may receive warnings about exposure times and/or cross-filter combinations even when you have correctly selected this combination. Please ignore these warnings.

• You may see incorrectly triggered warning messages when completing MODS arcs or flats that suggest that the combination of filters and modes is non-standard. These warnings should only trigger for science; ignore any that appear for calibrations

• The LBC image is too small when fetched from any image server other than the default image server, accessed via the default “image” button.

• Bulk imports of XML files may result in a Java error message

• If the LBC image is too small (see above) it will impact the GS query.

• Selected zoom level in one instrument can affect FOV of other instruments in the Position Editor when switching between observations

• LBC Instrument Tab: When setting the Science Chip Readout, it is possible to put a minimum that is larger than maximum (don’t do this).

• Offset Tab: when manually changing the offsets using the two text boxes at the bottom of the tab (X/Y or RA/Dec) note the extra spaces. Editing may require backspacing, especially to add a negative sign.

• When loading your own FITS file and running catalog search, display of default image may not act as expected. Reproducible and under investigation.

• LBC Offset Iterator: When manually changing offsets, some times backspacing is required (e.g. negative signs)

• Use of 2nd Gen DSS @ CADC gives null pointer exceptions.

• Use of DSS v2 infrared @ ESO may give sporadic timeouts.