... | ... | @@ -39,7 +39,20 @@ estimate how much work remains to be done for a beamline a list must be complete |
|
|
talk about Beamline restart (therefore the scope will be larger than Bliss, but it will cover Bliss and the conversion of
|
|
|
beamlines). ACTION TO REMAIN OPEN. DATE TO BE CHANGED TO 20/12/2019
|
|
|
|
|
|
*Action 3* P Berkvens confirmed during the Beamline Restart Management day how access to EXPH will work. For clarity **VEIJO will provide the data that will be pasted here**
|
|
|
*Action 3* P Berkvens confirmed during the Beamline Restart Management day how access to EXPH will work. For clarity this is what he said:
|
|
|
|
|
|
During commissioning: <br/>Maintain non-exposure policy, but officially relax dose constraint from 4 hours to 1 month:
|
|
|
• 2 mSv per 4 hours -> 80 mSv per month.
|
|
|
• No longer possible to guarantee non exposure of short term visitors:
|
|
|
-> access to experimental hall and technical zone limited to ESRF and CRG staff, long term
|
|
|
visitors and long term contractors (maintenance company, cabling contractor, …).
|
|
|
Access restrictions do not concern Chartreuse and Belledonne halls.
|
|
|
|
|
|
End of 2019: <br/>
|
|
|
based on the results of the 1st month of commissioning, safety will decide whether
|
|
|
we maintain the monthly dose limit or whether, from beginning of January 2020 onward, we
|
|
|
will officially return to the 2 mSv per 4 hours limit, in which case we remove the access
|
|
|
restrictions for ExpH and Technical Zone.
|
|
|
|
|
|
*Action 4* Jens explained that he met with Joel Chavanne, Olivier Mathon and Peter Glatzel early October.
|
|
|
The approach to be followed would be to test on one undulator in ID26 before the summer, to which Harald
|
... | ... | @@ -81,19 +94,27 @@ Matias explained that Bliss has been using Packages for a while and that by the |
|
|
Jean wondered if it is known already what functionality won't be provided for the start and Laurent said this will be clear once we agree on the stable version that we keep. Matias explained that his team is working on the Data Policy, Logbook, scans and that if we could wait a bit more the stable version will be better. Jens requested a stable version by the end of November as the teams doing the conversion of the beamlines cannot wait more. **NEW ACTION: List of what is included and what not** possible in the stable Bliss version. That could take the form of a MosCow list (Must be included, Should be included, Could be Included and Won't be included).
|
|
|
|
|
|
**STATUS OF CORE DEVELOPMENT**
|
|
|
|
|
|
Andy presented a table showed already the day before durig the BL restart day, saying that most things will be ready for the stable version. Veijo asked if anything is a problem and Andy replied that HKL won't be ready.
|
|
|
Harald asked about Archiving and Backups. Andy explained that this part belongs to TID and that Rudolf will present at the
|
|
|
next EDMB the changes behind the scenes. Andy stressed the fact that backups and archiving is not part of Bliss but TID.
|
|
|
Manfred said that if GPFS performance is going to change that will affect them as users. Andy explained that the servers will be load balancing and bandwith will be shared, so there will be an impact. That's why a buffer system will be tested. That could affect fast detectors, analysis and visualisation.
|
|
|
|
|
|
**AOB**
|
|
|
|
|
|
Veijo explained what reamains to be done at ID31. He requires Continuous Scans and would like to have a software solution
|
|
|
for the _Master Energy_. He also would like to be able to import/load OH session into a global session, however he doesn't see any showstoppers.
|
|
|
for the _Master Energy_. He also would like to be able to import/load OH session into a global session, however he doesn't see any showstoppers. Jens asked who is interested in the _Master Energy_ and the response was that everyone with more than one monochromator (so pretty much all beamlines except the spectroscopy ones). Andy suggested to do a pseudomotor for energy while a final solution is put in place.
|
|
|
|
|
|
Harald asked Veijo how long did it take to get used to the new system: Veijo said it was fast and easy to use Bliss. Macros and loops took a little bit more of time to get used to them, but that for users it won't make a difference. He struggled to find the XAML configuration files as it was not obvious where they are stored. How to debug and log for problems is not always evident. Laurant then pointed out that beamline technicians may have the same problems and that they will require training.
|
|
|
Harald understood that it is therefore possible to get up to speed rather quickly. Manfred then pointed out that yes as long as you know Python basics. Andy said that a Python course would be very beneficial and that is something that beamline staff can start doing now. Manfred also said that at the beginning of the documentation it should be clear what content is where.
|
|
|
|
|
|
Laurent asked whether config editing through the web application should be removed as it is not a priority. Matias explained that the web application is working again since yesterday. Andy said that it looks reasonable given the amount of work left to reduce the scope. Laurent said that it should be ok for people to edit the config file directly without using the web application. Andy confirmed that the web application for editing the configuration is a nice to have but not a priority and that Stuart Fisher will look at that later on in 2020.
|
|
|
|
|
|
Manfred said that now in Python 3 it is possible to have software working with different versions at the same time. He said whether this could be used in Bliss to get new features while having a "frozen" stable version. Andy and Laurent said that this does not look like a good idea. Matias said that they will focus on ensuring backward compatibility.
|
|
|
|
|
|
**NEW ACTION**: Stuart Fisher to talk about GUIs in the next BSC meeting
|
|
|
**NEW ACTION**: Harald would like a quick summary of CRG status. Jens said that French CRGs want to migrate to BLISS one instrument per Beamline. In any case a CRG status report regarding Bliss will be presented in the next BSC meeting.
|
|
|
|
|
|
|
|
|
Minutes from previous meetings:
|
|
|
* [4th BSC 13/09/2019](https://gitlab.esrf.fr/bliss/bliss/wikis/bsc_meeting_20190905)
|
... | ... | |