ELOG SASE1 Status and SASE3 Readiness

Group Selection Page HELP DOC Controls Group Data Analysis Group ITDM WP76 DET Vacuum XRO EEE WP78 WP74 FXE SCS SPB MID HED SQS SXP Sample Environment Photon Commissioning Team Operation PSPO XO TS

Technical integration and coordination SASE1 Status and SASE3 Readiness

Joint Operation and Readiness Logbook, Contact: T.Haas, A. Violante, G. Wellenreuther, Page 21 of 30

Not logged in

List | Find | Login | Help

Full | Summary | Threaded | Hide attachments

597 Entries

Goto page Previous 1, 2, 3 ... 20, 21, 22 ... 28, 29, 30 Next

Online storage update on Monday 9th Oct

After today's discussion with WP75 group, we decided to postpone the update of the online storage to the next Monday 16th October.

Janusz Szuba wrote:

We would like to take the oportunity of the shutdown period and update the online storage next week on Monday 9th Oct. This will take approx. half a day. During that time the online storage will not be available on the online computing cluster as well as on pclayer servers used for DAQ. In the same way, the nfs export for data logger is also affected.

Regarding data collected on the online cluster, although it should not have any influence, but as a precautionary measures, please make sure that all relevant data from all past proposals are migrated to offline storage, which in practice means requesting migration via metadata catalog web interface. If there are still issues with particular runs not being able to be migrated, please contact ITDM.

regards,

Janusz

Office network in XTD10

Dear All,

In XTD10 there are now office network ports available in each rack. These can be used to connect your regular laptops with a network cable without special configuration and registration of your laptop.

The list of racks and corresponding port numbers is listed below. Please, note that in lead racks (3.4, 3.7, and 3.13) you need to plug the cable directly to the office switch port 24. This port is located in the bottom row, most to the right.

Rack3.1	116.732
Rack3.2	116.741
Rack3.3	116.755
Rack3.4	switch: SW-HH-AL-285 port: 24(last, bottom row)
Rack3.5	116.762
Rack3.6	116.877
Rack3.7	switch: SW-HH-AL-286 port 24 (last, bottom row)
Rack3.8	116.885
Rack3.9	116.891
Rack3.10	116.895
Rack3.11	116.903
Rack3.12	116.909
Rack3.13	Switch SW-HH-AL-287 port 24 (last, bottom row)
Rack3.14	117.021
Rack3.15	117.032

Dear all,

The OCD number for tonight (15/05) for the CAS group is 98053.

thanks

Dear all,

The OCD numbers for this weekend and today will be:

PLC Support: 9-8040 / 0151-68822383

DAQ Electronics (incl. timing, MicroTCA) Support: 9-8041 / 0151-68822386

Thank you.

Dear all,

The OCD AE numbers for the following days will be:

PLC support: 9-8040 / 0151-68822383

DAQ Electronics (incl. timing, MicroTCA) Support: 9-6941

If there are any change in the numbers, we will let you know.

Thank you.

Dear all,

The OCD AE numbers for the following days will be:

PLC support: 9-8040

DAQ Electronics (incl. timing, MicroTCA) Support: 9-8041

If there are any change in the numbers, we will let you know.

Thank you.

Dear all,

The service of On-call Duty will be available from AE group during weekend in this number: 6442

Please make a post with the OCD numbers from CAS, WP74 and WP73.

Thank you and bests.

No Restricted Areas for Radiation Commissioning

Desired parameters where reached for radiation measurments of the SPB OPT and SPB EXP hutches. Radiaiton could not be detected inside the hutch with the beam shutters open and beam verified hitting the target, therefore it was not deemed necessary to take radiation measurments outside the hutches. As a result there are no additional access restrictions in SASE 1.

No Radiation Measurements in SASE 1 This week

Do to repairs that need to be made with the cold compressor. We will be unable to perform Radiation Hutch Commissioning for SASE 1 this week. We will attempt to reschedule the Measurments for Thursday or Friday (10.08 or 11.08) of next week, depending on if it can be coordinated with all involved parties.

There is no restricted access to SASE 1 until then.

New Deployment of Karabo for the SASE1 control machines.

I will ramp down the system and bring it back up during the lunch break after installing the
tag 2.1.10.

To install a new version of Karabo use the script attached on your terminal

move your the karabo directory to a backup or remove it.

to backup:
$ mv ~/karabo ~/karabo.bkp

to remove:
$ rm -fr ~/karabo

then execute:
$ bash PATHTO/download.sh

Attachment 1: download.sh

#!/bin/bash

if [ -z ${outfilename} ]
then
    outfilename=.karabo.sh
fi
echo $outfilename
git clone https://xfel.redmine:K9Sss5CmWtQ_nbx3gyt2@git.xfel.eu/gitlab/Karabo/commissioning-guidelines .temp-commissioning --depth=1
cp -f .temp-commissioning/project_generation/install.sh .install.sh
rm -fr .temp-commissioning
. .install.sh
rm ${outfilename}
rm .install.sh

New Deployment of Karabo for the SASE1 control machines.

Alessandro Silenzi wrote:

I will ramp down the system and bring it back up during the lunch break after installing the
tag 2.1.10.

To install a new version of Karabo use the script attached on your terminal

move your the karabo directory to a backup or remove it.

to backup:
$ mv ~/karabo ~/karabo.bkp

to remove:
$ rm -fr ~/karabo

then execute:
$ bash PATHTO/download.sh

The system is up.

The users using virtual machines will encounter problems installing karabo 2.1.10 in the way that was described.
Further instructions will come later in the day

New Deployment of Karabo for the SASE1 control machines.

Alessandro Silenzi wrote:

I will ramp down the system and bring it back up during the lunch break after installing the
tag 2.1.10.

To install a new version of Karabo use the script attached on your terminal

move your the karabo directory to a backup or remove it.

to backup:
$ mv ~/karabo ~/karabo.bkp

to remove:
$ rm -fr ~/karabo

then execute:
$ bash PATHTO/download.sh

The system is up.

The users using virtual machines will encounter problems installing karabo 2.1.10 in the way that was described.
Further instructions will come later in the day

for Users with a VM:
- use the download script
- Remove the karabo directory:
$ rm -fr ~/karabo
- then execute:
$ bash PATHTO/download.sh

Sorry for the delayed instructions

Network upgrade /information and problem

The upgrade of the switches is finished to the extend that it allows Advanced Electronic group to work on KMono (Nerea is informed)

However, during the upgrade of the network one switch got stuck and this is the switch in XTD2 tunnel. The IP network in the XTD2 tunnel is not reachable at the moment (Beckhoff loops are fine) and we are going top the tunnel soon.

Network and servers maintenance

As discussed offline with NOC, Monday schedule was already fixed and not movable to Tuesday. Therefore, the network maintenance will take place on Monday 7:00 - 9:00.

During that time, no stable network is guaranteed.

After the network maintenance, the foreseen update and restart of all control server will take place, which take approx. ~2 hours. The exceptions are sase1 control servers and plc gateways as well as data logger and brokers and probably most importantly, exflgateway. These will be done after the work in sase1 (KMONO integration) is finished.

Called at 21.18 for SASE1_XTD2_IMGSR/MOTOR/Y being in error.

Solved by pressing 'Reset' button in Karabo GUI

Dear all,

The Motion loop is up and running again.

Thank you!

Dear all,

We will start with the Motion loop update. Will take us a little bit, around 3 hours, but I will let you know when it has finished.

Thank you,

Dear all,

The Motion loop is running again. We have included today the Mc2motor devices that were already before configured (FXE PBLMs and MCP), tomorrow we will include the rest of the PBLMs.

Right now is also into the loop the Hirex hardware in Rack 1.8 and the new crate of the Rack 1.18 for the temperature measurements.

Thank you,

Dear all,

Due to some hardware changes needed in Motion loop, we will last a little bit more in the Motion update. You will loose communication but I will come back when it is running again.

Thank you and sorry for inconvenience.

Dear all,

Motion loop is up and running again, now with all the PBLMs configured.

Thank you,

Goto page Previous 1, 2, 3 ... 20, 21, 22 ... 28, 29, 30 Next

ELOG V3.1.4-7c3fd00