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

nnstats

v0.0.8

Published

Javascript package for analyzing Neural Networks.

Downloads

5

Readme

nnstats

NPM version Build Status Dependency Status Coverage percentage

Javascript package for analyzing Neural Networks.

Installation

  npm install --save nnstats

Usage

Basic usage

The following show basic usage for analyzing CNN in Tensorflow (padding takes either SAME or VALID).

'use strict';


let nnStats = require('./');
let analyzer = nnStats.analyzer;
let utils = nnStats.utils;

let model = [{
	'type': 'conv',
	'filter': [5, 5, 32],
	'strides': [1, 1],
	'padding': 'SAME',
	'datasize': 4
},{
	'type': 'pool',
	'filter': [2, 2],
	'strides': [2, 2],
	'padding': 'SAME',
	'datasize': 4
},{
	'type': 'conv',
	'filter': [5, 5, 64],
	'strides': [2, 2],
	'padding': 'SAME',
	'datasize': 4
},{
	'type': 'pool',
	'filter': [2, 2],
	'strides': [2, 2],
	'padding': 'SAME',
	'datasize': 4
},{
	'type': 'fc',
	'hidden': 2048
},{
	'type': 'fc',
	'hidden': 1000
}]


let input = [28, 28, 1]
let options = {
	tensorflow: true
}

let stats = analyzer.analyzeNetwork(model, input, options);

utils.report(stats);

Model layout

Currently, here are 3 supported layers type: convolution layer (conv), pooling layer (pool), and fully-connected layer ('fc'). In all cases, type field is required in layer object to identity layer type.

Fields in conv layer:

  1. filter: 3D array kernal size (height, width, outChannel).
  2. strides: 2D array strides size (height, width).
  3. padding: 2D array padding size (height, width).
  4. datasize (optional): number of byte of one value (for float32, this should be 4 because 32 / 8 = 4). This value is used to calculate how much memory needed for the network.

Fields in pool layer:

  1. filter: 2D array kernal size (height, width).
  2. strides: 2D array strides size (height, width).
  3. padding: 2D array padding size (height, width).
  4. datasize (optional): number of byte of one value (for float32, this should be 4 because 32 / 8 = 4). This value is used to calculate how much memory needed for the network.

Fields in fc layer:

  1. hidden: number of neurons in hiddent layers.

Documentation

https://knapsack-lab.github.io/nnstats/

Created with

Yeoman and Generator-simple-package

License

MIT © nghiattran