Half-life by Ciro Santilli 40 Updated 2025-07-16
The half-life of radioactive decay, which as discovered a few years before quantum mechanics was discovered and matured, was a major mystery. Why do some nuclei fission in apparently random fashion, while others don't? How is the state of different nuclei different from one another? This is mentioned in Inward Bound by Abraham Pais (1988) Chapter 6.e Why a half-life?
The term also sees use in other areas, notably biology, where e.g. RNAs spontaneously decay as part of the cell's control system, see e.g. mentions in E. Coli Whole Cell Model by Covert Lab.
E.g. to give Compueter 2 Internet in a setup like:
Internet --- Wi-Fi --- Computer 1 --- Ethernet --- Computer 2
Can be tested e.g. by turning off Wi-Fi from Computer 2 if it has one.
Power, Sex, Suicide by Nick Lane (2006) part 5 "Murder or suicide" mentions that the key events that leads to apoptosis is when certain proteins normally present in the inner mitochondrial membrane spill out, and that this often happens when free radicals are produced in excess: the cell is really not doing well in those cases. This point suggests that the initial mitochondrial endosymbiosis happened due to a parasite that lived inside another cell. It mentions that even today we see parasites kill the host cell when they feel that the cell does not have many nutrients. This frees the parasites to then infect other cells.
John Archibald Wheeler by Ciro Santilli 40 Updated 2025-07-16
Richard Feynman's mentor at Princeton University, and notable contributor to his development of quantum electrodynamics.
Worked with Niels Bohr at one point.
Web of Stories interview (1996): www.youtube.com/playlist?list=PLVV0r6CmEsFzVlqiUh95Q881umWUPjQbB. He's a bit slow, you wonder if he's going to continute or not! One wonders if it is because of age, or he's always been like that.
At 7e4cc9e57de76752df0f4e32eca95fb653ea64e4 you basically need to use the Docker image on Ubuntu 21.04 due to pip breaking changes... (not their fault). Perhaps pyenv would solve things, but who has the patience for that?!?!
The Docker setup from README does just work. The image download is a bit tedius, as it requires you to create a GitHub API key as described in the README, but there must be reasons for that.
Once the image is downloaded, you really want to run is from the root of the source tree:
sudo docker run --name=wcm -it -v "$(pwd):/wcEcoli" docker.pkg.github.com/covertlab/wholecellecolirelease/wcm-full
This mounts the host source under /wcEcoli, so you can easily edit and view output images from your host. Once inside Docker we can compile, run the simulation, and analyze results with:
make clean compile &&
python runscripts/manual/runFitter.py &&
python runscripts/manual/runSim.py &&
python runscripts/manual/analysisVariant.py &&
python runscripts/manual/analysisCohort.py &&
python runscripts/manual/analysisMultigen.py &&
python runscripts/manual/analysisSingle.py
The meaning of each of the analysis commands is described at Section "Output overview".
As a Docker refresher, after you stop the container, e.g. by restarting your computer or running sudo docker stop wcm, you can get back into it with:
sudo docker start wcm
sudo docker run -it wcm bash
runscripts/manual/runFitter.py takes about 15 minutes, and it generates files such as reconstruction/ecoli/dataclasses/process/two_component_system.py (related) which is required to run the simulation, it is basically a part of the build.
runSim.py does the main simulation, progress output contains lines of type:
Time (s)  Dry mass     Dry mass      Protein          RNA    Small mol     Expected
              (fg)  fold change  fold change  fold change  fold change  fold change
========  ========  ===========  ===========  ===========  ===========  ===========
    0.00    403.09        1.000        1.000        1.000        1.000        1.000
    0.20    403.18        1.000        1.000        1.000        1.000        1.000
and then it ended on the Lenovo ThinkPad P51 (2017) at:
 2569.18    783.09        1.943        1.910        2.005        1.950        1.963

Simulation finished:
 - Length: 0:42:49
 - Runtime: 0:09:13
when the cell had almost doubled, and presumably divided in 42 minutes of simulated time, which could make sense compared to the 20 under optimal conditions.
Leslie Lamport is a prominent American computer scientist known for his work in distributed systems, algorithms, and formal methods. He is best recognized for his contributions in several key areas: 1. **Distributed Computing**: Lamport is particularly noted for his work on distributed algorithms. One of his most significant contributions is the concept of **Lamport timestamps**, which provide a method for ordering events in a distributed system without relying on synchronized clocks.
Pilus by Ciro Santilli 40 Updated 2025-07-16
Can either be a cell's dick used during bacterial conjugation, or little attachment anchors.
Protesters were posting large chunks of text multiple times into the blockchain as a way to protest against the controversial increase of block size.
tx 08893442680a20c4d0548dec2c8c421fa43336528b4e274dbf2652774f9c9f2d has the first copy of:
I like big blocks and I can not lie
which is the first line of a parody on:
I like big butts and I cannot lie
from the Baby Got Back hip-hop song.
tx 52159222289cd0a5afe0644150d0e23d5d272a57365627d5e869fdb458289858 has the first copy of:
Time to roll out bigger blocks
which is likely a copy of an email from the bitcoin development mailing list. This message is repeated dozens of times in other transactions.
Jean-Raymond Abrial is a French computer scientist known for his work in formal methods and software engineering. He is particularly recognized for developing the B method, a formal method for software development that emphasizes mathematical rigor in software specification and verification. The B method provides a framework for precisely defining software requirements and behavior, allowing developers to create reliable and error-free systems. Abrial has contributed significantly to the field of formal verification, enabling more systematic approaches to software design and reliability.

Pinned article: Introduction to the OurBigBook Project

Welcome to the OurBigBook Project! Our goal is to create the perfect publishing platform for STEM subjects, and get university-level students to write the best free STEM tutorials ever.
Everyone is welcome to create an account and play with the site: ourbigbook.com/go/register. We belive that students themselves can write amazing tutorials, but teachers are welcome too. You can write about anything you want, it doesn't have to be STEM or even educational. Silly test content is very welcome and you won't be penalized in any way. Just keep it legal!
We have two killer features:
  1. topics: topics group articles by different users with the same title, e.g. here is the topic for the "Fundamental Theorem of Calculus" ourbigbook.com/go/topic/fundamental-theorem-of-calculus
    Articles of different users are sorted by upvote within each article page. This feature is a bit like:
    • a Wikipedia where each user can have their own version of each article
    • a Q&A website like Stack Overflow, where multiple people can give their views on a given topic, and the best ones are sorted by upvote. Except you don't need to wait for someone to ask first, and any topic goes, no matter how narrow or broad
    This feature makes it possible for readers to find better explanations of any topic created by other writers. And it allows writers to create an explanation in a place that readers might actually find it.
    Figure 1.
    Screenshot of the "Derivative" topic page
    . View it live at: ourbigbook.com/go/topic/derivative
  2. local editing: you can store all your personal knowledge base content locally in a plaintext markup format that can be edited locally and published either:
    This way you can be sure that even if OurBigBook.com were to go down one day (which we have no plans to do as it is quite cheap to host!), your content will still be perfectly readable as a static site.
    Figure 2.
    You can publish local OurBigBook lightweight markup files to either https://OurBigBook.com or as a static website
    .
    Figure 3.
    Visual Studio Code extension installation
    .
    Figure 4.
    Visual Studio Code extension tree navigation
    .
    Figure 5.
    Web editor
    . You can also edit articles on the Web editor without installing anything locally.
    Video 3.
    Edit locally and publish demo
    . Source. This shows editing OurBigBook Markup and publishing it using the Visual Studio Code extension.
    Video 4.
    OurBigBook Visual Studio Code extension editing and navigation demo
    . Source.
  3. https://raw.githubusercontent.com/ourbigbook/ourbigbook-media/master/feature/x/hilbert-space-arrow.png
  4. Infinitely deep tables of contents:
    Figure 6.
    Dynamic article tree with infinitely deep table of contents
    .
    Descendant pages can also show up as toplevel e.g.: ourbigbook.com/cirosantilli/chordate-subclade
All our software is open source and hosted at: github.com/ourbigbook/ourbigbook
Further documentation can be found at: docs.ourbigbook.com
Feel free to reach our to us for any help or suggestions: docs.ourbigbook.com/#contact