Page History
...
| Code Block |
|---|
[psana]
# list of file names
files = /reg/d/psdm/AMO/amo00000/xtc/e00-r0000-s00-c00.xtc \
/reg/d/psdm/AMO/amo00000/xtc/e00-r0000-s01-c00.xtc \
/reg/d/psdm/AMO/amo00000/xtc/e00-r0000-s02-c00.xtc
# list of modules, PrintSeparator and PrintEventId are from psana package
# and do not need package name
modules = PrintSeparator PrintEventId psana_examples.DumpAcqiris
|
User Modules Options
| Wiki Markup |
|---|
Options for user modules appear in the separate sections named after the modules. For example the module with name "TestPackage.ExampleModule" will read its options from the section {{\[TestPackage.ExampleModule\]}}. If the module name includes modifier after colon then it will try to find option value in the corresponding section first and if it does not exist there it will try to read option form section which does not have qualifier. In this way the modules can share common options. For example the module "TestPackage.ExampleModule:test" will try to read an option from {{\[TestPackage.ExampleModule:test\]}} section first and section {{\[TestPackage.ExampleModule\]}} after that. |
Here is an example of configuration for some fictional analysis job:
| Code Block |
|---|
[psana]
modules = TestPackage.Analysis:mode1 TestPackage.Analysis:mode2
[TestPackage.Analysis]
# these are common options for all TestPackage.Analysis modules,
# but instances can override then in their own sections
calib-mode = fancy
subpixel = off
threshold = 0.001
[TestPackage.Analysis:mode1]
# options specific to mode1 module
range-min = 0
range-max = 1000000
[TestPackage.Analysis:mode2]
# options specific to mode2 module
range-min = 1000
range-min = 10000
subpixel = on
|
Overview
Content Tools