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

ltlparse

v1.0.1

Published

Verify ROS states using LTL expressions

Downloads

5

Readme

ltlparse: temporal expression evaluator

ltlparse provides a language specification for defining temporal expressions which act on timed data, from either a simulation or a real-time system. During execution of either, ltlparse will verify the truthiness of the user-specified formulas.

Timed data is (currently) sourced from a set of user-specified comma-separated-value files, which are written to by external programs, and watched/read by ltlparse.

In the configuration file, each formula defined has an associated csv path, allowing for different formulas to work on data from different sources. Nonetheless, multiple formulas may take data from the same csv file.

The intended use-case of ltlparse is real-time evaluation of temporal formulas for error and safety-checking, especially for robotic systems.

This brings us to the following roadmap:

Development Roadmap

  • [x] Define syntax
  • [x] Define state-trajectory data format (JSON)
  • [x] Parse ASTs
  • [x] Finalize CLI
  • [x] Support unbounded linear operators
  • [x] Create API communication interface. (CSVs, for now)
  • [ ] Support bounded linear operators
  • [ ] Automated testing?

Syntax specification

To maximize usability, the arithmetic syntax is an infix representation similar to that used C/C++. Here we define all of the operators included in the syntax, in order of increasing execution priority.

| Priority | Ops | Arity | Description | | -------- | ---- | ----- | --------------------------- | | 1 | || | 2 | Logical OR | | 2 | ^^ | 2 | Logical XOR | | 3 | && | 2 | Logical AND | | 4 | == | 2 | Equals | | 4 | != | 2 | Not-equals | | 5 | < | 2 | Less-than | | 5 | <= | 2 | Less-than-or-equal | | 5 | > | 2 | Greater-than | | 5 | >= | 2 | Greater-than-or-equal | | 6 | + | 2 | Add | | 6 | - | 2 | Subtract | | 7 | * | 2 | Multiply | | 7 | / | 2 | Divide | | 7 | % | 2 | Modulo (Remainder) | | 8 | ^ | 2 | Power | | 9 | ! | 1 | Logical NOT | | 10 | N: | 1 | Next 1 | | 10 | A: | 1 | Always 2 | | 10 | E: | 1 | Eventually 3 | | 10 | U: | 2 | Until 4 | | 10 | R: | 2 | Release 5 |

_

| Unbounded LTL Operators | Description | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------- | | N: (x) | x must have held in the previous time instance. | | A: (x) | x must have held in all previous time instances, as well as the current instance. | | E: (x) | x must hold in any of the previous time instances, or the current instance. | | (x) U: (y) | x must have held at least until y became true, which must have held during any point, including now. | | (x) R: (y) | y had to have held until and including the first instance where x held; if x never holds, y must always hold. |