Page tree


General Concept

A large number of parameters which are essential for ALL Experiments is continuously saved (pulse energy, arrival time, Beamline settings ...) in the PHOTONDIAGNOSTIC FLASH DAQ system.
Other experiment related information is ONLY saved by the users ON DEMAND in the FLASH DAQ system. To record this type of data we have 3 User DAQs at FLASH1 (FLASH1_USER1,FLASH1_USER2 and FLASH1_USER3) and one at FLASH 2 (FLASH2_USER1)
How to save this experiment related "User-Data" will be explained briefly in this page:


Taking User data: Starting and stopping runs (Users)

In order to save the experiment related data from ADCs, Images, delayline detectors etc. the User DAQ has to be started to record the experiment data. The options which data can be saved, have to be discussed way before the beamtime. For regular beamtime operation the DAQ also was setup by experts before the beamtime. If things do not look like described here look in the troubleshooting section below.


DAQ control panel

To get to the User DAQ control one has to go to Experiment control -> User DAQ tab -> FLxUSERy DAQ CTRL
jddd_DAQ-control-manual-how_to_get.png

The following window opens. Here the User DAQ can be started and stopped as well as the incoming data can be visualized, information about data rates and saved properties is presented as well as the panel is automatically printed in to the logbook:

jddd_DAQ-control-manual2.png



  • By pressing the start and stop button, besides sending the commands to the DAQ the button prints the panel to the respective beamline / experiments logbook. Here you can later on keep track of the runs. Links to the Beamline logbooks can be found here (DESY internal link)
  • After starting, the stop button appears only after saving abut 200 shots to prevent too early stopping which may disturb the DAQ.
  • Each run has a unique run number. This number is needed to retrieve the data later on. So it is important to keep track which number is associated to what experimental parameters. Note that the run numbers are used by all FLASH DAQs (currently about 10). It might thus well be, that two consecutive runs from you do have run numbers which are spaced by more than one if another DAQ has been started in-between ...


Checklist for proper saving of the data

  • Check that some 20 seconds after starting a run the DAQ control shows that the internal checks did not show errors -> the DAQ traffic light is green (... still there may be undetected problems !!!)
  • The number of shots has to count up with 10 Hz
  • The data rate has to be the same as for the other runs with the same settings (one may click on the number to open a window with the history of the data rate to compare)
  • The file size of the file in which the data is written has to increase with the same speed as for the other runs with the same settings
  • check the data shown in the DAQ monitor.
    • are all required channels shown ?
    • is the range set correctly ?
    • does the ADC trace, image ... look as expected ?
    • are the images, ADC traces ... UPDATING ? (depending on the setting typically the display update is about 1 Hz)
  • Are the selected channels checked with the offline monitor (lower part of the DAQ control) saved with ~ 100 % for fast - 10 Hz- properties (and about 10-20 % for slow values saved only ~1 per second)
  • Is the time shown in the offline monitor the actual time? (Otherwise it did not read the current files and shows old data !)
  • And finally the ultimate check is using the DAQ Data GUI to look at the saved data - this should be done once in a while to be sure that the data is saved correctly

If not all points of the list are o.k. there may be some problem with the writing of the data. Look to the troubleshooting section and / or talk to beamline stuff.


More infos on the tools to check the proper saving of the data


DAQ monitor

The DAQ monitor shows a predefined selection of parameters as they are received in the DAQ before writing to a file. Here one can check if the desired data arrives in the DAQ and if the ranges are set correctly (e.g. sufficient acquisition time). The parameters to look at are defined before the beamtime with the local contact / DAQ group (details see below)


Offline DAQ monitor

This tool looks if a predefined selection of parameters is saved in the raw file. When a raw.-file reached its maximum size ( ~ 1 GB) it is closed and a new file is opened. Once closed, the Offline DAQ monitor reads the file and checks if there are entris for the selected parameters. It shows the fraction of events containing data. For “fast” data (data written with 10 Hz and bunch ID synchronous like images, ADC traces) this should be close to 100%. For “slow” data (saved about every second e.g. pressures , temperatures...) this is about 10-20%. However it is to note that this program just check if there is anything saved. It does not check if it is the proper data.


DAQ Data GUI

To ultimately check if the correct data is saved one can use the DAQ data GUI to look at the saved raw. files.

DAQgui1.jpg DAQgui2.jpg daqgui3.png

