Science Highlight




Known Issues

Known Issues affecting the Cycle 9 release of the ALMA Observing Tool

The following table lists those issues which are known to affect the Cycle 9 version of the Observing Tool. This will be updated to denote whether an issue has been fixed and whether this fix has made it into an updated release.

Issue Description Resolved? Deployed?
C1_032 Leaving the OT open for days at a time can cause an error upon saving. Saving to another file, closing the OT and re-opening produces a "ZLIB input stream" error i.e. the project is unreadable. This issue is yet to be satisfactorily characterised.    
C2_009 Placing spectral windows that are exactly as far apart as they can possibly be can cause an error, the text of which is also misleading.    
C6_001 The OT's mosaicing algorithm will not allow an even number of pointings along a single row. A custom mosaic may be used instead.    
C8_001 The time estimate dialogue for VLBI and Phased Array Science Goals is not enforcing the three-hour minimum. However, the correct time is shown on the Cover Sheet and will be used by the Proposal Handling Team.    
C8_002 When setting the hour of a multiple visit using the time-constraint interface, it may not be possible to select certain values and attempting to do so may cause the OT to freeze. There is no known workaround at present.    
C8_003 Sources with different velocities may bring up a validation error relating to 'tuning groups'. Small changes to the source velocity may solve the problem. The first source typically seems to be the problem.    
C8_004 For a "simultaneous" 12-m + ACA proposal, the Cover Sheet will show TP time even if the TP Array is not required. However, TP Time will not be charged to the project.    
C9_001 For single continuum proposals where the source velocity is much larger than 0, the “Achieved RMS” in the Techincal Justification (second line) is miscalculated. The OT may also file validation errors warning that one (or more) spw has low transmission. Setting the source velocity to 0 – which should not affect a single-continuum proposal – can temporarily solve this issue.