You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for submitting an issue. Please refer to our issue policy
for information on what types of issues we address.
Please fill in this template to ensure a timely and thorough response
Remove the section instructions but leave the section header
Place an "x" between the brackets next to an option if it applies. For
example:
Selected option
Please delete everything above this line before submitting the issue
Describe the problem
The problem is the following:
Having fiftyone dataset with 'keypoints' field I am trying to use annotate() method to upload dataset to labelstudio. I attach screenshots. There is always only one point is uplaoded with coordinates (0, 0).
I did the same workflow for uploading fiftyone dataset with annotate() method for bbox objects and it works fine. However, i can not do the same for 'keypoints'.
I have not found similar issue and examples in repo on this topic so would be grateful to any assistance.
Thank you.
Code to reproduce issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. Please avoid sharing code that relies on your local data or
datasets. Include a short video or screenshot if the bug is in the App.
Versions of label-studio and tools:
label-studio 1.12.0
label-studio-converter 0.0.58
label-studio-sdk 0.0.32
label-studio-tools 0.0.3
Include any logs or source code that would be helpful to diagnose the problem.
If including tracebacks, please include the full traceback. Large logs and
files should be attached. Please do not use screenshots for sharing text. Code
snippets should be used instead when providing tracebacks, logs, etc.
Willingness to contribute
The FiftyOne Community encourages bug fix contributions. Would you or another
member of your organization be willing to contribute a fix for this bug to the
FiftyOne codebase?
Yes. I can contribute a fix for this bug independently
Yes. I would be willing to contribute a fix for this bug with guidance
from the FiftyOne community
[x ] No. I cannot contribute a bug fix at this time
The text was updated successfully, but these errors were encountered:
Instructions
Thank you for submitting an issue. Please refer to our
issue policy
for information on what types of issues we address.
example:
Describe the problem
The problem is the following:
Having fiftyone dataset with 'keypoints' field I am trying to use annotate() method to upload dataset to labelstudio. I attach screenshots. There is always only one point is uplaoded with coordinates (0, 0).
I did the same workflow for uploading fiftyone dataset with annotate() method for bbox objects and it works fine. However, i can not do the same for 'keypoints'.
I have not found similar issue and examples in repo on this topic so would be grateful to any assistance.
Thank you.
Code to reproduce issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. Please avoid sharing code that relies on your local data or
datasets. Include a short video or screenshot if the bug is in the App.
System information
python --version
): Python 3.10.9fiftyone --version
):- fiftyone 0.23.4
fiftyone-brain 0.16.0
fiftyone-db 0.4.0
fiftyone-desktop 0.33.2
Other info/logs
Versions of label-studio and tools:
label-studio 1.12.0
label-studio-converter 0.0.58
label-studio-sdk 0.0.32
label-studio-tools 0.0.3
Include any logs or source code that would be helpful to diagnose the problem.
If including tracebacks, please include the full traceback. Large logs and
files should be attached. Please do not use screenshots for sharing text. Code
snippets should be used instead when providing tracebacks, logs, etc.
Willingness to contribute
The FiftyOne Community encourages bug fix contributions. Would you or another
member of your organization be willing to contribute a fix for this bug to the
FiftyOne codebase?
from the FiftyOne community
The text was updated successfully, but these errors were encountered: