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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@almaobservatory/model

v1.0.1

Published

ALMA observation tool data models: APDM types, value wrappers (DoubleWithUnit, Frequency, SkyCoordinates, etc.), and concurrent-access support.

Readme

@almaobservatory/model

An Angular library of TypeScript interfaces and helper builders for the ALMA observation-tool data model. The shapes mirror the APDM (ALMA Project Data Model) class structure described at https://www.roe.ac.uk/ukatc/projects/alma/APDM-Cycle10/.

The interfaces were generated by fetching json from the NGOT backend and using typescript-generator.

Shared between ngOT and SnooPI, and consumed transitively by @almaobservatory/astro.


What's inside

  • APDM domain typesObsProject, ScienceGoal, TargetParameters, SpectralSetupParameters, Rectangle, SinglePoint, etc.
  • Value wrappersDoubleWithUnit, Frequency, Velocity, Angle, SkyCoordinates, Latitude, Longitude
  • Spectral-setup modelReceiverBand, ReceiverBands table, science / expected / overlaid spectral-line shapes
  • Configuration types — control-and-performance, time estimates, calibration
  • Concurrent-access support — STOMP / WebSocket helpers used by ngOT's real-time collaboration features

The full public surface is in src/public-api.ts.


Installation

npm install @almaobservatory/model

If you're installing @almaobservatory/astro, this package is pulled in as a peer dependency automatically.

The @stomp/rx-stomp and uuid packages are runtime dependencies and will be installed alongside.


Usage

import { SkyCoordinates, Frequency, Field, buildField } from '@almaobservatory/model';

const coords: SkyCoordinates = {
  longitude: { value: 86.8, unit: 'deg' },
  latitude: { value: -70.7, unit: 'deg' },
  type: 'ABSOLUTE'
};

const freq: Frequency = { value: 230.5, unit: 'GHz' };

// Builder for a default SinglePoint Field
const field = buildField('ICRS');

Most consumers use these types alongside the converters in @almaobservatory/astro.


Development

The library lives under projects/model/ in the ngOT workspace. From the workspace root:

# Build the library to dist/model
ng build model

# Full workspace rebuild
npm run build-all

ngOT's own code imports from model (path-mapped to dist/model); you do not need to publish to npm in order to consume changes inside ngOT.


Publishing a new version

When the data model changes and external consumers (SnooPI, etc.) need to pick up the new version, publish a new release.

# 1. Bump the version in projects/model/package.json
#    (patch / minor / major per semver)

# 2. From the workspace root:
npm run publish-model

# 3. Verify
npm view @almaobservatory/model

When making breaking changes — renaming or removing types, restructuring an interface — bump the major version. Note that @almaobservatory/astro declares @almaobservatory/model: ^1.0.0 as a peer dependency, so a 2.0.0 of model requires a coordinated bump in astro.

Requires npm credentials for the @almaobservatory org.


License

ALMA Observatory.