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 model with BBP-tests #332

Open
alex4200 opened this issue Jul 31, 2018 · 17 comments
Open

Analysis of Hippocampus-CA1 model with BBP-tests #332

alex4200 opened this issue Jul 31, 2018 · 17 comments
Assignees
Labels
Topic_Validation Issues related to validation use cases Type_New Label to identify a new use case
Milestone

Comments

@alex4200
Copy link
Contributor

alex4200 commented Jul 31, 2018

Summary

Aspect Detail
Summary Notebooks with existing BBP-tests for CA1, that will be registered in the HBP-VF. Tests will be able to register the results. The outcome are 2-3 notebooks containing BBP tests for Hippocampus CA1 model, i.e. comparisons between model predictions and experimental data.
Usecase Group Validation
State
Expert Pedro
Scientific User
Deadline June 2019
Target audience Experts in CA1
Target interface Notebooks
HPC Requirements
Dependencies
Nominal runtime

List of features

  • A notebook showing how to use a test for synapses distributions of the Hippocampus CA1 circuit BBP-model.
  • 2-3 notebooks containing BBP tests for Hippocampus CA1 model, i.e. comparisons between model predictions and experimental data.
  • If possible, outcome of the tests are registered in the Validation Framework (VF)

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

Model

Main directory: proj_dir = '/gpfs/bbp.cscs.ch/project/proj42/'
***********
Directories:
***********
$proj_dir/circuits/CA1.O1/20181114 (file SEGMENT_payload.dat in this directory is not needed)
$proj_dir/entities/morphologies/20180417/
$proj_dir/entities/emodels/20180504b/
$proj_dir/entities/bionames/20181114
$proj_dir/entities/dev/atlas/O1-243

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

@pedroernesto
Copy link
Collaborator

pedroernesto commented Mar 29, 2019

Most of BBP-tests currently do not include any score to register on the VF, but plots and visual comparisons. A lot of coding is needed yet, and getting familiar with their own approaches and tools as well. More importantly, the right statistical test to produce a relevant score for each particular situation must be found.

I propose to eliminate this issue. I can then focus on more realistic goals related with issues #323 and #331

@apdavison
Copy link
Collaborator

I don't think we should eliminate this, it is very central to our work. I think the milestone of M18 seems reasonable.

@pedroernesto
Copy link
Collaborator

pedroernesto commented Apr 2, 2019

Ok.
Actually, one of those BBP cases with figures and no scores, is the one considered in issue #331: a real test for synapses distributions in the CA1 circuit model is missing. So, it would be clearer if the content of issue #331 were actually one of the notebooks I mentioned in the title of this issue #332. Issue #331 is redundant.

@alex4200 alex4200 added the Topic_Validation Issues related to validation use cases label Apr 3, 2019
@pedroernesto
Copy link
Collaborator

pedroernesto commented Sep 6, 2019

@alex4200 , I have spoken to Andrew about this use-case and we agreed that to start we will need:

(1) to have saved a model version of the CA1 circuit in some repository accessible from the Collab (currently > 300 Gb, but can likely be reduced, since not all files are needed for the use-case)

(2) that the user have access to BBP-VPN from the Collab, to install a few BBP software (e.g. BluePy). This will happen anytime a user runs the use-case for the first time.

@alex4200
Copy link
Contributor Author

alex4200 commented Sep 6, 2019

Moved to later milestone

@alex4200
Copy link
Contributor Author

@pedroernesto Where is that CA1 circuit saved currently? Can you give me the location?

@alex4200
Copy link
Contributor Author

@pedroernesto Before we can proceed, we need to clarify some issues, since the model you want to use is in the realm of BBP, and the Collaboratory and use cases on the Brain Simulation Platform in the realm of HBP.
I will keep you posted.

@romani79
Copy link
Collaborator

@pedroernesto, putting the model in BSP means sharing the model with everyone. We have to discuss which versions can be shared and in which modalities. We will have a meeting in 10 days and I hope we will have a plan.

@pedroernesto
Copy link
Collaborator

pedroernesto commented Sep 24, 2019

I understand your point, no problem.
Specifically, I told @alex4200 about the following directories of (a little bit old) release of the model. But maybe @romani79 can reduce the list of dirs/files needed, even more. In fact, this usecase will be based on a previous version of some his notebooks for circuit analysis. The directories are part of proj_dir = '/gpfs/bbp.cscs.ch/project/proj42/':

$proj_dir/circuits/CA1.O1/20181114 (excluding file SEGMENT_payload.dat of this directory)
$proj_dir/entities/morphologies/20180417/
$proj_dir/entities/emodels/20180504b/
$proj_dir/entities/bionames/20181114
$proj_dir/entities/dev/atlas/O1-243

The tests are about circuit structure only, no simulation results.

@alex4200
Copy link
Contributor Author

@romani79 Do you have any updates regarding this issue? In your last comment you mentioned a meeting - do you have any news from that?

@romani79
Copy link
Collaborator

We are going to release a rat CA1 microcircuit, but not the full-scale.
The release date should be defined. It could be at the same time of the release of the MOOC or earlier.

@pedroernesto
Copy link
Collaborator

@romani79 Was this mircro-circuit already released in some computer?

@romani79
Copy link
Collaborator

@pedroernesto, the O1 is available in a private HBP storage and it will be released once the paper is out. You can access it as part of the hippocampus team, but this is still confidential.
If you would like to access it, please ask @antonelepfl.

@alex4200 alex4200 removed this from the M22: January 2020 milestone Jan 28, 2020
@alex4200 alex4200 added this to the M24: March 2020 milestone Jan 28, 2020
@pedroernesto
Copy link
Collaborator

Ok, the point was granting access to that circuit to have this use-case on the Collab. But since not everybody on the Collab belongs to HBP, I guess this issue will stay opened till the paper gets published.

@alex4200
Copy link
Contributor Author

@romani79 @pedroernesto Should this task be moved to SGA3?

@pedroernesto
Copy link
Collaborator

As Armando says above, the circuit will not be released till the publication of the paper. But the circuit might still need fixes and the simulations more analysis and validations. Besides, the reviewing process after submission. This might take about 2 years I think. So, I propose to close this issue temporarily and then re-open it again afterwards.

@alex4200 alex4200 modified the milestones: M24: March 2020, SGA3 Mar 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Topic_Validation Issues related to validation use cases Type_New Label to identify a new use case
Projects
None yet
Development

No branches or pull requests

4 participants