Analytics

MATLAB code,without the licence

GNU Octave's editor and console, on a Void Linux desktop of your own.Run the .m files you already have, and plot from the same window.

GNU Octave 11.1.02 cores · 4 GBOpens in a browser tab

hub://octave

$ dxflow workflow create --identity octave hub://octave --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

The languageyou already write

Octave takes MATLAB syntax, so most scripts run unchanged.

Matrices first

Linear algebra, ODEs, optimization and statistics are in the language itself.

Plots in the window

Figures draw in the session and export to PNG, PDF or SVG on the volume.

Or no window at all

octave --no-gui runs the same script from a shell when nobody needs to watch.

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 editor 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 octave --override env.app.VNC_PASSWORD=something-long

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

The session

The editorfills the screen

Streamed to your browser, with Octave 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

A desktop you canwalk away from

The GUI is one way in. The same image runs the same script with nobody watching.

Two ways to drive it

Sit in the editor, or open a shell and run octave --no-gui against a script. Same Octave, same volume, same results.

Built on Void

A small desktop underneath, which is why the image stays under half a gigabyte.

Figures belong on the volume

Export to PNG, PDF or SVG under /volume and the plot outlives the machine that drew it.

The image

Pulled once,then it stays

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

440Mamd64compressed, the way the registry counts it

436Marm64compressed, the way the registry counts it

20GOn diskunpacked, with room to work beside it

ghcr.io/dxflow-ai/octave: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

GNU Octave 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 GNU Octave on your own machinePick a machine that meets it, and it opens about a minute after you ask.

Start GNU Octave Browse workflows