Browse › Medical › Drug Response Prediction › GDSCv2
GDSCv2 Benchmark (Drug Response Prediction)
Drug response prediction is about using computer methods to guess how someone will react to certain medicines. It involves looking at various types of data, like genes, drug structures, and medical records, to predict how well a person will respond to a particular treatment. The aim is to create personalized treatment plans for patients, ensuring they get the best results with the fewest side effects. This approach not only helps doctors choose the right medicines for each patient but also speeds up the development of new drugs by predicting their effectiveness and safety. Techniques like machine learning and deep learning are commonly used to make these predictions based on different types of data, such as genetics and medical history.
The archive carries no text for this table; the description above is the archive's text for the task Drug Response Prediction. archive 2025-07-28
Over time archive 2025-07-28
The chart needs JavaScript; the table below carries every value.
Direction inferred from the metric name, not from the archive: Pearson correlation coefficient (PCC) (higher is better). Not inferred (points only, no best-so-far line): mRMSE. Points are placed at the row's paper date; 1 of 1 rows carry one.
Results archive 2025-07-28
Archive rows end at the archive snapshot, 2025-07-28: no result published after that date is in this table. Rank is the archive's row order at that snapshot; not re-ranked here. Metric values are the archive's strings. Column headers sort the table in your browser; each row keeps its archive rank.
| Paper | Code | Ran Syntology | Report | ||||||
|---|---|---|---|---|---|---|---|---|---|
| 1 | TransEDRP | 0.93807 | 0.0229 | – | Paper | Code | 2022 | linked, not harvested | report |
All 1 rows shown. 1 link to a paper page on this site; 0 are marked as using additional training data in the archive. No GitHub stars are tracked; "Code" is the first repository the archive lists for the row. The archive carries no row tags, review links or community-submitted rows for this table; none are shown. archive 2025-07-28
Syntology Ran reads "N of M ran · U unverified": of the M code samples Syntology harvested from repositories linked to that row's paper (joined by arXiv id), N executed on a synthesized input and the other U = M−N are unverified (harvested, no recorded run). It counts code from repositories linked to that row's paper, not this result: the row's number was not reproduced and nothing here is a correctness claim. The other cell texts mean no graph line for the row: "linked, not harvested" (the archive links code, Syntology has not harvested it), "no code linked" (no code link in the archive), "not matched" (the row's paper URL matched no paper on this site). 0 rows have a graph line, from 0 distinct papers; 0 rows (0 papers) have at least one sample that ran. Counting each paper once: Syntology ran 0 of 0 samples; 0 unverified. Separately, 0 of those 0 are pointer-only (licence): the site points at that code rather than redistributing it, a licence property recorded for ran and unverified samples alike; each cell's tooltip carries the row's own pointer-only count. Read from the graph 2026-09-25. Per-sample status is on the paper page.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections