@pikaa-ai/pikaa 0.2.5 → 0.3.1

package/skills/fluidsim/SKILL.md

@@ -0,0 +1,279 @@
+---
+name: fluidsim
+description: Plan, configure, inspect, restart, and analyze bounded FluidSim computational-fluid-dynamics simulations with explicit numerical-validity and HPC safety checks. Use for FluidSim solver selection, parameter review, FFT/MPI setup, output diagnostics, or restart compatibility.
+license: MIT
+compatibility: Bundled CLIs require Python 3.11+ and use the standard library; HDF5/netCDF4 metadata tools lazily use h5py when available. Simulation examples target fluidsim 0.9.0, fluidfft 0.4.5, and pyFFTW 0.15.1. MPI/native FFT use requires a site-compatible MPI implementation, development headers, FFTW/PFFT/P3DFFT libraries, compilers, and an approved scheduler workflow. No GPU backend is assumed.
+allowed-tools: Read Write Bash Glob Python
+metadata:
+  version: "1.1"
+  skill-author: "K-Dense Inc."
+  last-reviewed: "2026-07-23"
+---
+
+# 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 solver-specific. A current normalized random example is:
+
+```python
+params.forcing.enable = True
+params.forcing.type = "tcrandom"
+params.forcing.forcing_rate = 1.0
+params.forcing.nkmin_forcing = 4
+params.forcing.nkmax_forcing = 5
+params.forcing.tcrandom.time_correlation = "based_on_forcing_rate"
+```
+
+Record the forced variable, normalization definition, wave-number band, random
+seed/state, injection target, and measured injection. FluidSim 0.9 saves state
+parameters for restart; 0.8.6 fixed time-correlated forcing restart behavior.
+
+Available pseudospectral schemes include Euler/RK2 phase-shift variants,
+`RK2_trapezoid`, and `RK4`. A named order does not establish accuracy. Check CFL,
+fast-wave/diffusive limits, `deltat_max`, and time-step refinement. See
+[advanced features](references/advanced_features.md).
+
+## Outputs, loading, and restart
+
+For read-only analysis:
+
+```python
+from fluidsim import load_sim_for_plot
+
+sim = load_sim_for_plot("run-directory", hide_stdout=True)
+sim.output.spatial_means.plot()
+sim.output.spectra.plot1d()
+sim.output.phys_fields.plot(time=1.0)
+```
+
+`load_sim_for_plot` uses a coarse operator and disables saving/online plotting.
+For a state-bearing object:
+
+```python
+from fluidsim import load_state_phys_file
+
+sim = load_state_phys_file("run-directory", t_approx="last")
+```
+
+For a controlled restart, prefer `load_for_restart` or first run
+`fluidsim-restart --only-check`. Do not use `--modify-params` with untrusted text:
+the upstream CLI executes Python code supplied to that option. This skill's
+generator never emits it. Verify solver, grid/domain, state variables, versions,
+forcing state, checksum, target time, output destination, and resource bounds.
+Resolution changes require the dedicated reviewed workflow, not a silent grid
+edit. See [simulation workflow](references/simulation_workflow.md) and
+[output analysis](references/output_analysis.md).
+
+## Scientific acceptance gate
+
+Before interpreting results, require:
+
+- Explicit dimensional units or a complete nondimensionalization map.
+- Correct equations, periodic geometry/boundaries, initial state, forcing, and
+  diagnostic definitions.
+- Resolution and dealiasing evidence: spectra/tails, resolved gradients, and
+  solver-appropriate small-scale criteria.
+- Timestep evidence: CFL history, fastest-wave and dissipative limits, and
+  smaller-step comparison.
+- Conservation and budget checks including forcing, dissipation, transfers, and
+  residuals.
+- Grid/time refinement with uncertainty or sensitivity for reported
+  observables.
+- Comparison to an analytical solution, manufactured solution, benchmark, or
+  independently reproduced result where appropriate.
+- Complete provenance and restart lineage.
+
+Never label a run “DNS,” “converged,” “validated,” “steady,” or “physically
+correct” from parameter values or plots alone.
+
+## Bundled local tools
+
+All tools emit strict JSON, reject URLs/traversal/symlinks, enforce hard bounds,
+use no network or subprocess, and never launch a simulation:
+
+```bash
+python3 scripts/solver_config_validator.py --example
+python3 scripts/solver_config_validator.py --config config.json
+python3 scripts/grid_resource_estimator.py --config config.json
+python3 scripts/simulation_dry_run.py --config config.json --output run.py
+python3 scripts/output_inventory.py --path run-directory
+python3 scripts/budget_summary.py --path run-directory
+python3 scripts/restart_compatibility.py --source state.nc --target-config config.json
+```
+
+The HDF5 tools lazily require `h5py`, inspect bounded metadata/hyperslabs, and
+never follow external links or load full field arrays.
+
+## References
+
+- [Installation and FFT/MPI backends](references/installation.md)
+- [Solver registry and selection](references/solvers.md)
+- [Simulation, pilot, and restart workflow](references/simulation_workflow.md)
+- [Verified parameter surface](references/parameters.md)
+- [Output, plotting, and budget analysis](references/output_analysis.md)
+- [Forcing, operators, MPI, and migrations](references/advanced_features.md)
+
+## Dated upstream basis
+
+Verified 2026-07-23 against
+[PyPI 0.9.0](https://pypi.org/project/fluidsim/),
+[FluidSim 0.9 docs](https://fluidsim.readthedocs.io/en/latest/),
+[release notes](https://fluidsim.readthedocs.io/en/latest/changes.html),
+[official source mirror](https://github.com/fluiddyn/fluidsim),
+[FluidFFT 0.4.5 docs](https://fluidfft.readthedocs.io/en/latest/), and the
+primary FluidSim ([DOI 10.5334/jors.239](https://doi.org/10.5334/jors.239))
+and FluidFFT ([DOI 10.5334/jors.238](https://doi.org/10.5334/jors.238))
+papers. API claims use official docs/source; method/performance claims in the
+references are scoped to the cited primary papers and their benchmark setups.

package/skills/fluidsim/references/advanced_features.md

@@ -0,0 +1,347 @@
+# Forcing, operators, MPI, extensions, and migrations
+
+## Forcing architecture
+
+FluidSim assembles forcing classes through the selected solver's registry.
+NS2D 0.9 advertises:
+
+- `in_script`
+- `in_script_coarse`
+- `pseudo_spectral`
+- `proportional`
+- `tcrandom`
+- `tcrandom_anisotropic`
+
+Availability and default forced variable are solver-specific.
+
+Base fields:
+
+```python
+params.forcing.enable = True
+params.forcing.type = "tcrandom"
+params.forcing.forcing_rate = 1.0
+params.forcing.key_forced = None
+params.forcing.nkmin_forcing = 4
+params.forcing.nkmax_forcing = 5
+params.forcing.tcrandom.time_correlation = "based_on_forcing_rate"
+```
+
+Current source converts `nkmin_forcing`/`nkmax_forcing` to dimensional
+wave-number bounds using the operator's wave-number spacing. Inspect the
+resulting forced region; the integers are not necessarily physical wave
+numbers.
+
+### Normalization
+
+Current normalized-forcing fields include:
+
+```python
+params.forcing.normalized.constant_rate_of = None
+params.forcing.normalized.type = "2nd_degree_eq"
+params.forcing.normalized.which_root = "minabs"
+```
+
+The implementation can solve a quadratic normalization so the time-step-mean
+injection of a quadratic quantity matches `forcing_rate`. The exact quadratic
+quantity and key depend on the solver/forced field. Therefore:
+
+- State the intended injected invariant and units.
+- Confirm `key_forced`.
+- Measure forcing power in output.
+- Check the global/spectral budget using the same convention.
+- Test time-step sensitivity of the measured injection.
+
+Do not call `forcing_rate` “energy input” without verifying the selected class.
+
+### Time-correlated random forcing
+
+The 0.9 field is:
+
+```python
+params.forcing.tcrandom.time_correlation = "based_on_forcing_rate"
+```
+
+or a finite time value. Current source derives the default period as a power of
+the forcing rate and stores two random seeds plus the last-change time in state
+parameters. FluidSim 0.9.0 writes these state parameters into restart files;
+0.8.6 fixed a time-correlated forcing restart bug.
+
+For reproducibility, preserve:
+
+- Initial random seed strategy.
+- Saved forcing state parameters.
+- MPI rank count/decomposition and package versions.
+- Correlation-time setting and measured autocorrelation.
+- Restart boundary diagnostics.
+
+### In-script forcing
+
+Use the solver's registered `InScriptForcing*` interface and documented
+`compute_forcing_fft_each_time` or coarse equivalent. Do not monkey-patch a
+method with a lambda copied from an old example:
+
+- State keys have changed in some solvers.
+- Local spectral layout depends on FFT/MPI backend.
+- Hermitian/reality constraints and normalization must be preserved.
+- A literal global Fourier index is not portable across decompositions.
+
+Implement a reviewed subclass/extension with unit tests on tiny sequential and
+MPI layouts. Validate zero-net/target injection, symmetry, and budget effects.
+
+## Operators and array ownership
+
+`sim.oper` provides solver-selected grids, FFT/IFFT, differentiation, vector
+calculus, projections, spectra, dealiasing, and distributed-array helpers.
+Method names and array layouts depend on operator class.
+
+Never assume:
+
+- Axis order from `nx`, `ny`, `nz`.
+- Full global arrays on every rank.
+- A Fourier mode has the same local index under another backend/rank count.
+- All FFT backends use the same spectral shape.
+- A gathered array fits rank-0 memory.
+- Direct NumPy sums have the same normalization as
+  `oper.sum_wavenumbers`.
+
+Use documented operator methods and inspect:
+
+```python
+print(type(sim.oper))
+print(sim.oper.axes)
+print(sim.params.oper)
+```
+
+For custom diagnostics, test sequential and distributed shapes and compare
+against analytical transforms at tiny resolution.
+
+## Dealiasing
+
+The common Cartesian field is:
+
+```python
+params.oper.coef_dealiasing = 2 / 3
+params.oper.truncation_shape = "cubic"
+```
+
+FluidSim also implements phase-shift time schemes. A coefficient or scheme name
+does not prove alias removal for a custom nonlinearity. Verify:
+
+- Polynomial/nonlinear form and expected alias interactions.
+- Where dealiasing is applied.
+- Truncation geometry.
+- Spectral tails and invariant transfer.
+- Results under stricter truncation or exact phase-shift method.
+
+Do not combine an aggressive cutoff and high-order dissipation merely to obtain
+a visually smooth spectrum.
+
+## Time schemes
+
+Documented pseudospectral names:
+
+- `Euler`
+- `Euler_phaseshift`
+- `Euler_phaseshift_random`
+- `RK2`
+- `RK2_trapezoid`
+- `RK2_phaseshift`
+- `RK2_phaseshift_random`
+- `RK2_phaseshift_random_split`
+- `RK2_phaseshift_exact`
+- `RK4`
+
+The implementation treats linear terms with exact coefficients in its
+pseudospectral stepper and evaluates nonlinear tendencies according to the
+named scheme. Verify source and solver coupling before making an order/stability
+claim.
+
+Always check:
+
+- Advective CFL.
+- Wave frequency limits (stratification, rotation, shallow-water waves).
+- Diffusive/hyperdiffusive limits.
+- Forcing correlation and output cadence relative to `deltat`.
+- Smaller `cfl_coef`/`deltat_max` comparison.
+
+`USE_CFL=True` only activates the solver's CFL logic; it does not guarantee all
+accuracy/stability constraints are resolved.
+
+## Custom initial conditions
+
+`in_script` gives direct control, but use current state keys:
+
+1. Construct `Simul` with `init_fields.type = "in_script"`.
+2. Inspect the solver's state documentation/keys.
+3. Fill canonical physical or spectral variables.
+4. Call the documented conversion in the correct direction.
+5. Apply projection/dealiasing/constraints as required.
+6. Save an initialization checkpoint and verify budgets before stepping.
+
+Old examples that fill `vx`/`vy` and then call a
+spectral-to-physical conversion can overwrite the intended state. NS2D 0.9
+documentation shows physical keys including `ux`, `uy`, and `rot`; use the
+selected solver's actual keys.
+
+## Extending a solver
+
+FluidSim's `InfoSolver`/class registry supports extensions. For a research
+extension:
+
+- Pin FluidSim/FluidSim Core source and version.
+- Subclass the closest solver and extend default parameters through the current
+  class mechanism.
+- Register state variables, operators, initialization, forcing, outputs, and
+  restart state explicitly.
+- Define nonlinear tendencies with documented sign and normalization.
+- Add unit/manufactured-solution tests and budget identities.
+- Test serialization/restart and old/new parameter merging.
+- Benchmark only after correctness tests.
+
+Avoid private-method snippets from old versions without source review.
+
+## FluidFFT backend selection
+
+Installed methods are entry points. Discover them:
+
+```python
+from fluidfft import get_methods
+
+print(sorted(get_methods(ndim=2)))
+print(sorted(get_methods(ndim=3)))
+```
+
+Set per run:
+
+```python
+params.oper.type_fft = "fft2d.with_pyfftw"
+```
+
+or use `FLUIDSIM_TYPE_FFT2D`/`FLUIDSIM_TYPE_FFT3D` before process start.
+Record actual method and plugin distribution.
+
+FluidFFT's 2019 primary paper demonstrates:
+
+- Unified C++/Python APIs for multiple FFT libraries.
+- One-dimensional and pencil/two-dimensional MPI decompositions.
+- Hardware/shape/process-count-dependent fastest methods.
+- Scaling beyond the limits of slab decomposition in the tested cases.
+
+Do not transfer its fastest-method or wall-time numbers to current hardware.
+Benchmark a bounded representative shape in the target environment.
+
+## MPI planning and safety
+
+Never call `mpirun`, `mpiexec`, `srun`, `qsub`, `sbatch`, OAR tools, or a
+FluidDyn cluster submitter automatically.
+
+Required preflight:
+
+- Written resource estimate and output estimate.
+- Approved allocation and partition/account.
+- Exact MPI implementation/ABI and launcher.
+- FFT plugin/native library compatibility.
+- Rank/thread placement and oversubscription check.
+- Per-rank local shapes and no zero-sized unsupported decomposition.
+- Memory/rank and rank-0 gather/output risk.
+- Wall-time signal/checkpoint behavior.
+- Filesystem quota, inode count, stripe policy, and cleanup.
+- Tiny serial then two-rank smoke.
+- Restart plan with immutable parent state.
+
+Output behavior can differ with MPI-enabled h5py. Standard h5py usually causes
+rank 0 to write assembled state; MPI h5py can use an `mpio` driver. Verify the
+locked h5py build and output path with a tiny test.
+
+## Parametric studies
+
+Do not loop over simulations and start them directly in one script by default.
+Instead:
+
+1. Materialize one strict config per case.
+2. Assign a stable case ID and seed.
+3. Validate/estimate each case.
+4. Sum aggregate CPU, memory concurrency, disk, files, and wall time.
+5. Generate scripts only.
+6. Review sampling design and avoid changing multiple factors ambiguously.
+7. Submit through an approved external workflow.
+8. Track failures/missing cases without silently resampling.
+
+Analyze observables with refinement and stochastic uncertainty, not only final
+values.
+
+## Checkpoint and restart
+
+Physical-state saving is checkpoint creation:
+
+```python
+params.output.periods_save.phys_fields = 1.0
+```
+
+But checkpoint usability requires:
+
+- Complete `/state_phys` datasets.
+- `/info_simul/params` and solver metadata.
+- 0.9 state parameters where needed.
+- Matching solver/grid/domain/state.
+- SHA-256 and parent lineage.
+- Enough disk for parent and child.
+
+Use the bundled compatibility checker before every continuation. A mechanically
+compatible state can still be scientifically invalid after changed viscosity,
+forcing, timestep, backend, or resolution.
+
+## Migration notes to 0.9.0
+
+### 0.9.0 (release notes dated 2025-12-03)
+
+- Restart files store state parameters.
+- Added basic physical-field utilities.
+- Fixed restart filenames.
+- Improved post-initialization information and profile analysis.
+
+### 0.8.6 (2025-11-23)
+
+- h5netcdf 1.7 compatibility.
+- Fixed incorrect restart for time-correlated forcing.
+
+### 0.8.5 (2025-10-23)
+
+- Python 3.14 support.
+
+### 0.8.2 (2024-08-17)
+
+- Python 3.12, NumPy 2.0, and mpi4py 4.0 compatibility.
+
+### 0.8.0 (2024-01-31)
+
+- Meson/meson-python build system.
+
+Practical migrations from the previous skill:
+
+- Python baseline: `>=3.11`, not `>=3.9` for 0.9.0.
+- Use exact `fluidsim==0.9.0` and lock dependencies.
+- Pseudospectral defaults need the `fft` extra.
+- Use `time_stepping.cfl_coef`, not `CFL`.
+- Use `forcing.tcrandom.time_correlation`, not a flat field.
+- Use `plate2d`, not `fvk`.
+- Physical states default to `.nc`, not `.h5`; spectra remain `.h5`.
+- Use `spect_energy_budg.h5`, not a timestamped budget glob.
+- Prefer `load_for_restart`/`fluidsim-restart --only-check`; preserve state
+  parameters and hashes.
+- Do not advertise ParaView direct compatibility without an explicit tested
+  conversion/plugin.
+
+## Sources (verified 2026-07-23)
+
+- [FluidSim forcing base source](https://github.com/fluiddyn/fluidsim/blob/branch/default/fluidsim/base/forcing/base.py).
+- [Specific forcing source](https://github.com/fluiddyn/fluidsim/blob/branch/default/fluidsim/base/forcing/specific.py).
+- [Pseudospectral time-step API](https://fluidsim.readthedocs.io/en/latest/generated/fluidsim.base.time_stepping.pseudo_spect.html).
+- [FluidSim development tutorial](https://fluidsim.readthedocs.io/en/latest/ipynb/tuto_dev.html).
+- [FluidSim release notes](https://fluidsim.readthedocs.io/en/latest/changes.html).
+- [FluidFFT plugins](https://fluidfft.readthedocs.io/en/latest/plugins.html).
+- [FluidFFT supported libraries](https://fluidfft.readthedocs.io/en/latest/install/fft_libs.html).
+- Mohanan et al., [FluidFFT primary paper](https://doi.org/10.5334/jors.238),
+  published 2019-04-01.
+- Mohanan et al., [FluidSim primary paper](https://doi.org/10.5334/jors.239),
+  published 2019-04-26.