FlowSlider: CFD & Generative Methods
- FlowSlider is a term for two distinct methods in CFD and generative modeling, each defined by unique mathematical frameworks and evaluation criteria.
- In computational fluid dynamics, FlowSlider employs a mortar-based sliding interface for DGSEM that ensures conservation, free-stream preservation, and efficient MPI communication.
- In generative modeling, FlowSlider enables training-free continuous image editing via a fidelity-steering decomposition that maintains edit fidelity while allowing slider-style control.
FlowSlider is a term that appears in two distinct technical contexts in the arXiv literature. In computational fluid dynamics, it denotes a high-order, mortar-based sliding-mesh interface for DGSEM, introduced as an efficient implementation for discontinuous Galerkin compressible Navier–Stokes solvers and demonstrated in large-scale turbomachinery LES (Dürrwächter et al., 2020). In generative modeling, it denotes a training-free method for continuous image editing in Rectified Flow, based on a fidelity-steering decomposition of FlowEdit’s update that enables slider-style control without post-training (Endo et al., 2 Apr 2026). The shared name therefore refers not to a single framework, but to two domain-specific constructions with different mathematical objects, implementation constraints, and evaluation criteria.
1. Name, scope, and disciplinary usage
In the current literature represented here, “FlowSlider” names two separate methods.
| Usage | Domain | Core characterization |
|---|---|---|
| FlowSlider | Computational fluid dynamics | High-order, mortar-based sliding-mesh interface for DGSEM |
| FlowSlider | Generative modeling | Training-free continuous image editing via fidelity-steering decomposition |
The CFD usage is embedded in the theory and implementation of sliding meshes for deformed domains, where different parts of the domain are in relative motion. Its primary concerns are non-conforming interface coupling, conservation, free-stream preservation, and efficient MPI communication in a dynamically changing mesh topology. The image-editing usage is embedded in Rectified Flow-based prompt-pair editing on real images, where the central problem is continuous edit-strength control under fidelity constraints.
A recurrent source of ambiguity is therefore terminological rather than methodological. The two methods share a label but operate on different state spaces: DG face and mortar representations in one case, and latent ODE trajectories and guided velocity fields in the other.
2. Mortar-based sliding interfaces for DGSEM
In the CFD setting, FlowSlider is defined as a high-order, mortar-based sliding-mesh interface for DGSEM with minimal overhead in both computation and MPI communication (Dürrwächter et al., 2020). At each non-conforming interface between a static and a moving sub-domain, a layer of 2D mortar elements is introduced, and each DG face is split into two mortars . The coupling consists of three operations: projecting the DG solution, and its gradients for viscous terms, from the face onto the mortars; computing a unique numerical flux via a Riemann solver on each mortar; and projecting that flux back onto the two faces.
For the projection , with denoting the 1D Lagrange basis on at the Gauss–Lobatto nodes, the face representation is written as
On the mortar , a local coordinate is introduced, with a linear mapping depending on the hanging-node position . The un-weighted 0 projection onto 1 yields
2
where
3
The operator 4 depends only on 5 and 6 and can be precomputed for planar interfaces or assembled on the fly for curved ones.
For the back-projection 7, after computing a unique flux 8 on the mortar, FlowSlider enforces
9
which yields
0
For straight faces, conservation follows because 1 and 2 are exact for polynomials of degree 3, so that
4
The free-stream test is also exact: for 5, one has 6 for all 7, and therefore
8
with back-projection again returning 9. This establishes constant-state preservation on plane interfaces.
3. Three-dimensional algorithmics, MPI workflow, and scaling
For the general curved-interface case, FlowSlider represents surface mortars as 2D curved patches. In DGSEM, each mortar is represented by tensor-product polynomials of degree 0 in both mortar directions, and the 2D projections decompose into two successive 1D operations along each coordinate line (Dürrwächter et al., 2020). In the planar-interface specialization, interfaces are Cartesian in one movement-parallel direction and possibly curved in the other two. If the movement is pure rotation about a fixed axis or pure translation, hanging-node positions 1 are identical for all faces at a given time, so 2 and 3 are shared.
The implementation uses explicit connectivity and storage structures. Each static face is indexed by 4, and each mortar has a sub-index 5. A one-to-one map 6 stores process-local ordering. The principal arrays are 7, 8, 9, and 0. The parameter 1 is updated every stage or time-step; if 2 crosses 3, hanging indices 4 shift by one and the sorting is recomputed only then.
Parallelization emphasizes a priori communication partner determination. During initialization, for each static face 5, the MPI rank 6 of the adjacent moving-subdomain process is looked up and broadcast, and the moving side stores 7. This global exchange is performed once. To satisfy the conditions that partners and message size are known a priori, data are contiguous, and ordering is identical on send and receive, a local index array 8 of tuples 9 is built and sorted lexicographically by 0. The sorted column index is 1, which defines both packing of 2 before MPI_Isend and unpacking of incoming 3 after MPI_Irecv. The inverse map 4 is retained for fast packing and unpacking during projection.
The per-stage or per-time-step workflow computes local 5; checks whether 6 has changed and, if so, recomputes 7 and the sorting; interpolates 8 using 9; exchanges replica and primary data by nonblocking MPI; overlaps the exchange with local DG interior work; waits for the arrival of 0; computes the mortar flux 1 on the static side via a Riemann solver; exchanges flux data; and finally projects 2 on the moving side and 3 on the static side.
Performance data were reported on Hazel Hen, a Cray XC40 with 24 cores per node, at DG order 4. Strong scaling up to 12 288 cores achieved efficiency 5 for 6 DOF/core. Weak scaling from 36 to 288 elements/core achieved efficiency 7. Relative to static DGSEM, PID degrades by approximately 8 due to ALE flux and mortar operations. Additional memory scales as 9, and for a typical rotor-stator partition it adds approximately 0–1 to total memory.
4. Validation and turbomachinery application
The CFD FlowSlider was validated by both analytical and application-oriented studies (Dürrwächter et al., 2020). In a 2D isentropic vortex crossing a curved interface, 2 errors of 3 at 4 showed rates approximately 5 for 6. In a 3D manufactured sine wave with a planar sliding interface, 7 errors at 8 recovered full order. These results support the stated high-order accuracy of the mortar-based interface treatment.
A large-scale practical application was a wall-resolved implicit LES of the 1½-stage Aachen turbine. The mesh comprised 966 288 hexahedral elements, 24 layers in span, 5th-order curved geometry, and approximately 208 M DOF with sixth-order polynomials. Sliding interfaces were placed between stator–rotor and rotor–stator, with periodicity in pitch. Boundary conditions were measured inflow 9 at the stator inlet, pressure outflow with sponge, and adiabatic no-slip walls. Time integration used a 4-stage low-storage RK scheme with 0, 1, 2, and 3.
The reported compute cost was approximately 27 000 CPU h per rotor period on 4800 cores, with 4. Phase-averaged surface pressure on stator 1, rotor, and stator 2 matched URANS and experiments at trailing edges. Instantaneous 5-isosurfaces revealed transition on the stator suction side, wake–rotor interaction, and vortex shedding. Rotor blade lift versus phase showed maxima and minima when the stator wake impinged on the pressure side and suction side, and the lift spectrum exhibited a dominant 3rd harmonic of the blade-passing frequency and peaks near stator-wake shedding frequency.
Taken together, these results support the concluding characterization that the mortar approach achieves high-order accuracy 6 across moving interfaces, provable conservation and free-stream preservation, excellent strong and weak scaling with only approximately 7 overhead, and practical utility in expensive LES of turbomachinery.
5. Continuous image editing in Rectified Flow
In the generative-modeling setting, FlowSlider is a training-free method for continuous image editing in Rectified Flow that requires no post-training (Endo et al., 2 Apr 2026). Rectified Flow models define a learnable ODE via the straight-line interpolation
8
with learned velocity 9. Conditioning by classifier-free guidance is written as
0
where 1 is the guidance scale.
The immediate precursor is FlowEdit, which extends Rectified Flow from single-prompt generation to prompt-pair editing 2 on real images without inversion. At each integration time 3, FlowEdit forms a noisy source state
4
maintains an edit trajectory 5 initialized to 6 at the chosen edit-start step, anchors a target state
7
computes the difference update
8
and advances 9 by 00.
The motivation for FlowSlider is that FlowEdit, at its default strength 01, produces high-fidelity edits, but naively scaling 02 by 03 amplifies both semantic change and residual noise, leading to artifacts and drift, including ringing and structural collapse. FlowSlider addresses this by introducing an additional term 04 and decomposing
05
In compact form,
06
with
07
and
08
Within this formulation, the fidelity term 09 acts as a source-conditioned stabilizer because both velocities use the same prompt 10 and differ only in state, while the steering term 11 isolates the cross-prompt velocity difference at the same state 12. The strength-parameterized update is then defined as
13
or, in shorthand,
14
This recovers FlowEdit exactly at 15 and permits attenuated edits for 16 and amplified edits for 17 without retraining.
6. Fidelity-steering geometry, inference-time procedure, and empirical behavior
A central claim of the image-editing FlowSlider is geometric: the instantaneous angle 18 between 19 and 20 is measured by
21
and empirically clusters near 22 (Endo et al., 2 Apr 2026). Under the scaled update 23, the squared norm becomes
24
When 25, varying 26 changes the steering magnitude almost independently of the fidelity component. The reported projections are
27
and
28
which formalize the claim that steering grows linearly in 29 while fidelity remains stable.
Implementation is entirely at inference time. At each solver step, three guided velocity fields are evaluated: 30, 31, and 32. Relative to FlowEdit’s two calls, this adds one extra network call but introduces no new weights and no training. With 33 ODE steps, as in the experiments, and one RK2 or Euler step per 34, the velocity evaluations are the only stated overhead. The operational loop initializes 35 and 36 at 37; for 38, recomputes 39, forms 40, computes 41 and 42, forms 43, and updates 44 before returning 45.
The experiments used FLUX.1-dev and Stable Diffusion 3 Medium as Rectified Flow backbones. Evaluation included a 250-image continuous-editing benchmark spanning season, weather, decay, style, and portrait attributes, together with PIE-Bench general editing for out-of-distribution evaluation. Edit quality was measured by CLIP-dir and DreamSim, while slider behavior was measured by Monotonicity, defined as the fraction of consecutive 46 steps where CLIP-T47 and DreamSim48, and by Smoothness, defined as the worst-case normalized triangle deficit over LPIPS distances. Baselines included learning-based sliders, namely Kontinuous Kontext and SliderEdit, as well as heuristic alternatives such as CFG-scale tuning, edit-window tuning 49, naive 50 scaling, and linear interpolation of velocities.
On the FLUX.1 backbone, averaged over 51, FlowSlider achieved the highest 52 and lowest 53, together with top-tier edit quality at 54 and 55. Qualitatively, it yielded artifact-free, smoothly intensifying edits across the stated tasks. The paper identifies several advantages: no fine-tuning, no extra data, plug-in compatibility with Rectified Flow editors, exact recovery of FlowEdit at 56, and bidirectional editing by 57. It also states clear limitations: at very large 58, orthogonality breaks down and structure can collapse, so practical 59 is recommended; and discrete concept changes such as “rabbit 60 cat” saturate at 61, after which further scaling yields artifacts. The stated future directions are adaptive step-size or higher-order integrators, combination with learned inversion or latent-space adapters, and extension to multi-instruction editing by decomposing additional steering axes in a similar fidelity-steering subspace.