Open hechth opened 2 years ago
@xtrojak now since this is fixed in RAMClustR, do you think this could also be done in xMSannotator?
@hechth just to clarify, we are just talking about memory consumption optimisation, otherwise it works fine in xMSannotator
? Or was there any case when a run failed for insufficient memory?
No - this is just a preliminary "issue" on GitHub since I expect to run into similar problems with xMSannotator as with RAMClustR.
For large peak tables, the computation of the correlation matrix might produce very large outputs - this is the same problem as in the RAMClustR package.
Maybe it would make sense to find some common
sparse correlation matrix
implementation?