You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

Please note, this page is a work in progress, viewing has been restricted to staff with editing privileges and should be removed when it is ready for public viewing.

 

Overview

The LCLS provides a number of tools that allow users and staff to participate remotely in experiments while access to the site is restricted due to COVID-19 safety protocols.  These were demonstrated in the LCLS User Town Hall held on July 23, 2020, and available at this link.  This page will provide an overview of tools for external (incl. users) and internal (staff only) use, and provides links to pages with additional details such as installation and usage guides, as well as minimum system requirements.

Public Tools for Users

The LCLS provides a number of internally developed and 3rd party tools to share information before, during, and following an experiment.  At all times during the process, the spokesperson and collaborators should continue to communicate directly with their assigned LCLS Point of Contact, and use the standard tools such as the Experiment Questionnaire and Electronic Log Book of Experiment, "eLog", (links below).

In addition to these historical tools, the LCLS provides video-conferencing capabilities through zoom, and high definition, read-only, screen sharing through video streaming.

Bandwidth Speed-test

 

Minimum System Requirements

Video-conferencing

The LCLS will provide real-time interactive video conferencing on the zoom platform.  The meeting ID and password will be provided within the eLog for each group, to maintain the privacy of each collaboration.

 

 

Description, Stanford site license, passwords, distribution (via eLog or email), live plots of AMI (camera images, histograms, etc.)

 

Link to download and install

Video Streaming

Each hutch control room will be equipped with a streaming host.

  • Each of the other computers in the control room will have one of their monitors duplicated on the streaming host.
  • The shared monitors will appear on the streaming host as webcams
  • The shared monitor webcams can be used in Zoom, Slack, and other applications just like other webcams
  • The shared monitor webcams can also be opened for viewing on the streaming host desktop view
  • The streaming host desktop view will be made available as an embedded, non-interactive video stream via pswww

This allows viewers to get information from each hutch control room computer with minimal additional load on the computers or the operator(s).

Software Applications Provided by LCLS

 

Internal Tools

Internally, we are using or developing additional remote access tools.  They are described here for information purposes.  If you believe your experiment would benefit from the use of these tools, contact your LCLS experiment Point of Contact.

Interactive chat software

Stanford University maintains an enterprise license to the slack chat application.  Guests from other facilities can be added to specific channels.

 

Remote Access Software

NoMachineTo support remote operations a dedicated NoMachine Terminal Server has been deployed: psnxopr.slac.stanford.edu.

Then, NoMachine Enterprise Desktop will be installed on all DAQ workstations. 

The following link provides guidelines to configure NoMachine Client: Remote Visualization.

To access the DAQ workstation, use the following steps:

  1. Access or create a new desktop session. 
  2. Select the NoMachine icon on the upper right to get a drop down menu, then select the control room workstation:
  3. A new window requesting login access will appear
  4. After login, the operator will have to grant authorization for view-only mode on a selected or default monitor.
  5. As the remote user, any display can be accessed
    1. After access has been confirmed by the operator, select the menu option
    2. On the menu screen, select change monitor icon
    3. Then select the monitor to visualize its displayed content or All to see all monitors. (This setup has only 3 monitors)

 

AR Headsets

LCLS has acquired a number of augmented reality headsets to allow staff technicians and engineers to co-view a workspace while respecting social-distancing protocols.

Hardware:  https://www.realwear.com/products/hmt-1/

Software:   https://www.amaxperteye.com/

We are using Space1 as the software platform for communicating with the AR headset.

Login here to call the headset and use the communication tools: 

http://portal.space1.it/

Login for operator:

Help1@slac.stanford.edu    Help1!

Login for headset (Virtual collaboration – Space1)

User3@slac.stanford.edu    User3!

Within the call you can,

  • share screen with the headset
  • control the headset (camera zoom, flashlight, volume, etc)
  • send files, pictures, 3D models
  • draw on their camera feed and draw on a whiteboard
  • chat via text

We were able to establish calls from psconsole to the headset over EDUROAM wifi in the FEH.

Demo video recorded from psconsole screen (no sound):

realware.mp4

Robotic assistants

We have purchased two remote presence robots to assist remote viewing and debugging of instrumentation at beam height where fixed overhead web cameras may have difficulty looking while an area is locked during beam delivery.  https://www.doublerobotics.com/double3.html. At present these

Current features:
  1. Driving and viewing
    1. User joins call with a web browser on PC, Mac, Linux, iPhone, Android, or mobile app on iOS with their unique login credentials
    2. Authorize audio and video (required)
    3. Receive video and audio feed from the Double 3, the robot has pan, and zoom options
    4. Take photo of current view
    5. Drive with point-and-click on ground or by navigating with arrow keys
    6. Built in collision avoidance works very well
    7. Built in stabilization, does not knock over
    8. Able to go over cables on the ground
    9. Auto-docking

  2. Screen sharing
    1. Share specific windows, e.g. interconnect or cable drawings, grafana pages, terminal output


    2.  Share web window interactively, allow user at robot to navigate the webpage you share


  3. Administrative controls: fleet usage
    1. Manage user access, allow multiple users with different usage privilege levels


    2. Schedule users to avoid access conflict


    3. Monitor calls, usage, drive time

 

Developer features:

One of the units is enabled in developer mode, this allows development work with the base Unix environment that the robot is running on, as well as full access to the programming of the robot drive, and detectors.

 

Potential development features include:

  1. Enable Zoom conferencing
  2. Video recording
  3. Direct controls interface
  • No labels