Paul Demorest

Thanks Mike. It has been quite a long time since I looked at this stuff, but yes the idea of the "pointer_tracker" stuff in psrchive.i is to automatically create Reference::To instances for python variables when relevant. I think this should happen automatically for any class that inherits Reference::Able (including ProfileShiftFit), and we should not have to explicitly name all such classes (it's basically all of psrchive). This at least used to work, I guess we should look closely at those commits...

Hi Jacob, I think there is a simple setting in dspsr that can correct this sort of thing. Can you provide a sample command line, and ideally a small test data set, to check against?

Hi Ryan, you should submit this request at https://github.com/conda-forge/dspsr-feedstock The short answer is I briefly looked into it a few years ago and ended up not doing it so there may have been some problem. But it's probably worth revisiting.

Thanks for the quick fix, Willem. I can confirm that it fixes the issue on my system.

psrstat segfaults

psrstat segfaults

unable to change edit type of data after folded by dspsr

Hi Yixuan, I'm glad you sorted it out already. In case this wasn't clear, I think the issue arose because the source name in your VLA file is 3C286, which is in psrchive's built-in list of flux calibrator sources (in file $PSRCHIVE/share/fluxcal.on). So psrchive automatically assumes it is a FluxCal-on observation. If needed you can work around this most easily by changing the source name.