-
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
add_noise_to_model includes Ecorr even if -pta flag is different from NANOGrav in timfile #44
Comments
This probably results from the fact that PINT Pal was originally developed with a narrow focus on the NANOGrav 15-year data set, where we always used ECORR. Some of us have been using it with IPTA data for Early DR3, but in the IPTA work we've been using a very different noise modeling setup that doesn't use |
@FrancescoIraci Have you had a chance to test this since the fix was merged? It's not in the PyPI version yet, and won't be until we release the new version, but you can get the latest changes either by cloning this repository and using
|
Hi @rossjjennings, I will probably be able to check that next week. Sorry for the delay |
Closing since this should be fixed by #45. |
In the notebook [https://github.com/nanograv/pint_pal/blob/main/nb_templates/process_v1.2.ipynb] I'm facing an issue with the function
nu.add_noise_to_model
: I'm running the noise analysis using the timfile attached, with flags -pta EPTA and -f ciao (dummy variable). Since -pta flag is different from NANOGrav, the ecorr parameter is not included in the noise modelling (only efac and equad). However, while calling nu.add_noise_to_model, it seems that an ecorr parameter must be added when performing non wide-band timing as in my case (I'm attaching the error).The error should come from lines 414-418 of https://github.com/nanograv/pint_pal/blob/main/src/pint_pal/noise_utils.py#L251 in which:
It could solved by adding the case of non-wide-band toas without writing ecorr parameter in the parfile.
toa.tim.txt
Parfile is:
parfile.txt
The text was updated successfully, but these errors were encountered: