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
This is a problem that I've seen for a very long time, but it's never a consistent behavior which is very confusing. Sometimes when I run locally a config file which is definitely tested and working well, the discriminator passes zero points and no track finding takes place. On several occasions I have run the exact same command, immediately afterward, and get normal results. Thus the problem is not reproducible as far as I can understand.
I don't know how to approach a solution, I don't know whether this is a problem which depends on the system, but I want to document it anyway. I can only guess that the root of the problem is a bad construction of the gain variation. I wonder if the gain variation has been known to sometimes give inconsistent results.
I suppose the upside is that all this really does is effectively discard some files when an analysis is run on a large set of data. In the grand scheme of bugs, that's not so bad.
The text was updated successfully, but these errors were encountered:
This is a problem that I've seen for a very long time, but it's never a consistent behavior which is very confusing. Sometimes when I run locally a config file which is definitely tested and working well, the discriminator passes zero points and no track finding takes place. On several occasions I have run the exact same command, immediately afterward, and get normal results. Thus the problem is not reproducible as far as I can understand.
I don't know how to approach a solution, I don't know whether this is a problem which depends on the system, but I want to document it anyway. I can only guess that the root of the problem is a bad construction of the gain variation. I wonder if the gain variation has been known to sometimes give inconsistent results.
I suppose the upside is that all this really does is effectively discard some files when an analysis is run on a large set of data. In the grand scheme of bugs, that's not so bad.
The text was updated successfully, but these errors were encountered: