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

Idea: Add rose(), fell() and possible other state-changing methods to analog sources OR create a specific ChangeDetector unit to do so for all nodes #89

Open
sofian opened this issue Jan 27, 2024 · 1 comment

Comments

@sofian
Copy link
Collaborator

sofian commented Jan 27, 2024

These would need an extra argument which could be some kind of tolerance.
Problem with this could be that is would represent an extra cost in memory to keep the previous value.

Different things to consider:

  • roseAbove(threshold)
  • fellBelow(threshold)
  • roseBy(variationPerSecond)
  • fellBy(variationPerSecond)
  • crossed(threshold)
  • changedBy(variationPerSecond)
@sofian
Copy link
Collaborator Author

sofian commented Jan 3, 2025

An alternative would be to create a specific Node for the job that would generalize the concept. It could potentially be able to handle both digital and analog nodes. Something like ChangeDetector or something.

@sofian sofian changed the title Idea: Add rose(), fell() and possible other state-changing methods to analog sources Idea: Add rose(), fell() and possible other state-changing methods to analog sources OR create a specific ChangeDetector unit to do so for all nodes Jan 3, 2025
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

1 participant