-
Notifications
You must be signed in to change notification settings - Fork 3
Roadmap for V2 of the ML Model Extension #7
Comments
Added some comments to the HackMD summary file. Happy to take on some of the tasks above to push this forward. |
Hi @devisperessutti thanks a bunch. I talked with Francis and I think the main things left to do are to update the example with the current spec (which I can do) and to make a schema json that follows the README description of the schema. We now have an example.json that combines required pystac common metadata with required ML Model Extension metadata. do you want to take a stab at writing the schema json and PR that against #2 ? I'm happy to review and assist. I think improving the spec so that output tasks have their own object structure can be a to do for post Version 2 so that we can start contributing smaller PRs after this large refactor. |
Sounds good, I'll try to tackle this early next week. |
Related by not directly impacting the roadmap: stac-extensions/ml-aoi#8 |
@rbavery I would like to get your review of rbavery#2 so that we can integrate it in #2, and realign all branches together. |
@devisperessutti |
Moved to crim-ca#4 |
Below are acceptance criteria for #2 the new version of the ML Model Extension. After all these items are done I think #2 is ready to merge and we can publish a new version 2 release to https://github.com/stac-extensions/ml-model/issues . I'm working on most of these, let me know if you think other acceptance criteria should be included cc @fmigneault
improve output section of the spec for popular detection tasks #4 by creating output objects for common detection tasks. At a minimum, start with single label classification, semantic segmentation, object detection. This will help resolve common ambiguities when interpreting model outputs, like the bbox coordinate ordering for object detection.EDIT this can be left for after the v2 releaseend_datetime: null
not supported by STAC Core spec(Datasets without time radiantearth/stac-spec#1268)
The text was updated successfully, but these errors were encountered: