Isolate BluePyMM from BluePyOpt using API provided by user

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

No files or tests are named; start by tracing the BluePyOpt-specific code in the BluePyMM main code and identify the model interactions that need an API boundary. Define the user-provided API and the proposed example submodule, then verify that the core no longer depends on BluePyOpt and the example supports easier model testing.

Written by the indexing model from the issue text.

Description

enhancement

To allow for easier testing of the e-models provided, and to simplify the bluepymm main code, we should remove the bluepyopt specific code from the bluepymm core, and let the user implement an API to interact with the model.
Example of api functions (names are crazy of course):
create_hoc_for_parameters
run_model_and_return_score_for_certain_morphology

We probably should add a submodule to bluepymm to provide an example of such an API that can be adapted for user specific needs if necessary.

Dominant language
Python
Stars
13
Forks
9
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 BlueBrain/BluePyMM

All issues in BlueBrain/BluePyMM

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.