Lesson 19 of 20
From prediction to experiment — what the twin can and cannot say
The gap between simulation and the wet lab
We reached the conclusion "switch DDX54 off and the cancer attractor disappears and the cell returns to normal". Now let us see what it takes to carry that sentence into a lab.
Separating what the model can say from what it cannot is the whole of this lesson.
| What the model says | What the model does not say |
|---|---|
| Take DDX54 to 0 and proliferation stops | How far you have to lower it (70%? 90%?) |
| The attractor disappears | How many days it takes |
| It moves to the normal attractor | Whether that state equals a real normal cell |
| There are no side effects inside this circuit | What happens to genes outside the circuit |
| PDL1 alone is ineffective | Whether it is ineffective in real patients |
This is the price of throwing away everything between 0 and 1 — the other side of the computing power we gained in lesson 4.
Python
Runs in your browser
Check that the model gets right what it already knows, and only then ask it what it does not.
Python
Runs in your browser
Write down predictions without a falsifier and you will claim you were right whatever comes out.
Python
Runs in your browser
🎮 Prediction checklist
Match each prediction of the model to the experiment it would take to test it.
🤔 Check yourself
Why can a Boolean model not express a 'partial knockdown'?
Answer It is the price paid in lesson 1 for throwing away continuous expression levels. In exchange we got exhaustive enumeration, and that trade is the essence of Boolean modelling.
🤔 Check yourself
Why check 'does it reproduce what we already know' first?
Answer It is called calibration. A prediction made without this step is 'a story that might be true', not a scientific hypothesis.
🤔 Check yourself
Why write a 'falsifier' into the experimental plan in advance?
Answer Without it written down you will read any result as 'partly right'. Post-hoc interpretation validates nothing.