sasp debayer

Never realised it made such a difference.
Thanks to Frankin for refining these algorithms:

october galaxy and dust

Clear night but the brightest gibbous moon you can imagine. Or so it seemed. Gradients galore.

Hiindsight. Should have imaged these targets instead of the clusters and the clusters instead of these targets.

dust surrounding nebula ngc1333 in taurus
veTEC571 on sv550    80 x 4 min @ hcg100

galaxies l to r m31 m32 m110 in andromeda
veTEC571 on sv550    54 x 4 min @ hcg100

october clusters

New moon, so had a go without filter. Oh, the good old days.
Recogniosable colour without jumping through hoops.

All taken using 36 x 180s frames: veTEC-571 on sv550 @ hcg100

ngc129 in cassiopeia

clusters ngc2158 with m35 in gemini

m45 in tautus

ngc884 with ngc869 in perseo

ngc663 and friends in cassiopeia

ekos shutdown

Timing race sometinms if a flip is scheduled during shutdown. The mount is not parked.

Big thanks to @Andy on the stellarmate discord for the workaround/fix...

Hi, thanks for the log and files, that made it easy to track down.

Workaround until the fix is released: in `/home/steve/Pictures/my_queue.kstarsqueue`, add this as the first entry of the park task's `"actions"` list, before the TELESCOPE_PARK step:

    {

"type": "EVALUATE",
"device": "EQMod Mount",
"property": "EQUATORIAL_EOD_COORD",
"element": "STATE",
"property_type": 4,
"condition": 1,
"target": "Busy",
"margin": 0,
"timeout": 180,
"retries": 0,
"failure_action": 1
},

It waits until the mount has stopped slewing (max 180 s), then parks. Without a flip it passes at once, and if it ever times out the park is still sent, so it's never worse than now. In the simulator the flip finished and the mount parked. Keep a backup of the file: re-creating the park task from the template removes the extra step. In the morning, the scheduler log should show "Pre-shutdown queue completed successfully".

double cluster resolution

 Can't get the cluster stars separate. Poor optics? Poor user processing more like. At least I tried...

open clusters ngc869 left with ngc884 in perseo
veTEC571 on sv550    36x3min @ hcg100

plasmashell crash after chrome update

A recent Chrome update interferes with the fontconfig. The font cache needs to be regenerated before plasmashell starts.

So, from here:

mkdir -p ~/.config/systemd/user/plasma-plasmashell.service.d

cat > ~/.config/systemd/user/plasma-plasmashell.service.d/fontcache.conf << 'EOF' [Service]
 ExecStartPre=/usr/bin/fc-cache -f
 EOF

systemctl --user daemon-reload
 sudo reboot

Did it work?

systemctl --user status plasma-plasmashell | head -10

You should see:

Process: ExecStartPre=/usr/bin/fc-cache -f (code=exited, status=0/SUCCESS) Active: active (running)

setiastrosuitepro numpy

Setting the runtime virtual environment

 Kununtu 26.04 uses python3.14 and installs
numpy==2.5.0
which gives errors with the stacking suite alignment. The error messages suggests numpy 2.4, so...

 ...activate python3.14 venv at:
 ~/.local/share/SASpro/runtime/py314/ 

Then it's just

pip uninstall numpy
pip install numpy==2.4.4 --no-cache-dir