Hello. Not much to go on, but I'm pretty sure this is unrelated to this 2012 bug regarding telescope site codes.
Your bug seems to be tempo2 crashing when trying to make a predictor from your pulsar in dspsr. I would suggest to manually run the tempo2 command on your ephemeris (replace pulsar.par with your ephemeris) to see if any errors are thrown, and if that works ok, check the directories in /tmp to verify that the ephemeris and stuff there makes sense.
If you can't resolve the issue, this should at least help to see to see if it's a dspsr bug or a tempo2 bug, and you re-post this with more details in the tempo2 or dspsr bug tracker.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Fixed by Math: the Telescope extension was not properly initialized when site == '8' ... it is now set ... not sure why/how this worked before.
Is this error related?
$ dspsr -E 0950.eph -s -K -b 128 1141224136_ch133-156_0002.fits
dspsr: Loading ephemeris from 0950.eph
itoa_code no alias found for unknown
Error::stack
SystemCall::run
Error::FailedCall
Error::message
system ("tempo2 -npsr 1 -f pulsar.par -pred "MWA 57452.6025694444 57453.6025694444 169.600000000000023 200.319999999999993 12 2 3599.9999999999998" > stdout.txt 2> stderr.txt") failed:
returned error code 127
Hello. Not much to go on, but I'm pretty sure this is unrelated to this 2012 bug regarding telescope site codes.
Your bug seems to be tempo2 crashing when trying to make a predictor from your pulsar in dspsr. I would suggest to manually run the tempo2 command on your ephemeris (replace pulsar.par with your ephemeris) to see if any errors are thrown, and if that works ok, check the directories in /tmp to verify that the ephemeris and stuff there makes sense.
If you can't resolve the issue, this should at least help to see to see if it's a dspsr bug or a tempo2 bug, and you re-post this with more details in the tempo2 or dspsr bug tracker.