semvec/pypi-packages huggingface dataset:
eda-ts 1.1.0
An exploratory data analysys (EDA) tool for time series data
License: MIT
Requires Python: <4.0.0,>=3.11
Keywords: eda, time series, exploratory data analysis

# 📘 Urecsys EDA Tool

Welcome to the Urecsys Exploratory Data Analysis (EDA) tools. This toolkit provides various features for analyzing and visualizing your datasets.

## Overview

EDA is a crucial step in the data analysis process that helps you:
- Summarize main characteristics of datasets
- Detect anomalies
- Uncover patterns
- Visualize data relationships
## Getting Started

1. Set up a virtual environment:
```bash
python -m venv .venv
source .venv/bin/activate  
```
> **Tip**: You can also create a virtual environment in VS Code by pressing `Ctrl+Shift+P` (`⌘ + Shift + P` on macOS), typing `Python: Create Environment`, and following the prompts.


2. Install dependencies using Poetry:
```bash
poetry install
```

3. Launch the EDA tool:
```bash
streamlit run 0_📘_EDA.py
```
> **Tip**: You can type `streamlit run 0` and press Tab for auto-completion

4. Once launched, navigate to 🏠Overview in the sidebar

5. Upload your pickle file to begin analysis


## Development

### Adding New EDA Features

New EDA tools should be added under the `eda/pages` directory following this naming convention:

```
<number>_<emoji>_<title>.py
```

Example: `1_📊_overview.py`

This naming pattern ensures proper ordering and visual organization in the Streamlit sidebar.

To create a new EDA page, you can start by copying the `101_📝_Template.py` file. This template provides a basic structure for your new page.

Replace `<number>`, `<emoji>`, and `<title>` with appropriate values for your new page. This will help maintain consistency and organization within the project.
terrajinja-cli 0.8.0
Terrajinja extension for automation using cdktf
License: MIT

# Terrajinja CLI

Is a intermediate command line interface that accepts YAML/Jinja2 template files as input in order to generate a terraform deployment

#### CLI command structure

Each command is represented as a command or subcommand, and there are a number of command and subcommand options available:

```
$ tjcli <command> {deploy,template,init} [args]
```
* init - creates the config directory structure
* template - list or add templates to your config
* deploy - create a deployment for your config

for additional help ad the --help parameter to the sub command
e.g.:
```
$ tjcli template --help
```

## Getting started
start by installing the cli using pip
```
$ pip install terrajinja-cli
```

next step is to choose a place to store your config, in general this is a git repository.
you can then create the initial directory stucture in that directory
```
$ tjcli init
creating directory project/deployments
creating directory project/templates
creating directory project/parameters
```

to get some inspiration look at the available templates that have already been created for your inspiration.
```
$ tjcli template --list
available templates:
  gitlab-runner: for creating a gitlab runner on kubernetes
```

you can add any of these templates to your project
```
$ tjcli template --add gitlab-runner
requesting to add template {args.template}...
dest: project/templates/generic_gitlab_runner_v0.0.1.yaml
adding: templates / generic_gitlab_runner_v0.0.1.yaml
dest: project/parameters/gitlab_runner.yaml
adding: parameters / gitlab_runner.yaml
```

## Configuring a deployment
Terra jinja expects the following paths to contain YAML or Jinja2 template files:

| directory | files | description |
| ------ | ------ | ------ |
| parameters | YAML only | main input to be used by all deployments |
| deployments | YAML/Jinja2 | this defines the accepted parameters and what templates to execute |
| templates | YAML/Jinja2 | the templates define the terraform modules to execute |

Please refer to the documentation for the full file specifications

## Deploying your deployment
Which deployment is available depends on the files you created in the deployments directory
e.g.:
```
$ tjcli deploy -d my_deployment -a mailrelay -e test
```
Note that the parameters are dynamicly based on the deployment file, so the actual parameters availabe will vary on your config.

Once terrajinja created your deployment you can run cdktf to apply or destroy your deployment. e.g.:
```
cdktf apply
```



History
-------

0.0.1 (14-03-2024)
---------------------

* First code creation