Found this in a box of unrelated stuff:

Based on past experience, the longer it hangs there, the bigger it will become.
My packing skillz obviously suffered a blackout during the move …
The Smell of Molten Projects in the Morning
Ed Nisley's Blog: Shop notes, electronics, firmware, machinery, 3D printing, laser cuttery, and curiosities. Contents: 100% human thinking, 0% AI slop.
Who’d’a thunk it?

Found this in a box of unrelated stuff:

Based on past experience, the longer it hangs there, the bigger it will become.
My packing skillz obviously suffered a blackout during the move …

Having once again reawakened a back injury from long ago, I figured these were good for some comic relief:

The full-scale L4-L5 vertebrae are from Printables and the ¾ scale L5 is from somewhere I cannot recall. A mother lode of anatomical models is on Thingiverse if you want some 3D printing challenges.
The L4-L5 pair are part of an extensive human anatomic model locating all the pieces at their proper coordinates, so these two hovered about 800 mm above the XY plane. I ran them through the Grid:Tool mesh editor to center them at the XY origin, then put the bottom-most point at Z=0.
Rotating them individually in PrusaSlicer and painting only the most essential support got them to this state:

Each one take about three hours, so I ran them individually to reduce surface blemishes and maximize the likelihood of happy outcomes. Worked like a champ.
The retina-burn orange disk is not anatomically correct, because the InterWebz apparently does not have a model for spinal cartilage:

Instead, it’s a rounded cylinder resized into an oval, with its top and bottom surfaces formed by subtracting the vertebrae:

The OpenSCAD code doing the heavy lifting:
// Disk between L4 and L5 vertebrae
// Ed Nisley - KE4ZNU
// 2025-03-07
Layout = "Show"; // [Show,Build]
include <BOSL2/std.scad>
module Disk() {
color("Red")
difference() {
translate([9,-18,36])
rotate(110)
resize([33,45])
cyl(d=50,h=14,$fn=48,rounding=7,anchor=BOTTOM);
import("../Spine/human-spinal-column-including-cervical-thoracic-and-lumbar-vertebra-model_files/L4 L5 vertebrae stacked.stl",
convexity=10);
}
}
if (Layout == "Show") {
Disk();
color("White",0.3)
import("../Spine/human-spinal-column-including-cervical-thoracic-and-lumbar-vertebra-model_files/L4 L5 vertebrae stacked.stl",
convexity=10);
}
if (Layout == "Build") {
Disk();
}
All of the magic numbers come from eyeballometric measurement & successive approximation.
The Build layout left the disk floating in space, whereupon I used PrusaSlicer to reorient it edge-downward on the platform with painted-on support for minimal distortion:

Two dots of E6000+ adhesive hold everything together.
All in all, it was a useful distraction. I’ve been vertically polarized for the last five days and it’s good to be … back.

I asked for the images from recent X-ray and MRI sessions, whereupon a CD arrived in the mail. Popping it into my desktop Linux box produced this directory listing:
ll /run/media/ed/Feb\ 21\ 2025/
total 146M
dr-xr-xr-x 2 ed ed 136 Feb 21 13:14 ./
drwxr-x---+ 3 root root 60 Mar 2 13:40 ../
-r--r--r-- 1 ed ed 146M Feb 21 13:14 -NISLEY-DMBG8yMQcf8qXcVj.iso
It seems whoever / whatever produced the CD copied the ISO image to the CD, rather than burning the ISO directly to the CD. As a result, the CD has one file.
Raise your hand if you’ve never done that.
Well, I was going to save the CD as an ISO file anyway, so I just copied it to the file server.
Attempting to mount it produces an odd result:
sudo mount -o loop "-NISLEY-DMBG8yMQcf8qXcVj.iso" /mnt/loop/
[sudo] password for ed: <make up your own>
mount: failed to set target namespace to ISLEY-DMBG8yMQcf8qXcVj.iso: No such file or directory
Oh, right, starting a filename with a leading dash is never a Good Idea™.
Rename it:
mv -NISLEY-DMBG8yMQcf8qXcVj.iso NISLEY-DMBG8yMQcf8qXcVj.iso
mv: invalid option -- 'N'
Try 'mv --help' for more information.
Which is why leading dashes are a Terrible Idea™.
Force the rename to happen:
mv ./-NISLEY-DMBG8yMQcf8qXcVj.iso NISLEY-DMBG8yMQcf8qXcVj.iso
The same syntax works in the mount command, but it’s easier to solve the problem once and be done with it.
Now mount the file:
sudo mount NISLEY-DMBG8yMQcf8qXcVj.iso /mnt/loop
mount: /mnt/loop: WARNING: source write-protected, mounted read-only.
That’s entirely expected, because the whole filesystem is intended for a non-writeable CD.
What’s inside?
ll /mnt/loop/
ls: cannot open directory '/mnt/loop/': Permission denied
Why would that be?
ll /mnt
total 58K
drwxr-xr-x 15 root root 4.0K May 21 2023 ./
drwxr-xr-x 17 root root 4.0K Mar 2 13:43 ../
… omitted …
drwxrwx--- 4 496 495 2.0K Feb 21 13:13 loop/
… omitted …
Maybe 496 and 495 are the UID and GID of whatever created the CD?
Force it to my UID:
sudo umount /mnt/loop
[ed@shiitake tmp]$ sudo mount -o uid=ed NISLEY-DMBG8yMQcf8qXcVj.iso /mnt/loop
mount: /mnt/loop: WARNING: source write-protected, mounted read-only.
[ed@shiitake tmp]$ ll /mnt/loop
total 16K
drwxrwx--- 4 ed 495 2.0K Feb 21 13:13 ./
drwxr-xr-x 15 root root 4.0K May 21 2023 ../
drwxrwx--- 4 ed 495 2.0K Feb 21 13:12 data/
drwxr-xr-x 5 ed 495 2.0K Feb 21 13:13 DICOM/
-rw-rw---- 1 ed 495 1.7K Feb 21 13:12 README.txt
-rw-rw---- 1 ed 495 3.2K Feb 21 13:12 view-studies.html
Now that’s more like it.
Finally, I can fire up Weasis to look at pretty DICOM images:

Apparently things looks suspicious around L4.

You can’t make this stuff up:

We didn’t get half a foot of any precipitation that day.
That is apparently the “Pixel At a Glance” app using info scraped from weather-dot-com. The other Google Weather app, the one that may or may not still have the Weather Frog, scrapes info from noaa-dot-gov and seems somewhat less uncoordinated.
The two apps generally disagree on what kind and how much precipitation will occur, sometimes absurdly, and rarely agree with the official National Weather Service forecast.
Sometimes the forecasts have not converged by the time the weather arrives outside the window.

Given the cracking caused by vector patterns on CDs and DVDs, seeing stress cracks open up on large-area engravings came as no surprise:

They start smaller in the more closely engraved areas:

But eventually spread over the entire surface:

They’re not always straight:

And aren’t aligned with the engraving path:

My threat model says those discs are definitely unreadable …

Although we had considerable success trapping voles during the last half of the 2024 gardening season, Mary found a description of what might be a better technique: a box with small entrance holes taking advantage of rodent thigmotaxis: their tendency to follow walls. The writeup shows nicely made wood boxes, but I no longer have machinery capable of cutting arbitrarily large wood slabs into pieces.
I do, however, have a vast pile of cardboard boxes:

That’s a rat-size trap.
A smaller box has room for two mouse-size traps (one hidden on the left):

The general idea: plunk the box in a garden plot, arm the trap(s), close the lid, and eventually a vole will venture inside, whereupon wall-following leads to disaster. Apparently bait is optional, as wall-following inevitably takes them over the trap pedal. I won’t begrudge them a walnut or two, should bait become necessary.
Cardboard is obviously the wrong material for a box in an outdoor garden, but I figure they’ll survive long enough to show feasibility and I can deploy a lot of small boxes before having to conjure something more durable.
Yes, those are laser-cut rounded-rectangle holes: 30 mm and 40 mm, assuming voles care about such things.
Edit: More on voles.

As the poster says, “Until you spread your wings, you’ll have no idea how far you can walk”:

My feet get chilly just looking:

We think the flock has a Rules Compliance Officer who gave one miscreant goose an all-around inspection:

Just another day at the office …
The WordPress AI generated an excerpt for this post:
The poster emphasizes potential discovery through exploration, while the goose flock exhibits curiosity, hinting at humorous governance among them at Vassar Sunset Lake.
I had no idea “governance” was a goose thing.