Echtzeitsysteme / Echtzeitsysteme/iflye
Metric idea: Embedding quality per time
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 5
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Maybe we can implement a metric that gives a result for "embedding quality per time". This could give a trade-off between long runtimes but good results (pure ILP algorithms) and short runtimes but bad results (pure heuristic algorithm).
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
The issue names no files, tests, or entry points. First inspect the existing evaluation code and how ILP and heuristic algorithms record embedding quality and runtime; done requires a clearly defined, reproducible metric that supports comparing those trade-offs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- networking, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100