dftracer-analyzer 0.0.2__tar.gz

dftracer_analyzer-0.0.2/.devcontainer.json

@@ -0,0 +1,36 @@
+{
+    "name": "dfanalyzer-devcontainer",
+    "build": {
+        "dockerfile": "Dockerfile"
+    },
+    "customizations": {
+        "vscode": {
+            "extensions": [
+                "GitHub.copilot",
+                "GitHub.copilot-chat",
+                "Tyriar.sort-lines",
+                "WakaTime.vscode-wakatime",
+                "charliermarsh.ruff",
+                "foxundermoon.shell-format",
+                "mesonbuild.mesonbuild",
+                "ms-azuretools.vscode-containers",
+                "ms-python.debugpy",
+                "ms-python.python",
+                "ms-toolsai.jupyter",
+                "ms-toolsai.jupyter-renderers",
+                "ms-toolsai.vscode-jupyter-cell-tags",
+                "ms-vscode.cpptools-extension-pack",
+                "ms-vscode-remote.remote-containers",
+                "redhat.vscode-yaml",
+                "tamasfe.even-better-toml",
+                "vscode-icons-team.vscode-icons"
+            ]
+        }
+    },
+    "postCreateCommand": "ulimit -c unlimited && git config --global core.autocrlf input",
+    "remoteEnv": {
+        "OMPI_ALLOW_RUN_AS_ROOT": "1",
+        "OMPI_ALLOW_RUN_AS_ROOT_CONFIRM": "1",
+        "PYTHONPATH": "${containerWorkspaceFolder}"
+    }
+}

dftracer_analyzer-0.0.2/.gitattributes

@@ -0,0 +1,8 @@
+.git/* export-ignore
+.github/* export-ignore
+.vscode/* export-ignore
+
+notebooks/* export-ignore
+tests/* export-ignore
+
+.wakatime-project export-ignore

dftracer_analyzer-0.0.2/.gitignore

@@ -0,0 +1,199 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/latest/usage/project/#working-with-version-control
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv*
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# Abstra
+# Abstra is an AI-powered process automation framework.
+# Ignore directories containing user credentials, local state, and settings.
+# Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#  Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#  that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#  and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#  you could uncomment the following to ignore the enitre vscode folder
+# .vscode/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Cursor
+#  Cursor is an AI-powered code editor. `.cursorignore` specifies files/directories to
+#  exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
+#  refer to https://docs.cursor.com/context/ignore-files
+.cursorignore
+.cursorindexingignore
+
+# DFAnalyzer
+.dfanalyzer
+outputs/
+tmp/

dftracer_analyzer-0.0.2/.readthedocs.yaml

@@ -0,0 +1,34 @@
+# Read the Docs configuration file for Sphinx projects
+# See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
+
+# Required
+version: 2
+
+# Set the OS, Python version and other tools you might need
+build:
+  os: ubuntu-22.04
+  tools:
+    python: "3.12"
+    # You can also specify other tool versions:
+    # nodejs: "20"
+    # rust: "1.70"
+    # golang: "1.20"
+
+# Build documentation in the "docs/" directory with Sphinx
+sphinx:
+  configuration: docs/conf.py
+  # You can configure Sphinx to use a different builder, for instance use the dirhtml builder for simpler URLs
+  # builder: "dirhtml"
+  # Fail on all warnings to avoid broken references
+  # fail_on_warning: true
+# Optionally build your docs in additional formats such as PDF and ePub
+# formats:
+#   - pdf
+#   - epub
+
+# Optional but recommended, declare the Python requirements required
+# to build your documentation
+# See https://docs.readthedocs.io/en/stable/guides/reproducible-builds.html
+python:
+  install:
+    - requirements: docs/requirements.txt

dftracer_analyzer-0.0.2/CITATION.cff

@@ -0,0 +1,56 @@
+cff-version: 1.2.0
+message: "If you use this software, please cite the software and the paper."
+title: "WisIO: Automated I/O Bottleneck Detection with Multi-Perspective Views for HPC Workflows"
+version: 0.1.0
+abstract: "Analyze, visualize, and understand I/O performance issues in HPC workflows."
+license: MIT
+url: https://github.com/grc-iit/wisio
+repository-code: https://github.com/grc-iit/wisio
+contact:
+  - name: Izzet Yildirim
+    email: izzetcyildirim@gmail.com
+authors:
+  - family-names: Yildirim
+    given-names: Izzet
+    orcid: https://orcid.org/0000-0003-3513-0764
+  - family-names: Devarajan
+    given-names: Hariharan
+    orcid: https://orcid.org/0000-0001-5625-3494
+  - family-names: Kougkas
+    given-names: Anthony
+    orcid: https://orcid.org/0000-0003-3943-663X
+  - family-names: Sun
+    given-names: Xian-He
+    orcid: https://orcid.org/0000-0002-1093-0792
+  - family-names: Mohror
+    given-names: Kathryn
+    orcid: https://orcid.org/0000-0002-1366-1655
+preferred-citation:
+  type: conference-paper
+  title: "WisIO: Automated I/O Bottleneck Detection with Multi-Perspective Views for HPC Workflows"
+  year: 2025
+  authors:
+    - family-names: Yildirim
+      given-names: Izzet
+      orcid: https://orcid.org/0000-0003-3513-0764
+    - family-names: Devarajan
+      given-names: Hariharan
+      orcid: https://orcid.org/0000-0001-5625-3494
+    - family-names: Kougkas
+      given-names: Anthony
+      orcid: https://orcid.org/0000-0003-3943-663X
+    - family-names: Sun
+      given-names: Xian-He
+      orcid: https://orcid.org/0000-0002-1093-0792
+    - family-names: Mohror
+      given-names: Kathryn
+      orcid: https://orcid.org/0000-0002-1366-1655
+  conference:
+    name: "ICS'25: 2025 International Conference on Supercomputing"
+    city: "Salt Lake City"
+    region: UT
+    country: USA
+    date-start: 2025-06-08
+    date-end: 2025-06-11
+  doi: 10.1145/3721145.3725742
+  url: https://doi.org/10.1145/3721145.3725742

dftracer_analyzer-0.0.2/CONTRIBUTING.md

@@ -0,0 +1,93 @@
+# Contributing to DFAnalyzer
+
+First off, thank you for considering contributing to DFAnalyzer! We welcome any help to make this tool better.
+
+## How Can I Contribute?
+
+### Reporting Bugs
+
+If you encounter a bug, please report it by opening an issue on our [GitHub Issue Tracker](https://github.com/LLNL/dfanalyzer/issues).
+
+When reporting a bug, please include:
+
+- A clear and descriptive title.
+- Steps to reproduce the bug.
+- What you expected to happen.
+- What actually happened.
+- Your environment details (e.g., OS, Python version, DFAnalyzer version, relevant libraries).
+
+### Suggesting Enhancements
+
+If you have an idea for a new feature or an improvement to an existing one, please open an issue on our [GitHub Issue Tracker](https://github.com/LLNL/dfanalyzer/issues) to discuss it.
+
+Please include:
+
+- A clear and descriptive title.
+- A detailed description of the proposed enhancement.
+- The use case or problem this enhancement would solve.
+- Any potential benefits or drawbacks.
+
+### Submitting Pull Requests
+
+We love pull requests! If you'd like to contribute code:
+
+1.  **Fork the Repository:** Start by forking the [main DFAnalyzer repository](https://github.com/LLNL/dfanalyzer).
+2.  **Create a Branch:** Create a new branch in your fork for your changes (e.g., `git checkout -b feature/my-new-feature` or `bugfix/issue-123`).
+3.  **Make Your Changes:** Implement your feature or bug fix.
+4.  **Test Your Changes:** Ensure your changes pass all tests. You can run tests locally (see "Setting Up a Development Environment" below and refer to the test execution steps in `.github/workflows/ci.yml`).
+5.  **Format and Lint:** Ensure your code adheres to our coding standards (see below).
+6.  **Commit Your Changes:** Use clear and descriptive commit messages.
+7.  **Push to Your Fork:** Push your changes to your forked repository.
+8.  **Submit a Pull Request:** Open a pull request from your branch to the `main` branch of the DFAnalyzer repository. Provide a clear description of your changes in the PR.
+
+## Coding Standards
+
+We use [Ruff](https://github.com/astral-sh/ruff) for linting and formatting. Please ensure your contributions adhere to these standards. Key configurations (from `pyproject.toml`):
+
+- Line length: 88 characters
+- Quote style: Preserve existing quotes (`quote-style = "preserve"`)
+
+You can run Ruff locally to check and format your code:
+
+```bash
+ruff check .
+ruff format .
+```
+
+## Setting Up a Development Environment
+
+1.  **Clone the Repository:**
+
+    ```bash
+    git clone https://github.com/LLNL/dfanalyzer.git
+    cd dfanalyzer
+    ```
+
+2.  **Install Python Dependencies:**
+    Install DFAnalyzer in editable mode along with its optional dependencies (like Darshan support) and dependencies required for running tests.
+
+    ```bash
+    python -m pip install --upgrade pip
+    # Install DFAnalyzer in editable mode with optional extras
+    pip install -e .[darshan]
+    # Install dependencies for tests
+    pip install -r tests/requirements.txt
+    # Ensure build tools are available
+    # pip install meson-python setuptools wheel
+    ```
+
+3.  **Install System Dependencies (for C++ components):** DFAnalyzer includes C++ components. To develop these, you'll need system dependencies such as a C++ compiler, CMake, Meson, Ninja, and various development libraries (e.g., `libarrow-dev`, `libhdf5-dev`).
+    A comprehensive list and example installation commands for Ubuntu can be found in the "Install system dependencies" step within the `.github/workflows/ci.yml` file.
+
+4.  **Build C++ Components (if making changes to them):**
+    When you install DFAnalyzer in editable mode (`pip install -e .`), the C++ components are typically built. If you make changes to the C++ source files, you may need to recompile them.
+    ```bash
+    # Navigate to the build directory (usually created by the editable install)
+    # meson compile -C build
+    # Or, if you need to reconfigure and then build:
+    # meson setup build --reconfigure -Denable_tests=true -Denable_tools=true
+    # meson compile -C build
+    ```
+    The editable pip install should handle most build aspects, but manual recompilation with Meson might be needed for iterative C++ development.
+
+We look forward to your contributions!

dftracer_analyzer-0.0.2/Dockerfile

@@ -0,0 +1,38 @@
+FROM ubuntu:22.04
+
+RUN apt-get update && \
+    apt-get install -y \
+    ca-certificates \
+    lsb-release \
+    wget && \
+    wget https://apache.jfrog.io/artifactory/arrow/$(lsb_release --id --short | tr 'A-Z' 'a-z')/apache-arrow-apt-source-latest-$(lsb_release --codename --short).deb && \
+    apt-get install -y ./apache-arrow-apt-source-latest-$(lsb_release --codename --short).deb && \
+    apt-get update && \
+    apt-get install -y \
+    build-essential \
+    cmake \
+    git \
+    libarrow-dev \
+    libhdf5-dev \
+    libncurses-dev \
+    libopenmpi-dev \
+    libparquet-dev \
+    libreadline-dev \
+    meson \
+    ninja-build \
+    nlohmann-json3-dev \
+    openmpi-bin \
+    openmpi-common \
+    python3.10 \
+    python3-pip && \
+    rm -rf /var/lib/apt/lists/*
+
+WORKDIR /dfanalyzer
+
+COPY . .
+
+RUN pip install --upgrade pip && \
+    pip install build meson-python setuptools streamlit wheel && \
+    pip install .[darshan] -Csetup-args="-Denable_tools=true"
+
+ENTRYPOINT ["dfanalyzer"]

dftracer_analyzer-0.0.2/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Lawrence Livermore National Laboratory
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

dftracer_analyzer-0.0.2/PKG-INFO

@@ -0,0 +1,163 @@
+Metadata-Version: 2.1
+Name: dftracer-analyzer
+Version: 0.0.2
+Summary: Analyze, visualize, and understand I/O performance issues in HPC workflows
+Author-Email: Izzet Yildirim <izzetcyildirim@gmail.com>
+Maintainer-Email: Izzet Yildirim <izzetcyildirim@gmail.com>
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Science/Research
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Topic :: Scientific/Engineering
+Classifier: Topic :: Software Development :: Build Tools
+Classifier: Typing :: Typed
+Project-URL: documentation, https://dfanalyzer.readthedocs.io/en/latest/
+Project-URL: source, https://github.com/LLNL/dfanalyzer
+Project-URL: tracker, https://github.com/LLNL/dfanalyzer/issues
+Requires-Python: <3.12,>3.8
+Requires-Dist: dask[bag,dataframe,distributed]<2025,>=2024.1.0
+Requires-Dist: dask_jobqueue~=0.8.0
+Requires-Dist: hydra-core~=1.3.0
+Requires-Dist: inflect==7.0
+Requires-Dist: numpy==1.24.3
+Requires-Dist: pandas>=2.0
+Requires-Dist: portion>=2.4.0
+Requires-Dist: pyarrow>=13
+Requires-Dist: rich~=14.1.0
+Requires-Dist: strenum>=0.4
+Requires-Dist: structlog>=25
+Requires-Dist: dftracer-utils>=0.0.5
+Provides-Extra: darshan
+Requires-Dist: darshan>=3.4; extra == "darshan"
+Description-Content-Type: text/markdown
+
+# Data Flow Analyzer
+
+<!-- ![Build and Test](https://github.com/LLNL/dfanalyzer/actions/workflows/ci.yml/badge.svg)
+![PyPI - Version](https://img.shields.io/pypi/v/dfanalyzer?label=PyPI)
+![PyPI - Wheel](https://img.shields.io/pypi/wheel/dfanalyzer?label=Wheel)
+![PyPI - Python Version](https://img.shields.io/pypi/pyversions/dfanalyzer?label=Python) -->
+
+## Overview
+
+DFAnalyzer is an open-source tool for analyzing performance data from large-scale workflows on distributed systems. It presents a hierarchical, layer-by-layer summary of an application's execution, from high-level application events down to low-level POSIX calls. For each layer, DFAnalyzer quantifies time, operation counts, and data volume, and calculates key performance metrics like bandwidth and operations per second. It also visualizes the overlap between different layers, helping to characterize and understand complex I/O and compute patterns.
+
+## Installation
+
+To install DFAnalyzer through `pip` (recommended for most users):
+
+```bash
+# Ensure runtime dependencies for optional features (e.g., Darshan, Recorder) are installed.
+# This might involve using your system's package manager or a tool like Spack.
+# Example using Spack to prepare the environment:
+# spack -e tools install
+pip install dfanalyzer
+```
+
+To install DFAnalyzer from source (for developers or custom builds):
+
+```bash
+# 1. Install system dependencies:
+#    Refer to the "Install system dependencies" step in .github/workflows/ci.yml
+#    (e.g., build-essential, cmake, libarrow-dev, libhdf5-dev, ninja-build, etc.).
+#    Alternatively, tools like Spack can help manage these:
+#    # spack -e tools install
+module load ninja
+
+# 2. Install Python build dependencies:
+python -m pip install --upgrade pip meson-python setuptools wheel
+
+# 3. Install DFAnalyzer from the root of this repository:
+#    The following command includes optional C++ components (tests and tools).
+#    The --prefix argument is optional and specifies the installation location.
+pip install -e . \
+  -Csetup-args="--prefix=$HOME/.local" \
+  -Csetup-args="-Denable_tests=true" \
+  -Csetup-args="-Denable_tools=true"
+
+# (Optional) Install dependencies for running tests if you plan to contribute or run local tests:
+# pip install -r tests/requirements.txt
+```
+
+## Usage
+
+Here's an example of how to run DFAnalyzer using sample data included in the repository:
+
+```bash
+# Before running, ensure the sample data is extracted.
+# For example, to extract the 'dftracer-dlio' sample used below:
+# mkdir -p tests/data/extracted
+# tar -xzf tests/data/dftracer-dlio.tar.gz -C tests/data/extracted
+dfanalyzer analyzer/preset=dlio trace_path=tests/data/extracted/dftracer-dlio view_types=[time_range]
+```
+
+This command analyzes the traces and prints a high-level summary of the application's execution. Below is a sample of the "Time Period Summary" output:
+
+```bash
+                                                  Time Period Summary
+┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━┓
+┃ Metric                                                                        ┃ Unit           ┃              Value ┃
+┡━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━┩
+│ Job Time                                                                      │ seconds        │             56.695 │
+│ Total Count                                                                   │ count          │             15,901 │
+│ Total Files                                                                   │ count          │                 87 │
+│ Total Nodes                                                                   │ count          │                  0 │
+│ Total Processes                                                               │ count          │                 23 │
+│ App Count                                                                     │ count          │                  8 │
+│ Training Count                                                                │ count          │                 40 │
+│ Compute Count                                                                 │ count          │                200 │
+│ Fetch Data Count                                                              │ count          │                160 │
+│ Data Loader Count                                                             │ count          │                808 │
+│ Data Loader Fork Count                                                        │ count          │                 96 │
+│ Reader Count                                                                  │ count          │              4,008 │
+│ Reader POSIX (Lustre) Count                                                   │ count          │             10,432 │
+│ Reader POSIX (Lustre) Size                                                    │ MB             │         111833.161 │
+│ Reader POSIX (Lustre) Bandwidth                                               │ MB/s           │            874.982 │
+│ Reader POSIX (Lustre) Avg Transfer Size                                       │ MB             │             10.720 │
+│ Checkpoint Count                                                              │ count          │                  8 │
+│ Checkpoint POSIX (Lustre) Count                                               │ count          │                 45 │
+│ Checkpoint POSIX (Lustre) Size                                                │ MB             │              0.011 │
+│ Checkpoint POSIX (Lustre) Bandwidth                                           │ MB/s           │              0.791 │
+│ Checkpoint POSIX (Lustre) Avg Transfer Size                                   │ MB             │              0.000 │
+│ Other POSIX Count                                                             │ count          │                 96 │
+└───────────────────────────────────────────────────────────────────────────────┴────────────────┴────────────────────┘
+```
+
+DFAnalyzer also provides a detailed breakdown of performance metrics for each layer of the application. Here is a snippet of the "Layer Breakdown" section from the same run, which includes the percentage of time each layer overlaps with its parent layer:
+
+```bash
+                                            Layer Breakdown (w/ overlap %)
+┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━┳━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━┓
+┃ Layer                       ┃         Time (s) ┃            Ops ┃   Ops/sec ┃          Size (MB) ┃ Bandwidth (MB/s) ┃
+┡━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━╇━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━┩
+│ App                         │   441.967 (----) │       8 (----) │     0.018 │                  - │                - │
+│ Training                    │   439.442 (----) │      40 (----) │     0.091 │                  - │                - │
+│ Compute                     │   272.356 (----) │     200 (----) │     0.734 │                  - │                - │
+│ Fetch Data                  │   126.179 ( 16%) │     160 ( 25%) │     1.268 │                  - │                - │
+│ Data Loader                 │   151.471 ( 45%) │     808 ( 46%) │     5.334 │                  - │                - │
+│ Data Loader Fork            │     2.392 (  0%) │      96 (  0%) │    40.135 │                  - │                - │
+│ Reader                      │   299.992 ( 40%) │   4,008 ( 51%) │    13.360 │                  - │                - │
+│ Reader POSIX (Lustre)       │   127.812 ( 45%) │  10,432 ( 48%) │    81.620 │  111833.161 ( 46%) │          874.982 │
+│ Checkpoint                  │     0.014 (  0%) │       8 (  0%) │   571.551 │                  - │                - │
+│ Checkpoint POSIX (Lustre)   │     0.014 (  0%) │      45 (  0%) │  3268.686 │       0.011 (  0%) │            0.791 │
+│ Other POSIX                 │     2.392 (  0%) │      96 (  0%) │    40.135 │       0.000 (----) │                - │
+└─────────────────────────────┴──────────────────┴────────────────┴───────────┴────────────────────┴──────────────────┘
+```
+
+## Further Information
+
+For more details, to report issues, or to contribute to DFAnalyzer, please refer to the following resources:
+
+- **[Official DFAnalyzer Documentation](https://dfanalyzer.readthedocs.io/)**: For detailed usage, configuration options, and information about analyzers.
+- **[Issue Tracker](https://github.com/LLNL/dfanalyzer/issues)**: To report bugs or suggest new features.
+- **[Contributing Guidelines](./CONTRIBUTING.md)**: For information on how to contribute to the project, including setting up a development environment and coding standards.
+- **[Citation File](./CITATION.cff)**: If you use DFAnalyzer in your research, please cite it using the information in this file.
+
+## Acknowledgments
+
+This work was performed under the auspices of the U.S. Department of Energy by Lawrence Livermore National Laboratory under Contract DE-AC52-07NA27344. This material is based upon work supported by the U.S. Department of Energy, Office of Science, Office of Advanced Scientific Computing Research under the DOE Early Career Research Program (LLNL-CONF-862440). Also, this research is supported in part by the National Science Foundation (NSF) under Grants OAC-2104013, OAC-2313154, and OAC-2411318.