You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For high-rate beam tests with asynchronous data streams between devices we need a data format that supports time-stamp meta-information; furthermore, the new data format should not rely on the "event" number (determined by trigger ID) but needs to allow trigger-ID/event counting, time-stamps, time-stamp ranges or any mixture of these.
Implication: For the online monitoring/analysis, these data streams would have to be synchronized first.
These changes should not require modifications to existing producers as long as the old data-taking scheme is still allowed.
Opening of binary files in the old format is not required (but would be nice) -- clear identification of new files and warning of the user if file format is not supported is a must however
For high-rate beam tests with asynchronous data streams between devices we need a data format that supports time-stamp meta-information; furthermore, the new data format should not rely on the "event" number (determined by trigger ID) but needs to allow trigger-ID/event counting, time-stamps, time-stamp ranges or any mixture of these.
Implication: For the online monitoring/analysis, these data streams would have to be synchronized first.
The text was updated successfully, but these errors were encountered: