-
Notifications
You must be signed in to change notification settings - Fork 18
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
FOM Behaviour #29
Comments
Are you using |
Er probably not sorry; does tc.compute_scores just need jax-cosmo=True or something? |
yes, essentially :-) |
Yes, it seems that this was the issue. We are using jax-cosmo now. Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dear @joezuntz and @EiffL. We found out that the resulting FOM_3x2 can be very different in multiple trainings.
For instance, if we use the RF example w/ 5% for training (100 times - 5 bins) we have found in the validation
Thus, one can find 10^4 as well as 6*10^4 using the same algorithm.
while the SNR_3x2 have variations lowers than 0.6 :
`
If, instead of using RF we add the same the redshifts in the correct bin for the validation sample we find (5 bins) FOM_3x2 lower than 3x10^4, depending upon some selection. Thus we are getting Higher values than using the truth table.
Does this make sense for you?
The text was updated successfully, but these errors were encountered: