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

step-fields

v1.0.0

Published

spatial fields for computation and imaging

Downloads

3

Readme

Overview

STEP is a work in progress medical image computing project.

The goal is to implement GPU accelerated volume calculations using JavaScript and WebGL 2.0. Everything should run in the browser with only data access coming from external servers.

Internal data structures should be as close as possible to native DICOM representations.

Conventions

Spaces

Coordinates and matrices are defined with respect to reference coordinates with these names:

Patient or LPS is world space in millimeters with respect to the subject (patient) in LPS convention (left, posterior, superior) as defined in DICOM and Slicer.

Pixel or IJK is index space of the array. Layout in memory is as defined by the DICOM multiframe dataset values, but is for now implemented as pixel = volume[k][j][i] or pixel = volume[slice][row][column] where slice goes from 0 to dataset.NumberOfFrames-1, row goes from 0 to dataset.Rows-1, and column goes from 0 to dataset.Columns-1. The elements of a pixel coordinate are stored in column, row, slice order for consistency with stp space order.

Texture or stp is coordinate access when the volume is loaded in a WebGL 3D texture. Here the coordinates are 0 to 1 with sample.s selecting the column, sample.t selecting the row, and sample.p selecting the slice (reverse order of Pixel space).

Naming

Values that map from one space to another are named to indicate the direction of mapping. E.g. patientToPixel is a 4x4 matrix that maps from LPS space to slice,row,colum space and textureToPixel is a vec3 that goes from stp space to slice,row,colum.

Acknowledgments

This work is supported in part by the Neuroimage Analysis Center, 4P41EB015902.