SciWIn Studio is the graphical desktop companion to SciWIn-Client (s4n), the FAIRagro Scientific Workflow Infrastructure. It gives researchers a visual way to build, inspect, and run reproducible Common Workflow Language (CWL) workflows, without needing to touch a terminal.
Note
SciWIn Studio is currently in beta. Features and functionality may still change as development progresses.
Computational workflows make complex, multi-step analyses reproducible, scalable, and shareable, but authoring and running them by hand is tedious and error-prone. SciWIn Studio is a Tauri desktop application, a Rust backend paired with a SvelteKit/Svelte 5 frontend, that wraps the sciwin crate, so that creating CWL CommandLineTools and Workflows, wiring them together, and executing them is possible without ever leaving a graphical interface.
Every SciWIn Studio project is a sciwin/s4n project on disk (a workflow.toml plus a git repository), so projects created or edited in the GUI stay fully compatible with the s4n CLI and vice versa.
- Visual workflow design — arrange CWL tools on a canvas and connect their inputs and outputs with drag-and-drop, powered by
@xyflow/svelte - Tool authoring — generate new CWL
CommandLineTools from a command, container image, and arguments through a guided form - Built-in code editor — inspect and edit the underlying CWL YAML with a Monaco-powered editor, with language features (diagnostics, completion) served by an in-process
cwl-lspserver - Git-backed projects — every change is staged and committed automatically, so a project's history is always a working, versioned record
- Workflow execution — run workflows locally or remotely against a REANA instance, with credentials stored in the OS keychain and live execution logs in an in-app terminal
Tagged releases are built for Windows, macOS (Intel and Apple Silicon), and Linux and published as GitHub Releases by .github/workflows/release.yml.
SciWIn Studio is built with Tauri v2. To run it in development mode you need Node.js 22+, a recent Rust toolchain, and the native GTK/WebKit dependencies used by Tauri's desktop renderer.
On Debian/Ubuntu:
# Install native dependencies
sudo apt-get update
sudo apt-get install -y \
libgtk-3-dev \
libglib2.0-dev \
libwebkit2gtk-4.1-dev \
build-essential \
curl \
wget \
file \
libxdo-dev \
libssl-dev \
libayatana-appindicator3-dev \
librsvg2-dev
# Install frontend dependencies
npm install
# Launch SciWIn Studio in dev mode (backend + frontend, hot reload)
npx tauri devFor macOS and Windows, follow the platform-specific prerequisites in the Tauri getting started guide.
Production bundles are produced with npx tauri build. Tagged releases (v*.*.*) are built and published automatically for all platforms via tauri-apps/tauri-action (see .github/workflows/release.yml).
SciWIn Studio depends on the sciwin and commonwl crates (including cwl-lsp, commonwl's bundled CWL language server) from the main SciWIn-Client repository for project management, CWL parsing, and execution. Read the SciWIn-Client documentation to learn more about the underlying CLI, project layout, and CWL concepts shared by both tools.
Made with contrib.rocks.
| Measure 4.4 | ||
|---|---|---|
| Jens Krumsieck |  @jenskrumsieck |
ORCID: 0000-0001-6242-5846 |
| Antonia Leidel | @aleidel |
ORCID: 0009-0007-1765-0527 |
| Patrick König | @patrick-koenig |
ORCID: 0000-0002-8948-6793 |
| Xaver Stiensmeier | @XaverStiensmeier |
ORCID: 0009-0005-3274-122X |
| Harald von Waldow | @hvwaldow |
ORCID: 0000-0003-4800-2833 |
This work is dual-licensed under Apache 2.0 and MIT. You can choose between one of them if you use this work.
SPDX-License-Identifier: Apache-2.0 OR MIT