semvec/pypi-packages huggingface dataset:
kzn 0.0.1
Random but useful python packages for make our lives easier.
Requires Python: >=3.9

# KZN Python helper packages

One place to include all of our reusable Python namespaced packages. Follow the instructions below to learn how to use
and add new packages.

## Add new package

**IMPORTANT:**
Please  follow [PEP-8](https://www.python.org/dev/peps/pep-0008/#package-and-module-names) when creating packages & modules
> Modules should have short, all-lowercase names. Underscores can be used in the module name if it improves readability. 
> Python packages should also have short, all-lowercase names, although the use of underscores is discouraged.
 
### STEP 1 - Create directory
Create a directory for your package within `src/kzn` directory or its sub-directory.

Only add a `__init__.py` to the directory where your modules are going to be. No `__init__.py` must be in any of the 
namespace directories. 

### STEP 2 - Add the code
Add your awesome code/modules to the newly created directory. 

It is highly recommended modularising your code to make it easier for testing. 

#### LOGGING & STDOUTS
If you want to print something to console, it's highly recommended using the built-in custom logging package. One main 
advantage of doing so is we can easily redirect the output to different streams.  

_EXAMPLE_
```python
from kzn.common.logging import logger
logger.info('Logging message')
```

* **DON'T** Import Python's builtin logging library
```python
import logging # don't do this 
```

* **DON'T** get confused with `logging` & `logger

```python
logging.info() # WRONG
logger.info() # CORRECT
```

### STEP 3 - Add tests
* Create a file in the `tests` directory using `test_your_module_name.py` format
* Create a class in `testing_your_module_name.py` using the same name in PascalCase `TestYourModuleName`
* Write your individual test cases using `test_what_am_i_testing` format. It's always good practice limiting the number 
* of assertions to 1 in each test case. 

**Life hack:** If you use PyCharm or any IntelliJ IDE you can easily generate a test file by: Code --> Generate --> test

## Using these packages 

### 1. Required for CDK app / infrastructure (recommended for production) 
If your CDK app requires this library, add it to `install_requires` in `setup.py`
```
git+https://github.com/pypa/sampleproject.git@main
```

### 2. Required in Lambda function (recommended for production) 
If you want to use the library for the Lambda function or any other runtime, add it to the relevant `requirements.txt` file
```
git+https://github.com/pypa/sampleproject.git@main
```

### 3. Use in development 
You can install the package in `editable mode (-e)` for development use. 

Adding a library in `editable mode` is the best approach if you want to make changes to your library while sourcing it 
within another project.
```
pip install -e "git+ssh://git@github.com/KZNGroup/kzn-helpers.git@master#egg=kzn&subdirectory=python"
```
or
```
pip install -e <path>/kzn-helpers/python
```
vnpy-extra-tb 0.2.20210916.0
该项目主要用于在vnpy框架下扩展部分 Trade Blazer (TB) 的函数包，以方便部分TB程序的迁移使用。
Requires Python: >=3.7

# vnpy_extra_tb
该项目主要用于在vnpy框架下扩展部分 Trade Blazer (TB) 的函数包，以方便部分TB程序的迁移使用。

### 1. 版本历史
* 2021-09-16 v0.2.20210916.0
  > refactor: transfer current_bar_daily and relative features to vnpy_extra.utils.enhancement.CtaSignal.

* 2021-07-28 v0.2.20210728.0
  > refactor: transfer strategy_obj param and relative features to vnpy_extra.utils.enhancement.CtaSignal.

* 2021-06-16 v0.2.20210616.0
  > fix: self.bg_daily is not None check.

* 2021-05-10 v0.2.20210511.1
  > fix: self.bg.win_bar is None. \
  > fix: self.current_bar_daily is None. \ 
  > fix: window=1 by default on bg_daily.

* 2021-05-08 v0.2.20210508.0
  > feat: add ohlcv _current properties for on-going bar value.

* 2021-04-16 v0.2.20210416.0
  > feat: add Daily ohlcv properties.\
  > feat: _his -> _array.\
  > feat: 将 Signal, ArrayManager 拆分成两个单独的模块

* 2021-03-25 v0.1.20210325.0
  >feat: new TBCtaSignal logic
cclogs 1.0.4
Colored console logs
Requires Python: >=3.6

# Colored console logs for Python 3(>=3.6)

The project is aimed to give specific handlers and log formatters to users for coloring stream logs in multiple ways.  
Among the main features some utilities are also provided in order to make use easier.

## Outputs

Output of the logger is defaulted to stdout but can be changed just in case as normal logger.

## Formats

All default formatting styles are supported (`%(levelname)s`, `{levelname}` and `${levelname}`).

## Modes

There are four different modes at the moment for coloring:

* Mode 0 - NO_COLOR  
  No coloring (output formatting) is done, everything remains the same as in normal cases
* Mode 1 - LEVEL  
  Only `levelname` is colored according to the setup
* Mode 2 - MESSAGE  
  Only `message` is colored according to the setup
* Mode 3 - ALL  
  The whole output is colored according to the setup

## Colors

Colors are stored in an enum and represent standard terminal formatting escapes such as ```\x1b[0m```.  
The following colors could be used (and represent the following formatting):

``` 
NO_COLOR = "\x1b[0m"  
BLACK = "\x1b[30m"  
RED = "\x1b[31m"  
GREEN = "\x1b[32m"  
YELLOW = "\x1b[33m"  
BLUE = "\x1b[34m"  
MAGENTA = "\x1b[35m"  
CYAN = "\x1b[36m"  
LIGHT_GRAY = "\x1b[37m"  
DARK_GRAY = "\x1b[90m"  
LIGHT_RED = "\x1b[91m"  
LIGHT_GREEN = "\x1b[92m"  
LIGHT_YELLOW = "\x1b[93m"  
LIGHT_BLUE = "\x1b[94m"  
LIGHT_MAGENTA = "\x1b[95m"  
LIGHT_CYAN = "\x1b[96m"  
WHITE = "\x1b[97m"  
```

## Levels

The level can be set through the Handler and Formatter objects as well.  
The defaults are the following:

```
logging.NOTSET: TerminalColors.NO_COLOR,
logging.DEBUG: TerminalColors.BLUE,
logging.INFO: TerminalColors.GREEN,
logging.WARNING: TerminalColors.YELLOW,
logging.ERROR: TerminalColors.RED,
logging.CRITICAL: TerminalColors.MAGENTA
```

## Install

```
pip3 install cclogs
```

## Basic usage

See examples attached
swot-simulator 1.2.1
Simulate SWOT measurements on sea surface height with simulated errors
Requires Python: >=3.6

################################
SWOT Simulator for Ocean Science
################################

|Latest Documentation Status| |Conda| |Downloads statistics| |Platforms|
|Latest Release Date| |License| |Binder|

This software simulates SWOT observations of the sea surface height (SSH) that
can be applied to an ocean general circulation model (OGCM), allowing the
exploration of ideas and methods to optimize information retrieval from the SWOT
Mission in the future. From OGCM SSH inputs, the software generates SWOT-like
outputs on a swath along the orbit ground track and adds measurement errors and
noise, which are generated according to technical characteristics published by
the SWOT project team. Not designed to directly simulate the payload instrument
performance, this SWOT simulator aims at providing statistically realistic
outputs for the science community with a simple software package released as an
open source in Python. The software is scalable and designed to support future
evolution of orbital parameters, error budget estimates from the project team
and suggestions from the science community.

Tutorial and reference documentation is provided at
`swot-simulator.readthedocs.io <https://swot-simulator.readthedocs.io>`_.

About
-----

This project was created by Clement Ubelmann, Lucile Gaultier and Lee-Lueng Fu.

Jet Propulsion Laboratory, California Institute of Technology, CNES

License
-------

``swot_simulator`` is provided under a BSD-style license that can be found in
the `LICENSE <https://github.com/CNES/swot_simulator/blob/master/LICENSE>`_
file. By using, distributing, or contributing to this project, you agree to the
terms and conditions of this license.

.. |Latest Documentation Status| image:: https://dev.azure.com/fbriol/swot_simulator/_apis/build/status/CNES.swot_simulator?branchName=master
    :target: https://dev.azure.com/fbriol/swot_simulator/_build/latest?definitionId=2&branchName=master
.. |Conda| image:: https://anaconda.org/conda-forge/swot_simulator/badges/installer/conda.svg?service=github
    :target: https://www.anaconda.com/distribution/
.. |Downloads statistics| image:: https://anaconda.org/conda-forge/swot_simulator/badges/downloads.svg?service=github
    :target: https://www.anaconda.com/distribution/
.. |Platforms| image:: https://anaconda.org/conda-forge/swot_simulator/badges/platforms.svg?service=github
    :target: https://anaconda.org/conda-forge/swot_simulator
.. |Latest Release Date| image:: https://anaconda.org/conda-forge/swot_simulator/badges/latest_release_date.svg?service=github
    :target: https://github.com/CNES/swot_simulator/commits/master
.. |License| image:: https://anaconda.org/conda-forge/swot_simulator/badges/license.svg?service=github
    :target: https://opensource.org/licenses/BSD-3-Clause
.. |Binder| image:: https://binder.pangeo.io/badge_logo.svg
    :target: https://binder.pangeo.io/v2/gh/CNES/swot_simulator/master?filepath=notebooks
skyworker-processor-name 0.1.1
Skyworker AI Processor
Requires Python: >=3.6

# Skyworker Processor: {processor_name}

Template repository for the Skyworker AI Processor

## Requirements

- `Python >= 3.6`
- `pip`
- `venv (recommended)`

## Usage

- Clone this repository
- Update todos in [setup.py](setup.py) file
- Update todos in [skyworker_processor/\_\_init\_\_.py](skyworker_processor/__init__.py) file
- Define your logic in [skyworker_processor/core/processor.py](skyworker_processor/core/processor.py) module's `process` function

The return value of `skyworker_processor.process()` function should be the `pandas.DataFrame` object with following columns:

- `measurement` - Measurement Name
- `value` - Calculated Value

and the index of each row should be the unique timestamp.

### Example

```python
import pandas as pd
from datetime import datetime

time_series = [
    {
        "timestamp": 1628150400,
        "measurement": "Electricity Price",
        "value": 0.23,
    },
    {
        "timestamp": 1628236800,
        "measurement": "Electricity Price",
        "value": 0.25,
    }
]

data_frame = pd.DataFrame(time_series)
# Set "timestamp" column as index.
data_frame.index = data_frame["timestamp"]
# Compose "time" column from the "timestamp"
data_frame["time"] = data_frame["timestamp"].map(datetime.fromtimestamp)
del data_frame["timestamp"]
```

## Changelog

Please see [CHANGELOG](CHANGELOG.md) for details.

## Authors

- [Temuri Takalandze](https://abgeo.dev) - *Author and Maintainer*

## License

Copyright © 2021 [Omedia](https://omedia.dev).  
Released under the [Other/Proprietary License](LICENSE).
OscarsTimeTest2 0.0.1
An improved time module

Bug Tracker = https://github.com/Oscar-Hogben/Timer-Module/issues
Author: Oscar Hogben
Author-email: oscarhogben@gmail.com
License: UNKNOWN
Description: This will change :)
Platform: UNKNOWN
Classifier: Programming Language :: Python :: 3
Classifier: License :: OSI Approved :: MIT License
Classifier: Operating System :: OS Independent
Requires-Python: >=3.6
Description-Content-Type: markdown