consider file output code
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
No file, test, or entry point is named. Start by locating the code that produces file output and the algorithm-parameter dump, then determine which parameters and release boundaries are intended. Done means the repository has an agreed, implementable scope for exposing the post-analysis data.
Written by the indexing model from the issue text.
Description
Internally, we have a large dump of important algorithm parameters that we use for post-anlaysis. That code is not being released currently. Let's consider making that part of this repository also.
- Dominant language
- C++
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
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.
More from mitre/im_sample_algorithm
-
Remove old code Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mitre/im_sample_algorithm#14 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
mitre/im_sample_algorithm#15 ·
-
example analysis Opendocumentation
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
All issues in mitre/im_sample_algorithm
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·