Analytics

Figuresa journal accepts

Veusz, on an Ubuntu desktop of your own.Build the figure by hand, or generate the same one from Python.

Veusz 4.12 cores · 4 GBOpens in a browser tab

hub://veusz

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

Draw it once,then script it

Every click has an equivalent in the Python API, so a figure repeats.

Publication output

Vector PDF, EPS and SVG with the fonts and line weights a journal asks for.

The same plot from code

Import veusz as a library and redraw the figure when the data changes.

Pages and insets

Grids, shared axes and insets, each a node in a tree you can go back to.

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 plot window 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 veusz --override env.app.VNC_PASSWORD=something-long

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

The session

The plot windowfills the screen

Streamed to your browser, with Veusz 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 documentis a text file

A Veusz plot is saved as a script, which is why the same figure can be rebuilt without you.

Read it, diff it, keep it

The saved document is plain text. It goes into version control beside the analysis that made the numbers.

Built on Ubuntu

Void has no Veusz package, so this entry sits on the Ubuntu desktop instead of the usual base.

Figures belong on the volume

Export PDF, EPS or SVG under /volume and the journal-ready file is still there next time.

The image

Pulled once,then it stays

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

538Mamd64compressed, the way the registry counts it

524Marm64compressed, the way the registry counts it

20GOn diskunpacked, with room to work beside it

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

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

Start Veusz Browse workflows