FWWG

Wednesday 14 May 2008, 14:00 → 16:00 Europe/Zurich

14/4-002

Slides FWWG_FSM.pdf FWWG_FSM.ppt

Participants: Clara, Fernando, Oliver, Francisca, Manuel, Jim, Alba, Carmen, Bobby, Frank, Giacinto, Peter, Stefan, Wayne 1) FSM - Clara Clara presented new features of the FSM. Her slides can be found in InDiCo: http://indico.cern.ch/conferenceDisplay.py?confId=33972 The following points were raised: - What is the State of a node when all children are Excluded? Not well defined but difficult to determine correctly. - Could the message indicating which nodes in the tree were not Taken be in a table to allow to scroll through them when there are a lot? Clara will look at this. - Could there be access control on the ForcedTake? Yes. - To avoid taking by mistake one should use the LockOut. - Clara confirmed that it is now possible to restart FSM nodes on remote machines. - The AbortCommand currently only works for a CU. Clara could not say exactly what was killed and will check. - Peter asked about the speed of displaying the view of the LHCb FSM tree. Clare noted that it only builds two levels and that the other levels are only built when a user navigates downwards. - Would it be possible to have the command/exclude options from the FSM Tree. No, too difficult. - Originally the functions in fwFsmUser.ctl were only called if the action is initiated by a user. Now, in recent versions, there are other functions which are called for each node during recursive tree actions. - If a node dies it is set to Manual. No user function is called when this happens. - The RestartAll only works within the tree from whose top node it is called. - The Generate and Handle Summary Alarms should take into account the users previous wishes, i.e. if a Summary Alarm, i.e. it should not overwrite the existing Summary Alarm - which it doesn't - nor created a Summary Alarm if not wished for. Clara agreed that she needed to take into account the value of the flag set in the project. - If Dist=0 is set for a manager that is only required to work with local data, then it does not load all dpIds from the distributed system. The following requests for new features were raised: - Possibility to have recipes of FSM modes, e.g. excluded, etc. This was requested by both ALICE and ATLAS. CMS did not see a need for this. It would be good to get a clear idea of the Use Cases. Clara could envision storing the Enable/Disable and LockOut states of the nodes but is this sufficient? - Instead of using the UI manager identification as the Owner use the PVSS logged in user in conjunction with the JCOP Access Control Component. Clara will provide a user function to allow each experiment to pass whatever it wants as Owner. However, she warned that one needed to be careful as the Owner is used in many places and should be unique. - Frank and Stefan noted that the lock symbol had become very complicated in the sense that it represented a lot of information and that there were many different representations. They asked whether it was not possible to provide more information to the user on the meaning of a particular representation. Clara will investigate. - There was a request to put SMI log messages into the Central Logging mechanism. Clara will discuss this with Boda. Frank requested that this should be structured, e.g. separate elements for date, object name and message string. - Stefan noted that when an SMI process freezes there are MS popups. Apparently these can be avoided by modifying some registry settings and maybe these could be CMF policies. To be investigated. - Could there be a restart FSM (node and/or tree) in the expert menu? Yes, Clara will implement this. 2) Possible Topics for Future Meetings The following installation and commissioning topics have not yet been covered: - Diagnostics tools. - Performance issues on large installations with Caen, Wiener, etc. - Messenger facility for information generated by external systems, e.g. FEC (use of the PVSS central logger?) Please let Wayne know which of these you would like to cover in the next FWWG meeting. Proposed date 28th May in 13/3-005.