Open aewallwi opened 4 years ago
Wouldn't it make more sense to go the other way? Have vis_clean
call fourier_filter
?
Wouldn't it make more sense to go the other way? Have
vis_clean
callfourier_filter
?
Yes.
Wouldn't it make more sense to go the other way? Have
vis_clean
callfourier_filter
?Yes.
I agree with @jsdillon here. Let's rename high_pass_fourier_filter
to something like vis_clean
, throw out the half-baked dayenu
functionality, and have it call fourier_filter
I'm fine with that as long as we maintain a high_pass_fourier_filter
function (even as a thin wrapper) to maintain backwards compatibility.
(we can stick in a deprecation warning though)
Also, I would suggest not naming it visclean, since it's also used on calibration solutions. Maybe CLEAN_filter
or clean_filter
?
Some discussion items with @jsdillon
fitting_options
to kwargs
in fourier_filter
. dayenu
in the fourier_filter
docstring. fourier_filter
and just determine from filter_dims. Here is the planned organization we have settled on.
fourier_filter
has lots of nearly duplicate code fromhigh_pass_fourier_filter
for doing cleaning.high_pass_fourier_filter
has some half bakeddayenu
functionality that is no longer needed. Ideally,fourier_filter
should be able to callhigh_pass_fourier_filter
for it's cleaning functionality. The holdup on this is thathigh_pass_fourier_filter
does not support cleaning of arbitrary numbers areas not centered around delay=0. If we generalizehigh_pass_fourier_filter
to support off center cleaning, we can just havefourier_filter
call it and avoid lots of redundant code. We should also remove the half-bakeddayenu
functionality and rename it to something more appropriate likevis_clean
since it will do cleaning only.