Disk space used triples after DP3 A-Team clipping

I noticed that during my run the disk space seems to grow to non-dysco compressed levels during the A-Team clipping step.

I expect the initial growth by ~4 TB as that is applying LINC solutions and stuff, basically copying the data, but afterwards it grew an additional ~10TB over the course of the A-Team clipping step, which I believe is not expected/intended? I think this is related to our discussion on !50 (merged) and whether using dysco in this DP3 call would apply to MODEL_DATA or DATA. If I remember right DP3 has the option to explicitly not write by leaving msout empty, but I don't know if that affects the flags being applied. I will try to do a simpler test with less data outside the pipeline.