PSRCHIVE Pulsar Data Archival & Analysis / Bugs / #464 T-scrunching with pam introduces spike into profile

T-scrunching with pam introduces spike into profile

#464 T-scrunching with pam introduces spike into profile

Milestone: next release

Status: open

Owner: nobody

Labels: None

Priority: 5

Updated: 2022-06-27

Created: 2022-06-13

Creator: William Fiore

Private: No

When T-scrunching a file with pam -T, the resulting pulse profile sometimes has as a spike at a particular pulse phase, even though there is no such spike in any sub-integrations prior to scrunching, and this spike is not present when viewed with pav -DT.

2 Attachments

Screen Shot 2022-04-06 at 15.56.34.png

Screen Shot 2022-04-06 at 15.57.05.png

Discussion

Paul Demorest - 2022-06-13

This sounds very similar to issue #446, which was fixed a while back. What version of psrchive are you using?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

William Fiore - 2022-06-13

I'm working on a GBO machine, and it seems the PSRCHIVE version is still back in 2020. I'll ask that it be updated and make sure the bug's not happening anymore. Sorry for the possible duplicate report!

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

William Fiore - 2022-06-27

This was fixed by updating the PSRCHIVE version.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

T-scrunching with pam introduces spike into profile

Group

Searches

Help

#464 T-scrunching with pam introduces spike into profile

Discussion