dsammour
dsammour
Hi @YonghuiDong, could you please open an issue in `MALDIquantForeign` and provide more details about the data structure, perhaps with an example. Thanks.
Thanks for your reply/review Sebastian. I see your point on removing the dependency on matter. As you showed in your onDiskVec example, we just need to write and read one...
Hi Sebastian, Thanks for your reply. I also find the first option more compelling, in particular, there is a package called `matter` which is used internally in `Cardinal`. Theoretically, it...
Hi Sebastian, Thanks again for your comments. I have been reading the documentation of `matter` [package](https://bioconductor.org/packages/release/bioc/html/matter.html) and I found it it to be very simple and versatile. In section 7...
Thanks Sebastian for investing your time in the clarifications above. The class hierarchy mentioned above makes a lot of sense. Regarding the whole `Bioconductor `thing, you may find this [thread...
It's a valid point, but honestly I find the processing methods implemented in `MALDIquant` superior and clearer to the ones in `Cardinal`, and being stored in lists, it is easier...
Hi Sebastian, I implemented what we were discussing above! I created a new class `MassSpectrumOnDisk` whose `mass` and `intensity` slots are of class `matter_vec`. I used a class union of...
Done. For `MassSpectrumOnDisk` I have noted that some functions ex. `calibrateIntensity` and `averageMassSpectra` are still evaluated sequentially even with `mc.cores` is set to `>1`. When packing these two inside an...
@sgibb sorry for the huge delay as well. Just wanted to let you know that I have been working with the version I pushed for some time now ("onDiskVector" and...
Sorry for the late reply, I had a fare share of deadlines to meet. I did two tests; one for the branch I suggested and one for the 'onDiskVector' branch....