-
Notifications
You must be signed in to change notification settings - Fork 21
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
Remove print message of H0 in picca_xcf #948
Labels
Comments
See the comments in PR #971. The value of H0 should be 100 since we are computing things in Mpc/h, so yes, I think we should remove the print to avoid confusion |
This is all very confusing. I thought we were using the same default cosmo
in all DESI papers! I don't see why would Picca ever use H_0=100 as
default, regardless of the units we use (km/s, Mpc or Mpc/h). Ignasi, maybe
you and Calum can explain this to me in person?
…On Wed, 19 Apr 2023, 10:57 Ignasi Pérez-Ràfols, ***@***.***> wrote:
See the comments in PR #971 <#971>.
The value of H0 should be 100 since we are computing things in Mpc/h, so
yes, I think we should remove the print to avoid confusion
—
Reply to this email directly, view it on GitHub
<#948 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA5RYRYWPCIL6XFSSGOF3Z3XB6SJJANCNFSM6AAAAAATEKBZBQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Avís -
Aviso - Legal Notice - (LOPD) - http://legal.ifae.es
<http://legal.ifae.es/>
|
To clarify my comment: when computing pixel pair separations from angles /
redshifts in picca_cf you don't need to use H_0, the only thing that
matters is Omega_m (in a flat LCDM, otherwise you also need Omega_k or
Omega_Lambda). Unless if you compute the correlations in Mpc, buy that's a
different discussion.
You need to specify other cosmological parameters at the fitting level, but
I believe this is not what you are discussing now.
Andreu
…On Wed, 19 Apr 2023, 11:21 Andreu Font Ribera, ***@***.***> wrote:
This is all very confusing. I thought we were using the same default cosmo
in all DESI papers! I don't see why would Picca ever use H_0=100 as
default, regardless of the units we use (km/s, Mpc or Mpc/h). Ignasi, maybe
you and Calum can explain this to me in person?
On Wed, 19 Apr 2023, 10:57 Ignasi Pérez-Ràfols, ***@***.***>
wrote:
> See the comments in PR #971 <#971>.
> The value of H0 should be 100 since we are computing things in Mpc/h, so
> yes, I think we should remove the print to avoid confusion
>
> —
> Reply to this email directly, view it on GitHub
> <#948 (comment)>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AA5RYRYWPCIL6XFSSGOF3Z3XB6SJJANCNFSM6AAAAAATEKBZBQ>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
--
Avís -
Aviso - Legal Notice - (LOPD) - http://legal.ifae.es
<http://legal.ifae.es/>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I just noticed a message of H0=100, what is at least confusing. I believe H0 is not used in picca_xcf, but if we use it we should use a more standard value.
The text was updated successfully, but these errors were encountered: