[WIP]: Init Project

.github/ISSUE_TEMPLATE/bug.md

@@ -0,0 +1,46 @@
+---
+name: Bug Report
+about: Submit a bug report
+title: "[Bug Report] Bug title"
+
+---
+
+If you are submitting a bug report, please fill in the following details and use the tag [bug].
+
+### Describe the bug
+
+A clear and concise description of what the bug is.
+
+### Steps to reproduce
+
+Please try to provide a minimal example to reproduce the bug. Error messages and stack traces are also helpful.
+
+<!-- Please post terminal logs, minimal example to reproduce, or command to run under three backticks (```) to allow code formatting.
+
+```
+Paste your error here
+```
+
+For more information on this, check: https://www.markdownguide.org/extended-syntax/#fenced-code-blocks
+
+-->
+
+### System Info
+
+Describe the characteristic of your environment:
+
+<!-- Please complete the following description. -->
+- Commit: [e.g. 8f3b9ca or main branch]
+- OS: [e.g. Ubuntu 22.04]
+- GPU: [e.g. RTX 3060]
+- CUDA: [e.g. 12.8]
+- GPU Driver: [e.g. 570.195.03, this can be seen by using `nvidia-smi` command.]
+
+### Additional context
+
+Add any other context about the problem here.
+
+### Checklist
+
+- [ ] I have checked that there is no similar issue in the repo (**required**)
+

.github/ISSUE_TEMPLATE/proposal.md

@@ -0,0 +1,26 @@
+---
+name: Proposal
+about: Propose changes that are not bug fixes
+title: "[Proposal] Proposal title"
+---
+
+
+### Proposal
+
+A clear and concise description of the proposal. In a few sentences, describe the feature and its core capabilities.
+
+### Motivation
+
+Please outline the motivation for the proposal. Summarize the core use cases and user problems and needs you are trying to solve.
+
+Is your feature request related to a problem? e.g.,"I'm always frustrated when [...]".
+
+If this is related to another GitHub issue, please link here too.
+
+### Additional context
+
+Add any other context or screenshots about the feature request here.
+
+### Checklist
+
+- [ ] I have checked that there is no similar issue in the repo (**required**)

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,54 @@
+# Description
+
+<!--
+Thank you for your interest in sending a pull request. Please make sure to check the contribution guidelines.
+
+💡 Please try to keep PRs small and focused. Large PRs are harder to review and merge.
+-->
+
+Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
+List any dependencies that are required for this change.
+
+Fixes # (issue)
+
+<!-- As a practice, it is recommended to open an issue to have discussions on the proposed pull request.
+This makes it easier for the community to keep track of what is being developed or added, and if a given feature
+is demanded by more than one party. -->
+
+## Type of change
+
+<!-- As you go through the list, delete the ones that are not applicable. -->
+
+- Bug fix (non-breaking change which fixes an issue)
+- New feature (non-breaking change which adds functionality)
+- Breaking change (existing functionality will not work without user modification)
+- Documentation update
+
+## Screenshots
+
+Please attach before and after screenshots of the change if applicable.
+
+<!--
+Example:
+
+| Before | After |
+| ------ | ----- |
+| _gif/png before_ | _gif/png after_ |
+
+To upload images to a PR -- simply drag and drop an image while in edit mode and it should upload the image directly. You can then paste that source into the above before/after sections.
+-->
+
+## Checklist
+
+- [ ] I have run the `black .` command to format the code base.
+- [ ] I have made corresponding changes to the documentation
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] Dependencies have been updated, if applicable.
+
+<!--
+As you go through the checklist above, you can mark something as done by putting an x character in it
+
+For example,
+- [x] I have done this task
+- [ ] I have not done this task
+-->

.gitignore

@@ -0,0 +1,222 @@
+# 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
+
+# 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/#use-with-ide
+.pdm.toml
+
+# 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
+
+#python api built by docs
+# docs/source/api
+
+# 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/
+
+# ignore file for vlac demo
+cache
+
+*.filament
+*.filamat
+*.png
+*.tiff
+*.npy
+*.pkl
+*.hdf5
+*.pt
+*.csv
+materials
+
+!embodichain/agents/dexforce_vla/data/empty_lang_embed.pt
+!resources/Arch.png
+embodichain/toolkits/outputs/*
+embodichain/toolkits/outputs/*
+
+embodichain/database/*
+
+3rdparty/
+Log/
+embodichain/deploy/h1/sim/unitree_h1
+embodichain/deploy/inspire/inspire_hand
+embodichain/devices/camera/king_fisher/kingfisher
+
+# tensorboard logs
+embodichain/agents/policy/runs/*
+embodichain/agents/dexrdt/wandb
+*.pth
+outputs
+test_configs/*
+
+wandb/
+embodichain/deploy/mobile_aloha/collect_data/data
+*.mp4
+
+# vscode settings
+.vscode/
+
+# web server backend
+*/backend/datas/
+*/backend/logs/
+*/backend/__pycache__/
+
+# web server frontend
+*/backend/export_datas/
+*/backend/**/__pycache__/
+
+# web server frontend
+!web_server/frontend/**/*
+!web_server/frontend/**/event*
+*/frontend/node_modules
+*/frontend/.DS_Store
+*/frontend/*.local
+*/frontend/.eslintcache
+*/frontend/.stylelintcache

.readthedocs.yaml

@@ -0,0 +1,23 @@
+# Read the Docs configuration file
+# 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.10"
+
+# Build documentation in the "docs/" directory with Sphinx
+sphinx:
+   configuration: docs/source/conf.py
+
+# Optionally, 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
+