Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Analysis of Hippocampus-CA1 circuit #331

Closed
alex4200 opened this issue Jul 31, 2018 · 2 comments
Closed

Analysis of Hippocampus-CA1 circuit #331

alex4200 opened this issue Jul 31, 2018 · 2 comments
Assignees
Labels
Type_New Label to identify a new use case

Comments

@alex4200
Copy link
Contributor

alex4200 commented Jul 31, 2018

Summary

Aspect Detail
Summary New test to compare the synapses distribution of different m-type cells across the CA1 layers. The outcome will be a notebook showing how to use a test for synapses distributions of the Hippocampus CA1 circuit BBP-model.
Usecase Group Validation
State
Expert Pedro
Scientific User
Deadline June 2019
Target audience Experts in CA1
Target interface Notebook
HPC Requirements
Dependencies
Nominal runtime

Remove anything that does not apply

List of features

What does your use case do (or the new/changed features)? What activities can users perform while using it? What makes it different from similar use cases? List the main functions that you will build into your product here. Also specify the priority ‘mandatory’, ‘important, ‘nice to have’.

Acceptance Tests

Define here the acceptance tests to evaluate the use case’s compliance with the requirements as defined above. Also possible end users for testing can be included here.

Extra Requirements

System

Does this use case require any special system requirements (any special software package)? Does this use case require HPC access? If so, which ones? List detailed system requirements here.

Performance

What are additional performance requirements for this use case? What time should it take to run from start to end?

@alex4200 alex4200 added the Type_Feature Label to identify new/changed features for an existing use case label Jul 31, 2018
@alex4200 alex4200 added this to the Issues for 2018-12 milestone Jul 31, 2018
@alex4200 alex4200 added Type_New Label to identify a new use case and removed Type_Feature Label to identify new/changed features for an existing use case labels Jul 31, 2018
@alex4200 alex4200 modified the milestones: Issues for 2018-12, M24: March 2020 Aug 20, 2018
@pedroernesto pedroernesto self-assigned this Sep 25, 2018
@pedroernesto
Copy link
Collaborator

Better to move the deadline to June/2019. It depends on setup completion of several tools and HPC resources.

@alex4200
Copy link
Contributor Author

alex4200 commented Apr 3, 2019

Task included in #332.

@alex4200 alex4200 closed this as completed Apr 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type_New Label to identify a new use case
Projects
None yet
Development

No branches or pull requests

2 participants