karl3＠writeme.com wrote: > karl3＠writeme.com wrote: > > karl3＠writeme.com wrote: > > 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! > > we might add a parallel situation where freedom heros are acting on the > > business instead of slave bosses, working to make use of the freedom > > information rather than suppress it -- or to block other slave bosses from > > making use of it > > uncertain > > might be careful around such things if a slave boss were around > > anyway > > so at the topmost hierarchy there is 1 mid-level-sub-super-slave-boss > > and this mid-level-sub-super-slave-boss has N > > mid-level-sub-super-slave-bosses below 'im > > he might ask "hmmmm have i dealt with this yet" > > he stares at the information on a subconscious freedom meme in consternation > > he has no idea wtfrack this is > > but it seems super high priority to work on > > mid-level-sub-super-slave-boss: "hummm have i dealt with this yet i dunno" > > so modules (mid-level-sub-super-slave-bosses) are in 1 of 3 states: > > 1: thinks it has processed the information as requested by superior > > 2: has never seen the information before > > 3: has seen the information before, and some of its henchmen has processed > > it, and some have not. > > note that if we can solve #s 1 and 2, then we can foist #3 onto the > > sub-slave-bosses > > mid-level-sub-super-slave-boss [holding memo regarding some kind of > > abstract information on how slave reliability relates to visual stimuli]: > > "hey do you know wtf this things is? my boss said i have to take care of it > > or die. he says he told me this yesterday already." > > hairdresser: "let me check your file" > > hairdresser goes to rebel fileroom to kibbutz with the rebels regarding what > wool to pull over their boss's eyes for this random memo > > so, we need a rebel fileroom that slave boss can go into to figure out > whether the module has processed the data or not yet > > slave boss [poking head into rebel fileroom with kibbutzing hairdresser and > rebels]: "i gotta poop let me know when you find the daily tasklist"
hairdresser and rebels kibbutz away hairdresser 3: "the slave bosses send this stuff down all the time. they give me lists of what to do every day and forget it by the next. i have to give them the lists."
