- ICS maintenace: IT replaced the F5 switch, load balancer, on tuesday morning.
This work affected the ICS. There were 2 possible risks: the service
to search the interlock areas was interrupted and automated procedures
accessing the ICS could run into time-outs. From our point of view
this date was inappropriate.
The responsible IT staff members have been informed that
IT maintenance should be done in maintenace weeks of Petra and Flash.
If IT cannot wait for some reason, work should be scheduled
in Petra maintenance weeks. In any case FS-EC should be involved.
- P06, 'permission denied' on close: Jan, CSIRO, IT investigate. IT considers
this as a significant issue, should be fully understood.
- ZMX repair: typical problems:
- Firmware needs to be updated to version 0.98
- Firmware load get's stuck at 8%
- several hardware issues
ZE has a test setup, repairs the devices and returns them to Ruediger Nowak.
It is helpful, if a broken device is accompanied by an error description.
- P10 gpfs use case: data are analysed by maxwell nodes in the core gpfs system.
The results have to be made available to the ExpPCs.
Has been discussed with IT (not finished to far). Options to be considered:
- Use common, bl-user has read-only access.
- Use a DESY account on a ExpPc to transfer the data from core to scratch_bl.
- Possible new feature: start_beamtime makes files in the core readable for the
BL user.
- Online: 'move/adjust motName' bug repaired. The problem occured, if
'move/adjust' was invoked from the TkI widget.
- External channels (any tango attribute) can be added to the MG by the online.xml file: see Sardana documentation.
- bastion logins for BL accounts: when a user logins in to bastion with a BL account an email is
sent to the owner of the account. The account owner may request to disable this feature.
- SardanaMonitor:
- 1st point can be zero (slow motors, long move to first point)
- Cursor widget crashes.
Several tests have been made, no result. Need more details.
- P65: need to change the slew rate during move. Possible solution: Variable Velocity
Contouring feature of the OmsMaxV.
