Rebase merger time regression branch on dev
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 28
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 7
Description
Rebase regress-merger-time onto dev and resolve conflicts in libs/architectures/architectures/supervised.py (regression head), projects/export/export/main.py (multi-output names), projects/infer/infer/data.py and postprocess.py (heatmap handling), and projects/train/train/data/base.py (regression dataset).
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
Compare the regress-merger-time branch with dev and inspect conflicts in the five listed Python files: supervised.py, export/main.py, infer/data.py, postprocess.py, and train/data/base.py. Done means the branch is rebased onto dev and the conflicts are resolved while preserving the regression head, multi-output names, heatmap handling, and regression dataset changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100