npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

node-red-contrib-signal-interval

v0.0.3

Published

Node-RED node to aggregate pairs of signals into intervals

Downloads

9

Readme

node-red-contrib-signal-interval

The purpose of this node is to identify pairs of signals/payloads and return the time distance (interval) between them.

A pair of signals consists of an on signal followed by an off signal. Upon arrival of the off signal, the node will emit a payload which includes information about the duration of the on period which is defined as the interval between the signals.

Example:

Input:  on--off-----on------------off---
             |                     |
             |                     |
Output:  interval: 0.2 s     interval: 1.2 s

Payload format

Input

The expected input for the node takes the form

{
    cmd: 'on' | 'off'
}

i.e. the on/off value is expected on the cmd property by default; a different property name can be specified on the node configuration if needed (only top-level properties supported, no nesting).

Output

The output format looks like

{
    type:"actual" | "dummy",
    duration:0.618
}

with the duration in seconds and the type explained below.

Noise

Generally transmissions can be noisy and signals can be blocked along the way. In our case, the effect of this would be that one (or multiple) signals are dropped and don't reach the node. If we miss out on an entire pair of signals (i.e. the on and the off signals are dropped) there is nothing we can do. If, however, the environment is not too noisy we can assume most of the signals coming through and we only have to compensate for a missing on or off signal every now and then. We can detect this situation by two consecutive on or two consecutive off signals. In this case, we know that we have missed a signal but don't know when, so we just assume a default interval duration. This is indicated by type: "dummy" with the default/dummy duration being configurable in the node configuration (also check the tests in spec.js for some examples).