1. JINR NICA beam transfer channels CS
32nd Tango Collaboration meeting
JINR NICA beam transfer channels CS
Matej Komel (Cosylab)
Alexey Tuzikov (JINR)
Evgeny Gorbachev (JINR)
Olivier Tasset-Maye (Sigmaphi)

3. Customers from Nearly All Major Labs Worldwide

4. „NICA Complex“ megaproject
Additional notes:
The main purpose of the booster is accumulation of 2*10e9 AU31+ ions and acceleration of heavy ion bunches to energy required for effective stripping.
The main purpose of the Nuclotron is acceleration to high energies (e.g. Au ions to 4.5GeV/u).
Existing facilities are Nuclotron and LU-20
NICA (Nuclotron-based Ion Collider fAcility) – designed to study properties of dense baryonic matter
Complex consists of 2 linear accelerators, 2 synchrotrons, 2 storage rings and 2 transport beam lines between the Nuclotron and the Collider
Commissioning planned to start in 2020

5. NICA beamline channels (Nuclotron-Collider beamline)
Magnetic subsystem:
- 27 dipole magnets
Beamline channels (or Nuclotron-Collider beamline) is intended for beam transportation from Nuclotron to Collider rings. It provides a beam transmission to both rings of the Collider and matching of beam parameters with lattice functions of Collider. Beam energy is varying from 1 GeV/u to 4.5 GeV/u.
Common part ~39m, north branch ~144m, south branch ~149m
3 subsystems – magnetic, vacuum, diagnostic
61 quadruople magnets and steerers

6. NICA beamline channels (Nuclotron-Collider beamline)
Vacuum subsystem:
- 12 gate valves
- 20 vacuum gauges
Common part ~39m, north branch ~144m, south branch ~149m
3 subsystems – magnetic, vacuum, diagnostic
- 50 ion and getter pumps

7. NICA beamline channels (Nuclotron-Collider beamline)
Diagnostics subsystem:
- 21 beam position monitors
- 4 fast current transformers
Common part ~39m, north branch ~144m, south branch ~149m
3 subsystems – magnetic, vacuum, diagnostic
- 8 beam loss monitors
- 12 beam profile monitors

8. The control system
Siemens PLC system (I/O signals handling; interlocking)
TANGO device servers (high-level CS)
Taurus (engineering screens; Vacuum GUI)

9. The control system – engineering screens
- SIP pumps controller screen
- NEG pumps controller screen

10. The control system – engineering screens
- Magnets PS screen
- High-level magnets screen

11. The control system – engineering screens
- Vacuum GUI

12. The control system - progress
High-level CS (Tango/Taurus) development to be finished in Aug 2018
75%
PLC development Sep-Dec 2018
95%
100% 0%
FAT in December 2018
100%
95%
90%
80%
Racks assembly&wiring in Feb-Mar 2019 0%
Installation & SAT planned towards the end of 2019

13. The TANGO/Taurus experience
Fast setup and ramp up
TangoBox helps a lot; installation from scratch is also simple (e.g. via apt in Ubuntu)
Good documentation
Active and helpful community (forums, github)
Very nice framework from SW programmers point of view (as opposed to using EPICS (EPICS DB, sequencers, etc..), in TANGO (almost) everything is done in code).

14. Issues/room for improvement (TANGO)
Support for structured data (e.g. like pvData in EPICS 4)
Performance (many device instances with lots of attributes severely hit the performance)
Currently no good Tango-OPCUA bridge existing

15. Issues/room for improvement (Taurus)
Spectrum attributes (or in general non-scalar attributes) support not perfect (
JDraw support has some issues:
Color support for non-DevState attribute items
Text labels are not always displayed as drawn in JDraw (vertical vs horizontal)
Few useful widgets are currently somewhat broken: e.g. TaurusValuesTable, TaurusGrid
useParentModel feature is not well supported (and might be removed altogether (
Performance – long startup time (gui thread is blocked while the widgets are being loaded)

16. Our involvement in the community
cppTango (#444): push_change_event() – events stop being issued after some time
In-depth analysis of the problem, suggested fix/workaround which was used at the end
Current status – fix commited and merged by bourtemb
Taurus (#660): TaurusValueComboBox does not change color
Pull request created and was merged
Taurus (#687): Fixing TaurusLed handling of spectrum attributes
Pull request created
Taurus(#648): taurusLabel.setModelIndex() not working
Taurus (#675): TaurusGrid seems to be broken
Taurus (#677): TaurusValuesTable locale (decimal delimiter) mixup
Taurus (#676): TaurusValuesTable cannot be used with „useParentModel“
Taurus (#720): taurusdesigned sometimes produces „----“ for taurusLabel text
Taurus (#732): TaurusCommandButton problem with useParentModel and tango device server not started when setting model
Taurus (#751): Support referencing to attribute slices in the model name
...

17. Thank YOU!
Matej Komel