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

Boolean network sensitivity measures #17

Open
bcdaniels opened this issue Apr 5, 2017 · 3 comments
Open

Boolean network sensitivity measures #17

bcdaniels opened this issue Apr 5, 2017 · 3 comments

Comments

@bcdaniels
Copy link
Contributor

As defined in

Shmulevich, I., & Kauffman, S. A. (2004). Activities and sensitivities in Boolean network models. Physical Review Letters, 93(4), 48701–1. http://doi.org/10.1103/PhysRevLett.93.048701

  1. In a synchronous network, the sensitivity of a Boolean function f on state vector x is the number of Hamming neighbors of x on which the function value is different than on x. What is the analogous quantity for asynchronous networks, where the output of f is a distribution over states? Probably a KL-divergence would work, but this still requires some thought...
  2. The average sensitivity is defined by taking the expectation of the sensitivity with respect to a distribution over states x.
@dglmoore dglmoore changed the title Boolean network sensitivity measures (asynchronous networks) Boolean network sensitivity measures Apr 5, 2017
@hbsmith hbsmith added this to the Version 0.1.0 milestone Oct 6, 2017
@dglmoore
Copy link
Contributor

I think this and issue #40 are both addressed by #71. @bcdaniels What do you think?

@bcdaniels
Copy link
Contributor Author

The point of this issue was to extend the sensitivity analysis to asynchronous networks—but that will require more thought. (We were thinking that asynchronous stuff would wait for version 0.2.0...)

@bcdaniels
Copy link
Contributor Author

I believe we are now arguing that the same sensitivity measure should be informative for both synchronous and asynchronous networks, in which case this is no longer necessary. Right?

@dglmoore dglmoore modified the milestones: Version 0.1.0, Version 0.2.0 Jul 5, 2018
@dglmoore dglmoore modified the milestones: Version 1.0.0, Version 2.0.0 Aug 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants