You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One question is how the time_scale is handled for TZRMJD. For most TZRSITE values, TZRMJD should be a pulsar_mjd in UTC, but fro TZRSITE at the barycenter, TZRMJD should be in the TDB timescale. Is this done correctly currently?
The text was updated successfully, but these errors were encountered:
I agree with you @paulray, it should convert to the right scale. However, the location in the timing scale is a tricky part. Should we allow MJDparameter has a location?
Nearly all MJD parameters are in TDB and should not have a location (e.g. T0, PEPOCH, TASC, etc...)
I think only TZRMJD is something that might want a location. However, its location is really specified by TZRSITE, so I think the TZRMJD parameter should not have a location associated with its Time object. Instead, when a TOA is constructed from TZRMJD, TZRSITE, TZRFRQ, it should get the location from TZRSITE.
Maybe in the future, astropy can allow a location at pulsar barycenter. and do the conversion for us. You know what, that is called astropy.pint module.
As I was writing docs, I found this:
PINT/src/pint/models/parameter.py
Line 852 in 30d916e
When you set an MJDParameter to an
astropy.Time
that is in a scale different than par.time_scale, it is not converted. I think probably it should be.returns
So I think probably the line should be
But this probably needs some discussion.
One question is how the time_scale is handled for TZRMJD. For most TZRSITE values, TZRMJD should be a pulsar_mjd in UTC, but fro TZRSITE at the barycenter, TZRMJD should be in the TDB timescale. Is this done correctly currently?
The text was updated successfully, but these errors were encountered: