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.

Sign up for GitHub

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

Jump to bottom

WTNetwork Threshold Function Performance #133

Open
3 tasks
dglmoore opened this issue Apr 13, 2019 · 0 comments
Open
3 tasks

WTNetwork Threshold Function Performance #133

dglmoore opened this issue Apr 13, 2019 · 0 comments
Labels
performance weight-threshold

Comments

@dglmoore
Copy link
Contributor

When we compare the performance of, for example, the Landscape.attractors algorithm on a WTNetwork and an equivalent LogicNetwork, we find that the former is about 2x slower. Profiling suggests that this is due in large part to the threshold functions.

Can we improve the performance by modifying the implementation of

  • WTNetwork.split_threshold
  • WTNetwork.negative_threshold
  • WTNetwork.positive_threshold
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
performance weight-threshold
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dglmoore @EnricoBorriello