Insufficient leveling options in attune.workup.intensity for array detection - this could be a pycmds issue

[DLafayetteII]

For optimal tune_intensity using the InGaAs array detector, it is necessary that I level along 'wa' prior to taking the zeroth moment. The current leveling = true/false toggle in pycmds for tune_intensity does not seem to support this requirement. The gtol and ltol vary between images, but I do not believe this relevant to the demonstration.

If I select level = false in my pycmds tune_intensity acquisition, the output appears to not level along 'wa', nor to level spectrally. This leaves me with a poor dynamic range on the fringes (due to having a high baseline), making peak finding difficult:

If I instead select level = true, I may be leveling along 'wa' (unclear), but I am certainly also leveling along the spectral axis w2=wa, which is a poor choice if I have signal at the edge of my spectral range. Here is a manual example where I level both along 'wa' before taking the zeroth moment, and then select level=true within attune.workup.intensity. You can see data on the left side of the spectral axis that has been paved over by the spectral w2=wm leveling currently intrinsic to attune.workup.intensity. This action is not desirable and obscures real signal.

When I instead manually process my tune_intensity, leveling along 'wa' prior to taking the zeroth moment, and then choosing not to level within attune.workup.intensity, I get what I believe is the optimal output:

It seems to me that the level = true/false options turns all leveling on or off, when some applications require more nuance. Is it possible to add a catagory in the pycmds tune_intensity that allows specificity in type of leveling?

I will place the data, base curve, old curve, and script in here momentarily