-
Notifications
You must be signed in to change notification settings - Fork 296
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
Questions on how to organize training data and generate bounding box ground truth #55
Comments
in the experiments has demo you can learn |
I'm trying to do the same thing... will report back if I figure out how.. |
I do not see a demo in experiments showing expected training data hierarchy input, specifically for bboxes and/or voxel-level ground truth (if possible). Anyone have luck figuring this out? |
you can run, experiments/toy_exp/generate_toys.py . It will create the toy data. |
Found it, thank you! |
I am looking at the 3D LIDC example. Is it possible to specify the format of the data which is returned by preprocessing.py? I would like to avoid the preprocessing of the big LIDC dataset just to see how to prepare my data. I saw this: Just a small example and description of the data preparation for the 3D data would be really helpful. I looked and generated the toy example dataset, but I am interested in 3D data, patch loader and voxel-wise annotation. @delton137 did you figure it out? |
Sorry for asking this question,
My training set is CT images consisting of kidney and kidney tumor, whose ground truth is labeled in voxel level. Now I want to do 3D object detection of tumor. I'm wondering how should I organize my training data to feed into the network. And should I generate bounding box ground truth for tumors manually or your library supports to generate bounding box ground truth automatically?
Thanks you in advance!
Best wishes
The text was updated successfully, but these errors were encountered: