Update on ongoing CO Actions
AB-CO-Technical Committee, 24th August 2006
30 last TCs (Jan 05)…
summary following discussion and comments from many CO colleagues…
updated current status…
http://ab-co-tech-committee.web.cern.ch/ab-co-tech-committee/
1
Action ID1 – TC78
 System: LASER
 Deliverable: Interface for the introduction of power converter data into
LASER
 Section / Person: Katarina, Stephen
 Status / Comments: Done, used successfully during Short Circuit
AB-CO-Technical Committee, 24th August 2006
Tests of HWC
Everything OK!
In the FCR…
Robin’s slide from CO summary for HCC meeting
2
Action ID2 – TC82
 System: Vacuum - Cryogenics
 Deliverable: Verify the required cable installations for signal exchange
(+ eventual SW link)
 Section / Person: Philippe, P.Cruikshank
 Status / Comments: PLC-PLC connection established via HW links
AB-CO-Technical Committee, 24th August 2006
(for exchange of CRYO_OK, VAC_OK), additional data exchange on
PVSS level
3
Action ID3 – TC82
 System: Converter Controls
 Deliverable: Implement DB retrieval of WorldFIP addresses for PC
controls
 Section / Person: Raymond, Stephen, Pascal
 Status / Comments: DB Interface works, but on each occasion errors
AB-CO-Technical Committee, 24th August 2006
have been discovered at a late stage (takes 4 days/area) - Robin will
keep an eye on this in the future
4
Action ID4 – TC82
 System: Measurement DB client API
 Deliverable: Investigate the possibility to decrease the logging
frequency if required (due to e.g. storage limitations)
 Section / Person: Marine, Ronny
 Status / Comments: Has become void - Marine takes the full advantage of
the Measurement Service which copes with the requested frequencies (6 sec
AB-CO-Technical Committee, 24th August 2006
for SPS, 0.5s for HWC). The transfer from Measurement to Logging is fully
implemented by Chris and is driven by configurable conditions.
5
Action ID5 – TC87
 System: BCTs in Booster
 Deliverable: Validation of application software after move to FESA
 Section / Person: Eugenia, Marc
 Status / Comments:
AB-CO-Technical Committee, 24th August 2006
– For Booster: XMotif Working sets and Booster Vistar work OK
– The ISOLDE applications do not work as they are still based on the old
ASC layer which accesses the old Directory services. These applications
belong to Operators. We are in the middle of changing the most critical
ones to use JAPC with the help of Eric Roux. AP will decide with Michael
Benedikt how and when to change the rest of the non-critical applications.
6
Action ID6 – TC88
 System: TED, Beam Stoppers
 Deliverable: Migration of ATB equipment (namely TEDs and beam
stoppers) to FESA
 Section / Person: Bertrand
 Status / Comments: After discussions with A. Masi it was decided that ATB
equipment will remain on legacy system for 2006 (provided that porting of the
AB-CO-Technical Committee, 24th August 2006
local SW onto XP works satisfactorily) – But for 2007….?
7
Action ID7 – TC89
 System: REX power converters
 Deliverable: Application software for new power converters in REX –
commitment of CO for 2006 or not?
 Section / Person: CO, OP
 Status / Comments: Nikolai: OP has finally accepted responsibility for the
application software and provided all applications necessary for the REX
AB-CO-Technical Committee, 24th August 2006
2006 startup. Stephen: OK for PO, maybe some follow-up for 2007
REX-ISOLDE…
8
Action ID8 – TC89
 System: PPM copy
 Deliverable: Deploy PPM copy for timing libraries
 Section / Person: Ioan
 Status / Comments: "ppm copy" for LTIM got delayed because of its low
AB-CO-Technical Committee, 24th August 2006
priority. Operators are currently able to achieve the same results using
archives and references. Nevertheless it is very likely to be available in the
near future, say for the start-up of LEIR, since an upgrade of its deployed
FESA classes is being done anyhow - mainly FESA version upgrades.
9
Action ID9 & 11 – TC90 & 91
 System: Post Mortem
 Deliverable: Propose formats for the preparation of the PM native data on
