semvec/pypi-packages huggingface dataset:
hyprmonmon 0.1.0
Automatically manage multiple monitor setups for hyprland
License: MIT
Requires Python: >=3.12

# hyprmonmon

Manage, remember and monitor different display layouts for hyprland.

Install `click`, `hyprpy` and `nwg-displays`.

Add the following autostart to `hyprland.conf`:
```
exec-once = hyprmonmon watch
```

To configure the current layout using `nwg-displays`, run: `hyprmonmon
config`.

To re-apply the current layout use `hyprmonmon apply`.

By default, `hyprmonmon config` will ask `nwg-displays` to configure 10
workspaces, to use a different amount of workspaces, use `hyprmonmon config
--num_ws 5`.

`hyprmonmon` will save the display / workspace layout in config files based
on the fingerprint of your current setup. The fingerprint is based on a hash
of the name and description of each active display.

If a new display is connected, `hyprmonmon watch` will automatically try to
load the config for the new fingerprint.

The per-fingerprint config files can be found in `~/.config/hyprmonmon`.
frequenz-api-assets 0.1.0
Frequenz gRPC API to retrieval platform assets information
License: MIT
Requires Python: <4,>=3.11
Keywords: frequenz, python, api, grpc, protobuf, rpc, assets, assets, microgrid, gridpools, components

# Frequenz Assets API

[![Build Status](https://github.com/frequenz-floss/frequenz-api-assets/actions/workflows/ci.yaml/badge.svg)](https://github.com/frequenz-floss/frequenz-api-assets/actions/workflows/ci.yaml)
[![PyPI Package](https://img.shields.io/pypi/v/frequenz-api-assets)](https://pypi.org/project/frequenz-api-assets/)
[![Docs](https://img.shields.io/badge/docs-latest-informational)](https://frequenz-floss.github.io/frequenz-api-assets/)

## Overview

The Frequenz Platform Assets API allows for the retrieval of platform assets information. Unlike CRUD-centric 
APIs, the focus here is on accessing already registered assets ranging from microgrids and gridpools to 
individual electrical components within these structures, such as sensors and their respective electrical connections.

## Objective

The main objective is to enable the building of intelligent cloud applications that can orchestrate and manage 
microgrids and gridpools for various purposes. This includes discharging batteries in a coordinated manner 
across multiple microgrids, optimizing spot market trading based on real-time grid consumption, and more.

## Key Features

- Asset Retrieval: Provides programmatic access to a wide range of platform assets, including microgrids, 
   gridpools, electrical components, and connections.
- Data-Driven Optimization: Facilitates the development of applications that can read asset information and 
   statuses for real-time decision making.
- Scheduling Insights: Enables applications to understand and adapt to gridpool schedules for improved spot 
   market trading.

## Scope and Limitations

- Retrieval of detailed asset data for various entities such as microgrids, gridpools, and their electrical components.
- Enabling advanced analytics and data-driven decisions for cloud applications.
- Read-Only: The API is designed for data retrieval and doesn't support CRUD operations for assets.
- Dependence on Platform: The quality and timeliness of data are dependent on the capabilities of the underlying platform.

## Target Audience

The API is primarily geared towards cloud application developers focused on building intelligent software 
solutions for orchestrating microgrid operations or facilitating gridpool trading. 

## Contributing

If you want to know how to build this project and contribute to it, please
check out the [Contributing Guide](CONTRIBUTING.md).