min_drift argument does not appear to work

[telegraphic]

As noted by @ssmith00, Output .dat files clearly contain values below the minimum drift rate. Needs a fix and a unit test.

[texadactyl]

@telegraphic @ssmith00 @luigifcruz

• By "values below the minimum drift rate", do you mean in absolute value or signed value? Should the supplied parameter in FindDoppler __init__() be an absolute value or a signed value? Yes, I am probably showing a lack of understanding about the subject of "drift" and "drift rate".

• Same questions for the max_drift parameter?

[texadactyl]

Overdue: adding a --min-drift parameter to seti_event.py and allowing a default max_drift value in FindDoppler init().

[texadactyl]

@telegraphic @ssmith00
Closing this issue because I was able to reproduce the issue before PR #180 in a variety of files but afterwards, I observe the desired behviour. Would it be possible for either of you to try again the case which provided the error symptoms?

UPDATE on 2021-02-23: I unfortunately "verified" with a couple of setigen-generated files. This was an error and this issue has been re-opened.

[texadactyl]

@telegraphic @ssmith00
I forgot to mention that turboSETI now accepts a minimum drift rate parameter (issue #178).

[texadactyl]

Verified to still be broken somewhere in search_coarse_channel().

[texadactyl]

Reviewers: A proposed fix is in #199