CS Workshop, March 2017
we, the experiment control system group
, would like to invite you to a workshop dedicated to the CS framework
. Please feel free to forward this information to other colleagues.
The main idea behind this workshop is to bring the users and developers of CS
together to discuss about the present status and future developments.
This workshop will take place at the University of Greifswald, Institut für Physik, Room A102, Felix-Hausdorff-Straße 6, 17489 Greifswald
, on March 2, 2017
, Thursday, 9:00 to 18:00 (evening: dinner) and March 3, 2017
, Friday, 09:00 to 12:00.
We could run a Adobe Connect Web-Meeting in parallel, so that people from anywhere could join the workshop remotely. If you are interested to join via Web-Meeting, please tell HolgerBrand
. We need some time to prepare. Especially we would need all talks in advance to upload them to the Webmeeting server.
It would be nice if you could provide us with some suggestions about the topics you would like to be informed about and and/or the topics you would like to discuss. Please let us know, if you intend to come to the workshop or not.
How to Register
There is no registration fee and there are two possibilities to register. Either
- edit this web page and add your name to the list of registered participants below, or
- send an e-mail to HolgerBrand or DennisNeidherr.
If you would like to participate, please register as soon as possible! If you register until the end of the first week of January 2017 we can take care of the Hotel reservation in Greifswald.
In Greifswald we are distributed over 3 different hotels:
Maybe it is a good idea to contribute to the list of feature requests
or bug reports
to enable us to derive an agenda.
This is a workshop: All attendees are cordially invited to contribute by presenting something.
Authors are responsible for the contents of their own contributions.
Please, respect all concerned copyrights!
Wednesday, March 1, 2017
19:00 Dinner@ Il Ponte
Thursday, March 2, 2017
19:00 Dinner@ Brasserie Hermann
Friday, March 3, 2017
Agenda Pre-Meeting @ GSI
Attention: You need your identity card available to get access to GSI.
This year we will have a small pre-meeting at GSI before our offical CS workshop in Greifswald. This meeting will be held at the ground floor of the "Guest House"
. Please note, there will be no agenda for it. The idea is to discuss and train the daily work with the CS or LabVIEW
in general (maybe CS++) depending on the needs of the attendees.
: Of course it is also possible to attend just this meeting in case that someone cannot go to Greifswald.
Tuesday, Februrary 28, 2017
, Main.RyanRingle, MaximeBrodeur
Possible topics to discuss:
- Future of MM
- Continue development based on C++, or new development from scratch based on LabVIEW or Python?
- We should agree on an Memorandum of Understanding after discussion by the end of the workshop!
- Discussion of DIM problems
- Status update from PHELIX, the (only) installation experiencing it?
- Did the shielding of exposed PCs help?
- Is the operating system the limit, maybe number of threads?
- What about the security issues, meaning causing DIM problems when installing SW and asked for administration credentials?
- Possibility fur detailed tests in summer this year during maintenance period?
- Migration from CS to CS++
- Pure Actor Framework or collaboration on common class libraries like CS++?
- How is willing to contribute?
- Major tasks to be addressed:
- Communication layer in distributed systems.
- VI-Scripting wizards to convert CS classes to CS++ classes. Seems feasible for CS device classes developed with respect to CS guidelines. GUIs are always special, as well as application layer classes.
- Getting started:
- CS++ classes could be wrapped in CS classes, e.g. has been done by Dennis with IMAQ/IMAQdx.
- Combine CS and CS++ applications.
- Which experiment is willing take the leadership?
- Collaboration in general
- Framework integration of new features, like specialized sequencer.
- Framework integration of new measurement methods.
- Exchange of experience, e.g training for newcomers or code/design reviews.
- Common source code version control system based on Git.
- Github as public repository server with issue tracker and wiki for documentation purpose.
- How to deal with private source code? For example patch third party code or code restricted by NDA. BitBucket? A GSI solution like Subversion is in progress, but can not be promised.
- Avoid disruption of programming language basis: LabVIEW, C++, Python, SPS, VHDL. We had very good reasons to go for LabVIEW. They are still valid from my (HB) point of view.
Results MM discussion:
- MM9 will be also used in the future to visualize the data and configure the main parts of the experimental cycle.
- To implement the new detection techniques as a first step the format of the data sent from LabVIEW to MM9 has to be fixed for each technique.
- Afterwards plots and additional configuration windows have to be added to MM9.
- LEBIT and TRIGA-TRAP are working on this. An analysis software is part of this effort.
- First step is try to get the most recent source code of the SHIPTRAP software to extract the file Format. Afterwards we will fix a file format and Ryan will include the new plots into MM9.
- First ISOLTRAP has to provide a CS class for their new detector. Maybe the sequencer has to be changed in order to work with such high repetition rates. Afterwards new (contour-) plot can be added to MM9. Dennis will check this once he visits CERN again.
- We will try to include the automatic optimization / cross check routines into the CS.
- CS collaboration advises to use LabVIEW for additional Software.
- 12 Dec 2016