Salpa v0.5.0

Salpa v0.5.0

Desktop application for visual scientific workflows.

Available Downloads

macOS

• Intel (x64): Salpa-0.5.0-x64.dmg
• Apple Silicon (ARM64): Salpa-0.5.0-arm64.dmg

Installation note for macOS: the app is signed with a Developer ID and notarized by
Apple. Drag it to Applications, then open it — macOS will ask once whether you are sure,
because you downloaded it from the internet. Click Open. That is all.

Do not run xattr -cr. Earlier notes advised it, from when these builds were
ad-hoc signed and macOS refused them outright. Stripping the quarantine flag from a
properly notarized app gains nothing and skips the check that would tell you the download
was tampered with.

Windows

• NSIS installer: Salpa-Setup-0.5.0.exe

Installation note for Windows: SmartScreen may warn about an unrecognized publisher. Click "More info" → "Run anyway" to proceed.

Linux

• AppImage: Salpa-0.5.0.AppImage (universal, works on most distributions)
• Debian/Ubuntu: salpa_0.5.0_amd64.deb

Installation note for Linux: an AppImage needs two things a download does not give it.

chmod +x Salpa-0.5.0.AppImage      # a download is never executable
./Salpa-0.5.0.AppImage

If it will not start and says something about mounting, you need FUSE — not installed by
default on Ubuntu 22.04 and later:

sudo apt install libfuse2

Both failures are silent in the same way: nothing happens, and no error names the cause.

First launch takes a while

Salpa builds a Python environment the first time it runs. Measured on wiped machines with
nothing cached:

	time until usable
macOS (Apple Silicon)	~40 seconds
Windows	~1.5 minutes
Linux	~2.5 minutes

The window can look idle while this happens. It is working — give it the time above before
concluding it has hung. Later launches are immediate.

Known Issues

• Windows and Linux builds are unsigned. Windows SmartScreen will warn about an
  unrecognized publisher (see above). macOS is signed and notarized.

Feedback

Please report any issues at: https://github.com/BoundaryComputing/salpa/issues

Salpa v0.4.0

Salpa v0.4.0

Desktop application for visual scientific workflows.

Available Downloads

macOS

• Intel (x64): Salpa-0.4.0-x64.dmg
• Apple Silicon (ARM64): Salpa-0.4.0-arm64.dmg

Installation note for macOS: the app is signed with a Developer ID and notarized by
Apple. Drag it to Applications, then open it — macOS will ask once whether you are sure,
because you downloaded it from the internet. Click Open. That is all.

Do not run xattr -cr. Earlier notes advised it, from when these builds were
ad-hoc signed and macOS refused them outright. Stripping the quarantine flag from a
properly notarized app gains nothing and skips the check that would tell you the download
was tampered with.

Windows

• NSIS installer: Salpa-Setup-0.4.0.exe

Installation note for Windows: SmartScreen may warn about an unrecognized publisher. Click "More info" → "Run anyway" to proceed.

Linux

• AppImage: Salpa-0.4.0.AppImage (universal, works on most distributions)
• Debian/Ubuntu: salpa_0.4.0_amd64.deb

Installation note for Linux: an AppImage needs two things a download does not give it.

chmod +x Salpa-0.4.0.AppImage      # a download is never executable
./Salpa-0.4.0.AppImage

If it will not start and says something about mounting, you need FUSE — not installed by
default on Ubuntu 22.04 and later:

sudo apt install libfuse2

Both failures are silent in the same way: nothing happens, and no error names the cause.

First launch takes a while

Salpa builds a Python environment the first time it runs. Measured on wiped machines with
nothing cached:

	time until usable
macOS (Apple Silicon)	~30 seconds
Windows	~1.5 minutes
Linux	~2.5 minutes

The window can look idle while this happens. It is working — give it the time above before
concluding it has hung. Later launches are immediate.

Known Issues

• Windows and Linux builds are unsigned. Windows SmartScreen will warn about an
  unrecognized publisher (see above). macOS is signed and notarized.

Feedback

Please report any issues at: https://github.com/BoundaryComputing/salpa/issues

Salpa v0.3.2

Salpa v0.3.2

Desktop application for visual scientific workflows.

Available Downloads

macOS

• Intel (x64): Salpa-0.3.2-x64.dmg
• Apple Silicon (ARM64): Salpa-0.3.2-arm64.dmg

Installation note for macOS: the app is signed with a Developer ID and notarized by
Apple. Drag it to Applications, then open it — macOS will ask once whether you are sure,
because you downloaded it from the internet. Click Open. That is all.

Do not run xattr -cr. Earlier notes advised it, from when these builds were
ad-hoc signed and macOS refused them outright. Stripping the quarantine flag from a
properly notarized app gains nothing and skips the check that would tell you the download
was tampered with.

Windows

• NSIS installer: Salpa-Setup-0.3.2.exe

Installation note for Windows: SmartScreen may warn about an unrecognized publisher. Click "More info" → "Run anyway" to proceed.

Linux

• AppImage: Salpa-0.3.2.AppImage (universal, works on most distributions)
• Debian/Ubuntu: salpa_0.3.2_amd64.deb

Installation note for Linux: an AppImage needs two things a download does not give it.

chmod +x Salpa-0.3.2.AppImage      # a download is never executable
./Salpa-0.3.2.AppImage

If it will not start and says something about mounting, you need FUSE — not installed by
default on Ubuntu 22.04 and later:

sudo apt install libfuse2

Both failures are silent in the same way: nothing happens, and no error names the cause.

First launch takes a while

Salpa builds a Python environment the first time it runs. Measured on wiped machines with
nothing cached:

	time until usable
macOS (Apple Silicon)	~30 seconds
Windows	~1.5 minutes
Linux	~2.5 minutes

The window can look idle while this happens. It is working — give it the time above before
concluding it has hung. Later launches are immediate.

Known Issues

• Windows and Linux builds are unsigned. Windows SmartScreen will warn about an
  unrecognized publisher (see above). macOS is signed and notarized.

Feedback

Please report any issues at: https://github.com/BoundaryComputing/salpa/issues

Salpa v0.3.1

Salpa v0.3.1

Desktop application for visual scientific workflows.

Available Downloads

macOS

• Intel (x64): Salpa-0.3.1-x64.dmg
• Apple Silicon (ARM64): Salpa-0.3.1-arm64.dmg

Installation note for macOS: the app is signed with a Developer ID and notarized by
Apple. Drag it to Applications, then open it — macOS will ask once whether you are sure,
because you downloaded it from the internet. Click Open. That is all.

Do not run xattr -cr. Earlier notes advised it, from when these builds were
ad-hoc signed and macOS refused them outright. Stripping the quarantine flag from a
properly notarized app gains nothing and skips the check that would tell you the download
was tampered with.

Windows

• NSIS installer: Salpa-Setup-0.3.1.exe

Installation note for Windows: SmartScreen may warn about an unrecognized publisher. Click "More info" → "Run anyway" to proceed.

Linux

• AppImage: Salpa-0.3.1.AppImage (universal, works on most distributions)
• Debian/Ubuntu: salpa_0.3.1_amd64.deb

Installation note for Linux: an AppImage needs two things a download does not give it.

chmod +x Salpa-0.3.1.AppImage      # a download is never executable
./Salpa-0.3.1.AppImage

If it will not start and says something about mounting, you need FUSE — not installed by
default on Ubuntu 22.04 and later:

sudo apt install libfuse2

Both failures are silent in the same way: nothing happens, and no error names the cause.

First launch takes a while

Salpa builds a Python environment the first time it runs. Measured on wiped machines with
nothing cached:

	time until usable
macOS (Apple Silicon)	~30 seconds
Windows	~1.5 minutes
Linux	~2.5 minutes

The window can look idle while this happens. It is working — give it the time above before
concluding it has hung. Later launches are immediate.

Known Issues

• Windows and Linux builds are unsigned. Windows SmartScreen will warn about an
  unrecognized publisher (see above). macOS is signed and notarized.

Feedback

Please report any issues at: https://github.com/BoundaryComputing/salpa/issues

Salpa v0.3.0

Salpa v0.3.0

Desktop application for visual scientific workflows.

What changed in this release

Two changes to what the app does with your data. They are called out here rather than
left to a changelog because https://salpa.app/privacy states them publicly, and a promise
made on the website should be visible in the release that keeps it.

• The app no longer sends usage statistics. Preview builds up to and including 0.2.3
  reported anonymous usage events — the app being opened, screens being viewed — to
  Google Analytics, with a random installation identifier. Never your account details,
  workflows, or data. That code is gone.
• The sign-in dialog links the Terms of Service and Privacy Policy
  (terms, privacy).

Available Downloads

macOS

• Intel (x64): Salpa-0.3.0-x64.dmg
• Apple Silicon (ARM64): Salpa-0.3.0-arm64.dmg

Installation note for macOS: the app is signed with a Developer ID and notarized by
Apple. Drag it to Applications, then open it — macOS will ask once whether you are sure,
because you downloaded it from the internet. Click Open. That is all.

Do not run xattr -cr. Earlier notes advised it, from when these builds were
ad-hoc signed and macOS refused them outright. Stripping the quarantine flag from a
properly notarized app gains nothing and skips the check that would tell you the download
was tampered with.

Windows

• NSIS installer: Salpa-Setup-0.3.0.exe

Installation note for Windows: SmartScreen may warn about an unrecognized publisher. Click "More info" → "Run anyway" to proceed.

Linux

• AppImage: Salpa-0.3.0.AppImage (universal, works on most distributions)
• Debian/Ubuntu: salpa_0.3.0_amd64.deb

Installation note for Linux: an AppImage needs two things a download does not give it.

chmod +x Salpa-0.3.0.AppImage      # a download is never executable
./Salpa-0.3.0.AppImage

If it will not start and says something about mounting, you need FUSE — not installed by
default on Ubuntu 22.04 and later:

sudo apt install libfuse2

Both failures are silent in the same way: nothing happens, and no error names the cause.

First launch takes a while

Salpa builds a Python environment the first time it runs. Measured on wiped machines with
nothing cached:

	time until usable
macOS (Apple Silicon)	~30 seconds
Windows	~1.5 minutes
Linux	~2.5 minutes

The window can look idle while this happens. It is working — give it the time above before
concluding it has hung. Later launches are immediate.

Known Issues

• Windows and Linux builds are unsigned. Windows SmartScreen will warn about an
  unrecognized publisher (see above). macOS is signed and notarized.

Feedback

Please report any issues at: https://github.com/BoundaryComputing/salpa/issues

Salpa 0.2.3

Two fixes here can stop Salpa working entirely. If you are on Windows, or your
Mac has Redis installed, this release matters.

Salpa could refuse to start. On macOS and Linux it preferred a system Redis
over its own bundled one, chosen by whatever was on PATH when it launched — and
that differs between opening from the Dock and launching from a terminal. On a
machine with a newer Redis installed alongside, one launch could save state the
other could never read, after which every start failed with "Redis failed to
start within timeout". It now always uses the Redis it ships with, and if it
ever finds a saved state it cannot read, it moves that file aside and tells you,
instead of refusing to open.

On Windows, nothing would run on a fresh install. Executing any node returned
a 500. The Redis client resolved for new installations expects a newer Redis than
the one bundled for Windows, so every connection was rejected. Existing Windows
installations were unaffected, which is why this went unreported — it only broke
for people installing Salpa for the first time.

Also in this release:

• Stop now works on Windows. Cancelling a running node terminates the whole
  process tree, verified on real hardware.
• Stop tells the truth. Six places where it did the right thing and reported
  the wrong one: a workflow stop that said "stopped" before asking, a Job Queue
  that said nothing at all, and cancelled jobs that vanished from every counter.
• The connection recovers. The app used to give up reconnecting after five
  attempts — about fifteen seconds — and stay silent. It now keeps trying, and
  reconnects immediately when your network returns or you come back to the tab.

Salpa 0.2.2

An upgraded app can now see the Salpa Hub.

If you installed Salpa before the Hub became the official package source, your app
kept pointing at the old, private catalog URL after every upgrade. It failed in
the most convincing way possible: the request 404s, the Marketplace falls back to
the bundled copy and stays populated, and the source keeps reporting a fresh
"last synced" time on every launch. Nothing looked wrong — you just never saw
anything published after the day you installed.

Salpa now repairs that on startup. It also drops the stale local fallback that
kept the failure quiet in the first place.

Also in this release:

• Multi-node packages installed through /api/marketplace/install now stage their
  shared environment, instead of silently falling back to running without it.
• "Flush queue" now clears cancelled jobs too, rather than leaving them on the
  Jobs page after a flush that claimed to clear everything.

Nothing here changes how workflows run. If your app is working, this is a quiet
upgrade; if your Marketplace has looked frozen for a while, this is the fix.

