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

handling modifications to or deletion of network drives/biases #248

Closed
rythorpe opened this issue Jan 20, 2021 · 2 comments
Closed

handling modifications to or deletion of network drives/biases #248

rythorpe opened this issue Jan 20, 2021 · 2 comments

Comments

@rythorpe
Copy link
Contributor

Here's a place to resolve our discussion started in #221 about whether or not we should create formal methods in Network for modifying or deleting drive/bias attributes that have already been created.

As @ntolley pointed out, there is a common use case for modifying properties of a drive/bias after it has been added, attached, and possibly instantiated within a Network instance particularly if the user is running hnn-core using a jupyter notebook. In our example scripts, we also demonstrate ways that users can copy and modify properties of a given Network instance in order to rerun the simulation for different results. Regardless of whether or not we decide to expand the API, we should streamline our examples so that we either promote modification of existing (or copied) Network instances or solely promote the creation of new Network instances.

@jasmainak
Copy link
Collaborator

duplicate of #235 ?

@rythorpe
Copy link
Contributor Author

Sure enough, I didn't see that one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants