-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Suggestion for new model type #1729
Comments
@snosov1 could you please review this request? |
Hey, @edward9112 ! We've considered such a use case previously. The closest we could get is the set of "crossroad" models that has a certain amount of "overhead" data in the training set. Though, on practice it still requires the camera to be somewhat higher up than you show on your example image. That said, we could consider looking into it again. What kind of help in data collection do you imply? |
Hi @snosov1 ! I can provide video footage or assist with image annotation. |
As for the annotation - we have the means to do somewhat large-scale annotation with our resources (given that we have satisfactory answers on the questions above). |
|
1-2. That sounds like something we can work with. With regards to third item - the main reason I'm asking is that we, as a company, have to get data with clear terms on how we can use it. One of the simplest ways is if the dataset is public (i.e. accessible to general public, not only to us) with clear and non-restrictive terms of use/licensing. If you need to keep it between our parties - then there have to be some explicit license agreement between our companies (and if you're just you and not a company that we can have such kind of agreement with - then it's simply a no-go from our side). |
Do you have a draft of such agreement? How do I make a dataset public? |
No. When we purchase/acquire data - the providing company gives us its terms for review.
You host the binaries on a service of your choice and have a website with the links, description, license/terms of use. Popular examples are - WIDERFace, MS COCO and many others. |
Alright, I will let you know as soon as I collect the required data. |
Thx! Looking forward to it! |
Hi @snosov1 I have collected the dataset, it's around 25GB of video footage with motion in it. Many scenes and camera positions. The average resolution is 640x360px. Would that be sufficient? |
Hey, @edward9112 ! Great news! The spec sounds great - we'll need to execute some experiments to see what we can achieve with it, though! Please, refer any questions you might have with regards to sharing the data to @yssemaev . Once this is figured out and we can access the data - we'll plan the experiments accordingly. |
Awesome! @yssemaev can I send you the data sharing agreement draft? If so, can you provide your contact/email? |
@edward9112, please contact me directly by email: yuri.semaev at intel.com to discuss details |
Pinged legal team, waiting for response. |
@vladimir-dudnik @eaidova |
@edward9112 can you publish your data under permissive license on some public resource, like @snosov1 suggested in his comment? |
@snosov1 @vladimir-dudnik is it OK if we publish it on Kaggle.com ? |
@edward9112 I think it should be OK if dataset is available on public resource under permissive license |
@snosov1 @vladimir-dudnik it looks like the agreement has been signed today. I will proceed with uploading the data for sharing. |
@vladimir-dudnik @snosov1 @yssemaev data has been shared with you via Google Drive |
@vladimir-dudnik @snosov1 @yssemaev any comments/feedback regarding data quality? |
@vladimir-dudnik @snosov1 @yssemaev any feedback would be helpful. Should we add more data? |
I have a suggestion for a model for quite common use case: people detection in an overhead camera scene.
Regular models like person-detection-retail just won't detect in such circumstances but this is the best camera position for non-occlusive people counting. It would be great if you add this type of model. I could assist with data collection if necessary.
Here is the image example: https://ibb.co/37Ybx5b
The text was updated successfully, but these errors were encountered: