Add two toolkit for training/inference

examples/BMTrain/.dockerignore

@@ -0,0 +1,147 @@
+**/__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
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow
+__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/
+
+**/*.pt
+
+**/*.npy
+
+**/.DS_Store
+
+**/log
+**/*.qdrep
+!bmtrain/dist

examples/BMTrain/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,79 @@
+
+name: 🐞 Bug Report
+description: Report a bug/issue related to the PyTorch-based parallel model training toolkit
+title: "[BUG] <title>"
+labels: ["bug"]
+body:
+- type: checkboxes
+  attributes:
+    label: Is there an existing issue for this?
+    description: Please search to see if an issue already exists for the bug you encountered.
+    options:
+    - label: I have searched the existing issues
+      required: true
+- type: textarea
+  attributes:
+    label: Description of the Bug
+    description: Provide a clear and concise description of what the bug is.
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Environment Information
+    description: |
+      Provide details about your environment.
+      Example:
+        - GCC version: 9.3.0
+        - Torch version: 1.9.0
+        - Linux system version: Ubuntu 20.04
+        - CUDA version: 11.4
+        - Torch's CUDA version (as per `torch.cuda.version()`): 11.3
+    value: |
+        - GCC version:
+        - Torch version:
+        - Linux system version:
+        - CUDA version:
+        - Torch's CUDA version (as per `torch.cuda.version()`):
+    render: markdown
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: To Reproduce
+    description: Provide the steps and details to reproduce the behavior.
+    placeholder: |
+      1. Describe your environment setup, including any specific version requirements.
+      2. Clearly state the steps you took to trigger the error, including the specific code you executed.
+      3. Identify the file and line number where the error occurred, along with the full traceback of the error. Make sure to have `NCCL_DEBUG=INFO` and `CUDA_LAUNCH_BLOCKING=True` set to get accurate debug information.
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Expected Behavior
+    description: Describe what you expected to happen when you executed the code.
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Screenshots
+    description: If applicable, please add screenshots to help explain your problem.
+  validations:
+    required: false
+- type: textarea
+  attributes:
+    label: Additional Information
+    description: |
+      Provide any other relevant context or information about the problem here.
+      Links? References? Anything that will give us more context about the issue you are encountering!
+      Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
+  validations:
+    required: false
+- type: checkboxes
+  attributes:
+    label: Confirmation
+    description: Please confirm that you have reviewed all of the above requirements and verified the information provided before submitting this issue.
+    options:
+      - label: I have reviewed and verified all the information provided in this report.
+  validations:
+    required: true
+

examples/BMTrain/.github/ISSUE_TEMPLATE/build_err.yml

@@ -0,0 +1,94 @@
+name: 🛠️ Build Error
+description: Report a build error for this project
+title: "[BUILD ERROR] <title>"
+labels: ["Build ERR"]
+body:
+- type: checkboxes
+  id: prev_issue
+  attributes:
+    label: Is there an existing issue for this?
+    description: Please search to see if an issue already exists for the build error you encountered.
+    options:
+    - label: I have searched the existing issues
+      required: true
+- type: textarea
+  attributes:
+    label: Description of the Build Error
+    description: Provide a clear and concise description of what the build error is.
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Expected Behavior
+    description: Provide a clear and concise description of what you expected to happen.
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: To Reproduce
+    description: Describe the steps you took to trigger the build error. Include any commands you executed or files you modified.
+    placeholder: |
+      1. Go to '...'
+      2. Click on '....'
+      3. Scroll down to '....'
+      4. See error
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Environment Information
+    description: |
+      Provide details about your environment.
+      Example:
+        - Operating System version: Ubuntu 20.04
+        - GCC version: 9.3.0
+        - Pybind version: 2.8.1
+        - CUDA version: 11.4
+        - NVIDIA NCCL CU11 version: 2.14.3
+        - CMake version: 3.21.2
+        - Pip version: 22.0.0
+    value: |
+        - Operating System version:
+        - GCC version:
+        - Pybind version:
+        - CUDA version:
+        - NVIDIA NCCL CU11 version:
+        - CMake version:
+        - Pip version:
+    render: markdown
+  validations:
+    required: true
+- type: dropdown
+  attributes:
+    label: Installation Method
+    description: Please indicate if the error occurred during source code installation or when using the pip install .whl method.
+    options:
+      - Source Code Installation
+      - Pip Install .whl Method
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Full Error Traceback
+    description: Provide the complete error traceback.
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Additional Information
+    description: |
+      Provide any other relevant context or information about the problem here.
+      Links? References? Anything that will give us more context about the issue you are encountering!
+      Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
+  validations:
+    required: false
+- type: checkboxes
+  id: confirm
+  attributes:
+    label: Confirmation
+    description: Please confirm that you have reviewed all of the above requirements and verified the information provided before submitting this report.
+    options:
+      - label: I have reviewed and verified all the information provided in this report.
+  validations:
+    required: true
+

examples/BMTrain/.github/ISSUE_TEMPLATE/features_request.yml

@@ -0,0 +1,30 @@
+name: 🚀Feature Request
+description: Suggest an idea for this project
+title: "[Feature] <title>"
+labels: ["enhancement"]
+assignees: []
+body:
+- type: textarea
+  attributes:
+    label: Is your feature request related to a problem? Please describe.
+    description: "A clear and concise description of what the problem is. Example: I'm always frustrated when..."
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Describe the solution you'd like
+    description: "A clear and concise description of what you want to happen."
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Describe alternatives you've considered
+    description: "A clear and concise description of any alternative solutions or features you've considered."
+  validations:
+    required: false
+- type: textarea
+  attributes:
+    label: Additional context
+    description: "Add any other context or screenshots about the feature request here."
+  validations:
+    required: false

examples/BMTrain/.github/pull_request_template.md

@@ -0,0 +1,29 @@
+## Pull Request Template
+
+### Issue Reference
+Please mention the issue number if applicable, or write "N/A" if it's a new feature.
+
+Issue #...
+
+### Description
+Please describe your changes in detail. If it resolves an issue, please state how it resolves it.
+
+### Type of Change
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] This change requires a documentation update
+
+### How Has This Been Tested?
+Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
+
+### Checklist
+- [ ] I have read the [CONTRIBUTING](../../CONTRIBUTING.md) document.
+- [ ] My code follows the code style of this project.
+- [ ] My change requires a change to the documentation.
+- [ ] I have updated the documentation accordingly.
+- [ ] I have added tests to cover my changes.
+- [ ] All new and existing tests passed.
+
+### Additional Information
+Any additional information, configuration, or data that might be necessary for the review.