BlueBrain / BlueBrain/BluePyMM

Add option to save traces during run_combos

Open
#151 3 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
13
Forks
9
PR merge metrics
No merged PRs in 30d

Description

Would it be possible to save the traces during run step? It can be useful to check the behaviour of different me-combos and to choose appropriate thresholds for model rejection. Maybe 'save_traces' can be specified as an option, with default as False (to avoid saving too many traces in case of large morphology releases).

Contributor guide

No contributing guide indexed for this repository

Research direction

Locate the run_combos entry point and inspect how the run step processes traces and options. Add an opt-in save_traces setting with a default of False, then verify that traces are saved only when enabled and that the existing run behavior remains unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.