This page is inteded to gather questions around the Pattern Concept that need clarifiaction

If non-multiplexed devices do not receive a Process Key / BeamProcess ID ...
  • ... how can you correlate LSA Settings with Acquisition values?
  • ... , if values are archived how can you correlate archived values with LSA Settings?

If a device hast to measures in a beamprocess where it not has settings (e.g. continuous) ...
  • ... how can you correlate LSA Settings with Acquisition values?
  • ... , if values are archived how can you correlate archived values with LSA Settings?

If you have non-multiplexed devices in an injection chain, ...
  • ..., do you still want to prepare different settings for these devices (e.g. at Cryring, if a source changes, do you want to prepare already settings for the new source in LSA).
    • If Yes: This is currently not possible in LSA, non-mux settings are also non-mux in LSA and can not have different values. They exist only once for the whole LSA system.

Applications using beamprocess for context selection, ...
  • ..., how do they have to deal with acquisitions
    • belonging to non-multiplexed devices
    • if the setvalue was set in another beamprocess than the currently selected beamprocess
Topic revision: r4 - 04 Nov 2015, RaphaelMueller
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback