Page History
...
For examples that load a predefined graph (.fc file, for "flow chart") you should see a window like this, while examples with no .fc file will have an empty area in the upper right:
Loading Data in AMI
There are three different ways to load data in AMI, either through using the gui, providing a json file, or by passing command line arguments. The different methods are described below.
Command Line Configuration
Given a psana experiment and run number the xtc2 files can be loaded using the following syntax:
| Code Block |
|---|
ami-local psana://exp=tstx00417,run=82 |
A more complex example that loads a saved flowchart, sets the "heartbeat" interval (-b) to 1 (defaults to 10) and fetches events from disk at 1Hz ("-f interval", defaults to as fast as possible) is:
| Code Block |
|---|
ami-local -l spike.fc -b 1 -f interval=1 psana://exp=rixdaq18,run=18 |
The "-f init_time=NN" (where "NN" is a number of seconds) can also be important. It tells the data reading to wait and give the analysis side of ami a chance to startup. This is necessary because the data reading portion starts immediately and can drop events, which is what ami needs to do when running in realtime (to ensure that it is only looking at recent data).
Loading Data through the GUI
The first option is to run ami-local without any flags. Once the main window appears, click the Configure button and the window in the image above will appear. From there hdf5 files or xtc2 files can be loaded by clicking on Add. Only one type of file may be loaded at a time, either hdf5 or xtc2, but multiple files can be loaded. AMI will loop through all the events in each file in the order they are loaded. The different options are explained below.
Note: If a source is configured through the gui configuration window, the source configuration will be saved with the graph and can be automatically reloaded by running ami-local -l <graph.fc>
JSON Configuration File
| Code Block |
|---|
{
"interval": 0.01,
"init_time": 0.5,
"repeat": true,
"files": ["run22.h5"]
} |
...
Configuration Flags
...
These flags can be passed to the source using any of the three methods above, the gui configuration window, a json file, or using the -f command line flag. To specify multiple flags using the command line pass -f multiple times. For example:
| Code Block |
|---|
ami-local -f interval=1 psana://exp=tmoc00118,run=4,dir=/ffb01/data/tmo/tmoc00118/xtc/ |
Reporting AMI Issues
Users are encouraged to submit AMI bug reports, feature requests, and questions through github issues: https://github.com/slac-lcls/ami/issues
If appropriate, please include an experiment, run number, and example graph so AMI can be run in off-line mode to reproduce issues.
Simple Introductory Example
...
| Code Block |
|---|
ami-local -e test -l /reg/g/psdm/tutorials/ami2/random/export.fc random:///reg/g/psdm/tutorials/ami2/random/worker.json |
Loading Data in AMI
There are three different ways to load data in AMI, either through using the gui, providing a json file, or by passing command line arguments. The different methods are described below.
Command Line Configuration
Given a psana experiment and run number the xtc2 files can be loaded using the following syntax:
| Code Block |
|---|
ami-local psana://exp=tstx00417,run=82 |
A more complex example that loads a saved flowchart, sets the "heartbeat" interval (-b) to 1 (defaults to 10) and fetches events from disk at 1Hz ("-f interval", defaults to as fast as possible) is:
| Code Block |
|---|
ami-local -l spike.fc -b 1 -f interval=1 psana://exp=rixdaq18,run=18 |
The "-f init_time=NN" (where "NN" is a number of seconds) can also be important. It tells the data reading to wait and give the analysis side of ami a chance to startup. This is necessary because the data reading portion starts immediately and can drop events, which is what ami needs to do when running in realtime (to ensure that it is only looking at recent data).
Loading Data through the GUI
The first option is to run ami-local without any flags. Once the main window appears, click the Configure button and the window in the image above will appear. From there hdf5 files or xtc2 files can be loaded by clicking on Add. Only one type of file may be loaded at a time, either hdf5 or xtc2, but multiple files can be loaded. AMI will loop through all the events in each file in the order they are loaded. The different options are explained below.
Note: If a source is configured through the gui configuration window, the source configuration will be saved with the graph and can be automatically reloaded by running ami-local -l <graph.fc>
JSON Configuration File
| Code Block |
|---|
{
"interval": 0.01,
"init_time": 0.5,
"repeat": true,
"files": ["run22.h5"]
} |
Additionally a JSON file containing a source configuration may be provided. A URI to the file where the prefix contains the source type must be passed to AMI. For example to load the above file run ami-local hdf5:///worker.json to use the psana source run ami-local psana:///worker.json.
Configuration Flags
| Flag | Description |
|---|---|
| interval | Time in seconds to sleep between events |
| init_time | Time in seconds to sleep before emitting the first event |
| repeat | Loop over files/events after reaching end |
| files | Comma separated list of files to load (either xtc2 or hdf5) |
These flags can be passed to the source using any of the three methods above, the gui configuration window, a json file, or using the -f command line flag. To specify multiple flags using the command line pass -f multiple times. For example:
| Code Block |
|---|
ami-local -f interval=1 psana://exp=tmoc00118,run=4,dir=/ffb01/data/tmo/tmoc00118/xtc/ |
Reporting AMI Issues
Users are encouraged to submit AMI bug reports, feature requests, and questions through github issues: https://github.com/slac-lcls/ami/issues
If appropriate, please include an experiment, run number, and example graph so AMI can be run in off-line mode to reproduce issues.
Screenshots
From the first user experiment of 2020:
...
Overview
Content Tools