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

Investigate issues with capturing vertices' exposure at time of adoption with node_threshold() #70

Open
henriquesposito opened this issue Jun 21, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@henriquesposito
Copy link
Contributor

henriquesposito commented Jun 21, 2024

Although our node_threshold() function is more flexible (i.e. works on various types of networks), results are not consistent with those of netdiffuseR. We should investigate and fix or explain why this happens.

For example:

library(netdiffuseR) c(netdiffuseR::threshold(medInnovationsDiffNet))

vs.

library(manynet) unname(c(node_thresholds(as_diff_model(medInnovationsDiffNet))))

@henriquesposito henriquesposito added the bug Something isn't working label Jun 21, 2024
@henriquesposito henriquesposito self-assigned this Jun 21, 2024
@jhollway jhollway changed the title Investigate issues with capturing vertexes exposure at the time of adoption with node_threshold() function Investigate issues with capturing vertices' exposure at time of adoption with node_threshold() Jun 21, 2024
@jhollway jhollway assigned jhollway and unassigned henriquesposito Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants