Isoquant memory issue

[lianov]

Description of the bug

Related to IsoQuant issue ablab/IsoQuant#189

This issue carries over to the pipeline in the latest version of IsoQuant. Prior to first release, we'll need to proceed with one of the two options below:

• Check back on issue noted above to see if fixes have been applied (update and test in scnanoseq)
• If no fixes have been applied, then downgrade IsoQuant to version 3.3.1

[lianov]

For the record, the fix in the meantime was to downgrade IsoQuant to 3.3.1. We will update or patch the pipeline once a fix becomes available from IsoQuant

[lianov]

Adding one note here for the record: between the time this issue was closed and final changes for release, IsoQuant 3.5.0 was released. Since then this version has been upgraded in the pipeline with the fix we needed for the memory issue reported here.

As an additional bonus, this version drastically improved quantification as well (which were improvements that were on-going in the versions between 3.3.1 and 3.5.0).