Logging code in workflow.R
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 48.7k
- Forks
- 7.7k
- PR merge metrics
- No merged PRs in 30d
Description
🌟 Feature Description
Logging code in workflow.R
Motivation
Currently, Qlib could log commit hash value of code.
But user usally will not commit code before every experiments.
If Qlib can log the code diff between working directory and HEAD, it will bring much convenience for exp reproduction.
Alternatives
Sacred could automatically log stdout std error.
Contributor guide
No contributing guide indexed for this repository
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 workflow.R and the existing code that logs the commit hash. Check how workflow metadata is recorded, then define how the working-directory diff should be captured relative to HEAD and how it should appear in experiment records. Done means an experiment preserves that diff for later reproduction, with coverage for the logging behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100