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
I'm using gwfast to compute the SNR of binary neutron stars that merge within the age of the Universe. These BNSs are produced from a population synthesis code and thus each comes with a GW coalescence time, t_coal.
For a given detector, ie the CE with 40km baseline sensitivity, in the Signals dictionary if useEarthMotion=True, then astropy fails to compute LSMT from t_coal if it is too long, i.e ~> Myr, and gives an error because astropy does not know the motion of the Earth far in the future. See the astropy issue discussion here: astropy/astropy#16294
Am I misusing this flag/feature? For now I can just set useEarthMotion=False and pass t_coal to the waveform to avoid the error from astropy when computing LMST from t_GPS via gwfastUtils.GPSt_to_LMST().
Is this feature not appropriate for astrophysically derived coalescence timescales, or am I missing something here?
Thanks!
The text was updated successfully, but these errors were encountered:
I'm using gwfast to compute the SNR of binary neutron stars that merge within the age of the Universe. These BNSs are produced from a population synthesis code and thus each comes with a GW coalescence time, t_coal.
For a given detector, ie the CE with 40km baseline sensitivity, in the Signals dictionary if useEarthMotion=True, then astropy fails to compute LSMT from t_coal if it is too long, i.e ~> Myr, and gives an error because astropy does not know the motion of the Earth far in the future. See the astropy issue discussion here: astropy/astropy#16294
Am I misusing this flag/feature? For now I can just set useEarthMotion=False and pass t_coal to the waveform to avoid the error from astropy when computing LMST from t_GPS via gwfastUtils.GPSt_to_LMST().
Is this feature not appropriate for astrophysically derived coalescence timescales, or am I missing something here?
Thanks!
The text was updated successfully, but these errors were encountered: