From e6ec01d57a92e51b4b5961362742f3ce735d10da Mon Sep 17 00:00:00 2001 From: marcvivesmassana Date: Mon, 26 Jan 2026 16:34:39 +0100 Subject: [PATCH 1/3] new --- .../02.outputs-list/20.render-output.md | 311 ++++++++++++++++++ .../04.output/02.outputs-list/README.md | 6 + 2 files changed, 317 insertions(+) create mode 100644 docs/02.simulation-setup/04.output/02.outputs-list/20.render-output.md diff --git a/docs/02.simulation-setup/04.output/02.outputs-list/20.render-output.md b/docs/02.simulation-setup/04.output/02.outputs-list/20.render-output.md new file mode 100644 index 0000000..027062f --- /dev/null +++ b/docs/02.simulation-setup/04.output/02.outputs-list/20.render-output.md @@ -0,0 +1,311 @@ +# Render Output + +*Render Output in Flow360 automatically generates animations for unsteady simulations by rendering flow field visualizations. This output type creates rendered images that can be combined into animations, making it ideal for visualizing time-dependent flow phenomena such as vortex shedding, unsteady pressure waves, or moving boundaries.* + +--- + +## **Available Options** + +| *Option* | *Description* | *Applicable* | +|----------|---------------|--------------| +| **Name** | Name identifier for the render output | always | +| **Frequency** | How often to render frames | always | +| **Frequency offset** | Time step at which to start rendering | always | +| **Surface render** | Configure surface rendering groups | optional | +| **Slice render** | Configure slice rendering groups | optional | +| **IsoSurface render** | Configure isosurface rendering groups | optional | +| **Camera** | Camera/viewpoint settings for the render | optional | + +--- + +## **Important Notes** + +> **Important:** +> - Render Output is **only available for unsteady simulations**. It cannot be used with steady-state cases. + +--- + +## **Global Time Stepping in Child Cases** + +When working with **child cases** (cases forked from a parent simulation), it's important to understand that the `Frequency` and `Frequency offset` parameters refer to the **global** time step, which is transferred from the parent case. + +**Example:** If the parent case finished at `time_step=174`, the child case will start from `time_step=175`. If `Frequency=100` is set in the child case, the render will be generated at global time steps 200 (25 time steps into the child simulation), 300 (125 time steps into the child simulation), etc. `Frequency offset` also refers to the global time step, meaning that if in the previously mentioned child case, `Frequency offset=50` was set (with `Frequency=100`), the render would be generated at **global** time steps 250 (75 time steps into the child simulation), 350 (175 time steps into the child simulation), etc. + +--- + +## **Detailed Descriptions** + +### **Name** + +*An identifier for this render output configuration.* + +- **Default:** `"Render output"` +- **Example:** `"Vortex Animation"`, `"Pressure Wave Visualization"` +>**Note:** Use descriptive names when configuring multiple render outputs. + +### **Frequency** + +*Controls how often rendered frames are generated during the simulation.* + +- **Default:** `1` (render every time step) +- **Example:** `100` — renders a frame every 100 physical time steps. + - **Standalone case:** If you start a simulation from `time_step=0` with `frequency=100`, renders are generated at time steps 100, 200, 300, etc. + - **Parent-child case:** If the parent finished at `time_step=174`, the child starts from `time_step=175`. With `frequency=100` in the child, renders are generated at global time steps 200 (25 steps into child), 300 (125 steps into child), 400 (225 steps into child), etc. +>**Notes:** +> - Lower frequency values provide smoother animations but require more storage and computation. +> - Higher frequency values reduce storage but may result in choppier animations. +> - Important for child cases - this parameter refers to the **global** time step (see [Global Time Stepping](#global-time-stepping-in-child-cases)). + +### **Frequency offset** + +*Specifies the time step at which to begin rendering frames.* + +- **Default:** `0` (start at beginning of simulation) +- **Example:** `1000` — with `frequency=100`, renders are generated at time steps 1000, 1100, 1200, etc. + - **Standalone case:** If you start a simulation from `time_step=0` with `frequency=100` and `frequency_offset=1000`, renders are generated at time steps 1000, 1100, 1200, etc. + - **Parent-child case:** If the parent finished at `time_step=174`, the child starts from `time_step=175`. With `frequency=100` and `frequency_offset=200` in the child, renders are generated at global time steps 200 (25 steps into child), 300 (125 steps into child), 400 (225 steps into child), etc. +>**Notes:** +> - Useful when you want to skip initial transient flow development in animations. +> - Important for child cases - this parameter refers to the **global** time step (see [Global Time Stepping](#global-time-stepping-in-child-cases)). + +### **Surface render** + +*Configure one or more surface rendering groups. Each group can contain multiple boundaries that share the same material and visualization settings.* + +Each surface render group includes: + +- **Material:** Select the rendering material type: + - **Output fields:** Display a scalar field on the surface (e.g., `Cp`, `Cf`, `Mach`, `pressure_pa`) +- **Set output fields:** Choose which flow field variable to visualize on the surfaces +- **Colormap:** Select the color scheme for visualizing the field (e.g., rainbow, grayscale, temperature) +- **Range:** Define the minimum and maximum values for the colormap: + - **Min value:** Lower bound of the color scale + - **Max value:** Upper bound of the color scale +- **Assigned boundaries:** Select which boundary surfaces to include in this render group + - Use the search bar to find specific boundaries + - Multiple boundaries can be assigned to a single group + +>**Note:** You can create multiple surface render groups with different materials and field selections to visualize different aspects of your simulation simultaneously. + +### **Slice render** + +*Configure one or more slice rendering groups. Each group can contain multiple slices that share the same material and visualization settings.* + +Each slice render group includes: + +- **Material:** Select the rendering material type: + - **Output fields:** Display a scalar field on the slice (e.g., `Mach`, `pressure`, `T`) +- **Set output fields:** Choose which flow field variable to visualize on the slices +- **Colormap:** Select the color scheme for visualizing the field +- **Range:** Define the minimum and maximum values for the colormap +- **Assigned slices:** Select which slices to include in this render group + - Select slices from the 3D scene or from a list + - Multiple slices can be assigned to a single group + +>**Note:** Slice renders are useful for visualizing cross-sectional flow patterns and can be combined with surface renders in the same animation. + +### **IsoSurface render** + +*Configure one or more isosurface rendering groups. Each group can contain multiple isosurfaces that share the same material and visualization settings.* + +Each isosurface render group includes: + +- **Material:** Select the rendering material type: + - **Output fields:** Display a scalar field on the isosurface (e.g., `qcriterion`, `Mach`, `T`) +- **Set output fields:** Choose which flow field variable to visualize on the isosurfaces +- **Colormap:** Select the color scheme for visualizing the field +- **Range:** Define the minimum and maximum values for the colormap +- **Isosurfaces:** Define one or more isosurfaces by specifying: + - **Name:** A unique identifier for the isosurface + - **Field:** The flow variable used to define the isosurface (e.g., `qcriterion`, `Mach`) + - **Value:** The constant value of the field variable that defines the isosurface + +>**Note:** Isosurface renders are particularly useful for visualizing vortices (using Q-criterion) or shock waves (using Mach number). + +### **Camera** + +*Configure the camera/viewpoint settings for the render.* + +- **Set as current perspective:** Use the current 3D view as the camera position +- Additional camera settings may be available for fine-tuning the viewpoint + +>**Note:** The camera settings determine the viewing angle and perspective for all rendered frames in the animation. + +--- + +## **Use Cases** + +Render Output is ideal for: + +- **Vortex visualization:** Create animations showing vortex development and shedding over time +- **Pressure wave propagation:** Visualize unsteady pressure waves moving through the domain +- **Unsteady flow structures:** Capture time-dependent flow phenomena such as wake development +- **Presentation materials:** Generate high-quality animations for reports, presentations, or publications +- **Flow analysis:** Combine multiple visualization types (surfaces, slices, isosurfaces) in a single animation + +--- + +
+

