• Don't do linear estimation for DASCale values when the slope is negative or zero, instead go in DAScaleNegativeSlopePercentage steps to larger DAScale values. If negative or zero with further increase in DAScale, this is the max DAScale that is acquired. Then fill in, as described next (setQC is passing in this case, independent of NumSweepsWithSaturation):
• With negative slope, fill in between last DAScale with positive slope and first negative/zero slope DAScale based on DAScaleFillInPercentageNegativeSlope
• Round to pA in SetDAScale
• Add prefix (F or R or X) in "DAScale values left" to mark where the value came from
• Add an analysis parameter to determine how many SCIs we look back for failing adaptive suprathreshold data. We currently only look at the very previous one.

negative means negative and zero.

• Additional passing criteria: 1. two negative slopes in a row. 2. a FI slope QC passing and one negative slope in a row (in this order). If a negative slope is obtained, subsequent slope measurements are made from the last da scale that gave a positive slope (this is not reset after a possible positive slope as we want to ignore negative slopes always). After 1 or 2, one additional sweep is acquired with a DA scale that splits the difference between the last da scale with a positive slope and the first with a negative one. We still do frequency fillin as usual.

For all sweeps with negative slope we don't care about post pulse baseline QC. The purpose here is to minimize the number of sweeps acquired with depolarization block.

DAScaleNegativeSlopePercentage (1-100% of maxDASCaleStep) is applied after the first negative slope to set the DA scale.

New behaviour applies to RhSuAd data as well.