Five tries, same failure — narrowing v0.5.0's training problem by elimination
This is a follow-up to yesterday's post about the v0.5.0 C-train failures. Yesterday we ran four attempts and ruled out three suspects. Today we ran a fifth and ruled out a fourth. One hypothesis remains. The method we used comes directly from software debugging, so this post is written for engineers who haven't run a training campaign before.