neuropoly / neuropoly/SmaugLab
Order of transforms
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8
- Forks
- 0
- Avg merge
- 5d 2h
- Merged PRs (30d)
- 11
Description
Make it so the order of transforms from the config file is used
And/or support ordering based on pre-defined tags (geo, ta, ge) or (geo, ge, ta) ...
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 by locating where transforms are read from the config file and where their execution order is determined. Compare the requested config ordering with the proposed geo, ta, and ge tag orderings, then clarify whether both ordering approaches are required. Done means transforms run in the selected order and the behavior is covered by the project's existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100