The DAQ Data GUI is a general tool to select and visualise data that was saved in the DAQ . It has in addition simple analysis options like histogram, mean, min or max values as function of time etc. Also correlations between different parameters can be analyzed in the tool. More details can be found How to Use the FLASH DAQ Data GUI? and here (DAQdataGUI link collection)

The tool (separate Java program) can be started DAQdataGUI or in the DAQ control panel ( lower right) on your local (Desy) PC. In some cases the access via Windows does not work. An option which should always work is to log onto flashlxuser1 or flashlxuser2 and start DAQdataGUI from the command line.



To access the desired data one has to:

  • enter the run number of the run you want to look at at Run
  • select your DAQ in the Experiment drop down menu: FLASHy_USERx
  • press get Channels/Files
  • browse through the data tree and select your important parameters and drag them with the mouse in the selected window. The list of important parameters should have been defined before the experiment with the FLASH stuff together. This list can also be found in the offline monitor (lower part of DAQ control) )
  • press Start Display to open a new window with your data. In case it was a long run and / or a large amount of data per shot one can limit the number of shown events to a fraction: Events -> Reading Options -> Event Interval provides the option to show only every n th dataset.


How to get the data out for analysis (short summary)

The DAQdataGui is a powerful tool to visualize the saved data and to do very preliminary analysis. however for more detailed analysis the data has to be read into analysis programs ( matlab, python, Origin ...) here are different options one can use (what option is the best and how to set it up has to be discussed before hand with the FLASH DAQ experts ...)

  • The FLASH DAQ system records the data in binary " .raw " files.
    • reading the data via Matlab works not for all data types equally well and needs precise knowledge of the desired Parameters (useful to have a quick look / preliminary analysis on few parameters).
    • Examples how to read from .raw files can also be found in the user code collection
    • Note that the raw data is only accessible from certain computers within the DESY network and thus not very handy for offline analysis later on ...


  • To ease the data analysis we IN ADDITION provide ON REQUEST the data from the FLASH DAQ as HDF5 format
    • ONLINE HDF5s: To make efficient use of the HDF5 files for analysis during the beamtime and afterwards we provide a very useful tool (Beamtime Daq Access). Using this tool (working for Python and Matlab) one can get the data of parameters per run or for specific bunch ID intervals etc. without having to care from which subset of HDF5 files the data is read ...
    • Summary HDF5 files include complete runs. They will be put after the beamtime on the gpfs storage and are available from computers within DESY (for registered Beamtime participants) and also access
    • Intro to the HDF5 structure used at FLASH. This contains also a list of the most used Parameters saved at FLASH for analysis - including the HDF5 names, DOOCS and DAQ names ...
    • Short examples and user provided examples on how to read HDF5 in Matlab

