-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TOA reading as a model method? #748
Comments
That is a very good suggestion! Currently, something like pintempo has to do a bunch of checks to deal with various situations like setting ephemeris, adding TIM file JUMPs to the model, and computing pulse numbers is TRACK mode is on:
All this kind of stuff could be handled in one place, as you suggest. |
Are we going to make a component for these control parameters? If that is the case, we can add validate() and other fun stuff. |
This functionality is implemented in the |
So in our example fit-NGC6440E.py, we currently read the model first and then read the TOAs. But we don't use the information that is (potentially) in the model to do a better job reading to TOAs. For instance, we ignore the ephemeris used and also whether the planetary shapiro delay is going to be used or not.
Should we make using the model information an option for get_TOAs()? Or alternatively make a model method that uses the information to call get_TOAs() better with all of the appropriate keyword arguments set properly? Or maybe even both?
For example, instead of:
which can improperly load in TOAs without proper information from the model, we would do either:
or
?
The text was updated successfully, but these errors were encountered: