handle DMOFF #484
Comments
|
I think this is also an "issue" in libstempo that I opened last year, and that could be linked to.
… On Jun 26, 2019, at 9:48 AM, Paul T. Baker ***@***.***> wrote:
IPTA DR2 release VersionA uses DMOFF in it's .par files. My understanding is that this is similar to DMX. Neither PINT nor libstempo can handle this DM model. It has lines like:
DMMODEL DM 1
_DM 53281.0927574998 0.00145592665025232 5.36854989516535e-05
...
_CM 53341.0927574998 6.08366194548412e-07 1.10834102752821e-07
...
CONSTRAIN DMMODEL
Currently pint.models.dispersion_model only handles Taylor expanded DM variations (e.g. DM, DM1, DM2, ...) and DMX. Adding this functionality would allow us to use IPTA DR2 VersionA in addition to VersionB.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
see also: vallis/libstempo#15 |
|
Is there some documentation of the format of the IPTA data format and the
parameterization of the models? I was trying to use PINT process DR2 but
not very successfully. Does the DR2 paper list those things?
…-Jing
On Wed, Jun 26, 2019 at 9:50 AM Stephen Taylor <[email protected]>
wrote:
I think this is also an "issue" in libstempo that I opened last year, and
that could be linked to.
> On Jun 26, 2019, at 9:48 AM, Paul T. Baker ***@***.***>
wrote:
>
> IPTA DR2 release VersionA uses DMOFF in it's .par files. My
understanding is that this is similar to DMX. Neither PINT nor libstempo
can handle this DM model. It has lines like:
>
> DMMODEL DM 1
> _DM 53281.0927574998 0.00145592665025232 5.36854989516535e-05
> ...
> _CM 53341.0927574998 6.08366194548412e-07 1.10834102752821e-07
> ...
> CONSTRAIN DMMODEL
> Currently pint.models.dispersion_model only handles Taylor expanded DM
variations (e.g. DM, DM1, DM2, ...) and DMX. Adding this functionality
would allow us to use IPTA DR2 VersionA in addition to VersionB.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub, or mute the thread.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#484?email_source=notifications&email_token=ABIUBA2G5ZFNMDRVIFP6KZDP4NX3BA5CNFSM4H3SOSE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYTS25Y#issuecomment-505884023>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABIUBA6X4UACO5TAUGXNKBLP4NX3BANCNFSM4H3SOSEQ>
.
|
|
I suspect @scottransom, Ben Perara, and/or Megan DeCesar will know |
|
Or Mike Keith.
… On Jun 26, 2019, at 10:56 AM, Paul T. Baker ***@***.***> wrote:
I suspect @scottransom, Ben Perara, and/or Megan DeCesar will know
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
That model is described here: https://academic.oup.com/mnras/article/429/3/2161/1002440 I don't think this is super trivial to add, as I think it requires a change to the fitting process itself. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
IPTA DR2 release
VersionAusesDMOFFin it's.parfiles. My understanding is that this is similar toDMX. NeitherPINTnorlibstempocan handle this DM model. It has lines like:Currently
pint.models.dispersion_modelonly handles Taylor expanded DM variations (e.g.DM, DM1, DM2, ...) andDMX. Adding this functionality would allow us to use IPTA DR2VersionAin addition toVersionB.The text was updated successfully, but these errors were encountered: