FWWG

Tuesday 9 Oct 2007, 14:00 → 16:00 Europe/Zurich

14/4-002

Oliver's slides AlarmHelp.pdf AlarmHelp.ppt

Stefan's Slides fwwg_atlas_09102007.pdf fwwg_atlas_09102007.ppt

Present: Jim, Piotr, Oliver, Clara, Olivier, Stefan, Frank, Fernando, Bobby, Manuel, Francisca, Wayne 1) Alarm Handling Requests Clara had sent around a list of requests for features for alarm handling prior to the meeting. Oliver gave an overview of what was currently available in the JCOP Alarm screen and the ideas that had previously been developed for alarm help. He made some suggestions for improvements on this. Points raised: - Is there a mechanism to create the help files. Not yet. - Would be useful to be able to define a help file for a group of dp(e)s. - Would be nice to be able to have help files in pdf format. - Would be nice to be able to pass parameters with the url to a help file. - To access the help and other information via right-click and drop down menu. - Need to be able to create and modify help files easily - also update many help files with the same information, e.g. change name of contact. - Would be useful to be able to have links between help files. - It was suggested to have a database as the master of the information for the help files. However, the problem of having a dependency on an external system was raised. - Would be nice to have the help file based on the alias as well. - One should probably avoid having many open AESs as these put a significant load on the EV. Something to be investigated now that there are real large systems. His slides can be found here: http://indico.cern.ch/conferenceDisplay.py?confId=22406 Stefan presented the ATLAS modified version of the JCOP Alarm screen. He highlighted the changes that have been made and changes that ATLAS would still like to implement. His slides can be found here: http://indico.cern.ch/conferenceDisplay.py?confId=22406 Some of the enhancements require changes in the ETM code which will be a nightmare to maintain. Therefore, the strategy would be to agree on what enhancements to the JCOP AES are required and for Oliver to define which can be made without changing the ETM code and which would require a change to their code. CERN would then negotiate with ETM to have these made in the standard release of PVSS. Assuming that ETM agrees it is unlikely that they will make these changes within our required timescale and hence an intermediate solution is for CERN to make the changes and ask ETM to include them. Oliver will circulate a list of enhancement requests based on the LHCb document and Stefan's slides. Where possible he will already indicate which need changes to the ETM code and/or proposals for implementation.