Thresholding/Automatic Cutoff

[camlam]

Hey @avsastry, here is the update for thresholding stuff. Given a couple of people's notes during GA meeting today, I bumped the search space for the cutoff parameter to a max of 2000 instead of 1000. If that ends up being too slow (ran in ~4 minutes on all 229 iModulons of PRECISE 2.0 on my laptop, so it shouldn't be terrible since it should only be necessary once) I can try to make it a bit smarter about only trying larger cutoffs if the best cutoff found is also the largest (i.e. a super crude metric of "is this function still increasing").

[sapoudel]

For speeding up parameter search, we could start by searching sparsely in large intervals and then narrowing down on the ones that give the best f-scores. It could speed up the processing, but depending on how much the f-score fluctuates we could miss the optimal value.