semvec/pypi-packages huggingface dataset:
geomac-wildfires 0.1.14
Download wildfires data from NIFC
License: MIT

geomac-wildfires
================

Download wildfires data from GeoMAC

.. image:: https://travis-ci.org/datadesk/geomac-wildfires.svg?branch=master
    :target: https://travis-ci.org/datadesk/geomac-wildfires

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

::

    $ pipenv install geomac-wildfires


Command-line usage
------------------

::

    Usage: geomacwildfires [OPTIONS] COMMAND [ARGS]...

      A command-line interface for downloading wildfire perimeter data from
      GeoMAC. Returns GeoJSON.

    Options:
      --help  Show this message and exit.

    Commands:
      active-perimeters   Perimeters of active fires in a recent 24-hour period
      all-perimeters      Perimeters of all fires
      nifc-incidents      Fire incident points from NIFC situation reports


Download data from GeoMAC. ::

    $ geomacwildfires active-perimeters
    $ geomacwildfires all-perimeters
    $ geomacwildfires get-nifc-incidents


Python usage
------------

Import the library. ::

    >>> import geomac_wildfires
    >>> data = geomac_wildfires.get_active_perimeters()
    >>> data = geomac_wildfires.get_all_perimeters()
    >>> data = geomac_wildfires.get_nifc_incidents()


Contributing
------------

Install dependencies for development. ::

    $ pipenv install --dev

Run tests.::

    $ make test

Shipping new version to PyPI. ::

    $ make ship


Developing the CLI
------------------

The command-line interface is implemented using Click and setuptools. To install it locally for development inside your virtual environment, run the following installation command, as `prescribed by the Click documentation <https://click.palletsprojects.com/en/7.x/setuptools/#setuptools-integration>`_. ::

    $ pip install --editable .
FINANCEPP 1.3.3
Algorithm for finance
License: MIT

Documentation of the "CovidResilience" package

The purpose of the package is, given a list of stock tickers, to state what are the most covid resilient stocks and what are the worst ones.
It computes a very simple score based on the volatility and return of the stocks over different periods of time.


CovidResilience(stock_index = "STOXX 600", start_date = "2020-01-19", end_date = "2021-01-19", tickers = None)


Input: 

- stock_index : benchmark  (example : "CAC 40","S&P 500", "STOXX 600")
- start_date, end_date : strings, format "YYYY-MM-DD"
- tickers : list of tickers


Output:

- .relevant_data
- .relevant_data_returns
- .volatilities
- .rslt


Example (copy/paste):

!pip install FINANCEPP

from finance import covidresilient as cr

list_of_tickers = ["FP.PA","MC.PA","AI.PA","OR.PA", "RI.PA","AIR.PA"]

covidfilter = cr.CovidResilience("CAC 40","2020-01-19", "2021-01-19", tickers = list_of_tickers)

covidfilter.run()

covidfilter.rslt

Note that some of the tickers may not be the ones that are used by yahoo finance. Make sure you use the proper tickers.
jinjarecurse 0.0.3
Jinja Recursive Templating from the CLI
License: MIT
Keywords: jinja templater

# jinjarecurse CLI tool
_________________
![PyPI](https://img.shields.io/pypi/v/jinjarecurse?color=blue)
![GitHub Workflow Status](https://img.shields.io/github/workflow/status/diginc/jinja-recurse/Upload%20Python%20Package)
![GitHub](https://img.shields.io/github/license/diginc/jinja-recurse)
![PyPI - Downloads](https://img.shields.io/pypi/dm/jinjarecurse)
_________________

Jinja Recursive Templating for the CLI.  Recursively template one file or many
folders of many files like a config management languages allow, without the
whole config management language.  Useful if you're switching from managing an
application from config management to just docker and need some simple
templating logic.

## Installation

```
pip install jinjarecurse
```

## Example Usage

```
$ jinjarecurse --help
 jinjarecurse (CLI)

Usage:
    jinjarecurse --vars=VARS_FILE --input=INPUT_PATH --output=OUTPUT_PATH

Options:
    -v <file>, --vars   <file>
    -i <file>, --input  <file>
    -o <file>, --output <file>
```

### Single file

Given a config file containing your variables e.g. `vars.yaml`:

```
#comment: not available
root: /
number: 1
dictionary:
    street: 123 North Ave
    city: New York
    state: New York
list:
    - ABC
    - DEF
    - HJK
layer_1:
    layer_2:
        layer_3: last
```

And an input file jinja2 template e.g. `i_file`:

```
# Top level
{{root}}
{{number}}
{{dictionary}}
{{list}}
{{layer_1}}

# Nested data

{{dictionary.street}}
{{dictionary.city}}
{{dictionary.state}}
{{layer_1.layer_2.layer_3}}
```

You can populate it and specify an output filepath e.g. `o_file`:

```
$ jinjarecurse -v example/vars.yaml -i example/i_file -o example/o_file
WARNING: example/o_file (output) exists and any conflicting files will be overwritten
Writing from example/i_file to example/o_file
```

Contents of the output file e.g. `o_file`:

```
# Top level
/
1
{'street': '123 North Ave', 'city': 'New York', 'state': 'New York'}
['ABC', 'DEF', 'HJK']
{'layer_2': {'layer_3': 'last'}}

# Nested data

123 North Ave
New York
New York
last
```

### Directory

You can also template an entire directory e.g. `i_dir` at once. Note the
output files in the output directory will maintain the filenames from the
input directory:

```
$ jinjarecurse -v example/vars.yaml -i example/i_dir -o example/o_dir
Writing from example/i_dir/i_file to example/o_dir/i_file
Writing from example/i_dir/i_file_1 to example/o_dir/i_file_1
Writing from example/i_dir/i_file_2 to example/o_dir/i_file_2
```

## Tests

To run the unit tests, first install the dependencies:

```
$ pipenv install --dev .
```

Then invoke pytest:

```
$ pipenv run py.test -vvvs
```

## Changelog

Please see the [Releases](https://github.com/diginc/Jinja-Recurse/releases)
and [CHANGELOG.md](https://github.com/diginc/Jinja-Recurse/blob/master/CHANGELOG.md).