No alias for LOFAR

0 votes
When I run pav on some files produced by the LOFAR pulsar pipeline, it complains "itoa_code no alias found for LOFAR". Using -V, this does not appear to affect ephemerides, nor do the aliases found in Util/tempo/itoa.C bear any obvious relationship to anything found in the tempo2 distribution. The tempo distribution contains a different list of aliases, though at least tempo and psrchive seem to agree on the telescopes that occur in both lists. Does this error matter? Should I put an entry for LOFAR ("LF" in the CVS tempo) in the default aliases file? Is it intended that psrchive should maintain a duplicate of the tempo aliases list?
asked Jul 22, 2014 by anonymous

1 Answer

0 votes
It doesn't seem that this error is affecting the results, as far as I can say.
answered Mar 31, 2017 by Caterina (200 points)