Define a format for the configuration metadata and tool to rerun a job from it
Open
- Dominant language
- C++
- Stars
- 14
- Forks
- 34
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 6
Description
Following the conversation in https://github.com/key4hep/k4FWCore/issues/329#issuecomment-2988673619 and https://github.com/key4hep/k4FWCore/pull/329#issuecomment-2990054786, it would be good to define a format for the configuration metadata, possibly together with a tool to run jobs from it that would need to parse it.
Contributor guide
Research direction
Start by reading the discussion in issue 329 and the referenced pull request 329 comment. Define a configuration-metadata format and determine the scope of a tool that can parse it and rerun jobs; completion means both the format and the tool requirements are agreed and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100