stac-extensions / stac-extensions/mlm
Provide examples of `processing` extension
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 67
- Forks
- 6
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 6
Description
🚀 Feature Request
The section https://github.com/stac-extensions/mlm/blob/main/README.md#model-band-or-variable-object provides references to:
- https://github.com/stac-extensions/processing/issues/31
- https://github.com/stac-extensions/processing/pull/33
In order to guide toward using processing extension to describe the script that is used to invoked the model (training or inference).
More concrete examples should be provided in best practices.
🔉 Motivation
Make it clear about the best practices and recommended strategies for alignment between users.
📡 Alternatives
applicationextension could be used either conjointly or as replacement- https://github.com/stac-extensions/mlm/issues/117
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Model Band or Variable Object section of README.md and review the linked processing issue and pull request. Add concrete best-practice examples showing how the processing extension describes scripts used for model training or inference, while considering the application extension and issue 117; done means the recommended alignment is clear to users.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100