ansys-fluent-core 0.34.1__tar.gz → 0.35.dev0__tar.gz

{ansys_fluent_core-0.34.1 → ansys_fluent_core-0.35.dev0}/.ci/fluent_test_runner.py

@@ -46,7 +46,7 @@ def _run_single_test(
     logging.debug(f"journal_file: {journal_file}")
     src_pyfluent_dir = str(Path(pyfluent.__file__).parent)
     verion_for_file_name = FluentVersion.current_dev().number
-    dst_pyfluent_dir = f"/ansys_inc/v{verion_for_file_name}/commonfiles/CPython/3_10/linx64/Release/python/lib/python3.10/site-packages/ansys/fluent/core"
+    dst_pyfluent_dir = f"/ansys_inc/v{verion_for_file_name}/commonfiles/CPython/3_10/linx64/Release/Ansys/PyFluentCore/ansys/fluent/core"
     src_gen_dir = (
         Path(pyfluent.__file__).parent / "ansys" / "fluent" / "core" / "generated"
     )
@@ -71,7 +71,7 @@ def _run_single_test(
 
     docker_client = docker.from_env()
     version_for_image_tag = FluentVersion.current_dev().docker_image_tag
-    image_name = f"ghcr.io/ansys/pyfluent:{version_for_image_tag}"
+    image_name = f"ghcr.io/ansys/fluent:{version_for_image_tag}"
     container = docker_client.containers.run(
         image=image_name,
         volumes=[

{ansys_fluent_core-0.34.1 → ansys_fluent_core-0.35.dev0}/.ci/pull_fluent_image.py

@@ -2,21 +2,19 @@
 Pull a Fluent Docker image based on the FLUENT_IMAGE_TAG environment variable.
 """
 
-import os
 import subprocess
 
+from ansys.fluent.core import config
 from ansys.fluent.core.docker.utils import get_ghcr_fluent_image_name
 
 
 def pull_fluent_image():
     """Pull Fluent Docker image and clean up dangling images."""
-    fluent_image_tag = os.getenv("FLUENT_IMAGE_TAG", "latest")
-    image_name = (
-        f"ghcr.io/ansys/fluent@{fluent_image_tag}"
-        if fluent_image_tag.startswith("sha256")
-        else f"{get_ghcr_fluent_image_name(fluent_image_tag)}:{fluent_image_tag}"
-    )
-    subprocess.run(["docker", "pull", image_name], check=True)
+    fluent_image_tag = config.fluent_image_tag
+    image_name = get_ghcr_fluent_image_name(fluent_image_tag)
+    separator = "@" if fluent_image_tag.startswith("sha256") else ":"
+    full_image_name = f"{image_name}{separator}{fluent_image_tag}"
+    subprocess.run(["docker", "pull", full_image_name], check=True)
     subprocess.run(["docker", "image", "prune", "-f"], check=True)
 
 

{ansys_fluent_core-0.34.1 → ansys_fluent_core-0.35.dev0}/.github/workflows/ci.yml

@@ -246,7 +246,6 @@ jobs:
   build:
     name: Build
     if: ${{ !contains(github.event.pull_request.title, '[skip tests]') }}
-    needs: test-import
     runs-on: [self-hosted, pyfluent]
 
     steps:
@@ -429,17 +428,13 @@ jobs:
         if: steps.cache-api-code.outputs.cache-hit != 'true'
         run: make docker-pull
         env:
-          # FLUENT_IMAGE_TAG: ${{ vars.FLUENT_STABLE_IMAGE_DEV }}
-          # Temporary until the stable image tag is update for the new image path
-          FLUENT_IMAGE_TAG: v26.1.latest
+          FLUENT_IMAGE_TAG: ${{ vars.FLUENT_STABLE_IMAGE_DEV }}
 
       - name: Run 26.1 API codegen
         if: steps.cache-api-code.outputs.cache-hit != 'true'
         run: make api-codegen
         env:
-          # FLUENT_IMAGE_TAG: ${{ vars.FLUENT_STABLE_IMAGE_DEV }}
-          # Temporary until the stable image tag is update for the new image path
-          FLUENT_IMAGE_TAG: v26.1.latest
+          FLUENT_IMAGE_TAG: ${{ vars.FLUENT_STABLE_IMAGE_DEV }}
 
       - name: Print 26.1 Fluent version info
         run: |
@@ -494,9 +489,7 @@ jobs:
             version: 261
     timeout-minutes: 60
     env:
-      # FLUENT_IMAGE_TAG: ${{ matrix.version == 261 && vars.FLUENT_STABLE_IMAGE_DEV || matrix.image-tag }}
-      # Temporary until the stable image tag is update for the new image path
-      FLUENT_IMAGE_TAG: ${{ matrix.image-tag }}
+      FLUENT_IMAGE_TAG: ${{ matrix.version == 261 && vars.FLUENT_STABLE_IMAGE_DEV || matrix.image-tag }}
 
     steps:
       - uses: actions/checkout@v4

{ansys_fluent_core-0.34.1 → ansys_fluent_core-0.35.dev0}/.github/workflows/test-podman-compose.yml

@@ -19,7 +19,6 @@ env:
   ANSYSLMD_LICENSE_FILE: ${{ format('1055@{0}', secrets.LICENSE_SERVER) }}
   PYFLUENT_TIMEOUT_FORCE_EXIT: 30
   PYFLUENT_LAUNCH_CONTAINER: 1
-  PYFLUENT_USE_PODMAN_COMPOSE: 1
   PYFLUENT_LOGGING: "DEBUG"
   PYFLUENT_WATCHDOG_DEBUG: "OFF"
   PYFLUENT_HIDE_LOG_SECRETS: 1

{ansys_fluent_core-0.34.1 → ansys_fluent_core-0.35.dev0}/CONTRIBUTORS.md

@@ -31,6 +31,7 @@
 * [Mainak Kundu](https://github.com/mkundu1)
 * [Maxime Rey](https://github.com/MaxJPRey)
 * [mcgoldba](https://github.com/mcgoldba)
+* [Muhammed Adedigba](https://github.com/moe-ad)
 * [Oleg Chernukhin](https://github.com/ochernuk)
 * [Patrick Lagace](https://github.com/lagacep-ans)
 * [Pierre Lulé](https://github.com/plule-ansys)

{ansys_fluent_core-0.34.1 → ansys_fluent_core-0.35.dev0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: ansys-fluent-core
-Version: 0.34.1
+Version: 0.35.dev0
 Summary: PyFluent provides Pythonic access to Ansys Fluent.
 Author-email: "ANSYS, Inc." <pyansys.core@ansys.com>
 Maintainer-email: "ANSYS, Inc." <pyansys.core@ansys.com>

{ansys_fluent_core-0.34.1 → ansys_fluent_core-0.35.dev0}/codegen/allapigen.py

@@ -3,7 +3,7 @@
 import argparse
 from time import time
 
-from ansys.fluent.core import CODEGEN_OUTDIR, FluentMode, FluentVersion, launch_fluent
+from ansys.fluent.core import FluentMode, FluentVersion, config, launch_fluent
 from ansys.fluent.core.codegen import StaticInfoType, allapigen
 from ansys.fluent.core.codegen.print_fluent_version import print_fluent_version
 from ansys.fluent.core.search import _generate_api_data
@@ -61,7 +61,7 @@ if __name__ == "__main__":
         )
     t1 = time()
     print(f"\nTime to fetch static info: {t1 - t0:.2f} seconds")
-    CODEGEN_OUTDIR.mkdir(parents=True, exist_ok=True)
+    config.codegen_outdir.mkdir(parents=True, exist_ok=True)
     print_fluent_version(solver._app_utilities)
     solver.exit()
     parser = argparse.ArgumentParser(

{ansys_fluent_core-0.34.1 → ansys_fluent_core-0.35.dev0}/doc/api_rstgen.py

@@ -1,8 +1,90 @@
 """Provides a module for generating PyFluent API RST files."""
 
+import os
 from pathlib import Path
 import shutil
 
+from ansys.fluent.core import FluentVersion
+
+api_contents_path = (
+    Path(__file__).parents[0].resolve() / "source" / "api" / "api_contents.rst"
+)
+fluent_version = FluentVersion.current_release()
+
+
+def _write_rst_file(output_path: str, version: str):
+    content = f""".. _ref_api:
+
+API reference
+=============
+
+This API reference corresponds to {version}. PyFluent maintains strong backward compatibility guarantees, so scripts targeting older Ansys versions are expected to work without modification.
+
+This is PyFluent's class and function reference. Please refer to the :ref:`ref_user_guide` for
+full guidelines on their use.
+
+All the public APIs for PyFluent are listed in the left hand margin. Some key APIs are mentioned below:
+
+Meshing mode
+------------
+
+The following interfaces are specific to meshing mode.
+
+* :ref:`meshing <ref_meshing_datamodel_meshing>`
+* :ref:`PartManagement <ref_meshing_datamodel_part_management>`
+* :ref:`PMFileManagement <ref_meshing_datamodel_pm_file_management>`
+* :ref:`workflow <ref_meshing_datamodel_workflow>`
+* :ref:`meshing utilities <ref_meshing_datamodel_meshing_utilities>`
+
+Solution mode
+-------------
+
+The solver :ref:`settings API <ref_root>` is the main interface for controlling and running the solver.
+
+
+.. toctree::
+    :maxdepth: 2
+    :hidden:
+    :caption: ansys.fluent.core
+
+    docker/docker_contents
+    filereader/filereader_contents
+    launcher/launcher_contents
+    meshing/meshing_contents
+    scheduler/scheduler_contents
+    services/services_contents
+    solver/solver_contents
+    streaming_services/streaming_services_contents
+    utils/utils_contents
+    data_model_cache
+    exceptions
+    file_session
+    field_data_interfaces
+    fluent_connection
+    journaling
+    logger
+    module_config
+    parametric
+    rpvars
+    search
+    session_base_meshing
+    session_meshing
+    session_pure_meshing
+    session_solver_icing
+    session_solver_lite
+    session_solver
+    session
+    session_utilities
+    system_coupling
+    pyfluent_warnings
+    workflow
+    deprecated_apis
+"""
+
+    os.makedirs(os.path.dirname(output_path), exist_ok=True)
+    with open(output_path, "w", encoding="utf-8") as f:
+        f.write(content)
+
 
 def _get_folder_path(folder_name: str):
     """Get folder path.
@@ -105,6 +187,7 @@ hierarchy = {
         "setup_for_fluent",
     ],
     "other": [
+        "module_config",
         "exceptions",
         "file_session",
         "field_data_interfaces",
@@ -198,4 +281,5 @@ def _generate_api_index_rst_files():
 
 
 if __name__ == "__main__":
+    _write_rst_file(api_contents_path, fluent_version)
     _generate_api_index_rst_files()

{ansys_fluent_core-0.34.1 → ansys_fluent_core-0.35.dev0}/doc/deprecated_pyfluent_apis.py

@@ -251,4 +251,15 @@ PYFLUENT_DEPRECATED_DATA = [
         "0.23.dev0",
         "`surfaces`",
     ),
+    # Environment variables
+    (
+        "The `PYFLUENT_USE_DOCKER_COMPOSE` environment variable",
+        "0.34.0",
+        "``use_docker_compose`` argument of :py:func:`ansys.fluent.core.launcher.launcher.launch_fluent <ansys.fluent.core.launcher.launcher.launch_fluent>`",
+    ),
+    (
+        "The `PYFLUENT_USE_PODMAN_COMPOSE` environment variable",
+        "0.34.0",
+        "``use_podman_compose`` argument of :py:func:`ansys.fluent.core.launcher.launcher.launch_fluent <ansys.fluent.core.launcher.launcher.launch_fluent>`",
+    ),
 ]

{ansys_fluent_core-0.34.1 → ansys_fluent_core-0.35.dev0}/doc/make.bat

@@ -47,7 +47,7 @@ goto end
 :clean
 echo Cleaning build directories...
 rmdir /s /q %BUILDDIR% > NUL 2>&1
-del /q %SOURCEDIR%\examples\* > NUL 2>&1
+rmdir /s /q %SOURCEDIR%\examples > NUL 2>&1
 rmdir /s /q %SOURCEDIR%\api\meshing\datamodel > NUL 2>&1
 rmdir /s /q %SOURCEDIR%\api\meshing\tui > NUL 2>&1
 rmdir /s /q %SOURCEDIR%\api\solver\datamodel > NUL 2>&1

{ansys_fluent_core-0.34.1 → ansys_fluent_core-0.35.dev0}/doc/settings_rstgen.py

@@ -28,6 +28,7 @@ from pathlib import Path
 
 from deprecated_pyfluent_apis import PYFLUENT_DEPRECATED_DATA
 
+from ansys.fluent.core import config
 from ansys.fluent.core.search import search
 from ansys.fluent.core.utils.fluent_version import (
     FluentVersion,
@@ -285,9 +286,7 @@ if __name__ == "__main__":
     if not os.path.exists(rst_dir):
         os.makedirs(rst_dir)
 
-    image_tag = os.getenv(
-        "FLUENT_IMAGE_TAG", FluentVersion.current_dev().docker_image_tag
-    )
+    image_tag = config.fluent_image_tag
     version = get_version_for_file_name(image_tag.lstrip("v"))
     settings = importlib.import_module(
         f"ansys.fluent.core.generated.solver.settings_{version}"

{ansys_fluent_core-0.34.1 → ansys_fluent_core-0.35.dev0}/doc/source/changelog.rst

@@ -9,21 +9,118 @@ This document contains the release notes for the project.
 
 .. towncrier release notes start
 
-`0.34.1 <https://github.com/ansys/pyfluent/releases/tag/v0.34.1>`_ - August 04, 2025
-====================================================================================
+`0.35.dev0 <https://github.com/ansys/pyfluent/releases/tag/v0.35.dev0>`_ - August 12, 2025
+==========================================================================================
 
 .. tab-set::
 
 
+  .. tab-item:: Added
+
+    .. list-table::
+        :header-rows: 0
+        :widths: auto
+
+        * - Replace compose env vars with parameters
+          - `#4284 <https://github.com/ansys/pyfluent/pull/4284>`_
+
+        * - Config
+          - `#4313 <https://github.com/ansys/pyfluent/pull/4313>`_
+
+        * - Added a method to print all configs and added typehints
+          - `#4329 <https://github.com/ansys/pyfluent/pull/4329>`_
+
+        * - Expose both object and method classes for builtin commands
+          - `#4340 <https://github.com/ansys/pyfluent/pull/4340>`_
+
+        * - File handling for Ansys Notebook
+          - `#4349 <https://github.com/ansys/pyfluent/pull/4349>`_
+
+
   .. tab-item:: Fixed
 
     .. list-table::
         :header-rows: 0
         :widths: auto
 
+        * - Issue with 'wait_process_finished'
+          - `#4309 <https://github.com/ansys/pyfluent/pull/4309>`_
+
+        * - Remove 'plot_set_name' and 'report_name' from event streaming.
+          - `#4310 <https://github.com/ansys/pyfluent/pull/4310>`_
+
+        * - Ui_mode key error in Ansys lab
+          - `#4319 <https://github.com/ansys/pyfluent/pull/4319>`_
+
         * - Unavailable field data for some surfaces.
           - `#4345 <https://github.com/ansys/pyfluent/pull/4345>`_
 
+        * - Remove string check of error message.
+          - `#4355 <https://github.com/ansys/pyfluent/pull/4355>`_
+
+        * - Respect user-provided directory in Ansys Notebook
+          - `#4358 <https://github.com/ansys/pyfluent/pull/4358>`_
+
+
+  .. tab-item:: Miscellaneous
+
+    .. list-table::
+        :header-rows: 0
+        :widths: auto
+
+        * - Set default version to latest release and use max grpc limit
+          - `#4327 <https://github.com/ansys/pyfluent/pull/4327>`_
+
+        * - Update search API results handling
+          - `#4333 <https://github.com/ansys/pyfluent/pull/4333>`_
+
+        * - Add ui_mode and dry_run for PIM launcher
+          - `#4338 <https://github.com/ansys/pyfluent/pull/4338>`_
+
+        * - Fix codespell issue causing action failures
+          - `#4348 <https://github.com/ansys/pyfluent/pull/4348>`_
+
+
+  .. tab-item:: Documentation
+
+    .. list-table::
+        :header-rows: 0
+        :widths: auto
+
+        * - Api reference and docker image name update [skip tests]
+          - `#4307 <https://github.com/ansys/pyfluent/pull/4307>`_
+
+        * - Update a setting radiation headlamp [skip tests]
+          - `#4334 <https://github.com/ansys/pyfluent/pull/4334>`_
+
+        * - Overview and Decision Guide for Field Data vs Solution Variable Data APIs [skip tests]
+          - `#4352 <https://github.com/ansys/pyfluent/pull/4352>`_
+
+        * - Fix scheme_eval docs [skip tests]
+          - `#4362 <https://github.com/ansys/pyfluent/pull/4362>`_
+
+        * - Update ``CONTRIBUTORS.md`` with the latest contributors
+          - `#4365 <https://github.com/ansys/pyfluent/pull/4365>`_
+
+
+  .. tab-item:: Maintenance
+
+    .. list-table::
+        :header-rows: 0
+        :widths: auto
+
+        * - Use the stable image id in pr ci
+          - `#4305 <https://github.com/ansys/pyfluent/pull/4305>`_
+
+        * - Update changelog for v0.34.0
+          - `#4308 <https://github.com/ansys/pyfluent/pull/4308>`_
+
+        * - Fix Fluent journal run CI for the latest image path change
+          - `#4323 <https://github.com/ansys/pyfluent/pull/4323>`_
+
+        * - Minor update to Makefile to clean the example directory.
+          - `#4354 <https://github.com/ansys/pyfluent/pull/4354>`_
+
 
 `0.34.0 <https://github.com/ansys/pyfluent/releases/tag/v0.34.0>`_ - July 23, 2025
 ==================================================================================

{ansys_fluent_core-0.34.1 → ansys_fluent_core-0.35.dev0}/doc/source/contributing/environment_variables.rst

@@ -4,7 +4,11 @@
 Environment Variables
 =====================
 
-Following is a list of environment variables that can be set to control various aspects of PyFluent.
+This page lists the environment variables that can be set to control various aspects of PyFluent.
+The values of these variables are frozen at the time of importing the PyFluent package and
+any later changes to these variables within the same Python process does not affect
+the behavior of PyFluent. PyFluent also provides a set of configuration variables that can be used to
+control the behavior of PyFluent within the same Python process. Please see the :ref:`ref_config_variables` page for more details.
 
 .. vale off
 
@@ -74,7 +78,3 @@ Following is a list of environment variables that can be set to control various
       - Specifies the IP address of the Fluent server while launching Fluent in :func:`launch_fluent() <ansys.fluent.core.launcher.launcher.launch_fluent>`.
     * - SERVER_INFO_DIR
       - Specifies the directory where the server-info file is created while launching Fluent in :func:`launch_fluent() <ansys.fluent.core.launcher.launcher.launch_fluent>`.
-    * - PYFLUENT_USE_DOCKER_COMPOSE
-      - Specifies Docker as a compose source to launch Fluent in container mode.
-    * - PYFLUENT_USE_PODMAN_COMPOSE
-      - Specifies Podman as a compose source to launch Fluent in container mode.

ansys_fluent_core-0.35.dev0/doc/source/user_guide/config_variables.rst

@@ -0,0 +1,18 @@
+.. _ref_config_variables:
+
+Configuration variables
+=======================
+
+The PyFluent library provides a set of configuration variables that can be used to control various aspects of its behavior at runtime.
+These variables are accessible through the ``config`` object available in the ``ansys.fluent.core`` module.
+
+The following code demonstrates how to access and modify the path within the Fluent container which is mapped to the host system:
+
+.. code-block:: python
+
+    >>> from ansys.fluent.core import config
+    >>> config.container_mount_target  # default value
+    '/home/container/workdir'
+    >>> config.container_mount_target = '/home/my_user/workdir'  # set a new value
+    >>> config.container_mount_target  # new value
+    '/home/my_user/workdir'

ansys_fluent_core-0.35.dev0/doc/source/user_guide/fields/field_vs_svars_data.rst

@@ -0,0 +1,110 @@
+.. _field_data_vs_solution_variable_data:
+
+Choosing Between Field Data and Solution Variable Data APIs
+===========================================================
+
+Overview
+--------
+
+PyFluent provides two primary APIs for accessing field array data from Fluent:
+
+- **Field Data API** (``field_data``):
+  Surface-centric access to a wide range of CFD fields, mesh geometry, and pathlines.
+
+- **Solution Variable Data API** (``solution_variable_data``):
+  Zone-centric access to Fluent's core solution variable arrays (SVARs), with support for both reading and writing.
+
+This guide summarizes the scope, strengths, and intended use cases for each API, and provides guidance on how to choose the appropriate interface for your workflow.
+
+Field Data API (``field_data``)
+-------------------------------
+
+- **Scope**:
+  - Accesses field data on surfaces (boundaries, face zones, etc.).
+  - Supports scalar, vector, and pathlines data, as well as mesh geometry and connectivity.
+  - Designed for post-processing, visualization, and mesh extraction.
+- **Typical Use Cases**:
+  - Extracting pressure, velocity, temperature, or other fields on boundaries or surfaces.
+  - Accessing mesh geometry for visualization or export.
+  - Streaming field data for real-time updates (in meshing mode).
+- **Limitations**:
+  - Read-only access.
+  - Data is organized by surface, not by zone.
+  - Not all solver variables are available; some fields are derived or post-processed.
+
+Solution Variable Data API (``solution_variable_data``)
+-------------------------------------------------------
+
+- **Scope**:
+  - Accesses Fluent's internal solution variable arrays (SVARs) on zones (cell or face zones).
+  - Supports both reading and writing of SVAR data.
+  - Provides detailed metadata about zones and variables.
+- **Typical Use Cases**:
+  - Direct extraction or modification of solver arrays for advanced workflows.
+  - Custom initialization or manipulation of solution fields.
+  - Accessing zone-specific data for scripting or automation.
+- **Limitations**:
+  - Data is organized by zone, not by surface.
+  - Does not provide mesh geometry or general field/derived data.
+  - Requires knowledge of Fluent's SVAR naming conventions.
+
+How to Choose
+-------------
+
+Use the following table to help decide which API to use for your context:
+
++--------------------------+---------------------+-----------------------------+
+| **Requirement**          | **field_data**      | **solution_variable_data**  |
++==========================+=====================+=============================+
+| Data on a surface        | Yes                 | No                          |
++--------------------------+---------------------+-----------------------------+
+| Data on a zone           | No                  | Yes                         |
++--------------------------+---------------------+-----------------------------+
+| Mesh geometry/connectivity| Yes                | No                          |
++--------------------------+---------------------+-----------------------------+
+| Pathlines                | Yes                 | No                          |
++--------------------------+---------------------+-----------------------------+
+| Read/write access        | Read-only           | Read and write              |
++--------------------------+---------------------+-----------------------------+
+| Derived/post-processed fields | Yes            | No (SVARs only)             |
++--------------------------+---------------------+-----------------------------+
+| Direct solver arrays     | No                  | Yes                         |
++--------------------------+---------------------+-----------------------------+
+| Available in meshing mode | Yes                 | No                         |
++--------------------------+---------------------+-----------------------------+
+
+**General Guidance:**
+
+- Use **field_data** for post-processing, visualization, and mesh-related queries on surfaces.
+- Use **solution_variable_data** for direct access to solver variables on zones, especially when you need to modify data or work with SVARs.
+
+Examples
+--------
+
+**Extracting pressure on a surface:**
+
+.. code-block:: python
+
+    from ansys.fluent.core import ScalarFieldDataRequest
+    data = solver_session.fields.field_data.get_field_data(
+        ScalarFieldDataRequest(field_name="pressure", surfaces=["inlet"])
+    )
+
+**Extracting and modifying temperature in a cell zone:**
+
+.. code-block:: python
+
+    sv_t = solver_session.fields.solution_variable_data.get_data(
+        variable_name="SV_T", zone_names=["fluid"], domain_name="mixture"
+    )
+    temp_array = sv_t["fluid"]
+    temp_array[:] = 600  # Set all temperatures to 600
+    solver_session.fields.solution_variable_data.set_data(
+        variable_name="SV_T", zone_names_to_data={"fluid": temp_array}, domain_name="mixture"
+    )
+
+Further Reading
+---------------
+
+- :ref:`ref_field_data_guide`
+- :ref:`ref_solution_variable_data_guide`

ansys_fluent_core-0.35.dev0/doc/source/user_guide/fields/fields_contents.rst

@@ -0,0 +1,32 @@
+.. _ref_fields_guide:
+
+.. vale Google.Spacing = NO
+
+Fields
+======
+
+PyFluent provides several services that allow you to access field data in different ways.
+Every PyFluent solution and meshing :ref:`Session <ref_session_guide>` object contains a
+``fields`` object. In both solution and meshing modes, the ``fields`` object contains
+``field_data`` and ``field_data_streaming`` children. In
+:obj:`solution <ansys.fluent.core.session_solver.Solver>` mode, the ``fields`` object
+also has ``reduction``, ``solution_variable_data`` and ``solution_variable_info`` children.
+
+To help decide between using ``field_data`` and ``solution_variable_data``, refer to the
+:ref:`dedicated comparison guide <field_data_vs_solution_variable_data>`.
+
+This guide explains:
+
+- The surface-centric vs. zone-centric perspectives.
+- Read vs. read/write capabilities.
+- Typical use cases for each API.
+- Performance and scope considerations.
+
+.. toctree::
+   :maxdepth: 1
+   :hidden:
+
+   field_vs_svars_data
+   field_data
+   reduction
+   solution_data

{ansys_fluent_core-0.34.1 → ansys_fluent_core-0.35.dev0}/doc/source/user_guide/legacy/scheme.rst

@@ -15,7 +15,7 @@ Examples
 
    >>> session.scheme.exec(('(ti-menu-load-string "/report/system/proc-stats")',))
    >>> # Returns TUI output string
-   >>> session.scheme.eval("(rpgetvar 'mom/relax)")
+   >>> session.scheme.string_eval("(rpgetvar 'mom/relax)")
    '0.7'
    >>> session.scheme.eval("(+ 2 3)")
    5

{ansys_fluent_core-0.34.1 → ansys_fluent_core-0.35.dev0}/doc/source/user_guide/make_container_image.rst

@@ -86,10 +86,9 @@ Run Docker container using PyFluent
 
     import os
     import ansys.fluent.core as pyfluent
-    os.environ["PYFLUENT_USE_DOCKER_COMPOSE"] = "1"
     os.environ["ANSYSLMD_LICENSE_FILE"] = "<license file or server>"
     custom_config = {'fluent_image': 'ansys_inc:latest', 'mount_source': f"{os.getcwd()}", 'auto_remove': False}
-    solver_session = pyfluent.launch_fluent(container_dict=custom_config)
+    solver_session = pyfluent.launch_fluent(container_dict=custom_config, user_docker_compose=True)
 
 
 Run Podman container using the command line
@@ -137,7 +136,6 @@ Run Podman container using PyFluent
     import os
     import ansys.fluent.core as pyfluent
     os.environ["ANSYSLMD_LICENSE_FILE"] = "<license file or server>"
-    os.environ["PYFLUENT_USE_PODMAN_COMPOSE"] = "1"
     custom_config = {'fluent_image': 'ansys_inc:latest', 'mount_source': f"{os.getcwd()}", 'auto_remove': False}
-    solver_session = pyfluent.launch_fluent(container_dict=custom_config)
+    solver_session = pyfluent.launch_fluent(container_dict=custom_config, use_podman_compose=True)