-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
README #1
Comments
Hello, All the code used in the paper is in this repository and also in this one: [av-aloha-unity](https://github.com/soltanilara/av-aloha-unity). However, I want to note that the code organization could be improved, and I’ve only tested it on the system in my lab. I’m currently working on an extension of this project, which will be better organized and include additional features, but that will probably take a few months to finish. In short, the code should be reproducible, but it might require some debugging to get it working. If you attempt to reproduce it and run into any issues, feel free to reach out with your questions. |
Thank you very much for your reply. I have been watching your work recently and it has left me feeling very impressed. We recently bought a set of ALOHA original robotic arm and Meta Quest 3 VR headset, but according to the content provided by your README, we don't know where to start simulation operation (dual arm operation in VR and MUJOCO environments). We hope you can give us some guidance. We will continue to conduct research based on your project and hope to stay in touch. |
Hi, Sorry for the late reply, I didn't get a notification. I would first try setting up the VR app: You can try sideloading this apk on your meta quest 3: If that doesn't work, I'd try install Unity and building from source. The next thing would be to setup a signaling server to allow WebRTC communication: After that make sure the headset and your computer running the simulation are using the same the wifi network. You can try running
Then in the Unity app press "Load" then "Connect" And hopefully you can receive data from the headset. After that to run the simulation: Feel free to contact me at [email protected] |
|
Thank you very much for taking the trouble to help me. Have you ever encountered this error? The solution I got on the Internet is to modify part of the code, but I think your code is perfect and does not need to be modified.
…------------------ 原始邮件 ------------------
发件人: "Ian ***@***.***>;
发送时间: 2025年2月11日(星期二) 下午4:13
收件人: ***@***.***>;
抄送: ***@***.***>; ***@***.***>;
主题: Re: [Soltanilara/av-aloha] README (Issue #1)
can you try looking in /usr/local/zed/get_python_api.py
It should be something you can name as you please. On the headset app you'll see that ID after clicking the "Load" button. For the turn server information, you don't need a TURN server if you are connecting to the headset on the same local network. To not use the turn server information you can comment out these lines here and just leave the turn server information empty:
https://github.com/Soltanilara/av-aloha/blob/ed1d8c4cac988e16feb61e621175bcce0ed70688/data_collection_scripts/webrtc_headset.py#L312
https://github.com/Soltanilara/av-aloha/blob/ed1d8c4cac988e16feb61e621175bcce0ed70688/data_collection_scripts/webrtc_headset.py#L106
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Hello author, your work is impressive, but I have a question. Whether your work can be reproduced through open-source content. What does this mean, and can you explain that?————Note: The code is under active development, and a more organized codebase will be available in future updates.
The text was updated successfully, but these errors were encountered: