-
Notifications
You must be signed in to change notification settings - Fork 31
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
Amplitude estimation of Ramsey fringe #144
Comments
Hi Justin. I can't easily run your code because I don't know what to use as a) I tend to avoid
b) Yes, I would expect longer tails on the side away from 0.5 in both a bootstrap and a Bayesian posterior. I would call this hedging rather than bias. Tails near a hard boundaries in the low-to-mid data regimes are to be expected. Though with enough data you will be in central limit theorem territory and things will be symmetric about the true value. As an extreme example, suppose you flip a biased coin with unknown bias 100 times and get 100 heads. Assigning an estimate of p=1 is kind of crazy because it is very plausible that p=0.999, but an estimate p=1asserts you would be willing to bet everything that a tails will never happen. Therefore it is reasonable to have a posterior with a tail to the left of 1, which is exactly what you get if you use a uniform prior on p. |
Hi,
I am trying to modify the tutorial of simple_precession_estimation as in
https://github.com/QInfer/qinfer-examples/blob/master/simple_precession_estimation.ipynb
to estimate the amplitude of a Ramsey fringe. The model is set up to estimate two parameters, the amplitude and offset of the sigmal (signal = a * np.cos(true_omega * ts + phase) + offset) with omega and phase as fixed parameters.
I encoutnered two problems:
a. I used the method 'are_models_valid'of Model
to limit the range of parameters, which does not seem to take any effect and the algorithm will throw errors. I end up to limit the parameter range by using a post-selected distribution as the prior
Not sure if this is the proper way to use the package from the point of view of package designer.
b. With this modifications I could get the algorithm running. As the I run bootstrap on the model, the inferred amplitudes show bias towards smaller amplitude if the "true" amplitude is close to the maximum value 0.5. Is that the expected behavior? I expect the bayesian method to take this kind of bias out.
The full code can be found in this notebook https://github.com/Justin318/test_qinfer_share/blob/master/simple_est_amplitude.ipynb
Thanks for your time.
The text was updated successfully, but these errors were encountered: