[FEATURE] computation time and RAM monitoring

Open
#185 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
c
Domain
performance, testing

Research direction

No files, tests, or entry points are named. Start by reviewing the repository's test setup and the referenced panoptica approach, then clarify where computation time and RAM measurements should be collected and reported. Done should be defined by an agreed monitoring output that makes code-change effects visible.

Written by the indexing model from the issue text.

Description

enhancement

similar to panoptica, we would like to have computation time and ram monitoring for our tests to monitor the effects of code changes ;)

Dominant language
C
Stars
39
Forks
11
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from BrainLesion/preprocessing

All issues in BrainLesion/preprocessing

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.