💡 Tips

 + +#### Optimizing Render Output + +- **Frequency selection:** Choose an appropriate frequency based on your needs: + - For smooth animations: Use lower frequency values (e.g., 1-10) + - For storage efficiency: Use higher frequency values (e.g., 50-100) + - For presentation: Balance between smoothness and file size + +- **Field selection:** Select only the fields you need to visualize to reduce computation time + +- **Colormap range:** Set appropriate min/max values for your colormap to ensure good contrast and visibility + +- **Multiple groups:** Use multiple render groups to visualize different aspects simultaneously (e.g., pressure on surfaces and Q-criterion isosurfaces) + +#### Visualization Best Practices + +- **For pressure analysis:** Use `Cp` or `pressure_pa` on surfaces with a consistent color scale +- **For vortex identification:** Use Q-criterion isosurfaces with appropriate iso-values +- **For shock visualization:** Use Mach number isosurfaces or pressure fields +- **For boundary layer analysis:** Combine surface renders with slice renders through the boundary layer + +
+ +--- + +
+

❓ Frequently Asked Questions

 + +- **Can I use Render Output with steady simulations?** + > No, Render Output is only available for unsteady simulations. For steady simulations, use standard output types like Surface Output or Volume Output. + +- **How do I combine multiple visualization types in one animation?** + > Create multiple render groups (Surface, Slice, and/or IsoSurface) within the same Render Output configuration. Each group will be rendered together in the animation. + +- **What file format are the rendered images saved in?** + > The rendered images are typically saved in a format suitable for animation creation. Check the output directory for the specific format used. + +- **Can I change the camera position during the animation?** + > The camera position is fixed for all frames in a single Render Output. To create animations with different viewpoints, create multiple Render Output configurations with different camera settings. + +- **How do I control the quality/resolution of the rendered images?** + > Render quality settings may be available in the camera or render configuration options. Higher quality renders require more computation time. + +
