Conversation
Remove unused data and scripts Roberts param files exist in ibs_projects, and is also not really used in ISF beyond the one ongoing
… top of module, update docs
getattr and setattr work fine tested reproducibility with a single synapse activation simulation for identical results
- not dependant on barrel cortex - not dependent on old cluster paths - still can do the C2-relative redirect Todo: improve implementation, adapt tutorial Todo: finalize refactoring source data files etc
Added explicit default values for ongoing activity rates. useful for future
Network params can now be used in a builder pattern This makes it easy to add synapse dynamics, ongoing activity, evoked activity, and network embeddings to network parameter files in a modular, model system-agnostic way Todo: test if this gives the results we want and deprecate the runfiles Todo: ensure backwards compatible
Gives same results as old method :) Must however be invoked differently Todo: compatibility fix
Instead of having this specific reader for reading in whisker-evoked activity data, I simply pre-process the data here. The reader then only needs to worry about fetching the correct file, which I believe is the most configurable and general way it should work. I kept a notebook outlining how exactly I "augmented" the data. This was not very well documented. Added readme to explain the data as well.
Todo: test if this works, gives same results, and can be invoked same way
Had some wrong mappings
…dditional sources of activity
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #465 +/- ##
===========================================
+ Coverage 47.18% 47.75% +0.56%
===========================================
Files 243 244 +1
Lines 22476 22207 -269
===========================================
- Hits 10605 10604 -1
+ Misses 11871 11603 -268 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This was referenced Mar 19, 2026
Merged
Merged
bgmeulem
added a commit
that referenced
this pull request
Mar 23, 2026
Should be merged after #465 # Refactor network embedding pipelines ## The problem The network embedding pipelines is according to Udvary et al 2022 and Egger et al 2014. The current implementation has some hardcoded paths to data that are unclear to other users, and are not very generalizable ## The solution The top-level network mapping invocation has been refactor to a strategy pattern to decide which pipeline to invoke. This makes future extensions a bit easier Data locations have been moved to the user configuration. ## Todo - To which extent should we pre-process and explore the barrel cortex data? - To which extent do we want this specific pipeline to be generally applicable? - Should we suggest other researchers to start from syn and con files rather than extensively exploring the udvary2022 requirements?
bgmeulem
added a commit
that referenced
this pull request
Mar 23, 2026
This pr should be merged after #465 and #466 This PR removes all mentions of "ApicalDendrite" in those situations where it is overly specific. This means that it is still ok to use it for examples, some default values, L5PT specific functions, and those functions that specifically target "ApicalDendrite" Todo: refactor scim (again) to also make it more generic in the network embedding procedure
Open
bgmeulem
added a commit
that referenced
this pull request
Mar 23, 2026
This PR should me merged after #465 and #466 This PR moves the mechanisms to the user config folder. Instead of adding project-specific or cell type specific additional folders in a single `mechanisms` directory, the user can now simply adapt mechanisms in the dedicated `config/user` directory Sidenote: I removed `scale_apical_morph_86` here, but kept it in the test suite for reproducibility tests
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refactor the network parameter builder
Problem
The network parameters as built by the top-level pipeline
I.create_network_parameterscontained many hardcoded paths to activity data.This activity data was undocumented.
This method is poorly generalizable to toher researchers or model systems
Solution
Network parameters can now be built using the
NetworkParamBuilder, adding separately:I updated the tutorials and top-level pipeline
I.create_network_parametersto match the new syntax. As long as you use positional arguments (not keyword arguments), the top-level pipelines and results are identical.Testing and API stability
I tested backwards compatibility by cross-referencing with marias network parameter files from the decoding project for morphologies 64, 71, 88, 89, 91, for all columns, for all stimuli, and for positoin 1 in each column. All network parameters are exactly the same, except for the excitatory synaptic weights, which I didn't scale (see test code below)
To do so, I pre-processed the activity data so we don't need to infer the C2-relative stimulus / recording site.
Instead, I did the following:
Passing a string to the "whisker" argument is now interpreted as a globstring. The top-level pipeline expects you to then additionally pass a directory it should search in. If not, it falls back to a user-configured default data directory. This is currently set to our example data folder.
When it comes to generating activity data from a template or from scratch, all input data is now explicitly documented, and configured in
config/user, instead of hardcoded in the run scripts. The tutorial explores this data more extensively and clearly now.