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.AppImageIf 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 libfuse2Both 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