Closed mattpitkin closed 8 months ago
These functions expect numerical values, and they have even defaults for them. I am not sure it's appropriate to give them flow branches to handle None
. (Doing so, among other things, may prevent code compilation in some frameworks.) I would prefer a fix in e_e.
@vallis No problem. I'll close this and submit a PR for enterprise_extensions.
In white_signals.py, the
*_ndiag
functions fail if they get passedNone
values. This happens, for example, if thewhite_noise_block
in enterprise_extensions hasvary=False
, and therefore efac/equad/ecorr are set toConstant
parameters, which have default values of None.The two potential fixes are the one in this PR, i.e., allow
None
values, which forefac_ndiag
is equivalent to havingefac=1.0
, and settneqad_ndiag
to zeros if passedNone. The other fix would be to specify values for the
Constantsin the
white_noise_block` in enterprise_extensions, e.g.,: