semvec/pypi-packages huggingface dataset:
pyoes 0.26.1
pyoes
Requires Python: <=3.13,>=3.10
Keywords: compass, css, jinja2, pyramid, sass, style, templates

pyoes: Pyramid OE style
=======================

.. image:: https://travis-ci.org/OnroerendErfgoed/pyoes.png
        :target: https://travis-ci.org/OnroerendErfgoed/pyoes
.. image:: https://coveralls.io/repos/OnroerendErfgoed/pyoes/badge.png?branch=master
        :target: https://coveralls.io/r/OnroerendErfgoed/pyoes

.. image:: https://readthedocs.org/projects/pyoes/badge/?version=latest
        :target: https://readthedocs.org/projects/pyoes/?badge=latest
        :alt: Documentation Status
.. image:: https://badge.fury.io/py/pyoes.png
        :target: http://badge.fury.io/py/pyoes

Pyoes helps to share layout between different websites and applications of
Onroerend Erfgoed (Flanders Heritage).

More information about this library can be found in the docs `folder`. These can
be build using `Sphinx <http://sphinx-doc.org>`_.

.. code-block:: bash

    # activate your virtual env
    $ pip install -r requirements-dev.txt
    $ cd docs
    $ make html
    # You can also build a pdf, provided you have the correct latex toolchain installed.
    $ make latexpdf
ncCompare 0.2.5
netCDF Comparison Tool
Requires Python: <4.0,>=3.10

# netCDF Diff Comparison tool - ncpare

`ncpare` is a tool for comparing netCDF files, providing a detailed diff of their contents. It is designed to help users
identify differences between datasets stored in netCDF format.

![Python](https://img.shields.io/badge/Python->3.10-blue.svg)
[![Anaconda](https://img.shields.io/badge/conda->22.11.1-green.svg)](https://anaconda.org/)
[![Pip](https://img.shields.io/badge/pip->19.0.3-brown.svg)](https://pypi.org/project/pip/)
[![netcdf4](https://img.shields.io/badge/netcdf4-1.7.1.post1-brown.svg)](https://pypi.org/project/pip/)
[![xarray](https://img.shields.io/badge/xarray-2024.6.0-brown.svg)](https://pypi.org/project/pip/)
[![rich](https://img.shields.io/badge/rich-13.7.1-brown.svg)](https://github.com/Textualize/rich?tab=readme-ov-file)
![Tests](https://img.shields.io/badge/coverage-0%25-red)

![Output](https://github.com/anto6715/ncCompare/raw/master/docs/output.png)

## Installation

### Via PIP

```shell
pip install nccompare
```

## Usage

```shell
ncpare [-h] [-f--filter FILTER_NAME] [--common_pattern COMMON_PATTERN] [--variables VARIABLES [VARIABLES ...]] [--last_time_step] [-V] folder1 folder2

netCDF Comparison Tool

positional arguments:
  folder1               Path of first folder to compare
  folder2               Path of second folder to compare

options:
  -h, --help            show this help message and exit
  -f--filter FILTER_NAME
                        Filter to select files to compare. Examples: *.nc, *_grid_*
  --common_pattern COMMON_PATTERN
                        Common file pattern in two files to compareEs mfsX_date.nc and expX_date.nc -> date.nc is the common part
  -v, --variables VARIABLES [VARIABLES ...]
                        Variable to compare
  --last_time_step      If True, compare only the last time step available in each file
  -V, --version         Print version and exit

```

### Select Variables

It is possible to choose which parameter to compare:

```shell
ncpare folder1 folder2 -v "votemper" "vosaline"
```

![Variables](https://github.com/anto6715/ncCompare/raw/master/docs/variables.png)


### Filter files

As default **ncpare** read iterate over all files in **folder1** and expect to find them in **folder2**. Using filters,
it is possible to select only a subset of input files. For example:

```shell
ncpare folder1 folder2 -f "*_grid_T.nc"
```

### Compare files with different filenames

It is possible to compare two files also if the filenames are slightly different if they have a common pattern.
For example, if we have:

* `a/my-simu_19820101_grid_T.nc`
* `b/another-exp_19820101_grid_T.nc`

It is still possible to compare the file with:
```shell
ncpare folder1 folder2 --commom-pattern ".+_19820101_grid_T.nc"
```

Notice the regex syntax `.+` to match any pattern before `_19820101`

## Author

- Antonio Mariani (antonio.mariani@cmcc.it)

## Contributing
Contributions are welcome! Please open an issue or submit a pull request for any improvements or bug fixes.

## Contact
For any questions or suggestions, please open an issue on the project's GitHub repository.
lightcone-io 0.6.0
Module for reading SWIFT lightcone output.
Requires Python: >=3.10

# Lightcone I/O for SWIFT

This is a python module for reading lightcone output from SWIFT simulations.

The source code and issue tracker are hosted on github:
https://github.com/jchelly/LightconeIO

Releases are hosted on pypi: https://pypi.org/project/lightcone-io/

For documentation see: https://lightconeio.readthedocs.io/en/latest/

## Installation

For read-only use without MPI support, the module can be installed using pip:
```
pip install lightcone_io
```

## Building the documentation

The documentation is built using sphinx:
```
pip install sphinx sphinx-rtd-theme sphinx-autodoc-typehints
cd docs
make html
```

## Running unit tests

There are some unit tests which can be run with just
```
pytest
```
in the source directory.  This will test the classes for reading local
HDF5 files containing HEALPix map, particle and halo lightcone
data. These tests use downsampled lightcone outputs which are stored
in the git repository in `tests/data`.

To also test access to remote files:
```
pytest --hdfstream-server=<server_url>
```
pyEcoTrend-ista 3.5.0
Python EcoTrend-ista Api
Requires Python: >=3.11
Keywords: python, api, ecotrend, ista

# PyEcoTrend-ista

[![PyPI version](https://badge.fury.io/py/pyecotrend-ista.svg)](https://badge.fury.io/py/pyecotrend-ista) [![Downloads](https://pepy.tech/badge/pyecotrend-ista)](https://pepy.tech/project/pyecotrend-ista) [![Downloads](https://pepy.tech/badge/pyecotrend-ista/month)](https://pepy.tech/project/pyecotrend-ista) [![Downloads](https://pepy.tech/badge/pyecotrend-ista/week)](https://pepy.tech/project/pyecotrend-ista)

[![GitHub issues](https://img.shields.io/github/issues/Ludy87/pyecotrend-ista?style=for-the-badge&logo=github)](https://github.com/Ludy87/pyecotrend-ista/issues)
[![GitHub forks](https://img.shields.io/github/forks/Ludy87/pyecotrend-ista?style=for-the-badge&logo=github)](https://github.com/Ludy87/pyecotrend-ista)
[![GitHub stars](https://img.shields.io/github/stars/Ludy87/pyecotrend-ista?style=for-the-badge&logo=github)](https://github.com/Ludy87/pyecotrend-ista)
[![GitHub license](https://img.shields.io/github/license/Ludy87/pyecotrend-ista?style=for-the-badge&logo=github)](https://github.com/Ludy87/pyecotrend-ista/blob/main/LICENSE)
[![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg?style=for-the-badge&logo=code%20style-black)](https://github.com/psf/black)
![GitHub Release Date](https://img.shields.io/github/release-date/Ludy87/pyecotrend-ista?style=for-the-badge&logo=github)
[![codecov](https://codecov.io/github/Ludy87/pyecotrend-ista/branch/main/graph/badge.svg?token=BHU8J3OVRT)](https://codecov.io/github/Ludy87/pyecotrend-ista)
[![OpenSSF Best Practices](https://www.bestpractices.dev/projects/9868/badge)](https://www.bestpractices.dev/projects/9868)

[✨ Wishlist from Amazon ✨](https://smile.amazon.de/registry/wishlist/2MX8QK8VE9MV1)

---
Unofficial python library for the pyecotrend-ista API

![EcoTrend-ista](https://github.com/Ludy87/pyecotrend-ista/blob/main/image/logo.png?raw=true)
ryry-cli 6.13
ryry tools
Requires Python: >=3.5

ryry Python Tool
===============================================
The ryry Python Tool is a official tool, you can use it to **Register** device to ryry server, other person can use **ryry Application** assign tasks to you for implementation

Installation
------------

The ryry requires [Python](http://www.python.org/download) 3.10.6 or later.

##### Installing
    pip install ryry-cli

##### Uninstalling
    pip uninstall ryry-cli

Use
------------
##### 1. Running
    $ ryry service start
start a process to wait for the server to issue tasks. **Please do not close it**

Module Developer
------------
    $ ryry widget init

in empty folder, use above command craete a ryry module, structure is like 
    
    [widget folder]
        |-- config.json     //*required, do not change*
        |-- main.py         //*required, do not change* 
        |-- run.py

if other person share widget code to you , you can add widget path in your computer to ryry environment

    $ ryry widget add [path_with_widget_code]

you can modify script and h5 file yourself, then publish to ryry sever 
    
    $ ryry widget publish

get ryry status
    $ ryry services status