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
Can we use “consecutive-number mode” for run number assignment? I think supporting this makes sense, it will be easier when we use dataframes for run info, as it will be easier to lookup runs in order and see dates than just in the file system.
For retrieval using grouptrigger in dastard, addition of primary and secondary flags, and a
mechanism in mass for interpreting them. I maintain that we should be able to find these based on framecount and don't need a trigger, but we should show them how.
Timing was addressed outside of mass with the following code to apply time correction.
Consider if it can be absorbed by either mass or dastard. (minor) Not enough info in the presentation to assess this.
Include multi-run analysis in mass software. This would be fixed by the dataframe switch.
The text was updated successfully, but these errors were encountered:
From their June 26 update:
mechanism in mass for interpreting them. I maintain that we should be able to find these based on framecount and don't need a trigger, but we should show them how.
Consider if it can be absorbed by either mass or dastard. (minor) Not enough info in the presentation to assess this.
The text was updated successfully, but these errors were encountered: