CS Workshop, April 2014
The results of the workshop are available here
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 Institut for nuclear chemistry, Fritz Strassmann Weg 2 in 55128-Mainz
, on April 10th, 2014
, Thursday, 13:00 to 18:00 (evening: dinner) April 11th, 2014
, 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.
Friday only), YulinTian
Thursday, April 10, 2014
19:00 Dinner@ Eisgrub
Friday, April 11, 2014
Possible topics to discuss:
- Version Control with Git
- In the past we used a central subversion server for LabVIEW and related sources at GSI.
- It was also used by several colleagues not using the CS Framework.
- We created copies for each new LabVIEW Version and therefore discontinued the history.
- Due to messused of some users, the repository become very large.
- You need online connection to the central subversion server at GSI for commits.
- In order to clean up and to enable local commits I suggest to used Git in future.
- Distributed respositories with clear access permissions
- Local commits
- Easy branching
- Main Development
- Personnel developments
- Feature development
- Release Candidates
- Clean Release repository
- Distributed repositories.
- The developer may need to synchronize with several remote respositories and branches.
- Necessary discussion
- Splitting of the central respository in serveral project- or package-specific repositories
- Libraries, e.g. LVDImInterface, Instrument Driver etc.
- CS-Package A, B, C ...
- CS-Projects, e.g. ISOLTRAP, HITRAP, PHELIX, SHIPTRAP etc.
- Integration of repositories
submodule has some serious disadvantages
subtree would be the favorite Refer to manual, here and here
- Additional Features for the MM8-GUI
- PI-ICR: Needed? Possible at all?
- FT-ICR: Needed? For sure, but when? And how to implement it?
- Subcycles within measurement cycle (ISOLTRAP electrostatic trap)
- SWIFT support
- Migration of CS Systems
- Combination of CS & CS++ using DIM or Shared Variables
- 14 Apr 2014