Skip to content
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

Maia data import #95

Closed
dlangenk opened this issue Feb 18, 2022 · 4 comments
Closed

Maia data import #95

dlangenk opened this issue Feb 18, 2022 · 4 comments

Comments

@dlangenk
Copy link
Member

It would be great to be able to import data into Maia using the API. This way Maia could be used as a visualization device for external algorithms and would make the integration of new methods more easy and flexible.

@mzur
Copy link
Member

mzur commented Sep 27, 2022

This could be done as follows: Offer an option similar to the "training data method" to "upload detections" in the form to create a new MAIA job. Users can upload a COCO file (or iFDO?) here. When the job is submitted the uploaded file is parsed and annotation candidates are generated directly from the file. Then the job proceeds to the last stage, skipping novelty detection and object detection. It should also generate feature files for image sorting (#27).

This option should support more shapes than just circles. This must be supported in the "refine" view of the annotation candidates, which will probably involve most work required to implement this feature.

@dlangenk
Copy link
Member Author

If it is not a xor between COCO and iFDO I don't mind 😉. But otherwise an additional tool has to be written to convert a fiftyone/mmdetection/detectron/... dataset to iFDO and then the usage of this feature is limited to some degree.

@mzur
Copy link
Member

mzur commented Apr 19, 2024

This can use the new metadata parsers of biigle/core#709 We can implement a COCO parser that can both be used in the volume creation flow as well as the MAIA upload. This way we can support iFDO (and maybe other formats) for the MAIA upload, too.

@mzur
Copy link
Member

mzur commented Apr 19, 2024

Thinking about this... maybe this will become obsolete with the new create volume flow? If you generate offline detections you can simply upload them as a new volume and use Largo for review? You can even upload and review predicted classes this way.

@mzur mzur closed this as completed Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants