Geospatial

The sky,from anywhere, at any date

Stellarium, on a Void Linux desktop of your own.Set a place and a time, and look at what would have been overhead.

Stellarium 26.22 cores · 4 GBOpens in a browser tab

hub://stellarium

$ dxflow workflow create --identity stellarium hub://stellarium --start --link

01Pick a machinecores, memory and a rate per hour

02Create the workflowpulled from the hub, once

03Run it, then stopstopped when the work is done

The application

A planetarium,and a catalogue

Millions of objects, drawn where they were from where you say you stood.

Place and time

Pick coordinates and a date, forwards or back, and the sky follows.

Deep catalogues

Hipparcos and Tycho by default, with fainter sets added on the volume.

What an eyepiece sees

Telrad and ocular views, for planning a session before the night of it.

How you run it

Every defaultis one override away

The session reads its settings from the environment, so you set them on the start line.

VNC_PASSWORDWhat the tab asks for. It ships as dxflow, and everyone reading this knows that.

PANEL and TASKBARBoth hidden, so the sky has the whole screen. Show either one to get the desktop back.

AUDIOOff here. Turn it on and the desktop sound is streamed beside the picture.

start it your way

$ dxflow workflow start stellarium --override env.app.VNC_PASSWORD=something-long

$ dxflow workflow start stellarium --override env.app.TASKBAR=show --link

The session

The sky viewfills the screen

Streamed to your browser, with Stellarium already maximized.

6082Browserin the tab, at /vnc.html

5901VNCin a native client

/volumeStorageyour files, kept between runs

Open it from anywhereStart with --link and the session comes back on an HTTPS address.

Set a password firstVNC_PASSWORD defaults to dxflow, and everyone can read this page.

Good to know

The sky is drawnby the processor

Software OpenGL renders every star, so a big window costs cores rather than a graphics card.

When it feels heavy

Drop the window size or the catalogue depth. Both are the actual cost, and neither changes what you are looking at.

Any place, any date

Set a location and a time and the sky is what it was, or will be. That is the whole point of doing it in software.

Catalogues belong on the volume

A deeper star catalogue is a large download. Put it under /volume and you pay for it once.

The image

Pulled once,then it stays

Stellarium arrives as one image. This is what comes down the first time, and what the disk should have free for it.

888Mamd64compressed, the way the registry counts it

882Marm64compressed, the way the registry counts it

20GOn diskunpacked, with room to work beside it

ghcr.io/dxflow-ai/stellarium:latestPublished from the hub, pulled on the first start and kept for the ones after it.

Either architectureamd64 and arm64 are both published, and the machine pulls the one it runs.

What it asks for

What it wants,and what it needs

The definition asks for 2 cores and 4 GB. The image comes up on less than that, and a start given --fit trims the ask to whatever the machine actually has.

2 cores · 4 GBAsks forwhat the definition writes down

2 cores · 2 GBRuns onthe least the image comes up on

Not neededGPUit works on the cores alone

The ask is not the floorThe definition writes down what suits the work. The image itself starts on less, which is what the second figure is.

--fit caps it to the hostA start given --fit trims each step to what the machine actually has, for that start alone. The definition is never rewritten.

Machines that fit it

Stellarium asks for 2 cores and 4 GB. Cheapest first.

E2 Medium

$0.042/ hour2 cores · 4 GBStart this machine

T3 Medium

$0.052/ hour2 cores · 4 GBStart this machine

B2s

$0.052/ hour2 cores · 4 GBStart this machine

Run Stellarium on your own machinePick a machine that meets it, and it opens about a minute after you ask.

Start Stellarium Browse workflows