the client side + Further investigate and understand the data conversion
process from PM raw data into SDDS; if required, endorse other strategy
 Section / Person: Nikolai, Adriaan, Robin
xml
AB-CO-Technical Committee, 24th August 2006
Various buffers from clients
Current (used by PC, QPS)
bin
USER
xml definition
from Greg
Converter
SDDS
PM System
– More freedom for clients, but specific converters (even within same system)
– Already operational for PC and QPS, but slow due to parsing of xml
– SDDS conversion lengthy due to repetition of data (e.g. signal names…)
10
Action ID9 & 11 – TC90 & 91
– New proposal for more restrictive data preparation on client side
– Backward compatible, faster, but imposes limitations on clients
– Generic conversion process
– First prototype version released by Nikolai and presented in PM meeting; interest
from BI, RF, RADMON, BT
– One of the next TCs? - Ideas for Mini-Workshop in October to collect user feedback,
get their agreement and define how to go on after HWC (in discussion….)
AB-CO-Technical Committee, 24th August 2006
xml
Current (used by PC, QPS)
bin
Converter
SDDS
Generic structure
Graphs
New proposal
(for e.g. BI, RF, RADMON,..)
bin
PM Data
Object
Generic
Converter
USER
Tables
Data Viewer
PM System
SDDS
Logging,
Alarms
11
Action ID10 – TC90
 System: Naming, QAP
 Deliverable: Coherency of Naming scheme with Alarm service and
FESA devices and properties
 Section / Person: Marc, Ronny, Katarina, Niall
 Status / Comments: Ronny triggered some first e-mail exchange beg 06, receiving
AB-CO-Technical Committee, 24th August 2006
strong opinions and requests for flexibility in this SW area. On a case by case basis,
this has been done so far with BT, BI and ATB , but the link is still very loose…. ->
Pushes Problem down the line towards Logging where the naming scheme has been
enforced
 Replacement of current LASER archive is ongoing, expected in few weeks; agreement
that DM and LASER team will incite the equipment group as client of LASER and/or
Logging, that the LHC QAP naming schema is followed.
12
Action ID12 – TC91
 System: CNIC and HWC
 Deliverable: Hardware commissioning activities to use NICEFC and
LinuxFC
 Section / Person: Robin, Pierre
AB-CO-Technical Committee, 24th August 2006
 Status / Comments: First tests not very successful (UA83), initially small problems
with installations. Outstanding issues are the difficulties to support the roaming profile
of opera especially when accessing via the terminal server dedicated to HWC. There
are also frequent difficulties configuring the screens of FCR systems for both windows
and Linux. Introduction of CMF has improved the situation a lot, a specific login for
HWC will be discussed upon Pierre's return.
13
Action ID13 – TC92
 System: MCS (priority of this system has been confirmed at Chamonix 06)
 Deliverable: Put in place a small CO team to participate to the design and development
of the 'Management of critical settings (MCS)‘
AB-CO-Technical Committee, 24th August 2006
 Section / Person: Bertrand, Verena
 Status / Comments: Parts of the MCS implementation will be done within the frame
work of LSA defining a new settings type, "critical setting". Maciej and Anthony have
implemented and tested a mock-up version of the communication between a dummy
FESA server for a device with critical settings and a JAVA application (public key
authentication). The next big steps is to implement the investigated algorithms into LSA
and to prototype the authentication and authorization (along with role based access)
on the application side.
Trim
MCS
SW intlk
Setting
Front-end
Measure Interlock
setting
HW limit
Comparison process
HW intlk
14
Action ID14 & 15 – TC93
 System: FESA
 Deliverable: Discussions with OP to develop and validate the concept of
multiplexing and persistency in FESA – Implement most urgent improvements
and bug fixes into V2.7 for startup 06
 Section / Person: FE, OP
 Status / Comments: Bertrand organised two meetings with Mike, Jorg,