Salpa 0.2.1

Three fixes since 0.2.0.

Apple Silicon now installs packages that ship x86_64 builds. Packages such as
metaldock-vwf depend on tools with no arm64 build anywhere (AutoDock 4, MGLTools).
Salpa used to refuse these on Apple Silicon outright. It now installs them, and macOS
runs them through Rosetta. If Rosetta is missing, Salpa says so and gives you the exact
command:

softwareupdate --install-rosetta --agree-to-license

That check matters more than it looks: pixi does not verify Rosetta before falling back,
so without it a Mac lacking Rosetta would report a successful install whose every
binary then fails to launch. Intel Macs and Linux are unchanged.

A stale environment is no longer trusted because it exists. After an update, Salpa
verifies that its Python environment resolves inside the running build, and rebuilds it
if not, instead of silently running an older version's code.

Copilot installs packages the same way every other path does, through the shelf.

Salpa v0.2.0

Salpa 0.2.0

If you installed a package before this update, reinstall it once

Some packages — including the metal docking package and the cloud nodes — kept part of their setup inside the Salpa application itself. Updating Salpa replaces the application, so that part is lost and those nodes stop working.

Open the Marketplace and install the package again. It takes a minute, you only need to do it once, and it cannot happen again: setup now lives with your data rather than inside the app.

Startup and shutdown, rebuilt

The screens Salpa shows while it starts and stops have been redesigned, and they now tell you what is actually happening:

• If the backend fails to start, you are told. Previously you were dropped into an app that looked fine and did nothing. You now see which step failed and why, and you can view the log, retry, or quit.
• Real progress, step by step, instead of a spinner.
• The log is readable from the startup screen, including what happened before you opened it.

You can stop a running job

Stop now actually stops the work, including anything it started.

Worked examples can come with a written guide

A package can include a short guide alongside its example workflow, readable inside Salpa on the screen where you choose it — the author's own notes and figures, rather than just a diagram.

Also in this release

• Salpa stays correctly signed after you install and use it. Previously it modified itself as it ran, which could make macOS refuse to open a copy of it later.
• Faster, quieter startup.

Good to know

• The metal docking package needs an Intel Mac or Linux. The docking tools it depends on have no Apple Silicon version yet, so Salpa will tell you rather than fail partway through.
• Updating Salpa does not update your installed packages. If a newer version of a package is available, reinstall it from the Marketplace.

Salpa v0.1.6

Salpa v0.1.6

Desktop application for visual scientific workflows.

Available Downloads

macOS

• Intel (x64): Salpa-0.1.6-x64.dmg
• Apple Silicon (ARM64): Salpa-0.1.6-arm64.dmg

Installation note for macOS: the app is signed with a Developer ID and notarized by
Apple. Drag it to Applications, then open it — macOS will ask once whether you are sure,
because you downloaded it from the internet. Click Open. That is all.

Do not run xattr -cr. Earlier notes advised it, from when these builds were
ad-hoc signed and macOS refused them outright. Stripping the quarantine flag from a
properly notarized app gains nothing and skips the check that would tell you the download
was tampered with.

Windows

• NSIS installer: Salpa-Setup-0.1.6.exe

Installation note for Windows: SmartScreen may warn about an unrecognized publisher. Click "More info" → "Run anyway" to proceed.

Linux

• AppImage: Salpa-0.1.6.AppImage (universal, works on most distributions)

Installation note for Linux: an AppImage needs two things a download does not give it.

chmod +x Salpa-0.1.6.AppImage      # a download is never executable
./Salpa-0.1.6.AppImage

If it will not start and says something about mounting, you need FUSE — not installed by
default on Ubuntu 22.04 and later:

sudo apt install libfuse2

Both failures are silent in the same way: nothing happens, and no error names the cause.

First launch takes a while

Salpa builds a Python environment the first time it runs. Measured on wiped machines with
nothing cached:

	time until usable
macOS (Apple Silicon)	~30 seconds
Windows	~1.5 minutes
Linux	~2.5 minutes

The window can look idle while this happens. It is working — give it the time above before
concluding it has hung. Later launches are immediate.

Known Issues

• Windows and Linux builds are unsigned. Windows SmartScreen will warn about an
  unrecognized publisher (see above). macOS is signed and notarized.

Feedback

Please report any issues at: https://github.com/BoundaryComputing/salpa/issues