Comments (18)
Thanks for your interest in our work. Our code will be out in a few weeks.
from size_depth_disambiguation.
Thanks! Looking forward to the code release!
from size_depth_disambiguation.
@nicolasugrinovic Could you please provide the used frames / depth ground truth of 3DPW and MuPoTS-3D that you used for evaluation? And the function that you used to compute the d_{ord}. So that we can compare with the results reported in Tab. 1.
At least the used frames / depth ground truth of 3DPW and the function, which is supposed to be just a few line of code, I suppose?
Really looking forward to this!
from size_depth_disambiguation.
Hi,
For MuPoTS-3D we used all frames where the matching between estimated subjects and GT subjects was possible. Meaning that when estimating each persons pose/shape, we do not know which GT each corresponds to. For doing this, we compute distance of the 3D joints and the 2D bbox overlap of each estimated person w.r.t. to GT labels. It is hard to do that matching when people overlap in the image, so we discard frames where this happens.
For 3DPW we use only the frames where there is GT for 2 persons in the test set.
Depth ground truth is taken from the 3D joint annotations, we take the root depth as the person's depth. Once we have these correspondences, we score the depth order in a pairwise manner.
We will soon release the code.
from size_depth_disambiguation.
Thanks for your quick reply! It helps.
Could you provide the function (code) that you score the depth order in a pairwise manner
, like given the Depth ground truth
and the predicted depth value?
from size_depth_disambiguation.
@nicolasugrinovic Sorry for bothering. Is there any change that the code would be released in next week? At least the code describing evaluation matrix, which is supposed to be quite easy to organize?
from size_depth_disambiguation.
I'll try to get it ready for this week. Sorry about that.
from size_depth_disambiguation.
Thanks! Really looking forward to it.
from size_depth_disambiguation.
@nicolasugrinovic Thanks for your great work. Will the code be released this week?
from size_depth_disambiguation.
WOW, it's coming.
Looking forward to the evaluation part! Thanks in advance, Doc!
from size_depth_disambiguation.
Dear Doc. Nicolás Ugrinovic,
Thanks a lot for your efforts!
Best,
Yu
from size_depth_disambiguation.
Hi @Arthur151, sorry for the delay. I'll try to upload the d_{ord}
eval function as soon as possible and release the rest after that.
from size_depth_disambiguation.
@Arthur151 you now have the function to calculate depth order here. Basically a matrix operation to know which persons are behind or in front of the other persons.
from size_depth_disambiguation.
Thanks for the code! It seems that the depth order only describes the closer or farther, without equal class.
The if ... continue
in code makes it hard to determine which images are used for evaluation.
from size_depth_disambiguation.
What do you mean by equal class
?
Yes, some images where it is not possible to do an ID matching of the estimated person with its corresponding GT are not considered. This happens usually when a person is occluded by another person. This is similar to the matching used in the code for 3DPCK metric. Once you generate data and run the eval, you can tell which images are taken into account.
I could also make a list of the images being evaluated, throughout the week.
from size_depth_disambiguation.
When we try to determine the ordinal depth between each pair of subjects, we may need to classify the subjects to equal class that their difference in depth is less than a pre-defined threshold.
Thanks for your help!
from size_depth_disambiguation.
@Arthur151 you can check the file done_files_eval.csv. It is a list of all the images used for the evaluation. The evaluation code discards some examples in which it is impossible to assign a corresponding GT to a person due to heavy occlusions. Hope this helps
from size_depth_disambiguation.
Thanks for your efforts! Yes, it would be helpful.
from size_depth_disambiguation.
Related Issues (3)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from size_depth_disambiguation.