John is making a good progress on the 'recovery procedure web page'. Please check it and send him recovery procedures. The URL is,
JC installed audio alarm for severe alarms for detectors. It makes bird chirping sound when activated. He also made a MCS binder and stored it on top of the VNODE1 screen for shift crews. SVX is coming along. They hope the system could be ready by early April. TOF system is also very close. TOF pc is back in counting room now according to request.
Steve Hahn reported an incident when PSM lost heartbeat. Shift crews found the Voltman with more than 10 windows opened and there was an error message box. Because the pc was locked the shift crew had to page Mark. He wanted to have passwords for all MCS pc's for shift crews. Pat pointed out that current policy is paging experts on those case instead. Someone proposed that we could provie an intermediate priviledged account to shift crews so they can turn off a few hot channels etc. We have not converged in this issue.
The muon scintillator group (Ivan Vila and Oleg and others) want a new pc. We are trying very hard not to increase number of pc's to maintain. Pat is going to have a meeting with them.
Blinking of the Muon system bar at the CDFHVSummary page sometimes means adjusting HV to compensate pressure.
Yeongdae said CMX files were corrupted a few days ago and he had to copy back from backup files. Following is the text of his transparency.
Hvmon Progress Report 1. Building Working Infra. Practically Done. Needed unexpected time for security implementation. Built virtual network using 1 to 5 virtual machines. 2. Hvmon Web Site for Software Development and Maintenance. Web server was fully configured. Web page is preparing ^Ö one more week for competition. 3. Simulator Design. Need to be delayed because of the maintenance issue. 4. Hvmon Maintenance Issue. Users need Confidence and Carefulness. User training is important ^Ö Web Site. Careless Use of Hvmon would be disastrous. Wrong configuration may cause permanent damage to SY127 or detectors 5. Software Improvement. Data integrity check is required before any change is applied. User should not be allowed to change system configurations like channel numbers, I/O address, etc.