On 2019-12-30 06:58:01, user Koki Tsuyuzaki wrote:
I'm a developer of scTensor.<br />
Thanks for adding scTensor in your experiment,<br />
but there are many misleading or wrong parts as below,
so please consider the modification.
1. LRBase
In Figure 1C and the caption, you use "the database of scTensor", but please use "LRBase" (the name of our L-R database) instead.
Please note that the scTensor is the name of algorithm or the software package, and not L-R database.
Actually, scTensor can be used with any L-R database.<br />
https://rdrr.io/bioc/LRBase...
I think you should separately consider the effect of selection of L-R database and CCI detection algorithm based on the database.
2. Which is the largest LR database?
In the INTRODUCTION, you said
to the best of our knowledge, it is the largest database of this kind.
but in the Figure 1C, LRdb seems not so large.
3. Blank elements in Table 1
There are many blank elements in Table 1 scTensor column.
If you will add our method in your experiment, you should investigate it more.<br />
I still do not understand your intention of
complete pipeline<br />
the other items are as follow:
Accept preprocessed data Y
Export types<br />
tables Y<br />
circualar plots N<br />
graphML or equiv. N
Perhaps the complete pipeline means the built-in call type calling using t-SNE, k-means, or SIMLR but I don't think such name is appropriate, any tool can perform such task by combinined with the other tools.
Besides, if the user want to use other dimensional reduction, clustering, and cell type identification methods not included in your tool, your tool can be used with them?
4. UniProtKB/Swissprot
In the Comparison with other tools, you said
Swissprot annotations (secreted/membrane) automatically
but UniProt/Swissprot is based on the manual annotation.<br />
https://www.uniprot.org
We also used UniProt/TrEMBL and this database is based on the prediction by cellular localization algorithms.<br />
So please explain more accurately.
5. No registraction of LRdb in Bioconductor
In the AVAILABILITY, you said
the LRdb package is submitted to Bioconductor
but I couldn't confirm the submitted R/Bioconductor package,
although I could confirm that a TSV file is put on the GitHub.
https://github.com/Biocondu...<br />
https://www.bioconductor.or...<br />
https://github.com/SCA-IRCM...
Where was the package published?
6. Benchmark design
In the manuscript, you compared your method with other methods,
but the benchmark is not well designed; each method use different L-R databases and different algorithms, so even if your tool showed the good performance, the reader cannot understand why the tool was good.
Again, you should separately consider the effect of selection of L-R database and CCI detection algorithm based on the database.
7. Criticism against scTensor
As the criticism against scTensor, you said
We found 2 reliable LR pairs whereas scTensor returned 14 pairs, none in common<br />
or<br />
we found significant discrepancies with PyMINEr and scTensor
but there are no detail explanation or no quantitative evaluation,<br />
and these parts are just your impression.
Acutually, some L-R pairs detected by scTensor (Supplementary Table 3) are still curated and not "none in common".<br />
https://string-db.org/cgi/n...
Besides, as you said, LRBase includes many purative (not known) L-R pairs,<br />
you cannot simply say which L-R pair is correct or not.