initial sync commit

Author: thesct22

.gitattributes

@@ -0,0 +1,18 @@
+*.usd filter=lfs diff=lfs merge=lfs -text
+
+# Set default behavior to automatically normalize line endings
+* text=auto
+
+# Force Unix line endings for shell scripts
+*.sh text eol=lf
+
+# Force Unix line endings for other Unix-specific files
+*.yml text eol=lf
+*.yaml text eol=lf
+Dockerfile* text eol=lf
+*.conf text eol=lf
+
+# Force Windows line endings for Windows-specific files
+*.bat text eol=crlf
+*.cmd text eol=crlf
+*.ps1 text eol=crlf

.github/workflows/build-push-blueprint.yml

@@ -0,0 +1,41 @@
+name: Build and Push Blueprint
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - main
+    types: [opened, reopened, synchronize, ready_for_review]
+  release:
+    types: [published]
+  workflow_dispatch:
+
+jobs:
+  code-style:
+    name: "Code style"
+    runs-on: ubuntu-latest
+    steps:
+      - uses: ansys/actions/code-style@v10
+        with:
+          use-python-cache: false
+
+  run-unit-tests:
+    name: Run Messaging extension unit tests
+    runs-on: windows-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v3
+
+      - name: Set up Python
+        uses: actions/setup-python@v4
+        with:
+          python-version: '3.12' # Adjust the Python version as needed
+
+      - name: Install pytest
+        run: pip install pytest
+
+      - name: Run Unit Tests
+        run: |
+          cd blueprint/kit-app-source/source/extensions/ansys.messaging/ && pytest tests/unit

.gitignore

@@ -0,0 +1,11 @@
+*.pyc
+
+# Temporary build directories
+_temp-build/
+
+.DS_Store
+.vscode/
+.vs/
+
+# Pre-commit virtualenv
+.venv/

.pre-commit-config.yaml

@@ -0,0 +1,51 @@
+repos:
+
+  - repo: https://github.com/google/yamlfmt
+    rev: v0.20.0
+    hooks:
+      - id: yamlfmt
+        exclude: templates/.*
+        args:
+          - "-formatter"
+          - "max_line_length=120,retain_line_breaks=true,retain_line_breaks_single=true"
+
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.14.2
+    hooks:
+      # ONLY on blueprint\kit-app-source\source\extensions folder and Python files
+      - id: ruff-check
+        files: blueprint/kit-app-source/source/extensions/.*\.py
+        args: [--fix]
+      - id: ruff-format
+        files: blueprint/kit-app-source/source/extensions/.*\.py
+
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v6.0.0
+    hooks:
+      - id: check-merge-conflict
+      - id: debug-statements
+      - id: check-yaml
+        # Exclude files inside a "templates" folder and the pnpm-lock.yaml file
+        exclude: templates/.*|pnpm-lock\.yaml
+      - id: trailing-whitespace
+
+  - repo: https://github.com/ansys/pre-commit-hooks
+    rev: v0.5.2
+    hooks:
+      - id: add-license-headers
+        # ONLY on blueprint\kit-app-source\source\extensions folder and Python files
+        files: blueprint/kit-app-source/source/extensions/.*\.py
+        args:
+          - --start_year=2025
+
+  # this validates our github workflow files
+  - repo: https://github.com/python-jsonschema/check-jsonschema
+    rev: 0.34.1
+    hooks:
+      - id: check-github-workflows
+
+  # this validates our pre-commit.ci configuration
+  - repo: https://github.com/pre-commit-ci/pre-commit-ci-config
+    rev: v1.6.1
+    hooks:
+      - id: check-pre-commit-ci-config

README.md

@@ -0,0 +1,41 @@
+# bottle-filling-digital-twin Dev
+
+Blueprint for developing vertical digital twin applications using Ansys Fluids simulations and NVIDIA Omniverse for bottle filling use case.
+
+## Setting up pre-commit
+
+You need to setup pre-commit on this repo befor contributing. Follow these steps to setup pre-commit on your local machine.
+
+1. Add a python virtual environment at the root.
+
+    ```bash
+    python -m venv .venv
+    ```
+
+2. Activate the virtual environment.
+
+    ```bash
+    source .venv/bin/activate
+    ```
+
+    ```ps1
+    .venv/Scripts/activate
+    ```
+
+3. Install pre-commit
+
+    ```bash
+    pip install pre-commit
+    ```
+
+4. Run pre-commit install
+
+    ```bash
+    pre-commit install
+    ```
+
+To run pre-commit checks:
+
+```bash
+pre-commit run --all-files
+```

blueprint/.dockerignore.content

@@ -0,0 +1,51 @@
+# .dockerignore for content image build
+# Excludes unnecessary files from Docker build context
+
+# Documentation
+*.md
+README*
+LICENSE*
+CONTRIBUTING*
+CODE_OF_CONDUCT*
+
+# Version control
+.git
+.gitignore
+.gitattributes
+
+# Docker files (we only need content/)
+docker/
+!docker/Dockerfile.content
+
+# Kubernetes manifests
+k8s/
+manifests/
+
+# Scripts
+scripts/
+
+# Build artifacts
+*.log
+*.tmp
+*.bak
+*~
+
+# IDE and editor files
+.vscode/
+.idea/
+*.swp
+*.swo
+.DS_Store
+Thumbs.db
+
+# Kit app source (not needed for content image)
+kit-app-source/
+
+# Web app (not needed for content image)
+web-app/
+
+# Documentation
+doc/
+
+# Python cache
+__pycache__/

blueprint/.gitignore

@@ -0,0 +1,52 @@
+# All folders starting with _ are local.
+_*/
+
+# Compiled python files.
+*.py[cod]
+
+# Visual Studio files.
+/.vs
+**/.vscode/ipch
+
+# macOS files.
+.DS_Store
+
+# Generated license file.
+PACKAGE-DEPS.yaml
+
+# packman .user config
+*.packman.xml.user
+
+# kit user config
+deps/**/user.toml
+
+# vscode settings are copied and filled in from 'settings.json.template'
+.vscode/settings.json
+
+# PyCharm files.
+/.idea/
+
+# Linux in docker build $HOME dirs
+/.nvidia-omniverse
+/.local
+/.cache
+
+# Omniverse EULA breadcrumb
+/.omniverse_eula_accepted.txt
+
+# Streaming EventTrace
+*.etli
+
+**/web-app/node_modules/
+**/web-app/dist/
+
+/certificates/*
+/bicep/parameters/ccci/*
+/k8s/working/*
+/k8s/exports.sh
+/kas_installation/*
+
+/scripts/exports.sh
+
+
+/scripts/swa-cli.config.json

blueprint/CODE_OF_CONDUCT.md

@@ -0,0 +1,65 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our
+project and our community a harassment-free experience for everyone,
+regardless of age, body size, disability, ethnicity, sex
+characteristics, gender identity and expression, level of experience,
+education, socio-economic status, nationality, personal appearance,
+race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual
+  attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, or to ban temporarily or permanently any
+contributor for other behaviors that they deem inappropriate, threatening,
+offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 1.4, available at
+https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

blueprint/CONTRIBUTING.md

@@ -0,0 +1,49 @@
+# Contributing
+
+We absolutely welcome any code contributions and we hope that this
+guide will facilitate an understanding of the PyAEDT code
+repository. It is important to note that while the PyAEDT software
+package is maintained by ANSYS and any submissions will be reviewed
+thoroughly before merging, we still seek to foster a community that can
+support user questions and develop new features to make this software
+a useful tool for all users. As such, we welcome and encourage any
+questions or submissions to this repository.
+
+For contributing to this project, please refer to the [PyAnsys Developer's Guide].
+
+[PyAnsys Developer's Guide]: https://dev.docs.pyansys.com/index.html
+
+## Directing Issues and Features Requests
+
+For reporting bugs and proposing new features, please use the Issues tab instead of the Discussions tab. This will help us track and prioritize work in a more organized manner.
+
+## Purpose of Discussions
+
+The Discussions tab should primarily be used for general questions and discussions about the project. This could include discussions about potential improvements, the future direction of the project, brainstorming ideas, help with using the software, and other topics that don't exactly fit as an Issue.
+
+Remember, maintaining distinct places for different types of interactions helps keep our project organized and moving forward in a coordinated manner.
+
+## Modify the Code
+
+Everyone can contribute to this project, irrespective of their level of expertise. Your diverse skills, perspectives, and experiences are valuable and we welcome them.
+
+Here's a simple overview of how you can start making contributions:
+
+**Fork the Repository:** "Forking" means creating a personal copy of this repository on your GitHub account.
+
+**Clone the Repository:** After forking, you need to download the repository to your local machine. This can be done using the `git clone` command.
+
+**Create a New Branch:** A branch is used to isolate your changes from the main project. You can create a new branch using the `git branch` command. Remember to switch to your new branch with the `git checkout` command.
+
+**Commit Your Changes:** After making your changes, you need to "commit" them. A commit is a packaged set of alterations. Use `git add` to add your files to staging, and then `git commit -m "your message"` to commit them.
+
+**Push Your Changes:** After committing your changes, "push" them to your forked repository on GitHub with `git push origin <branch-name>`.
+
+**Create a Pull Request:** A Pull Request (PR) lets us know you have changes you think should be included in the main project. Go to your forked repository on GitHub and click on the 'Pull request' button. The title of your
+'Pull request' must follow the `conventional commits standard <https://github.com/commitizen/conventional-commit-types/blob/master/index.json>`_ where the type field is expected to be defined with upper cases.
+
+Following these steps ensures that your contributions will be easily reviewed and potentially included in the project much faster.
+
+Please don't get discouraged if you find these steps complex, we are here to help you throughout the process.
+
+We hope these rules will make the Discussions section a better place for every contributor.