BLM interface to MPS 
 
The only point of disagreement between the BLM group and MPS is in the responsability for the masking 
 of induced beam losses: LOLA and TDS activity, presence of wire scanners 
 
A new meeting with BLM and timing people will be held to come to a solution. 
 
Questions to be exposed in the meeting: 
- Is there a beam pickup in the machine that gives information about bunch pattern in the accelerator 
 to correlate with the provided timing? 
- Is the timing system aware of the presence of wire scanner activity? 
- How much effort is involved in: 
    - getting timing info in the BLMs 
    - masking BLM alarms in the MPS 
   
 
Sharing of documentation: 
 
- The regular bi-weekly meetings will be held on Thursdays at 10:30.  They will be handled via Indico 
 in following location (for the moment): 
Indico->XFEL->WP28 
 
- Report of incidences, minutes of meetings and documents will be kept in the MPS logbook: 
http://ttfinfo.desy.de/MPSelog/index.jsp 
 
- Common editing should be also handled through the logbook, taking care that the editor gets the 
 latest copy of the document to proceed with new updates (send email around??) 
In the meantime we could try the new tool suported by DESY: OwnCloud 
 
- For code sharing, Sven is already using DESY SVN 
 
- Final documents should go to EDMS 
 
    A meeting should be held to figure out how to communicate between MPS and timing system 
 
 
 Is everybody providing RS422 signals to MPS?