+ +--- + +
+

🐍 Python API Example

 + +#### Basic Render Output + +The following example shows how to set up a render output to create an animation of pressure on surfaces and Q-criterion isosurfaces: + +```python +# Define a render output with surface and isosurface groups +render_output = fl.RenderOutput( + name="Vortex Animation", + frequency=10, # Render every 10 time steps + frequency_offset=0, # Start from beginning + groups=[ + # Surface render group for wing surfaces + fl.RenderOutputGroup( + surfaces=[volume_mesh["wing*"]], + material=fl.render.FieldMaterial.rainbow( + field="Cp", + min_value=-1.0, + max_value=1.0, + alpha=1.0 + ) + ), + # Isosurface render group for vortices + fl.RenderOutputGroup( + isosurfaces=[ + fl.Isosurface( + name="Q-criterion", + iso_value=0.001, + field="qcriterion" + ) + ], + material=fl.render.FieldMaterial.rainbow( + field="Mach", + min_value=0.0, + max_value=1.5, + alpha=0.6 + ) + ) + ], + camera=fl.render.Camera.orthographic( + scale=5, + view=fl.Viewpoint.TOP + fl.Viewpoint.LEFT + ) +) + +# Include in simulation parameters +simulation_params = fl.SimulationParams( + # ... other parameters ... + time_stepping=fl.UnsteadyTimeStepping(...), # Must be unsteady + outputs=[render_output] +) + +# Submit through project interface +project.submit_simulation(simulation_params) +``` + +#### Render Output with Multiple Groups + +Creating a render output with surface, slice, and isosurface groups: + +```python +render_output = fl.RenderOutput( + name="Multi-View Animation", + frequency=20, + groups=[ + # Surface group for pressure visualization + fl.RenderOutputGroup( + surfaces=[volume_mesh["wing*"], volume_mesh["fuselage"]], + material=fl.render.FieldMaterial.rainbow( + field="pressure_pa", + min_value=80000, + max_value=120000, + alpha=1.0 + ) + ), + # Slice group for Mach number + fl.RenderOutputGroup( + slices=[ + fl.Slice( + name="Center Slice", + normal=(0, 1, 0), + origin=(0, 0, 0) + ) + ], + material=fl.render.FieldMaterial.rainbow( + field="Mach", + min_value=0.0, + max_value=0.8, + alpha=0.8 + ) + ), + # Isosurface group for Q-criterion + fl.RenderOutputGroup( + isosurfaces=[ + fl.Isosurface( + name="Vortices", + iso_value=0.0005, + field="qcriterion" + ) + ], + material=fl.render.PBRMaterial.metal(shine=0.7) + ) + ], + camera=fl.render.Camera.orthographic(scale=10) +) + +simulation_params = fl.SimulationParams( + # ... other parameters ... + outputs=[render_output] +) +``` + +
diff --git a/docs/02.simulation-setup/04.output/02.outputs-list/README.md b/docs/02.simulation-setup/04.output/02.outputs-list/README.md index 49475f1..ea21302 100644 --- a/docs/02.simulation-setup/04.output/02.outputs-list/README.md +++ b/docs/02.simulation-setup/04.output/02.outputs-list/README.md @@ -26,6 +26,7 @@ | **[Force Output](./16.force-output.md)** | Force and moment coefficient outputs with optional statistics | Tracking aerodynamic performance, monitoring convergence | | **[Force Distribution Output](./17.force-distribution-output.md)** | Custom force and moment distribution along a specified direction | Spanwise/chordwise loading analysis, directional force analysis | | **[Time-averaging Force Distribution Output](./18.time-averaging-force-distribution-output.md)** | Time-averaged custom force and moment distribution | Statistical analysis of unsteady force distributions | +| **[Render Output](./20.render-output.md)** | Automatically rendered animations for unsteady simulations | Creating animations of time-dependent flow phenomena | --- @@ -99,5 +100,10 @@ For configuration details specific to each output type, see the individual outpu ./16.force-output.md ./17.force-distribution-output.md ./18.time-averaging-force-distribution-output.md +<<<<<<< Updated upstream +======= +./20.render-output.md +./00.output-fields.md +>>>>>>> Stashed changes ./19.output-formats.md ``` \ No newline at end of file From 4d21bfd4530ea45bdbab5436435878385115d46e Mon Sep 17 00:00:00 2001 From: marcvivesmassana Date: Mon, 26 Jan 2026 18:53:05 +0100 Subject: [PATCH 2/3] update --- ...0.render-output.md => 21.render-output.md} | 181 +++--------------- .../04.output/02.outputs-list/README.md | 7 +- 2 files changed, 28 insertions(+), 160 deletions(-) rename docs/02.simulation-setup/04.output/02.outputs-list/{20.render-output.md => 21.render-output.md} (55%) diff --git a/docs/02.simulation-setup/04.output/02.outputs-list/20.render-output.md b/docs/02.simulation-setup/04.output/02.outputs-list/21.render-output.md similarity index 55% rename from docs/02.simulation-setup/04.output/02.outputs-list/20.render-output.md rename to docs/02.simulation-setup/04.output/02.outputs-list/21.render-output.md index 027062f..4ec0fee 100644 --- a/docs/02.simulation-setup/04.output/02.outputs-list/20.render-output.md +++ b/docs/02.simulation-setup/04.output/02.outputs-list/21.render-output.md @@ -37,20 +37,14 @@ When working with **child cases** (cases forked from a parent simulation), it's ### **Name** -*An identifier for this render output configuration.* - -- **Default:** `"Render output"` -- **Example:** `"Vortex Animation"`, `"Pressure Wave Visualization"` ->**Note:** Use descriptive names when configuring multiple render outputs. +An identifier for this render output configuration. ### **Frequency** -*Controls how often rendered frames are generated during the simulation.* +*Controls how often rendered frames are generated during the simulation in physical steps.* -- **Default:** `1` (render every time step) +- **Required** Yes - **Example:** `100` — renders a frame every 100 physical time steps. - - **Standalone case:** If you start a simulation from `time_step=0` with `frequency=100`, renders are generated at time steps 100, 200, 300, etc. - - **Parent-child case:** If the parent finished at `time_step=174`, the child starts from `time_step=175`. With `frequency=100` in the child, renders are generated at global time steps 200 (25 steps into child), 300 (125 steps into child), 400 (225 steps into child), etc. >**Notes:** > - Lower frequency values provide smoother animations but require more storage and computation. > - Higher frequency values reduce storage but may result in choppier animations. @@ -76,17 +70,18 @@ Each surface render group includes: - **Material:** Select the rendering material type: - **Output fields:** Display a scalar field on the surface (e.g., `Cp`, `Cf`, `Mach`, `pressure_pa`) -- **Set output fields:** Choose which flow field variable to visualize on the surfaces -- **Colormap:** Select the color scheme for visualizing the field (e.g., rainbow, grayscale, temperature) -- **Range:** Define the minimum and maximum values for the colormap: + - **PBR material:** Physically-based rendering material with customizable properties. Options include: + - **metal:** Metallic material with customizable shine + - **plastic:** Plastic material with customizable shine +- **Set output fields:** Choose which flow field variable to visualize on the surfaces (only available when Material is "Output fields") +- **Colormap:** Select the color scheme for visualizing the field (e.g., rainbow, grayscale, temperature) (only available when Material is "Output fields") +- **Range:** Define the minimum and maximum values for the colormap (only available when Material is "Output fields"): - **Min value:** Lower bound of the color scale - **Max value:** Upper bound of the color scale - **Assigned boundaries:** Select which boundary surfaces to include in this render group - Use the search bar to find specific boundaries - Multiple boundaries can be assigned to a single group ->**Note:** You can create multiple surface render groups with different materials and field selections to visualize different aspects of your simulation simultaneously. - ### **Slice render** *Configure one or more slice rendering groups. Each group can contain multiple slices that share the same material and visualization settings.* @@ -95,15 +90,16 @@ Each slice render group includes: - **Material:** Select the rendering material type: - **Output fields:** Display a scalar field on the slice (e.g., `Mach`, `pressure`, `T`) -- **Set output fields:** Choose which flow field variable to visualize on the slices -- **Colormap:** Select the color scheme for visualizing the field -- **Range:** Define the minimum and maximum values for the colormap + - **PBR material:** Physically-based rendering material with customizable properties. Options include: + - **metal:** Metallic material with customizable shine + - **plastic:** Plastic material with customizable shine +- **Set output fields:** Choose which flow field variable to visualize on the slices (only available when Material is "Output fields") +- **Colormap:** Select the color scheme for visualizing the field (only available when Material is "Output fields") +- **Range:** Define the minimum and maximum values for the colormap (only available when Material is "Output fields") - **Assigned slices:** Select which slices to include in this render group - Select slices from the 3D scene or from a list - Multiple slices can be assigned to a single group ->**Note:** Slice renders are useful for visualizing cross-sectional flow patterns and can be combined with surface renders in the same animation. - ### **IsoSurface render** *Configure one or more isosurface rendering groups. Each group can contain multiple isosurfaces that share the same material and visualization settings.* @@ -112,9 +108,12 @@ Each isosurface render group includes: - **Material:** Select the rendering material type: - **Output fields:** Display a scalar field on the isosurface (e.g., `qcriterion`, `Mach`, `T`) -- **Set output fields:** Choose which flow field variable to visualize on the isosurfaces -- **Colormap:** Select the color scheme for visualizing the field -- **Range:** Define the minimum and maximum values for the colormap + - **PBR material:** Physically-based rendering material with customizable properties. Options include: + - **metal:** Metallic material with customizable shine + - **plastic:** Plastic material with customizable shine +- **Set output fields:** Choose which flow field variable to visualize on the isosurfaces (only available when Material is "Output fields") +- **Colormap:** Select the color scheme for visualizing the field (only available when Material is "Output fields") +- **Range:** Define the minimum and maximum values for the colormap (only available when Material is "Output fields") - **Isosurfaces:** Define one or more isosurfaces by specifying: - **Name:** A unique identifier for the isosurface - **Field:** The flow variable used to define the isosurface (e.g., `qcriterion`, `Mach`) @@ -133,18 +132,6 @@ Each isosurface render group includes: --- -## **Use Cases** - -Render Output is ideal for: - -- **Vortex visualization:** Create animations showing vortex development and shedding over time -- **Pressure wave propagation:** Visualize unsteady pressure waves moving through the domain -- **Unsteady flow structures:** Capture time-dependent flow phenomena such as wake development -- **Presentation materials:** Generate high-quality animations for reports, presentations, or publications -- **Flow analysis:** Combine multiple visualization types (surfaces, slices, isosurfaces) in a single animation - ---- -

💡 Tips

 @@ -155,19 +142,6 @@ Render Output is ideal for: - For storage efficiency: Use higher frequency values (e.g., 50-100) - For presentation: Balance between smoothness and file size -- **Field selection:** Select only the fields you need to visualize to reduce computation time - -- **Colormap range:** Set appropriate min/max values for your colormap to ensure good contrast and visibility - -- **Multiple groups:** Use multiple render groups to visualize different aspects simultaneously (e.g., pressure on surfaces and Q-criterion isosurfaces) - -#### Visualization Best Practices - -- **For pressure analysis:** Use `Cp` or `pressure_pa` on surfaces with a consistent color scale -- **For vortex identification:** Use Q-criterion isosurfaces with appropriate iso-values -- **For shock visualization:** Use Mach number isosurfaces or pressure fields -- **For boundary layer analysis:** Combine surface renders with slice renders through the boundary layer -
--- @@ -180,16 +154,6 @@ Render Output is ideal for: - **How do I combine multiple visualization types in one animation?** > Create multiple render groups (Surface, Slice, and/or IsoSurface) within the same Render Output configuration. Each group will be rendered together in the animation. - -- **What file format are the rendered images saved in?** - > The rendered images are typically saved in a format suitable for animation creation. Check the output directory for the specific format used. - -- **Can I change the camera position during the animation?** - > The camera position is fixed for all frames in a single Render Output. To create animations with different viewpoints, create multiple Render Output configurations with different camera settings. - -- **How do I control the quality/resolution of the rendered images?** - > Render quality settings may be available in the camera or render configuration options. Higher quality renders require more computation time. - --- @@ -197,114 +161,21 @@ Render Output is ideal for:

🐍 Python API Example

 -#### Basic Render Output - -The following example shows how to set up a render output to create an animation of pressure on surfaces and Q-criterion isosurfaces: - ```python -# Define a render output with surface and isosurface groups render_output = fl.RenderOutput( - name="Vortex Animation", - frequency=10, # Render every 10 time steps - frequency_offset=0, # Start from beginning + name="Render output", + frequency=10, groups=[ - # Surface render group for wing surfaces fl.RenderOutputGroup( - surfaces=[volume_mesh["wing*"]], + surfaces=[volume_mesh["*"]], material=fl.render.FieldMaterial.rainbow( field="Cp", min_value=-1.0, - max_value=1.0, - alpha=1.0 - ) - ), - # Isosurface render group for vortices - fl.RenderOutputGroup( - isosurfaces=[ - fl.Isosurface( - name="Q-criterion", - iso_value=0.001, - field="qcriterion" - ) - ], - material=fl.render.FieldMaterial.rainbow( - field="Mach", - min_value=0.0, - max_value=1.5, - alpha=0.6 + max_value=1.0 ) ) ], - camera=fl.render.Camera.orthographic( - scale=5, - view=fl.Viewpoint.TOP + fl.Viewpoint.LEFT - ) -) - -# Include in simulation parameters -simulation_params = fl.SimulationParams( - # ... other parameters ... - time_stepping=fl.UnsteadyTimeStepping(...), # Must be unsteady - outputs=[render_output] -) - -# Submit through project interface -project.submit_simulation(simulation_params) -``` - -#### Render Output with Multiple Groups - -Creating a render output with surface, slice, and isosurface groups: - -```python -render_output = fl.RenderOutput( - name="Multi-View Animation", - frequency=20, - groups=[ - # Surface group for pressure visualization - fl.RenderOutputGroup( - surfaces=[volume_mesh["wing*"], volume_mesh["fuselage"]], - material=fl.render.FieldMaterial.rainbow( - field="pressure_pa", - min_value=80000, - max_value=120000, - alpha=1.0 - ) - ), - # Slice group for Mach number - fl.RenderOutputGroup( - slices=[ - fl.Slice( - name="Center Slice", - normal=(0, 1, 0), - origin=(0, 0, 0) - ) - ], - material=fl.render.FieldMaterial.rainbow( - field="Mach", - min_value=0.0, - max_value=0.8, - alpha=0.8 - ) - ), - # Isosurface group for Q-criterion - fl.RenderOutputGroup( - isosurfaces=[ - fl.Isosurface( - name="Vortices", - iso_value=0.0005, - field="qcriterion" - ) - ], - material=fl.render.PBRMaterial.metal(shine=0.7) - ) - ], - camera=fl.render.Camera.orthographic(scale=10) -) - -simulation_params = fl.SimulationParams( - # ... other parameters ... - outputs=[render_output] + camera=fl.render.Camera.orthographic(scale=5) ) ``` diff --git a/docs/02.simulation-setup/04.output/02.outputs-list/README.md b/docs/02.simulation-setup/04.output/02.outputs-list/README.md index ea21302..dbdf18a 100644 --- a/docs/02.simulation-setup/04.output/02.outputs-list/README.md +++ b/docs/02.simulation-setup/04.output/02.outputs-list/README.md @@ -26,7 +26,7 @@ | **[Force Output](./16.force-output.md)** | Force and moment coefficient outputs with optional statistics | Tracking aerodynamic performance, monitoring convergence | | **[Force Distribution Output](./17.force-distribution-output.md)** | Custom force and moment distribution along a specified direction | Spanwise/chordwise loading analysis, directional force analysis | | **[Time-averaging Force Distribution Output](./18.time-averaging-force-distribution-output.md)** | Time-averaged custom force and moment distribution | Statistical analysis of unsteady force distributions | -| **[Render Output](./20.render-output.md)** | Automatically rendered animations for unsteady simulations | Creating animations of time-dependent flow phenomena | +| **[Render Output](./21.render-output.md)** | Automatically rendered animations for unsteady simulations | Creating animations of time-dependent flow phenomena | --- @@ -100,10 +100,7 @@ For configuration details specific to each output type, see the individual outpu ./16.force-output.md ./17.force-distribution-output.md ./18.time-averaging-force-distribution-output.md -<<<<<<< Updated upstream -======= -./20.render-output.md +./21.render-output.md ./00.output-fields.md ->>>>>>> Stashed changes ./19.output-formats.md ``` \ No newline at end of file From 3dbbcedfcdbf97cd2a4a5a73953c8ccccfee83b7 Mon Sep 17 00:00:00 2001 From: marcvivesmassana Date: Tue, 27 Jan 2026 14:10:56 +0100 Subject: [PATCH 3/3] comments --- .../04.output/02.outputs-list/21.render-output.md | 2 +- docs/02.simulation-setup/04.output/02.outputs-list/README.md | 1 - 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/02.simulation-setup/04.output/02.outputs-list/21.render-output.md b/docs/02.simulation-setup/04.output/02.outputs-list/21.render-output.md index 4ec0fee..a536f52 100644 --- a/docs/02.simulation-setup/04.output/02.outputs-list/21.render-output.md +++ b/docs/02.simulation-setup/04.output/02.outputs-list/21.render-output.md @@ -1,6 +1,6 @@ # Render Output -*Render Output in Flow360 automatically generates animations for unsteady simulations by rendering flow field visualizations. This output type creates rendered images that can be combined into animations, making it ideal for visualizing time-dependent flow phenomena such as vortex shedding, unsteady pressure waves, or moving boundaries.* +*Render Output in Flow360 automatically generates animations for unsteady simulations by rendering flow field visualizations. This output creates rendered animations, making it ideal for visualizing time-dependent flow phenomena such as vortex shedding, unsteady pressure waves, or moving boundaries.* --- diff --git a/docs/02.simulation-setup/04.output/02.outputs-list/README.md b/docs/02.simulation-setup/04.output/02.outputs-list/README.md index dbdf18a..25132e7 100644 --- a/docs/02.simulation-setup/04.output/02.outputs-list/README.md +++ b/docs/02.simulation-setup/04.output/02.outputs-list/README.md @@ -101,6 +101,5 @@ For configuration details specific to each output type, see the individual outpu ./17.force-distribution-output.md ./18.time-averaging-force-distribution-output.md ./21.render-output.md -./00.output-fields.md ./19.output-formats.md ``` \ No newline at end of file