Before beamtime Checklist

Version 9.1 by sndueste on 2023/09/06 15:48
Warning: For security reasons, the document is displayed in restricted mode as it is not the current version. There may be differences and errors due to this.

Pre and post beamtime questionnaire

Failed to execute the [velocity] macro. Cause: [The execution of the [velocity] script macro is not allowed. Check the rights of its last author or the parameters if it's rendered from another script.]. Click on this message for details.

Failed to execute the [velocity] macro. Cause: [The execution of the [velocity] script macro is not allowed. Check the rights of its last author or the parameters if it's rendered from another script.]. Click on this message for details.

User experience feedback form

Printable version

On-screen version

Questions to consider before the beamtime - the pre beamtime form helps discussing these questions

Weeks before the actual beamtime the Usergroup should think about the needs for the experiment and get in contact to the DAQ / IT group at FLASH and define several boundary conditions:

  • What kind of data you want to record in the FLASH DAQ?
    • Several options of the photon diagnostic are available which are NOT operated as standard (VLS, OPIS, ... see Photon Diag pages)http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif
    • What kind of ADC is the best one for you? Are amplifiers needed? what sample rate, how many channels ...
    • several types of cameras can be integrated in the FLASH DAQ system - talk to the experts (well in advance !) if you plan to use cameras.
    • For detector systems such as pnCCD imaging- detectors and ion/electron spectrometers available at the CAMP end-station please contact us to discuss your particular requirements (well in advance !)
  • Do you have own detectors to be recorded ?
    • It has to be checked how they can be stored on the FLASH data storage (gpfs)
    • They could probably be included in the FLASH DAQ system - this needs sufficient lead time. Talk several WEEKS before the beam time to the local contact / experts 
  • What parameters you need to monitor life during the beamtime?
    • how you plan to monitor the parameters in jddd or  Python  (if absolutely needed: Matlab, Labview) ?
    • do you need online treatment of data ( averaging, integration of peaks ...) ?
    • do you have to control Hardware from FLASH ( e.g. delaylines ...). Do you need scans with online display ? - IF the control has to be done for a NOT DESY computer ( not DESY/FLASH login) this requires special attention as well . It wirks but has to be set up and tested !!
  • data analysis needs
    • Do you need  HDF5 files for your (semi-online) analysis during the beamtime.
    • Which parameters do you need for your (semi-online) analysis ?
    • how do you want to do analyze your data ? Can we find scripts from other users serving most of your needs? explain the FAB framework that helps analyzing data in advance 
    • How much computational power will the analysis need (can we use the analysis servers at the beamline or do we have to use more powerful ressources) ?
  • Data access after the beamtime:
    • data recorded with the FLASH DAQ will have to be moved to a long time (tape) storage few month after the beamtime. During / shortly after the beamtime it has to be decided where to put the locally recorded data.