-
Notifications
You must be signed in to change notification settings - Fork 3
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
Generation stuck #61
Comments
Please try using a more recent version of TDW, eg v1.11. |
Let me know if that works. If it doesn't, I'll try to sort out the specific versions that we used back in the day. |
Hi @felixbinder , I have fixed this issue by setting But it takes error if I use 1.11.23 version TDW:(It is in 1009 line of controllers/dominoes.py)
Only 1.8.8.0 version of TDW can work. Hope this information is useful |
Awesome, I'm glad you figured it out! Seems to be something to do with the interprocess communication—that can be hard to figure out. Thanks for the update |
Hi @felixbinder, it still didn't work for dataset generation: I used 1.8.8.0 version of TDW But if I use the command the generate dataset, it stuck at the same position....
Do you know why? |
One possibility might be that you do not have the right models installed. If I remember correctly, some of the models of the distractor/occluder objects that are placed in front/in the background are drawn from a library of 3D models that is only included by request in tdw. To test this, you could modify the generation code to not include any distractor/occluder objects and see if it still hangs. If that is the case, it is probably the proprietary model library. To get access to those models, write Jeremy Schwartz an email and cc me ([email protected]) |
Hi, thanks for your help. Yes. if don't set any distractors and occluders, the code can work for other 7 scenarios(without Drape). Drape needs flex.json file. I have tried all of them. If include distractor and occluder, the code will stuck in |
Hi @felixbinder, I have successfully set it up . And the Generation code can work. I also have another question about the depth image process. Do you have any instructor about how to transfer the depth image to point cloud. Because I have used camera_matric and projection_matric, but the depth point cloud is still not exactly consistent with true point cloud(3d position). So I think I loss some detail parameters. Here is some detail problems:
|
Hello, I'll loop in @htung0101 , who was working on the point cloud model pipeline. I'm personally not familiar with how that part of the pipeline works. |
Hi @htung0101 , do you have any guidance on this? It is vey important to know how to convert the Depth into Point Cloud. I would like to know how you set it up, because now I can't match the transformed point cloud with the real world coordinates exactly. Thanks. |
Hello!
I have tried the code to generate the Physion dataset(because the origin dataset doesn't contain depth image)
But the code didn't work.
I use the 1.8.8.0 version of TDW.
It is stuck at 50 line of
python3.10/site-packages/tdw/controller.py
:self.socket.recv()
The text was updated successfully, but these errors were encountered: