Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HEATES requests #293

Open
ggggggggg opened this issue Jun 26, 2024 · 0 comments
Open

HEATES requests #293

ggggggggg opened this issue Jun 26, 2024 · 0 comments

Comments

@ggggggggg
Copy link
Collaborator

From their June 26 update:

  • 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant