General ticket to record issues with findApertures

[KathleenLabrie]

This issue records problems or strange behavior of findApertures. The problems recorded here are not issues that need resolving immediately but rather examples to use to improve the performance of findApertures.

Ensure that each example is supported with downloadable data, a description of what the perceived problem is, a description of the desired behavior, and how to reproduce what is being reported.

[KathleenLabrie]

Data (2D spectra ready for findApertures): https://drive.google.com/drive/folders/1WNkwSjZdVMGwyC-n-M_3E0Cha2C2PO4x?usp=sharing

Raw: S20220926S0086.fits and S20220926S0089.fits - Using 20220930, release/3.1.x.

• When reduced in QL mode, the bright SN next to the galaxy core is picked up with a reasonable aperture by findApertures.
• When reduced in SQ mode, the SN is not picked up at all, even playing with the input parameters.
• The same calibrations were used to produced the 2D spectra.
• The only main difference is the flagging of the CRs by the SQ recipe which the QL recipe does not do.

   reduce -r findApertures S20220926S0086_2D.fits -p interactive=True
   reduce -r findApertures S20220926S0086_ql_2D.fits -p interactive=True