It is an unfortunate fact that this project went on for quite long. One could trace the roots to what I described in my ToR-ORd blog on RyRs and calcium handling, saying how we could not achieve everything we wanted. I hate to be beaten by a mystery and of course wanted to revisit this problem if I could (except within few weeks of finalizing ToR-ORd, while the arguably healthier mindset of “I’ll never make another model” lasted). The blog was published in Dec 2019, and the first unsuccessful forays into more realistic calcium handling we have taken might have even taken place in 2018. (I’m not the worst in this in our household though, my wife’s major project – and amazing success – took 8 years to finish)
The scale of development was simply on another level
compared to the prior ToR-ORd. There were many more and larger conceptual
decisions, more situations of “OK, I have NO idea what to do about this”. For
each development step (testing a new idea, running a genetic algorithm, analysing
something, etc.), I create a numbered script, so I can track and revisit
progress – there were over 900 of those scripts, and countless checks too small
to be assigned a number. I kept numbering distinct models, using major and
minor version numbers. The mostly final model we had was version 11.3.2. During
the development, there were versions such as 5.7.3.5.4 or 8.9.6.5. There was a
lot to explore, understand, parametrize and develop. Below are described
several choices we had to make, that will give some insight into why the
T-World making was quite tricky. They start with very high-level conceptual
decisions related to the philosophy of calcium handling, finishing with what
could be seen as a minor point (voltage dependence of the Na-K pump).
Comments
Post a Comment