fluidsim
FluidSim is a Python framework for computational fluid dynamics simulations using pseudospectral methods with FFT acceleration. Use it to run Navier-Stokes equations in 2D or 3D, shallow water equations, stratified flows, or analyze turbulence and vortex dynamics, with built-in support for high-performance computing via MPI parallelization and comprehensive post-processing capabilities.
git clone --depth 1 https://github.com/K-Dense-AI/scientific-agent-skills /tmp/fluidsim && cp -r /tmp/fluidsim/skills/fluidsim ~/.claude/skills/fluidsimSKILL.md
# FluidSim Use FluidSim 0.9.0 as a framework for Python-defined numerical solvers, especially periodic Cartesian pseudospectral CFD. Upstream FluidSim is CeCILL-2.1; the MIT frontmatter license applies only to this skill. This skill does **not** treat a completed run, a stable time step, a smooth plot, or a closed program exit as evidence of numerical convergence or physical validity. ## Required workflow 1. State equations, units or nondimensionalization, geometry, boundaries, initial conditions, forcing, observables, and acceptance criteria. 2. Select a verified solver and inspect its generated default parameters. 3. Create a strict JSON plan with explicit CPU, RAM, disk, wall-time, output-file, timestep, CFL, resolution, and dealiasing bounds. 4. Run the bundled validator and resource estimator. 5. Generate and review a dry-run script. It does nothing unless executed with an explicit config-ID acknowledgement. 6. Run one tiny serial pilot. Inspect budgets, divergence/constraints, spectral tails, CFL/time-step history, and output growth. 7. Refine grid and time step independently. Check conservation/budget residuals and observable sensitivity. 8. Only then prepare a site-specific MPI job. Never submit or launch MPI automatically. 9. Preserve config, script, `uv.lock`, package/platform/backend versions, logs, output inventory, checksums, and restart lineage. Stop if physical assumptions, units, boundary conditions, forcing semantics, resolution criteria, resource limits, or acceptance criteria are missing. ## Version and installation As verified on 2026-07-23: - Latest stable PyPI release: `fluidsim==0.9.0` (2025-12-04). - Package metadata requires Python `>=3.11` and lists Python 3.11–3.14. - Pseudospectral parameter creation needs FluidFFT; bare `fluidsim` imported in the smoke test, but `ns2d.create_default_params()` failed until the `fft` extra was installed. - Current companion versions tested here: `fluidfft==0.4.5` and `pyFFTW==0.15.1`. Prefer a project lock: ```bash uv init --python 3.11 uv add "fluidsim[fft]==0.9.0" "fluidfft==0.4.5" "pyFFTW==0.15.1" uv lock uv sync --frozen ``` For an isolated disposable environment: ```bash uv venv --python 3.11 uv pip install "fluidsim[fft]==0.9.0" "fluidfft==0.4.5" "pyFFTW==0.15.1" ``` The project lock is the reproducibility record; direct pins alone do not freeze all transitive artifacts. Do not reuse a lock across incompatible platforms or MPI ABIs. MPI is optional and native: ```bash uv add "mpi4py==4.1.2" "fluidfft-mpi-with-fftw==0.0.1" "fluidfft-fftwmpi==0.0.1" uv lock ``` Those packages still require a compatible MPI runtime and FFTW development libraries. The optional native plugins are: - `fluidfft-fftw==0.0.1`: sequential `fft2d.with_fftw1d`, `fft2d.with_fftw2d`, `fft3d.with_fftw3d`. - `fluidfft-mpi-with-fftw==0.0.1`: MPI `fft2d.mpi_with_fftw1d`, `fft3d.mpi_with_fftw1d`. - `fluidfft-fftwmpi==0.0.1`: MPI-enabled FFTW `fft2d.mpi_with_fftwmpi2d`, `fft3d.mpi_with_fftwmpi3d`. - `fluidfft-p3dfft==0.0.1`: `fft3d.mpi_with_p3dfft`; requires P3DFFT. - FluidFFT also declares PFFT and P3DFFT extras; audit and pin their native stacks for the target cluster. FluidFFT documents cuFFT historically, but FluidFFT 0.4.5 declares no CUDA extra or installed GPU plugin in its package metadata, and its CUDA installation page is unfinished. Do not claim GPU acceleration or install an unrelated CUDA wheel as a FluidSim backend. Treat GPU work as source-level experimental integration requiring separate validation. See [installation](references/installation.md) for system dependencies, MPI ABI, HDF5-MPI, backend discovery, and verification. ## API snapshot Use direct, versioned imports: ```python from fluidsim.solvers.ns2d.solver import Simul params = Simul.create_default_params() params.oper.nx = params.oper.ny = 32 params.oper.Lx = params.oper.Ly = 2 * 3.141592653589793 params.oper.coef_dealiasing = 2 / 3 params.time_stepping.USE_CFL = True params.time_stepping.cfl_coef = 0.5 params.time_stepping.deltat0 = 0.001 params.time_stepping.deltat_max = 0.01 params.time_stepping.t_end = 0.1 params.time_stepping.max_elapsed = "00:05:00" params.init_fields.type = "noise" params.init_fields.noise.velo_max = 0.01 params.output.HAS_TO_SAVE = False params.output.ONLINE_PLOT_OK = False ``` Important 0.9 corrections: - CFL field: `params.time_stepping.cfl_coef`, not `CFL`. - Time-correlated forcing: `params.forcing.tcrandom.time_correlation`, not a flat `tcrandom_time_correlation`. - NS2D default initial types include `constant`, `noise`, `jet`, `dipole`, `from_file`, `from_simul`, and `in_script`; do not invent a universal list for every solver. - Output state files default to `state_phys_t*.nc`; spectra use `spectra1D.h5`/`spectra2D.h5`; scalar means are solver-dependent `spatial_means.txt` or JSON-lines. - `params.output.sub_directory` is relative under `FLUIDSIM_PATH`. `ParamContainer` rejects undeclared attributes. Always generate defaults from the selected `Simul` class and inspect them before changing values. See [parameters](references/parameters.md). ## Solvers Primary Cartesian CFD keys and imports: ```python from fluidsim.solvers.ns2d.solver import Simul # ns2d from fluidsim.solvers.ns2d.bouss.solver import Simul # ns2d.bouss from fluidsim.solvers.ns2d.strat.solver import Simul # ns2d.strat from fluidsim.solvers.ns3d.solver import Simul # ns3d from fluidsim.solvers.ns3d.bouss.solver import Simul # ns3d.bouss from fluidsim.solvers.ns3d.strat.solver import Simul # ns3d.strat ``` The 0.9 registry also includes `plate2d`, `sw1l` variants, `waves2d`, 1D models, 0D models, spherical solvers, and framework adapters. Availability in the registry does not make a solver appropriate for a scientific question. Verify equations, variables, geometry, boundaries, and diagnostics in the solver source. See [solvers](references/solvers.md). ## Forcing and time advancement Forcing is solve
How to use the Adaptyv Bio Foundry API and Python SDK for protein experiment design, submission, and results retrieval. Use this skill whenever the user mentions Adaptyv, Foundry API, protein binding assays, protein screening experiments, BLI/SPR assays, thermostability assays, or wants to submit protein sequences for experimental characterization. Also trigger when code imports `adaptyv`, `adaptyv_sdk`, or `FoundryClient`, or references `foundry-api-public.adaptyvbio.com`.
This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Infer gene regulatory networks (GRNs) from gene expression data using scalable algorithms (GRNBoost2, GENIE3). Use when analyzing transcriptomics data (bulk RNA-seq, single-cell RNA-seq) to identify transcription factor-target gene relationships and regulatory interactions. Supports distributed computation for large-scale datasets.
Core Python library for astronomy and astrophysics workflows that need Astropy APIs, including units/quantities, coordinates, FITS I/O, tables, time systems, WCS, and cosmology. Use when implementing or debugging astronomical data analysis code with Astropy.
Observe the user's screen via screenpipe, detect repeated research workflows, match them against existing scientific-agent-skills, and draft new skills (or composition recipes that chain existing ones) for the patterns not yet covered. Use when the user asks to analyze their recent work and propose skills based on what they actually do. Requires the screenpipe daemon (https://github.com/screenpipe/screenpipe) running locally on port 3030 — the skill has no other data source and will refuse to run if screenpipe is unreachable. All detection runs locally; only redacted cluster summaries reach the LLM.
Benchling Python SDK and REST API integration for registry entities, inventory, ELN entries, workflows, Benchling Apps, and Data Warehouse queries. Use when automating lab data with benchling-sdk or the v2 API.
Search scientific papers and retrieve structured experimental data extracted from full-text studies via the BGPT MCP server. Returns 25+ fields per paper including methods, results, sample sizes, quality scores, and conclusions. Use for literature reviews, evidence synthesis, and finding experimental details not available in abstracts alone.