allow for non-complete emodels
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 30/100
Research direction
Start in bluepymm/prepare_combos/create_mm_sqlite.py around line 365, where missing emodels cause the crash. Read the surrounding check and the configuration handling, then determine how the proposed option should control incomplete emodels. Done means the process handles missing emodels without crashing when the option is enabled, while preserving the existing check otherwise.
Written by the indexing model from the issue text.
Description
If there are some missing emodels for some etypes, this is crashing:
https://github.com/BlueBrain/BluePyMM/blob/master/bluepymm/prepare_combos/create_mm_sqlite.py#L365
Maybe we could add an option from config to allow for non-complete emodels, and do:
morph_fullmtype_etype_map = morph_fullmtype_etype_map.dropna()
before the check.
- Dominant language
- Python
- Stars
- 13
- Forks
- 9
- 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 BlueBrain/BluePyMM
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
All issues in BlueBrain/BluePyMM
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100