==> DFS COMPONENT NAME: OT ==> DFS COMPONENT RELEASE NUMBER: 2_9beta4 ==> DFS RELEASE TYPE: minor ==> DELIVERED BY: User Support Systems team ON: 17-Dec-2004 ==> MAIN REASON OF THE DELIVERY: This is a beta OHS 2.7beta3 release. ==> DEADLINE FOR DELIVERY TO USERS: 08-12-2003 ==> CONFIGURATION REQUIRED FOR INTEGRATION TESTS: Standard test plan. ==> LIST AND LOCATION OF SPECIFIC TEST DATA TO BE RETRIEVED AND USED FOR INTEGRATION TESTS: N/A ==> POINTS ALREADY CHECKED DURING UNIT TESTS: ==> POINTS TO BE CAREFULLY CHECKED DURING INTEGRATION TESTS: ==> COMPLETE LIST OF ACTION ITEMS/PROBLEMS REPORTS ADDRESSED BY THIS RELEASE: RELEASE NOTES FOR 2.9beta4 In the current schema, the user can modify the README file and submit the new version any time, without asking the USG contact scientist. This possibility should be kept in the new schema. This puts the following requirements: * the user has to be able to check-out/modify/submit the README without the need of changing the status of the file itself; * On checkin for the first time the readme file gets set to Defined (D) and an entry is inserted in the usg_file table where only the preimaging flag that the user had entered is reflected taken from the readme file. The usg support astronomer also receives an e-mail telling him the programme id of the run which has been checked out. * When the usg support astronomer sets the status to + then the readme_replicate table is updated and the file will be visible on Paranal. * when the user checks out the README file, the USG contact scientist isnotified; * when the user re-submits the README file, the USG contact scientist is notified; * when the USG contact scientist has reviewed and approved the new version (setting the status flag to +) the new README version has to become visible to Paranal. All this interaction is stored in 2 history tabes one for any status changes and the other for value file changes in the readme. These are the tables support_history and support_status_history. Instrument specific comments at the run level were instroduced as part of the readme Now all obs for a given observing run that have User Comments or Instrument Specific comments are included as part of the readme Viewing of eph files are availble from the queue view and the Repository browser RELEASE NOTES FOR 2.9beta3 All data written by p2pp is now displayed in the database inclusing eph files and inst specific comments RELEASE NOTES FOR 2.8 [3806] Fixed obsblock breakdown report,tree display to only show correct constraints [3821] Added Sidereal Time Min and Max to sort criteria NOTES FOR OT 2.8beta4 [3805] Added to reports and tree control widget both values Added baselines in selection criteria column selection. Add ST Start and end in Queue View + Rep Browser. Visplots confirmed to be working by Markus Wittkoski RELEASE NOTES FOR OT 2.8beta2 AR 1781 Delete all now fixed Sidereal time added to queue view and repository browser RELEASE NOTES FOR 2.8alpha1 Sidereal time added to the Repository Browser. RELEASE NOTES FOR 2.7 No changes from previous beta RELEASE NOTES FOR OT 2.7beta4 [3242] Made exporting of OB's work with the database as well [3255] Fixed exception will no longer happen RELEASE NOTES FOR OT @2.7beta3@ [3131] Only displayed locally in P2PP if there is a database id which is non zero ObsBlock Breakdown report is shared code across OT and P2PP so it is fixed in both. [3194] Fixed it is now added can called evmGetNumberOfFindingCharts. I have added it to the scriptAPISetup.tcl file and informed Stephane Marteau [2716] OB Hostory is now added to the repository browser. [1745] Finding Chart support has been added. The main focus area is the Finding Chart Viewer which can be invoked from the QueueView,ExecutionSequence or the Repository Browser. [3170] Added printing of findsing charts to queue view, Execution Sequence and Repository borwser. The Finding Chart control prints the current screen display [3193] Added Finding Charts column selection to the DBB Panels for ExecutionSequence Queue View and Repository View For RepositoryBrowser and Queue View sort is also added [2671] Fixed Now only one window but the OB ID cannot be read only anymore as the user should be able to browse completely the database and not just thw selected OB from within the same single window RELEASE NOTES FOR OT @2.6beta3@ ************************************************************ 09-07-2003 RL [2685] use outer join in case OB Name doesn't exist 08-07-2003 RL [2664] OB History: selection criteria fixed (login) ************************************************************ RELEASE NOTES FOR OT @2.6beta2@ **************************************** * [2591,2637] The user id was getting put in the component field and vice verss This is now fixed * [2599] OB History selection criteria fixed (template) * [2656] OB History: status selection is a multi-select list * [2611] OB History: users can only see their own events * [2632] OB History browser size is set * [2597] OB History Timestamp format set to same as other windows * [2598] Print feature detects printer errors/failures * [2593] OB History Message column name set to Status * [2590] OB History selection criteria fixed (component) * [2594] OB History selection criteria fixed (status) * [2589] OB History selection criteria fixed (site) * [2587] OB History browser layout same as all Phase 2 apps ========================================================================= * [1616] ObsBLock atatus events are captured in the OT (Service Mode) and P2PP Visitor mode. At the moment there are only visible from within the OT. Please see Nicks spec document on the Web. I will give a demo of the workflow tomorrow * [1740] Externalised execution time for VLT instruments. Put in infrastructure code so exectime is now called from a script. in a directory called exectime off the instrument package definiton. As FLAMES needs the exectime ob the BOB side it also recalculates the exectime when the OB is sent to BOB. For FLAMES the OB exectime is also stored in the acquisition template * [2563] NEW: changed ordering of columns in execution sequence. * [2565] NEW: changed Visiplot start time. * [2566] NEW: Visiplot: now ignores moon constraints when moon is below the horizon. * [2568] NEW: Configuration reports window is now larger. * [2237,2239] NEW: Applications and stored procedures can now support Observing Run descriptors A-Z. * [2294] NEW: Added support for ~ (tilde) in configuration files, meaning the user's home directory. * [2131] NEW: Applications now handle more gracefully database connection errors (time-outs, etc.) * [2470/DFS01312] Fixed bug: Refreshing the queue list was making selected entries disappear. * [2484/DFS01307] Fixed bug: OB status flag not updated after execution (fix already delivered in 2.5.4). * [2556] Fixed bug: OT execution sequence: selection was lost after moving several OBs at once. * [1733] Fixed bug: Execution time report: total was negative for large number of OBs. * [2005] Fixed bug: sometimes a Queue View was disappearing * [2436] Fixed bug: there was a display (regression) problem in QC grade field. * [2196] Fixed bug: in a database browser it was possible to select a sort criterion without selecting the corresponding column, leading to unexpected result sets. * [2154] Fixed bug: applications now report an error message if the database configuration file is missing. * [2039] Fixed bug: EVM Header and Footers were badly placed * [2075] Changed Linux runtime setup * [1932,2015]: Removed own implementation of JSpinner and multi-line text widgets, now using Java 1.4 native widgets. * [2065] Code cleanup: removed Eclipse compilation warnings. * [1894] Fixed bug: no more java.lang.reflect.InvocationTargetException messages. * [2508] Updated SQL documentation (file obrep2-create-tables.sql). ==> LIST AND ISSUE OF UPDATED DOCUMENTS: None. ==> ADDITIONAL COMMENTS: None. $Id: SEG-RELEASE-NOTES-ot,v 1.50 2004/12/16 13:10:44 tcanavan Exp $