open-index/open-npm huggingface dataset:
npm package: @metalfs/aggregate
Description: This operator computes the count, sum, minimum and maximum of a stream of incoming integer values.
Author: Robert Schmid
Latest version: 0.0.1

# Metal FS Aggregate Operator

This operator computes the count, sum, minimum and maximum of a stream of incoming integer values.

## Installation
```
npm install @metalfs/aggregate
```

## Operator Details

| | Description |
 -| -
Input  | Stream of 64-bit big endian unsigned integer values
Output | Four 64-bit big endian unsigned integer values: count, sum, min, max
Stream Width | Adaptable

### Options

No options are available.
npm package: @metalfs/colorfilter
Description: This operator takes a bitmap file as the input, transforms it to grayscale except pixels with red as the dominant color.
Author: Robert Schmid
Latest version: 0.0.2

# Metal FS Color Filter Operator

This operator takes a bitmap file as the input, transforms it to grayscale except pixels with red as the dominant color.

For general information on Metal FS, please visit the [project website](https://metalfs.github.io).

## Installation
```
npm install @metalfs/colorfilter
```

Example `image.json`:
```json
{
    "streamBytes": 8,
    "target": "SNAP/WebPACK_Sim",
    "operators": {
        "colorfilter": "@metalfs/colorfilter"
    }
}
```

## Operator Details

| | Description |
 -| -
Input  | Stream of bitmap data with a 138-byte header.
Output | Transformed bitmap data.
Stream Width | Adaptable

### Options

No options are available.
npm package: @metalfs/filter
Description: This operator filters the incoming stream of integer values by a range that is defined by a lower bound (inclusive) and an upper bound (inclusive).
Author: Robert Schmid
Latest version: 0.0.1

# Metal FS Filter Operator

This operator filters the incoming stream of integer values by a range that is defined by a lower bound (inclusive) and an upper bound (inclusive).

## Installation
```
npm install @metalfs/filter
```

## Operator Details

| | Description |
 -| -
Input  | Stream of 64-bit big endian unsigned integer values
Output | Dense stream of matching values, single 0-byte if no matching entries were found
Stream Width | Adaptable

### Options

| | Type | Description |
 -| -    | -
lower-bound | uint64 | Pass on values greater than or equal to this parameter
upper-bound | uint64 | Pass on values less than or equal to this parameter
npm package: @metalfs/snappy-decompress
Description: This implementation adds a thin wrapper over the [FPGA-Snappy-Decompressor ](https://github.com/ChenJianyunp/FPGA-Snappy-Decompressor) implementation to provide Metal FS integration.
Author: Robert Schmid
Latest version: 0.0.1

# Snappy Decompression Metal FS Operator

This implementation adds a thin wrapper over the [FPGA-Snappy-Decompressor
](https://github.com/ChenJianyunp/FPGA-Snappy-Decompressor) implementation to provide Metal FS integration.
npm package: @metaliq/elements
Description: MetaliQ custom elements
Author: tstewart@klaudhaus.com
Latest version: 1.0.0-beta.146

# @metaliq/elements

This package is part of the metaliq/ui collection of User/Human Interface mechanisms, and contains a number of standards compliant Web Components - a.k.a Custom Elements - which extend the HTML element syntax in useful ways, along with MetaViews based on these components allowing them to be easily integrated with MetaModels.

The components are:

## AnimatedHideShow

The `<animated-hide-show>` element has a property called `mq-hidden`. When this changes, the element changes its height between zero and `auto`, but there is a short transition period (defined by `mq-duration`) during which `auto` is replaced by a specific value, equal to the sum of all its childrens' heights, hence giving a smooth transition.

The `animatedHideShow` MetaView wrapper links the `mq-hidden` property to the `hidden` term from the MetaModel.

Unlike `expander`, animated-hide-show retains its descendant DOM structure when hidden. This may be useful for fields such as dropdowns and date-pickers using 3rd party libraries which need to be re-instantiated when removed and added to the DOM.

## Expander

The `<expander>` element automatically expands and contracts, with a transition on height over a given period (`mq-duration`), whenever its child content changes.

The `expander` MetaView wrapper 

Whilst the behaviour of `expander` is automatic and unlike like `animated-hide-show` doesn't require a linked property, it doesn't allow for the retention of inner content during the contraction phase.
npm package: @metaliq/forms
Description: A range of basic form fields for MetaliQ
Author: tstewart@klaudhaus.com
Latest version: 1.0.0-beta.146

# Metaliq Forms

The `@metaliq/forms` module provides various utilities and components for delivering online forms using the Lit based `@metaliq/presentation` policy.

It includes MetaViews for various typical form components such as text fields, checkboxes, buttons etc. It can be extended with more specific components including those in other `@metaliq` packages such as date pickers and selectors.

The provided components automatically link events to state management with `@metaliq/up`  as well as validation with inline field errors provided by `@metaliq/validation`.

TODO: Link to interactive component showcase.
npm package: @metaliq/metadoc
Description: MetaliQ publication target for generating MetaViews from documents
Author: tstewart@klaudhaus.com
Latest version: 1.0.0-beta.146

# @metaliq/metadocs

This module provides a MetaliQ publication target enabling lit-based MetaViews to be generated from documents authored in the Markdown format.

## Usage

A typical setup would be to process documents in a "content" directory and produce MetaView modules within the `src/gen` directory, 
which is then included in downstream compilation of other publication targets (such as `@metaliq/web-page-app`),
but excluded from version control in the default MetaliQ solution template.

```ts
  export const metadocGeneration: MetaModel<any> = {
    label: "Generate MetaViews from MetaDocs",
    publicationTarget: metadoc({
      inDir: "content",
      outDir: ""
    })
  }
```

Such a MetaModel doesn't really need to be based on a specific data type (hence the use of `any`), 
but this approach will be compatible with possible future support for multiple publication targets,
enabling the metadoc stage to be added to a typical web page app MetaModel.