weather

Two days of proper weather, but back to climate for the weekend.

Citrus. Rain. But too late and never enough. Ask the agricultores...
Oranges ripe before mandarinas. ¿Cambio climático?

m45

 Never get this right. There are 4 hours here and still rubbish. Anyway...

open cluster m45 pleiades in taurus
veTEC571 on sv550    72x4min @ hcg100

...and finally getting the hang of stars and colour in setiastrosuitepro. 

setiastrosuitepro 1.6.1

 Quite an event. These days, this is all you need. Method for Kubuntu 25.10 but should be sufficiently generic for any modern distribution.

Big call out to Franklin and the Devs at setiastro.com

mkdir setiastrosuitepro
cd setiastrosuitepro
python3.12 -m venv venv
. venv/bin/activate
pip install --no-cache-dir setiastrosuitepro

cd venv/bin
python setiastrosuitepro  

... and yeyhhh...

upgrade
pip install setiastrosuitepro --upgrade

qscript
 I called it runsasp. Don't forget to chmod +x it.

#!/bin/bash

cd /home/steve/setiastrosuitepro

. venv/bin/activate

cd venv/bin

python setiastrosuitepro

plasma launcher

[Desktop Entry]

Comment[en_US]=sasp

Comment=sasp

Exec=/home/steve/runsasp

GenericName[en_US]=sasp

GenericName=sasp

Icon=/home/steve/sasp-dev/src/setiastro/images/astrosuite.png

MimeType=

Name[en_US]=sasp

Name=sasp

Path=

StartupNotify=true

Terminal=true

TerminalOptions=\s--noclose

Type=Application

X-KDE-SubstituteUID=false

X-KDE-Username=

winter solstice 2025

 

The sun reached it's most souttherly point, above the Tropic of Capricorn, today at 16:03 and Alicante will have its shortest day.

graxpert kubuntu 25.10

 Try GraXpert 3.1.0rc2 from here: https://github.com/Steffenhir/GraXpert/releases/tag/3.1.0rc2

Requires cuda 12 and cudnn 8

flatpak kstars allow access to filesystem

Not tested but... 

 flatpak override --user --filesystem=host org.kde.kstars

cc-build

Provisional only. I'll check and tidy this later... PROMISE 

Beg/borrow/steal the latest source you can can lay your hands on; ask Franklin, scour github, the seti Discord.,.. Or, do what I did, at least to get started...

git clone https://github.com/setiastro/cosmicclarity.git
cd cosmicclarity
python3.12 -m venv venv
pip install -r requirements.txt

At this point, you'll see how hopelessly old the git really is! So...
pip install pyinstaller xisf pyqt6 opencv-python-headless sep onnxruntime scikit-image lazy-loader

 build

pyinstaller --copy-metadata xisf setiastrocosmicclarity_darkstar.py

pyinstaller --copy-metadata xisf SetiAstroCosmicClarity.py

pyinstaller --copy-metadata xisf SetiAstroCosmicClarity_denoise.py

pyinstaller --copy-metadata xisf SetiAstroCosmicClarity_satellite.py

the _internal folder

When the .py has been built, your binary appears at e.g. dist/SetiAstroCosmicClarity/SetiAstroCosmicClarity Copy the _internal folder to the main directory along with the SetiAstroCosmicClarity binary. After the build of each module, copy the binary to the main folder and merge the respective _internal

--- --- ---

binary names
SASPro expects the following names for the binaries:
setiastrocosmicclarity_darkstar
SetiAstroCosmicClarity
SetiAstroCosmicClarity_denoise
setiastrocosmicclarity_satellite

Rename as necessary. For example:
 cp -a setiastrocosmicclaritylinux SetiAstroCosmicClarity

build isues
 getting sep recognised
copy
sep.cpython-312-x86_64-linux-gnu.so
from cosmicclarity/venv/lib64/python3.12/site-packages
to the
_internal folder in the main directory

satellite 

From the dist/SetiAstroCosmicClarity_satellitelinux/_internal 

folder, copy these:

lazy_loader
lazy_loader-0.4.dist-info 
rawpy

rawpy-0.25.1.dist-info

rawpy.libs

scikit_image-0.25.2.dist-info

scipy

scipy-1.16.3.dist-info

scipy.libs

skimage

to the _internal folder in the main directory

the ai  onnx and  pth files
Make  a new folder  to contain the binaries and  the  ai stuff. An  easy way to do this is  to  download the  current  cc  from the  setiastro site  and simply replace  the  binaries with the  ones you built AND  of  course the  _internal along with it.
 --- --- ---

.spec file to build Thanks to the setiastro discord, we now have a .spec file which builds all the binaries. Make a venv, install the requirements.txt and the other stuff listed above and pyinstaller master.spec https://discord.com/channels/1257377319765413961/1452498766757368001

The binaries and _internal folder created under dust are then dropped into an existing folder with containing theai pth and onnx files. An easy way to do this is to download the pre built cosmic clarity_linux and overwrite the respective files therein with your build. Much more elegant than my brute force and ignorance method...