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
The following runs seem to be problematic in cuts computation. Example error looks like below. [45501, 44405, 46721, 47083, 47287, 47296, 47298, 46731, 45437, 45451, 045462, 045501]
More details you can find logs at /project/lgrandi/xenonnt/data_management_reprocessing/job_logs. Already used --notlazy in straxer, and I am requiring single core at this point.
The text was updated successfully, but these errors were encountered:
I highly suspect that the reason for this error is deep in the algebra library of different nodes. Similar thing https://xenonnt.slack.com/archives/C016DM0JPK9/p1683044901706209 has been observed before. So if we re-process these three plugins on the same node, like xenon1t, we will get no error.
The quick fix would be just re-reprocess them. But for a long-term solution, we should test the output on different nodes, even on the same node multiple times to test the randomness of this phenomenon.
The following runs seem to be problematic in cuts computation. Example error looks like below.
[45501, 44405, 46721, 47083, 47287, 47296, 47298, 46731, 45437, 45451, 045462, 045501]
More details you can find logs at
/project/lgrandi/xenonnt/data_management_reprocessing/job_logs
. Already used--notlazy
instraxer
, and I am requiring single core at this point.The text was updated successfully, but these errors were encountered: