-
Notifications
You must be signed in to change notification settings - Fork 250
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
The training dataset prepareation #8
Comments
Hi @qianduoduolr, these are the settings that we used to prepare 11000 training sequences for Kubric MOVI-f:
Most of these sequences are repeated with different crops because we used |
Thanks for your reply. |
As far as I remember, we had to download the dataset first for it to work. Then, we load MOVI-f (not MOVI-e) from a local path. |
Ok, thanks, I will try later. |
Hi @nikitakaraevv, can you provide the link to download the MOVI-f data you used? Did you simply run create_point_tracking_dataset() with the mentioned parameters to generate annotations on the dataset? How was the file structure used for training? FYI, it seems like the description in the main README for generation of annotation is not complete. It is at least not so easy to follow, although I might miss something here... Thanks for your help! |
Hello @nikitakaraevv and @ernestchu, |
Hi @Anderstask1 and @NEbrahimi, Here are the changes I made:
Then I just ran |
Hi @nikitakaraevv, |
Hi @wwsource, I also had this problem. I had to install
|
Hi @nikitakaraevv, I simply downloaded the dataset.py script and updated the main function with the modifications you suggested. When I tried running dataset.py, I got the following error:
Then I changed
Do you have any suggestions on what I should do or what I might have done wrong? Also, the file structure that was being generated seemed wrong for the
but I just wanted to check that this is the correct file structure, seemed off. Thank you! |
Hi @rogerioagjr, sorry, somehow I missed your message. Honestly, I don't know why the Kubric data is failing now. You might want to open an issue here. As for your second question, |
Hi @nikitakaraevv . May I ask how large is the training data and the annotations? And if it is possible for you to upload the generated data to ease the data preparation process? Thanks! |
Hi @XiaoyuShi97, it would be better to ask the creators of Kubric to do it, as we simply generated a dataset using their provided script. |
Hi @XiaoyuShi97 , In my impression, it would require 500+G. According to the explanation upstairs, generating the annotations is not so difficult in my point of view. |
Hi @nikitakaraevv , I generate the training data following the instructions, but the total size is only ~65G, which is much smaller than @sinkers-lan 's experience. Could you please provide the size of training data? Thx! |
Hi @XiaoyuShi97, it seems to be correct. 65Gb must be the size of generated annotations, while the annotations + the tensorflow record consume 500+ Gb. |
Thanks for your kind reply! |
I download part of kubric_movi_f/512x512 datasets, then run create_point_tracking_dataset(),but got the following issue: why did this? |
Thanks for the great work, and thanks @nikitakaraevv for sharing these instructions here. Perhaps, useful to cross-reference on kubric as well. |
Hi @nikitakaraevv , I downloaded the tensorflow-record to local disk(only 512x512 of movi_f, which takes about ~552GB), and arrange them like this: |
It has been solved. |
Hi @nikitakaraevv, @qsisi Any assistance you could provide would be greatly appreciated. Thank you for your time. |
I remember such an issue is caused by either inappropriate tensorflow_datasets version, or messing around with the directory or dataset name. Try changing the tensorflow_datasets version, and try a different dataset name like "512x512" or "movi_f/512x512". |
@qsisi Setting different dataset name "movi_f/512x512" works. Thank you so much. |
Hi @nikitakaraevv, I followed your instructions and it is generating annotations now, but the generation speed is quite slow on my end, roughly 2 seconds per iteration. Is it the same on your side? Or any speed-up suggestions? |
Hi @nikitakaraevv , I'm following your CoTracker3, and I found that the previous Kubric dataset for CoTracker2 is not suitable for CoTracker3, as CoTracker3 requires a |
Hi, I am following your work to prepare the training data for MOVI-f.
Could you please give more details about the instructions for annotation generation?
I generally follow the function
create_kubric_eval_train_dataset
in this link, and set thetrain_size=(512,512)
andtracks_to_sample=2000
increate_point_tracking_dataset
.Besides, I also modify the
'movi_e/256x256'
in this link in order to generate MOVI-f.Is that right?
The text was updated successfully, but these errors were encountered: