Skip to content

Commit bacfcde

Browse files
yuecidengyuecideng
authored
Init Project (#1)
1 parent 31fd894 commit bacfcde

304 files changed

Lines changed: 63895 additions & 0 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎.github/ISSUE_TEMPLATE/bug.md‎

Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
---
2+
name: Bug Report
3+
about: Submit a bug report
4+
title: "[Bug Report] Bug title"
5+
6+
---
7+
8+
If you are submitting a bug report, please fill in the following details and use the tag [bug].
9+
10+
### Describe the bug
11+
12+
A clear and concise description of what the bug is.
13+
14+
### Steps to reproduce
15+
16+
Please try to provide a minimal example to reproduce the bug. Error messages and stack traces are also helpful.
17+
18+
<!-- Please post terminal logs, minimal example to reproduce, or command to run under three backticks (```) to allow code formatting.
19+
20+
```
21+
Paste your error here
22+
```
23+
24+
For more information on this, check: https://www.markdownguide.org/extended-syntax/#fenced-code-blocks
25+
26+
-->
27+
28+
### System Info
29+
30+
Describe the characteristic of your environment:
31+
32+
<!-- Please complete the following description. -->
33+
- Commit: [e.g. 8f3b9ca or main branch]
34+
- OS: [e.g. Ubuntu 22.04]
35+
- GPU: [e.g. RTX 3060]
36+
- CUDA: [e.g. 12.8]
37+
- GPU Driver: [e.g. 570.195.03, this can be seen by using `nvidia-smi` command.]
38+
39+
### Additional context
40+
41+
Add any other context about the problem here.
42+
43+
### Checklist
44+
45+
- [ ] I have checked that there is no similar issue in the repo (**required**)
46+

‎.github/ISSUE_TEMPLATE/proposal.md‎

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
---
2+
name: Proposal
3+
about: Propose changes that are not bug fixes
4+
title: "[Proposal] Proposal title"
5+
---
6+
7+
8+
### Proposal
9+
10+
A clear and concise description of the proposal. In a few sentences, describe the feature and its core capabilities.
11+
12+
### Motivation
13+
14+
Please outline the motivation for the proposal. Summarize the core use cases and user problems and needs you are trying to solve.
15+
16+
Is your feature request related to a problem? e.g.,"I'm always frustrated when [...]".
17+
18+
If this is related to another GitHub issue, please link here too.
19+
20+
### Additional context
21+
22+
Add any other context or screenshots about the feature request here.
23+
24+
### Checklist
25+
26+
- [ ] I have checked that there is no similar issue in the repo (**required**)

‎.github/PULL_REQUEST_TEMPLATE.md‎

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
# Description
2+
3+
<!--
4+
Thank you for your interest in sending a pull request. Please make sure to check the contribution guidelines.
5+
6+
💡 Please try to keep PRs small and focused. Large PRs are harder to review and merge.
7+
-->
8+
9+
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
10+
List any dependencies that are required for this change.
11+
12+
Fixes # (issue)
13+
14+
<!-- As a practice, it is recommended to open an issue to have discussions on the proposed pull request.
15+
This makes it easier for the community to keep track of what is being developed or added, and if a given feature
16+
is demanded by more than one party. -->
17+
18+
## Type of change
19+
20+
<!-- As you go through the list, delete the ones that are not applicable. -->
21+
22+
- Bug fix (non-breaking change which fixes an issue)
23+
- New feature (non-breaking change which adds functionality)
24+
- Breaking change (existing functionality will not work without user modification)
25+
- Documentation update
26+
27+
## Screenshots
28+
29+
Please attach before and after screenshots of the change if applicable.
30+
31+
<!--
32+
Example:
33+
34+
| Before | After |
35+
| ------ | ----- |
36+
| _gif/png before_ | _gif/png after_ |
37+
38+
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.
39+
-->
40+
41+
## Checklist
42+
43+
- [ ] I have run the `black .` command to format the code base.
44+
- [ ] I have made corresponding changes to the documentation
45+
- [ ] I have added tests that prove my fix is effective or that my feature works
46+
- [ ] Dependencies have been updated, if applicable.
47+
48+
<!--
49+
As you go through the checklist above, you can mark something as done by putting an x character in it
50+
51+
For example,
52+
- [x] I have done this task
53+
- [ ] I have not done this task
54+
-->

‎.gitignore‎

Lines changed: 222 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,222 @@
1+
# Byte-compiled / optimized / DLL files
2+
__pycache__/
3+
*.py[cod]
4+
*$py.class
5+
6+
# C extensions
7+
*.so
8+
9+
# Distribution / packaging
10+
.Python
11+
build/
12+
develop-eggs/
13+
dist/
14+
downloads/
15+
eggs/
16+
.eggs/
17+
lib/
18+
lib64/
19+
parts/
20+
sdist/
21+
var/
22+
wheels/
23+
share/python-wheels/
24+
*.egg-info/
25+
.installed.cfg
26+
*.egg
27+
MANIFEST
28+
29+
# PyInstaller
30+
# Usually these files are written by a python script from a template
31+
# before PyInstaller builds the exe, so as to inject date/other infos into it.
32+
*.manifest
33+
*.spec
34+
35+
# Installer logs
36+
pip-log.txt
37+
pip-delete-this-directory.txt
38+
39+
# Unit test / coverage reports
40+
htmlcov/
41+
.tox/
42+
.nox/
43+
.coverage
44+
.coverage.*
45+
.cache
46+
nosetests.xml
47+
coverage.xml
48+
*.cover
49+
*.py,cover
50+
.hypothesis/
51+
.pytest_cache/
52+
cover/
53+
54+
# Translations
55+
*.mo
56+
*.pot
57+
58+
# Django stuff:
59+
*.log
60+
local_settings.py
61+
db.sqlite3
62+
db.sqlite3-journal
63+
64+
# Flask stuff:
65+
instance/
66+
.webassets-cache
67+
68+
# Scrapy stuff:
69+
.scrapy
70+
71+
# Sphinx documentation
72+
docs/_build/
73+
74+
# PyBuilder
75+
.pybuilder/
76+
target/
77+
78+
# Jupyter Notebook
79+
.ipynb_checkpoints
80+
81+
# IPython
82+
profile_default/
83+
ipython_config.py
84+
85+
# pyenv
86+
# For a library or package, you might want to ignore these files since the code is
87+
# intended to run in multiple environments; otherwise, check them in:
88+
# .python-version
89+
90+
# pipenv
91+
# According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
92+
# However, in case of collaboration, if having platform-specific dependencies or dependencies
93+
# having no cross-platform support, pipenv may install dependencies that don't work, or not
94+
# install all needed dependencies.
95+
#Pipfile.lock
96+
97+
# poetry
98+
# Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
99+
# This is especially recommended for binary packages to ensure reproducibility, and is more
100+
# commonly ignored for libraries.
101+
# https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
102+
#poetry.lock
103+
104+
# pdm
105+
# Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
106+
#pdm.lock
107+
# pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
108+
# in version control.
109+
# https://pdm.fming.dev/#use-with-ide
110+
.pdm.toml
111+
112+
# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
113+
__pypackages__/
114+
115+
# Celery stuff
116+
celerybeat-schedule
117+
celerybeat.pid
118+
119+
# SageMath parsed files
120+
*.sage.py
121+
122+
# Environments
123+
.env
124+
.venv
125+
env/
126+
venv/
127+
ENV/
128+
env.bak/
129+
venv.bak/
130+
131+
# Spyder project settings
132+
.spyderproject
133+
.spyproject
134+
135+
# Rope project settings
136+
.ropeproject
137+
138+
# mkdocs documentation
139+
/site
140+
141+
#python api built by docs
142+
# docs/source/api
143+
144+
# mypy
145+
.mypy_cache/
146+
.dmypy.json
147+
dmypy.json
148+
149+
# Pyre type checker
150+
.pyre/
151+
152+
# pytype static type analyzer
153+
.pytype/
154+
155+
# Cython debug symbols
156+
cython_debug/
157+
158+
# PyCharm
159+
# JetBrains specific template is maintained in a separate JetBrains.gitignore that can
160+
# be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
161+
# and can be added to the global gitignore or merged into this file. For a more nuclear
162+
# option (not recommended) you can uncomment the following to ignore the entire idea folder.
163+
#.idea/
164+
165+
# ignore file for vlac demo
166+
cache
167+
168+
*.filament
169+
*.filamat
170+
*.png
171+
*.tiff
172+
*.npy
173+
*.pkl
174+
*.hdf5
175+
*.pt
176+
*.csv
177+
materials
178+
179+
!embodichain/agents/dexforce_vla/data/empty_lang_embed.pt
180+
!resources/Arch.png
181+
embodichain/toolkits/outputs/*
182+
embodichain/toolkits/outputs/*
183+
184+
embodichain/database/*
185+
186+
3rdparty/
187+
Log/
188+
embodichain/deploy/h1/sim/unitree_h1
189+
embodichain/deploy/inspire/inspire_hand
190+
embodichain/devices/camera/king_fisher/kingfisher
191+
192+
# tensorboard logs
193+
embodichain/agents/policy/runs/*
194+
embodichain/agents/dexrdt/wandb
195+
*.pth
196+
outputs
197+
test_configs/*
198+
199+
wandb/
200+
embodichain/deploy/mobile_aloha/collect_data/data
201+
*.mp4
202+
203+
# vscode settings
204+
.vscode/
205+
206+
# web server backend
207+
*/backend/datas/
208+
*/backend/logs/
209+
*/backend/__pycache__/
210+
211+
# web server frontend
212+
*/backend/export_datas/
213+
*/backend/**/__pycache__/
214+
215+
# web server frontend
216+
!web_server/frontend/**/*
217+
!web_server/frontend/**/event*
218+
*/frontend/node_modules
219+
*/frontend/.DS_Store
220+
*/frontend/*.local
221+
*/frontend/.eslintcache
222+
*/frontend/.stylelintcache

‎.readthedocs.yaml‎

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
# Read the Docs configuration file
2+
# See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
3+
4+
# Required
5+
version: 2
6+
7+
# Set the OS, Python version, and other tools you might need
8+
build:
9+
os: ubuntu-22.04
10+
tools:
11+
python: "3.10"
12+
13+
# Build documentation in the "docs/" directory with Sphinx
14+
sphinx:
15+
configuration: docs/source/conf.py
16+
17+
# Optionally, but recommended,
18+
# declare the Python requirements required to build your documentation
19+
# See https://docs.readthedocs.io/en/stable/guides/reproducible-builds.html
20+
python:
21+
install:
22+
- requirements: docs/requirements.txt
23+

0 commit comments

Comments
 (0)