1 / 7

ALMA Integrated Computing Team Coordination & Planning Meeting #3 Socorro, 17-19 June 2014

ALMA Integrated Computing Team Coordination & Planning Meeting #3 Socorro, 17-19 June 2014. OMC Issues Maurizio Chavan, ESO. Two OMC Issues. CorrGUIX (ICT-543) OMC disintegrations. CorrGUIX. A spin-off of the HCI initiative Brought to the state of useful prototype by Marcus

afric
Download Presentation

ALMA Integrated Computing Team Coordination & Planning Meeting #3 Socorro, 17-19 June 2014

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ALMA Integrated Computing TeamCoordination & Planning Meeting #3 Socorro, 17-19 June 2014 OMC Issues Maurizio Chavan, ESO

  2. Two OMC Issues • CorrGUIX (ICT-543) • OMC disintegrations

  3. CorrGUIX • A spin-off of the HCI initiative • Brought to the state of useful prototype by Marcus • Well received by DSO (Denis) • Last version: July 2013 • Some feedback/change requests, August 2013 • Dormant since then • We don't think it's within the OMC scope

  4. OMC Disintegration • The Ten Commandments of Alma Software Development – Joe Schwarz, 2005 • The eleventh (unwritten) was: Thou shalt have no other GUIs before me (the OMC) • Since then, several plug-ins have gone feral • Shift Log Tool – large panel • JLog – demanding in terms of resources • new QuickLook – also resource intensive

  5. OMC pros and cons OMC has architectural issues & looks "stale" OMC is one of the many tools on the console Original OMC concept had a rationale • consistent appearance • all-in-one-place • customizable OMC offers synchro & comms facilities

  6. We went slowly from the 11thcommandment to "anarchy" Do we have a problem with that?

  7. Do we have a problem? • NO, every Lead chooses whether to integrate or not • YES, we let e.g. the Subsystem Scientist decide • YES, we remove the structural & appearance issues • …we try to, anyway

More Related