Lesson 13 of 20
Exhaustive screening — what MObyDiCK does
Switch every gene off, and on, one at a time
Last lesson we chose DDX54 and switched it off. But why DDX54? If you picked it already knowing the answer, that is not a prediction.
Virtual screening takes the opposite line.
Do not choose. Try everything.
Then rank the results and let the computation choose the answer.
That is the skeleton of what a platform like Prof. Cho's MObyDiCK does. At a bench one gene takes weeks; here the whole lot goes by in a blink.
This takes well under a second in your browser.
Python
Runs in your browser
reversion = the share of once-cancerous cells that returned to normal. harm = how many normal ones became cancer.
Python
Runs in your browser
It splits three ways. Remember that PDL1 and CD47 are in the middle group (no effect).
Python
Runs in your browser
🎮 Screening table
Press a column heading to sort. What you rank by is what changes the 'best target'.
🤔 Check yourself
Why does virtual screening 'try everything' instead of choosing targets first?
Answer Testing a hypothesis and discovering one are different things. Exhaustive enumeration makes the second possible — but only while you can afford the compute.
🤔 Check yourself
How should you treat a screening row whose 'harm' column is not zero?
Answer There is little reason to push something into the lab that your own model already calls harmful. The reason it is 'review separately' rather than 'discard' is that the denominator of the harm figure is also ours to choose (lesson 14).
🤔 Check yourself
Reading it off the circuit, why did PDL1 knockout alone do nothing here?
Answer
T_Kill* = Proliferation and not PDL1 and not CD47. There are two brakes; release one and the car stays exactly where it was.