using same PSR distance parameter for multiple CW signals

[paulthebaker]

When a user initializes two (or more) CW signals to search simultaneously, each CW carries it's own set of pulsar distance parameters. These parameters should be collected so that all CW's use the same pulsar distance for each pulsar.

To my knowledge, this was discovered by @caitlinawitt during the IPTA MDC2. It will be important for when @bencebecsy incorporates pulsar terms in his N*CW work.

[bencebecsy]

I've just got to including pulsar terms. Thanks for the heads-up.

Shouldn't this be an issue at enterprise_extensions rather than enterprise? At least when I set up multiple CWs, the p_dist and pphase parameters are initiated by some enterprise_extension function (CWSignal, I think).

Note: It's a bit complicated though, because I'm not actually using the main of enterprise_extensions, but my own version due to a separate issue (https://github.com/stevertaylor/enterprise_extensions/issues/12). It looks like the current version of CWSignal in enterprise_extensions (https://github.com/stevertaylor/enterprise_extensions/blob/master/enterprise_extensions/models.py#L901) doesn't even set up pulsar distance and phase at psr parameters. Can maybe @stevertaylor explain why?

With that said, I'd be happy to look into this and come up with a solution, but I would need a fix first for issue #12 at enterprise_extensions.

[paulthebaker]

I think you are correct that the CW code is in enterprise_extensions. There was some discussion about moving it to enterprise base (the GW memory stuff is in enterprise.signals.utils).