Spin tone in FGL-DSL data when loading multiple days of data about bleeding_edge HOT 1 OPEN

I think that what happens here is that the spintone removal process gives results that may be inaccurate if the timespan of the data is too long. Ordinarily, the spintone removal process works in batches, but the batch times are determined by the times in the calibration file. Once we are past the last time in the cal file, then the spintone removal is processed for one big batch, and in this case the second day's spintone removal is wildly off. The differences are typically much less noticeable.
I could put in something that breaks the data into day-long batches if needed after the last cal file entry if needed. What do you all think?

from bleeding_edge.