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

@psbrandt/edf-parser

v0.2.8

Published

Edf parser

Downloads

3

Readme

Edf File parser

Build Status

Package to parse/process edf file as detailed on the specification

Important: This is not and edf+ parser

Terminology

Below some terminology found in the source code that will help understanding the implementation faster:

DataBlock: The raw byte-encoded data samples as found in the file.

Record: The decoded samples found on a data block.

SignalProcessor: Interface for objects that can process/translate a raw set of bytes, representing the digital values,into the real physical values of a signal.

RecordProcessor: Interface for objects that can process/translate and entire datablock into its record.

Sample

if there is no time for to much reading file sample/sample.js provides a quick usage intro.

Some Implementation details

edf.DataBlock, implementing the stream.Transform interface, should be pipe into a stream reading the edf raw content, it will parse the header, signals headers, triggering the events header and signals respectivily containing the models, right after it will begin streaming each datarecord as a block

edf.RecordsStream, also implementing the stream.Transform interface, is design to take as input each datablock and translate it into a record, which gets push out the pipe (using object mode)for extra processing. the RecordStream does the transformation with the help of an object implementing the edf.RecordProcessor

edf.RecordProcessor object is a composition of multiple edf.SignalProcessor, and each signal processor is in charge of processing/decoding the data of the signal it represents. The responsability of a RecordProcessor is simply coordinating between each signal processor and keeping a time log to determine the start time of each data record.

The idea behind the composition is that different implementations of the SignalProcessor can be combine together.As sample i see the to-be-implemented DiscardSignal processor which basically discards all signal data from the record (usefull if only a subset of the signals needs to be use) or the logarithmic transformation described here.

the edf.utils namespace contains utility functions that facilitates the interconnection of the different parts of the parser.