Skip to content
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

Interpolation problem between orbit files from merge.py #29

Open
sguillot opened this issue Mar 27, 2018 · 2 comments
Open

Interpolation problem between orbit files from merge.py #29

sguillot opened this issue Mar 27, 2018 · 2 comments

Comments

@sguillot
Copy link
Collaborator

Following an email discussion with @paulray:

When calling pint.photonphase from merge.py, for a merged event file with a list of orbit files, there seems to be an interpolation problem with the orbit files. This gives different results than when the PULSE_PHASES are calculated on each individual ObsID event files.
This only happens when using merge.py independently on events files that do not have the PULSE_PHASE column. This does not happen when the options '--par parfile.par' and '--merge' are used in psrpipe.py.

@sguillot
Copy link
Collaborator Author

@paulray, this issue is related to the one you posted recently on the PINT GitHub repository, correct?
nanograv/PINT#434

@paulray
Copy link
Owner

paulray commented Sep 26, 2018

I'm not sure if this is the same issue. The interpolator problem should only affect a few photons that are at the edges of GTIs and not bracketed by orbit values. If this issue is more significant than that, let me know.

paulray pushed a commit that referenced this issue May 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants