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

llquantize

v0.0.6

Published

log/linear quantization

Downloads

37

Readme

llquantize - Log/linear quantization

Build Status

For more information on log/linear quantization, see this blog post.

To summarize: log/linear quantization addresses the problem of using the wrong aggregation resolution, which leads to "clogging the system with unnecessarily fine-grained data, or discarding valuable information in overly coarse-grained data".

It does this by logarithmically aggregating by order of magnitude, but linearly aggregating within an order of magnitude.

Example

var llquantize = require('llquantize')
  , llq = llquantize()

// Input some data points.
llq(0.54); llq(0.55)
llq(2);    llq(3)
llq(12);   llq(14)
llq(24)
llq(124);  llq(199)

// Get the accumulated data.
llq()
// =>
// { "0.5": 2
// , "2":   1
// , "3":   1
// , "10":  2
// , "20":  1
// , "100": 2
// }

As you can see, the closer to zero the data points approach, the greater the precision used to track/group them (and vice-versa).

API

llquantize([bucket_size=10, [steps=10]])

Arguments:

  • bucket_size - The factor by which the bucket size should increase. (i.e. the first bucket will have the size bucket_size, the next will be bucket_size^2...)
  • steps - The number of divisions per bucket,

Installation

$ npm install llquantize

License

MIT