Whole-known-network
<p>So we do have a blank command at the end of an aborted frame already, nice. Have some more places to go through to make sure we have blanks everywhere we want to stop milling when done doing something.</p>
<p>Ok so it looks like the only time we are actually blanking is at the end of a pattern. At the end of acquiring an image we are not currently blanking. At the end of an image, the beam is returned to (0,0), the top left corner. You can see that it is digging deep holes there. So whenever I had previously acquired an image before starting a pattern, it ends up digging a hole there.</p><p>The holes are limited in size due to sputter re-deposition ratios that change as the hole gets deeper.</p>
<p>Doing some FIB pattern testing. Looks like we are dragging the beam between frames right now. Hmmmmmmmm.</p><p>The dark area around each test pattern is the result of taking an image with the FIB. Remember kids, a FIB is a milling machine that is always ablating the sample when the beam is on, and it only just so happens to be able to take pictures while doing so.</p>
<p><span class="h-card" translate="no"><a href="https://wandering.shop/@xgranade" class="u-url mention">@<span>xgranade</span></a></span> ... and the only reprieve many can think of is "I know! I'll call cops on cops" aka copyright</p>
<p>I'll at least partially blame that for a *long* time, F/OSS has been ideologically captured into effectively being a kind of free labor for giant corporations... the disconnect from labor politics is a major weakness of many F/OSS communities, IMHO.</p>
<p>The ideological capture of F/OSS communities by proprietary services and binaries* that are directly designed to work against their users' interests is at once fascinating and horrifying.</p><p>(*I strongly disagree with the idea that a serialized model is "open source," unless a debug-stripped P/E file is also "open source.")</p>
<p>Reading project READMEs is so weird now. The examples for OSS projects seem to always be a mix of a few genuinely nice but somewhat niche applications, mixed in with examples showing how to better use climate-destroying labor-betraying plagiarism machines that lie and that you can only use by giving money to eugenicist fascists who spend way, *way* too much time on LessWrong and SSC.</p>
<p><span class="h-card" translate="no"><a href="https://mastodon.social/@isagalaev" class="u-url mention">@<span>isagalaev</span></a></span> </p><p>Yeah, not a bad choice. There were two scenes in particular that were really well done in my opinion:<br /> - The Cultural Revolution "struggle" session in the early episodes.<br /> - The scene with the ship passing through the canal with the nano-fiber weapon<br />The portrayal of the detective throughout the series was also a highlight. </p><p>Other than that, it was mostly pretty decent special effects eye-candy.</p>
<p>the three trauma responses: fauna, flora and fungi</p>