semvec/pypi-packages huggingface dataset:
tiptop-ipy 0.2.0
A Python wrapper for the ESO TIPTOP adaptive optics PSF simulation microservice
Requires Python: >=3.9
Keywords: astronomy, adaptive optics, PSF, TIPTOP, ESO

# TIPTOP-iPy

A Python wrapper for the ESO TIPTOP adaptive optics PSF simulation microservice.

    $ pip install git+https://github.com/astronomyk/tiptop_ipy.git

## Basic Usage

List the available instrument templates:

    >>> from tiptop_ipy import TipTop

    >>> TipTop.list_instruments()
    ['ANDES', 'ERIS', 'ERIS_LGS', 'HARMONI_SCAO', 'HarmoniLTAO_1', ...]

Create a `TipTop` object and generate a PSF:

    >>> eris = TipTop("ERIS")
    >>> result = eris.generate_psf()
    >>> result.writeto("eris.fits", overwrite=True)

The result object provides convenient access to the PSF data:

    >>> result.psf.shape
    (1, 256, 256)

    >>> result.strehl
    array([0.891])

    >>> result.fwhm
    array([44.1])

## Playing with parameters

Parameters are accessed using tuple indexing on the `TipTop` object:

    >>> eris["atmosphere"]
    {'Cn2Weights': [0.59, 0.02, ...], 'Cn2Heights': [30, 140, ...], 'Seeing': 0.8, ...}

    >>> eris["atmosphere", "Seeing"]
    0.8

Values can be updated using the same syntax.
For example, we can ask TIPTOP to generate two PSFs (on-axis, 10" off-axis):

    >>> eris["sources_science", "Zenith"] = [0, 10]
    >>> eris["sources_science", "Azimuth"] = [0, 180]
    >>> result = eris.generate_psf()

    >>> result.plot()

To see what you've changed from the template defaults:

    >>> eris.diff()
    {'sources_science': {'Zenith': ([0], [0, 10]), 'Azimuth': ([0], [0, 180])}}

To reset back to the original template:

    >>> eris.reset()

## PSF FITS file format

The TIPTOP server returns a FITS file with 5 HDUs:

    >>> eris = TipTop("ERIS")
    >>> result = eris.generate_psf()
    >>> result
    TipTopResult(1 wavelength(s), 1 position(s), 5 HDUs, Strehl=0.891)

    HDU 0: PrimaryHDU — header with config parameters and timing
    HDU 1: ImageHDU   — PSF CUBE (N, FOV, FOV)
    HDU 2: ImageHDU   — OPEN-LOOP PSF (FOV, FOV)
    HDU 3: ImageHDU   — DIFFRACTION LIMITED PSF (FOV, FOV)
    HDU 4: ImageHDU   — Radial profiles

Strehl ratios, FWHM values, and coordinates are read from the PSF CUBE header cards.

## Documentation

Full documentation is available at [tiptop-ipy.readthedocs.io](https://tiptop-ipy.readthedocs.io).

For details on the TIPTOP configuration parameters, see the
[TIPTOP documentation](https://astro-tiptop-services.github.io/astro-tiptop-services/).

For bug reports and feature requests, please use the
[GitHub issues page](https://github.com/astronomyk/tiptop_ipy/).
pum 1.5.3
Pum stands for "Postgres Upgrades Manager". It is a Database migration management tool very similar to flyway-db or Liquibase, based on metadata tables.
Requires Python: >=3.10
Keywords: postgres, database, versioning

# PostgreSQL Upgrades Manager (PUM)

![logo](https://raw.githubusercontent.com/opengisch/pum/main/docs/docs/assets/images/pum.png)

## New version

This is the code of pum version 1.
You can find version 0.x documentation at https://github.com/opengisch/pum/tree/old-v1

## About

PUM (PostgreSQL Upgrades Manager) is a robust database migration management tool designed to streamline the process of managing PostgreSQL database upgrades. Inspired by tools like FlywayDB and Liquibase, PUM leverages metadata tables to ensure seamless database versioning and migration.

## Key Features

- **Flexible Database Connections**: Connect using PostgreSQL service names or direct connection strings (URI or parameters).
- **Command-line and Python Integration**: Use PUM as a standalone CLI tool or integrate it into your Python project.
- **Database Versioning**: Automatically manage database versioning with a metadata table.
- **Changelog Management**: Apply and track SQL delta files for database upgrades.
- **Droppable & recreatable app with data isolation**: PUM supports a clean rebuild workflow where an application environment can be dropped and recreated deterministically using hooks (pre and post migration).


## Why PUM?

Managing database migrations in a Version Control System (VCS) can be challenging, especially for production databases. PUM simplifies this process by embedding version metadata directly into the database, enabling efficient tracking and application of migrations.

PUM was developed to address challenges in the [TEKSI](https://github.com/TEKSI) project, an open-source GIS for network management based on [QGIS](http://qgis.org/).
herd-core 0.0.1
Agent team governance framework — execution-agnostic roles, authority models, decision capture, and craft standards for AI agent teams.
Requires Python: >=3.10
Keywords: agent-framework, agents, ai, craft-standards, decision-records, governance, multi-agent, team-topology

# The Herd

**Agent team governance framework.**

Execution-agnostic roles, authority models, decision capture, and craft
standards for AI agent teams.

> Your agent framework runs the agents. The Herd runs the team.

## Status

Pre-release — package name reserved. First functional release coming soon.

## What is The Herd?

The Herd is a governance framework for AI agent teams. It provides:

- **Canonical role definitions** with authority boundaries
- **Craft standards** that shape how agents work, not just what they do
- **Decision capture** (HDR — Herd Decision Records) from natural conversation
- **Pluggable execution** — bring your own agent engine (Claude Code, Codex, CrewAI, or anything else)
- **Team topology** — multi-team, multi-machine, multi-engine in one config file
- **QA gates** with tiered validation (automated + architectural review)

## Architecture

The Herd is modular by design:

| Package | Purpose |
|---------|---------|
| `herd-core` | Core framework, interfaces, topology, roles, HDR, craft |
| `herd-agent-claude` | Execution adapter for Claude Code CLI |
| `herd-store-duckdb` | Storage adapter (local DuckDB + MotherDuck) |
| `herd-ticket-linear` | Ticket lifecycle adapter (reference implementation) |
| `herd-repo-github` | Repository operations (PRs, branches, commits) |
| `herd-notify-slack` | Notification output |

## Quick Start (coming soon)

```bash
pip install herd-core herd-agent-claude herd-store-duckdb
herd init
```

## License

MIT