You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you very much for publishing this interesting work. I have reproduced the results on TCGA COADREAD cohort, and my results do not replicate your reported values. I downloaded the Case IDs as in your split files, patched using CLAM and encoded using CTransPath. I trained the model for 2 epochs as mentioned in your codebase. However validation c-index results that I obtained, averaged across splits for each LR,DECAY configuration is as follows.
When averaged across all configs, I get 0.589621869602649 ± 0.020049446852174125 as the val c-index which is significantly different to 0.673 reported in the paper.
Could you kindly help me understand why I am unable to reproduce the given numbers? I need to understand what I might be doing wrong. Are you reporting an averaged or the highest val c-index? And are there any other implementation details that is not mentioned in the paper?
Thank you.
The text was updated successfully, but these errors were encountered:
Hi,
Thank you very much for publishing this interesting work. I have reproduced the results on TCGA COADREAD cohort, and my results do not replicate your reported values. I downloaded the Case IDs as in your split files, patched using CLAM and encoded using CTransPath. I trained the model for 2 epochs as mentioned in your codebase. However validation c-index results that I obtained, averaged across splits for each LR,DECAY configuration is as follows.
When averaged across all configs, I get 0.589621869602649 ± 0.020049446852174125 as the val c-index which is significantly different to 0.673 reported in the paper.
Could you kindly help me understand why I am unable to reproduce the given numbers? I need to understand what I might be doing wrong. Are you reporting an averaged or the highest val c-index? And are there any other implementation details that is not mentioned in the paper?
Thank you.
The text was updated successfully, but these errors were encountered: