2017A Release Notes

NOTE: The Observing Tool is currently in its First Public Release. It will produce 1) monocular and binocular LBC Science scripts 2) monocular MODS scripts (which can be run at time of execution in “identical” twin mode) 3) monocular LUCI1 and LUCI2 Science seeing-limited scripts 4) limited binocular LUCI Science scripts; including “identical twin” OBs, with mirrored observations on both SX and DX, and a “fraternal twin” script that allows for nearly identical scripts with different mask names 5) calibration scripts for all instruments.

Libraries for all instruments are also available

2017A Version 1.2: May 23, 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.

Current Release:

• 2017A V1.2 (5/23/17): Point release of 2017OT

Fixes to previous releases:

• Upgrade of visualization to improve fidelity in high elevation ranges.

• Absorb offset type now handled correctly in both RA/Dec, Det XY axes

• Upgrade visualization to correctly position Pointing Origin and specified RA/Dec after DetXY and RA/Dec offsets

• Fix of visualization bug that showed AORef, MODSGS, and LUCIGS outside of the patrol field as valid and others that are in the patrol field as invalid. Corrected sign error that led to geometry issue

• Migration from Java 1.7 and Scala 2.10 upgraded to Java 1.8 and Scala 2.11

• Disabled Twin Fraternal option for Luci scripting if imaging is selected.

• Remove LUCI Dark camera default to N1.8. Unnecessary restriction that may impact data reduction scripts

• Remove Binocular Group from pull down menu on Group Tab

• Change User Type to be indexed at 1 on the TPE and Target Tab

Known Issues:

• Warning and error messages for LUCI may not be up-to-date with rapid developments in modes and mechanisms offered. Unless explicitly stated, errors will not prevent script generation and can be safely ignored if you are confident with your set-up. Please check with your ISA if you have any concerns.

• 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.

• LBC Focus and Guide Selection: Due to image distortion there is noguaranteethe Guide or Focus chip will land on the desired chip. FOR LBC Blue the image distortion is fairly minimal, for LBC Red, keep the Guide and Focus star on the inner portion of the tech chip overlay (the half closest to the science array) for best results.

• 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.

• 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:

 

• Downloads of the library into Windows sometimes fail with the message shown below. One potential solution is to be sure to import the library directly from the default browser download folder rather than using any browser drag-and-drop feature. Another solution is to close and reopen the OT and try the import again.

• Intermittent screen painting issue across all platforms. The Telescope Mode and Position Angle dropdown boxes may disappear from the Target Tab. If this occurs, you will need to close and re-open your OT.
• 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.

• 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.

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

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

Previous Release Notes:

2017A V1.1 (2/13/17): Point release of 2017OT

Fixes to previous releases:

• The N30 Field Stop is now included as a mask option for LUCI1 and LUCI2

• The associated xslt version now correctly inserts the flag for adaptive optics if an AORef star is specified

• A sign error in the patrol field geometry check for MODS and LUCI Guide Stars and LUCI AORef stars is now fixed

All fixes from 2017A v1.0 are still valid

Known Issues:

• Same as Known Issues in Current Release

• Visualization issues at high elevations

• Visualization issues when changing between DetXY and RA/Dec

Known Bugs

• Same as Known Bugs in Current Release

• Visualization bug shows AORef, MODSGS, and LUCIGS that fall outside of the patrol field as valid and others that are in the patrol field as invalid. Incorrect geometries due to a sign error (2/4/2017)

2017A V1.0 (2/3/17): Initial release of OT

Fixes to previous releases:

• The V1.0 OT now requires install/runtime memory of 6GB.
• Blind offsets no longer take automatic exposure. Observations with a blind offset in the last step of an acquisition will proceed directly to science set-up and exposures.

• Telluric Star Acquisition: Script now commands the cross-filters to move into the filter wheel immediately after previous exposure while the acquisition takes place to avoid saturation.

Known Issues:

• Same as Known Issues in Current Release

Known Bugs

• Same as Known Bugs in Current Release

• N30 Field Stop missing from LUCI1 and LUCI2 (2/4/2017)

• XSLT issue. AORef star should trigger flag to set adaptive optics on, but is currently not working (2/4/2017)
• Visualization bug shows AORef, MODSGS, and LUCIGS that fall outside of the patrol field as valid and others that are in the patrol field as invalid. Incorrect geometries due to a sign error (2/4/2017)