AB-CO-Technical Committee, 24th August 2006
Rende and Michael, outcome presented in TC95
15
Action ID16 – TC94
 System: Controls for Cryogenics
 Deliverable: Discuss the transfer and integration of the configuration
data and the generation scripts for device instantiation and PVSS into
the Oracle DB of DM
 Section / Person: Philippe, Ronny
 Status / Comments: First coffee discussion between Ronny and
AB-CO-Technical Committee, 24th August 2006
Philippe. Ronny will contact Philippe again to seriously discuss this
issue.
16
Action ID19 – TC99 & 100
 System: SIS
 Deliverable: Discuss a possible alignment of the SIS to a more
standard CO platform
 Section / Person: Claude-Henri, Vito, Jorg
AB-CO-Technical Committee, 24th August 2006
 Status / Comments:
– Jorg: Timing cards are needed for flexibility (all events and
telegrams available). The timing distribution over the network is
not reliable enough (has been tested but was very bad). Ever
since the system is running well, so why change? The orbit
feedback will require an equivalent configuration.
– Claude Henri: Replacement with a standard FE + appropriate
watchdogs should be possible ?
17
Action ID18 & 20 – TC99 & 101
 System: CO exploitation – Piquet service
 Deliverable: Discussion between FE / MI / IS and HT section in order
to agree on a common proposal for exploitation
 Section / Person: Bertrand, Bruno, Philippe, Marc, Javier
 Status / Comments: Discussion taken place on 9th of June, outcome
AB-CO-Technical Committee, 24th August 2006
presented in TC101
 System: Reorganization of Piquet service
 Deliverable: Prepare a proposal to CO3 for the new organization of
the CO piquet and a re-discussion of responsibility sharing in
between CO and EQ groups
 Section / Person: Hermann, Claude-Henri
 Status / Comments: no news yet…
18
Action ID21-24 – TC102
 System: Collimation project
 Deliverables:
AB-CO-Technical Committee, 24th August 2006
– Organize meetings inside AB-CO to come to a conclusion on the future
support of the PXI systems and by end of August organize a decision
making meeting with the collimation project.
– If the current FESA release cannot fulfill the requirements of the
collimator project, such additional features should be formulated
together with Michel and will have to be considered for an upcoming
FESA release.
• Comment received from Maciej and Marc – awaiting Hermann’s
comments
– Formulate together with the collimator project (R.Assmann) the
requirements for LHC Logging (frequency rates, data volume, etc..)
• Ronny has sent an invitation for a meeting - awaiting Ralph’s return
– Evaluate a detailed planning for the SPS tests and present the
resources needed to the CO-SLM before mid September 2006.
19
Action ID25 – TC103
 System: LASER - MUGEFs
 Deliverable: Evaluate current process (using obsolete SW von Claudio
Arimatea) for Alarms from MUGEFs / ROCS
 Section / Person: Jorg, Rudiger, Marc, Michel
AB-CO-Technical Committee, 24th August 2006
 Status / Comments:
– Proposal of Jorg an Rudiger: The functionality of this Nodal program
should be taken over by the SIS (currently only surveying some less
critical converters…). In this case the software interlock system would not
necessarily create a beam dump, but provide an alarm. Since this is not
high priority, this could possibly be done for next year.
– Michel: Proposal to investigate at a way to implement some form of
current survey in the rocs mugef on a cycle by cycle basis and to report
this. May have some implications that should be studied and discussed in
a larger audience.
20
Action ID26&27 – TC103
 System: LASER
 Deliverables:
– Document for implementation possibilities and improvements of the
LASER-FESA interface
AB-CO-Technical Committee, 24th August 2006
– Prepare a proposal for the replacement of ANS in collaboration with TI
21
…that’s it….
 System: Summary
 Deliverable: Review of latest CO Actions
 Section / Person: All
 Status / Comments:
AB-CO-Technical Committee, 24th August 2006
X 10
X 3 (not including the 2 latest TC’s)
X 4 (not including the 2 latest TC’s)
X0
22