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.

Sign up for GitHub

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

Jump to bottom

"Could not find run number" error #43

Open
pdeperio opened this issue Nov 22, 2016 · 1 comment
Open

"Could not find run number" error #43

pdeperio opened this issue Nov 22, 2016 · 1 comment

Comments

@pdeperio
Copy link
Contributor

pdeperio commented Nov 22, 2016 •
edited
Loading

Seems to be a benign error running on MC (command, pax_version_policy = 'loose'):

Could not find run number for Xenon1T_TPC_Kr83m_96.000000_g4mc_NEST_Patch_pax, got exception <class 'IndexError'>: index 0 is out of bounds for axis 0 with size 0. Setting run number to 0.

Would be nice to suppress/fix this to clean up logs and facilitate (real) error searching.
@JelleAalbers
Copy link
Contributor

Yes, that's an expected message. Probably it would be best to add a dont_search_rundb option or something to suppress this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JelleAalbers @pdeperio