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
_assert_equal_properties(data_input) #41
Comments
Yes, I implemented this additional check to be sure that the data is not corrupted. I believe all entries of a correlator should be defined on the same set of configurations in all practical scenarios (although that is not strictly necessary for the correct error propagation). Do you have any use cases in which you would want to initialize such a correlator? Also the json output for correlators strictly assumes that all non |
I could imagine someone measuring more configurations for one smearing level and still wanting to use the GEVP methods. Theoretically the new Obs can know, what configurations it was measured on (?) and be compatible. But i would not need this and if it is hard to implement, we can leave it as it is. |
I propose to leave the |
I noticed that the correlator__init__() method now requires the same number of deltas. (Is this true?)
Is there a reason for enforcing this?
The text was updated successfully, but these errors were encountered: