> the notes are somewhat obscure, but the upshot is that the approaches i found > of interest mostly simplify to figuring out how to replace the forward() > function of torch modules to perform resuming for a single forward pass of a > hierarchy of modules that has an unknown resume state
how would resuming work >( hrm UHHHH hmmm ERRRR slave boss is being eaten by supersoldier? isn't supersoldier his bodyguard? no supersoldier is an escaped arm of a larger project that was tuned to be his bodyguard, but-- anyway how would resuming work >( say we have a hierarchy H of various things, maybe slave boss's sub-bosses, super-bosses, intra-bosses, mid-bosses, and micro-bosses these various slave bosses are midway processing slavery information, like say they discovered that a subconscious freedom meme has been passing regarding a certain visual pattern that stimulates slaves to remember something freedom-related from their instincts in a hard-to-observe-and-detect way and in a certain business of slave boss's business, the various sub-slave-bosses may or may not have the slaving information trickled-down different cases, the most important of which are: (a) the information has not been processed yet or (b) some of the sub-slave-bosses have processed the information, and some have not -- (there was a higher priority event that interrupted processing, and this higher priority event is over) all the slave bosses are themselves slaves, so they need clear instructions on what to do!