The HDF5 files (online and summary) are saved in the "gpfs" system . it can be accessed from Windows and Linux computers at DESY by the persons ( logins) which are registered for the beamtime in DOOR ( functional accounts

The path to your data is structured the following way:

  • /asap3/flash/gpfs/ beamline used / year /data/ Beamtime application number /raw/hdf/ (the Beamtime application number can be fund in the pdf schedule sent around by Rolf ...)
  • as example: /asap3/flash/gpfs/bl2/2017/data/11003163/raw/hdf/

More details and links can be found in the User overview.




Setting up the DAQ - DAQ Run Control GUI (local contacts, FLASH stuff)

This section is intended for the local contacts / FLASH staff to set up the DAQ according to the needs of users before the beamtime. For troubleshooting this may also be helpful for users ...


Configuring the DAQ


RCGUI_2.jpg

Using the jddd DAQ control panel one can start and stop runs but in order to configure the DAQ which data to save one has to use a a separate *DAQ run control * java application. Since it needs write access to DOOCS internal file systems, which can not be made available elsewhere one has to start the system on our DOOCS control computers flashlxuser1.desy.de or flashlxuser2.desy.de.
Log in with the beamline account (bl1user, bl2user, ..., fl24user...) either via X-Win32 from windows or via ssh from Linux machines.
Once logged in to flashlxuser1 or flashlxuser2 the DAQ run control can be started. Depending on the DAQ you want to use the commands are:


Unix commandDAQ
RCGUIFL1USER1FLASH1_USER1 DAQ
RCGUIFL1USER2FLASH1_USER2 DAQ
RCGUIFL1USER3FLASH1_USER3 DAQ
RCGUIFL2USER1FLASH2_USER1 DAQ

Which DAQ to use is decided by the FLASH DAQ team according to the beamtime schedule.


RCGUI_properties.jpg


Using the Add and Rem(ove) buttons one can move the desired "subsystems" in the included side - meaning that they are saved. The "subsystems" contain typically several DOOCS parameters. E.g. EXPERIMENT_MHZ_ADC_BL1 contains all relevant DOOCS properties of the 4 MHZ ADC channels available at BL1. To get a detailled information about the saved parameters one can have a look to the "Show Properties in Subsystems" button . In addition, a list of all possible subsystems and their description can be found here.


Configuring the DAQ monitor

The DAQ monitor ( and the Offline monitor) can be confgured using DAQdataGUI.
Load a test run containing all relavant propoerties. Select all properties you want to monitor. Use Tools -> Channels to DAQMonitor and choose your DAQ. This sends a list with the selected properties to the DAQ monitor of your system.
daq_monitor_config.png



Start and Stop a run

In order to "activate" and test your configuration you have to start a run with the new configuration. NOTE: Whenever the configuration was changed with the RCGUI the new run HAS to be started with the RCGUI (starting with the jddd DAQ panel would only start the last configuration that has been running before !!!


To START a run - meaning starting to save the experiment related data - one has to press the "start" button in the Run Control GUI. This opens a confirmation window asking if you really want to start the run ("in default mode"). Press yes. Now it takes about 20 seconds for the system to start up and start recording data. Indication is the "Run Control: RUN" and "DAQ: RUN" greenish indicators on the upper left side of the run control.

To STOP a run one has to press the "stop" button. This opens a window for comments. This contains already the actual Experiment name by default. Please leave this information in. Add a comment for your run. This comment will be printed into the logbook and can later on be used to identify individual runs ... note you are required to type in something otherwise the run will not stop.

The stopping also needs about 20 seconds.*_IT IS IMPORTANT_ not to start and stop the DAQ while it is still ramping up or down. So please wait before restarting the DAQ.*

After the run use the DAQ data GUI to check if the data intended is saved properly.




Load/Save the configuration


whitelist.jpg

Once a list of subsystems is defined and tested this parameter combination should then be saved in a so-called white list. By loading this white list one can then easily configure the DAQ after changes / restarts ... to the initially defined settings to save the correct data.
The whitelist can be saved/loaded with the Run Control GUI by: File -> Group White List -> Save/Load. Note, while the top left rectangle's background of time and date is yellow, don't try any further controls of the GUI, you might confuse the program. It is busy reading the configuration from the run control database. The background changes back to grey when it has finished.

The filename convention for the White Lists are arranged in the way:
DAQ name - Date of creation - name of the PI / Experiment - optional comment on the type of data

The whitelists are stored in separate folders for each beamline.




Assigning the DAQ to the beamline in jddd

To assign which DAQ is used at what beamline one has to use the dropdown menu in the parameter monitor. In each Beamline overview tab (BL1,2,3) there is a button (upper right) that starts the parameter monitor panel. In the upper middle is a DAQ field in which the appropriate DAQ can be assigned to the Beamline.





Setting the logbook to print in / putting the Whitelist name in jddd

The jddd DAQ Control should be set up that it prints by default the relevant run information in the logbook associated to your beamline Logbooks

Define logbook / and whitelist for display in the jddd DAQ control (jddd otherwise does not "know" which White list was used ... this has to be put in by hand ...up to now)
setting_parameters.jpg





In case something goes wrong: Troubleshooting


No START or STOP buttons are visible in the DAQ control panel

* The jddd GUI only shows the Start and stop bunnon if the DAQ is in the "Idle" state. sometimes the DAQ "just" gets stuck in the stopping phase. Then stopping again or starting form the not "Idle" state can help. For this goto the "Advanced" tab of the jddd DAQ control . there the START and STOP buttons are always available ... independent of the state of the DAQ. If this does not help you may have to restart the DAQ ...


The DAQ does not start a run


  • Mainly the DAQ works fine but one of the properties that should be saved is not available or somehow corrupted. There the RC logfile helps (see below) to determine where to localize the problem. The pragmatic way is to exclude the subsystems which may contain the properties with problems. Thus exclude the "critical" subsystems. Start a run. If this works, include one by one the excluded subsystems and start runs. That way one should find out which subsystem causes the problem. Now one can investigate this one in more detail. Is the property available in DOOCS? Does it update? maybe restart the server providing the property ...



Data seems not properly saved


RC_logfile.jpg When checking the saved run with the DAQdataGUI it may happen that the property shows up in the data tree but no events are saved. Then (most likely) something is wrong with the sending of the data.

  • A very helpful tool is the RC logfile. in the RCGUI on the lower right side there is a button to start an editor with the log file. besides lots of standard entries there is usually also a hint on where to find the problem ...
  • check if the device is working properly. Is it connected? Can you see data in jddd / DOOCS ? . If not you have to fix the DOOCS part ... DAQ can only save what is properly implemented in DOOCS.
  • If camera images are not properly saved ( e.g. only "0"s in the image matrix or the DAQ sender can not be switched to "on") a restart of the camera server usually helps.
  • Sometimes also a restart of the DAQ (see below) helps ... This however is more the case if the DAQ does not start at all or saves no data at all ...
  • in several cases the reason is a configuration problem of the server. Then 2 servers are sending on the same "address". Then one property usually is saved without loss while the second one is only saved once in a while ( 1-5%). Here the server has to be fixed. As fast cure one can only exclude the less important subsystem and save the more important properly ...




Restarting the DAQ


  • If the RCGUI does not respond (and also the clock display does not count up) one has to restart the GUI. Usually the DAQ is not affected by the RCGUI hang up ...


  • Generally there 3 ways to "restart" the DAQ
    • 1. The least interferring way is the "all to INITIALIZE" that tries to reset the DAQ processes ... helps for simple "hickups"
    • 2. The "re-start DAQ" really reboots the whole DAQ process. The settings still should be as before ... this is the "Usual" restart
    • 3. In very hard and severe cases there is the ultimate restart button: "re-start DAQ (no RCSHM)"



*Here in more detail:*


  • if the DAQ gets stuck in the starting or stopping procedure one can try to initialize the DAQ or in the worst case restart it.
    • to be able to restart the DAQ one has to run jddd on the flashlxuser1 or flashlxuser2 (up to now (Aug 2018) the restat on our consoles (cons0...12) is NOT possible yet frown ) : log in at one of these machines with your beamline account (e.g. bl1user or fl24user). Start jddd with the jFLASH command. Click on "Photons" -> Experimental Hall "Photons main panel"
    • The DAQ "expert" panel can be reached from the User DAQ control panel.
      DAQ_expert.jpg



    • Then you see the following "DAQ expert panel":
    • first one may try the "all to INITIALIZE" button. it starts a script window and asks for the passwd (the beamline accounts (blxuser) should have the according rights. vuvfuser has it for sure. The script sets all subcomponents to initialize. It is helpful if one subcomponent got stuck.


UserDAQ_status.jpg


  • If this does not help you have to "re-start DAQ". This completely restarts all processes and takes a while. A script window appears and shows what steps are actually done. At the end is sais: "Cleanup finished".
    DAQ_restart_msg.jpg


  • For the "re-start DAQ" the DAQ should come up in the same state as before. Meaning that the subsystems (ADCs, cameras ..) are still loaded and displayed. If this is not the case you can try to load your white list and start a new run. If the data is saved correctly you are done.


  • IF the DAQ still does not work properly the final option is the: "re-start DAQ (no RCSHM)". This button does the same as the "re-start DAQ" but the Run Controller shared memory is not re-stored. It means that after the DAQ is back no run configuration is selected.
    • in the jddd control the list of subsystems sais "empty"
    • in the RCGUI in the lower part it sais "RUN mode is not set"
      restart_RCM_no_runmode.jpg


    • one has to go to the "Run Modes" tab and select the run mode FLASH1_EXP by clicking on it !
      runmode_set.jpg
    • then one has to go back to the Subsystems . now all subsystems are included.
    • finally you have to select your White list and start a run ...



  • If there are still components not working after the "re-start DAQ (no RCSHM)" you have to call the photon coordinator (4455) and pray ...




Some more details for experts ...


Re-read the data base

On flashlxuser1 or 2 start RCGUIFL1USER1 or appropriate to the DAQ you want to reconfigure. Select the tab "Run Modes". To then reload or re-init the run control database you need the expert menu entry:

Options -> "Show Expert Menu"

Then you go to "Expert" -> "Run Control Commands" -> "Remove SHM" (occasionally twice).

After you see a message in the RCGUI messages window that the SHM was removed you do:

"expert" -> "Run Control Commands" -> "Re-init SHM"

Now close the RCGUI and start it again. Switch to the tab "subsystems", wait for the subsystems to be reloaded and load the whitelist you want to use.

  • No labels