| Name | anomalytics JSON |
| Version |
0.2.2
JSON |
| download |
| home_page | |
| Summary | The ultimate anomaly detection library. |
| upload_time | 2023-12-21 10:34:33 |
| maintainer | |
| docs_url | None |
| author | |
| requires_python | >=3.10 |
| license | MIT License Copyright (c) 2023 Nino Lindenberg Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. |
| keywords |
anomaly
anomaly detection
statistics
mathematics
software engineering
data science
data analyst
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
<h1 align=center><strong>Anomalytics</strong></h1>
<h3 align=center><i>Your Ultimate Anomaly Detection & Analytics Tool</i></h3>
<p align="center">
<a href="https://app.codecov.io/gh/Aeternalis-Ingenium/anomalytics/tree/trunk" >
<img src="https://codecov.io/gh/Aeternalis-Ingenium/anomalytics/graph/badge.svg?token=eC84pMmUz8"/>
</a>
<a href="https://results.pre-commit.ci/latest/github/Aeternalis-Ingenium/anomalytics/trunk">
<img src="https://results.pre-commit.ci/badge/github/Aeternalis-Ingenium/anomalytics/trunk.svg" alt="pre-commit.ci status">
</a>
<a href="https://github.com/psf/black">
<img src="https://img.shields.io/badge/code%20style-black-000000.svg" alt="Code style: black">
</a>
<a href="https://pycqa.github.io/isort/">
<img src="https://img.shields.io/badge/%20imports-isort-%231674b1?style=flat&labelColor=ef8336" alt="Imports: isort">
</a>
<a href="#">
<img src="https://img.shields.io/badge/mypy-checked-blue" alt="mypy checked">
</a>
<a href="https://github.com/Aeternalis-Ingenium/anomalytics/actions/workflows/build.yaml">
<img src="https://github.com/Aeternalis-Ingenium/anomalytics/actions/workflows/build.yaml/badge.svg" alt="CI - Build">
</a>
<a href="https://github.com/Aeternalis-Ingenium/anomalytics/actions/workflows/code-quality.yaml">
<img src="https://github.com/Aeternalis-Ingenium/anomalytics/actions/workflows/code-quality.yaml/badge.svg" alt="CI - Code Quality">
</a>
<a href="https://github.com/Aeternalis-Ingenium/anomalytics/actions/workflows/test.yaml">
<img src="https://github.com/Aeternalis-Ingenium/anomalytics/actions/workflows/test.yaml/badge.svg" alt="CI - Automated Testing">
</a>
<a href="https://github.com/Aeternalis-Ingenium/anomalytics/blob/trunk/LICENSE">
<img src="https://img.shields.io/badge/License-MIT-yellow.svg" alt="License: MIT">
</a>
<a href="https://github.com/Aeternalis-Ingenium/anomalytics/blob/trunk/README.md">
<img src="https://img.shields.io/badge/docs-passing-brightgreen.svg" alt="Documentation">
</a>
<a href="https://pypi.org/project/anomalytics/">
<img src="https://img.shields.io/badge/PyPi-v0.2.1-blue.svg" alt="PyPi">
</a>
</p>
## Introduction
`anomalytics` is a Python library that aims to implement all statistical methods for the purpose of detecting any sort of anomaly e.g. extreme events, high or low anomalies, etc. This library utilises external dependencies such as:
- [Pandas 2.1.1](https://pandas.pydata.org/)
- [NumPy 1.26.0](https://numpy.org/)
- [SciPy 1.11.3](https://scipy.org/)
- [Matplotlib 3.8.2](https://matplotlib.org/)
- [Pytest-Cov 4.1.0.](https://pytest-cov.readthedocs.io/en/latest/)
- [Black 23.10.0](https://black.readthedocs.io/en/stable/)
- [Isort 5.12.0](https://pycqa.github.io/isort/)
- [MyPy 1.6.1](https://mypy.readthedocs.io/en/stable/)
- [Bandit 1.7.5](https://bandit.readthedocs.io/en/latest/)
`anomalytics` supports the following Python's versions: `3.10.x`, `3.11.x`, `3.12.0`.
## Installation
To use the library, you can install as follow:
```shell
# Install without openpyxl
$ pip3 install anomalytics
# Install with openpyxl
$ pip3 install "anomalytics[extra]"
```
As a contributor/collaborator, you may want to consider installing all external dependencies for development purposes:
```shell
# Install bandit, black, isort, mypy, openpyxl, pre-commit, and pytest-cov
$ pip3 install "anomalytics[codequality,docs,security,testcov,extra]"
```
## Use Case
`anomalytics` can be used to analyze anomalies in your dataset (both as `pandas.DataFrame` or `pandas.Series`). To start, let's follow along with this minimum example where we want to detect extremely high anomalies in our dataset.
Read the walkthrough below, or the concrete examples here:
* [Extreme Anomaly Analysis - DataFrame](https://github.com/Aeternalis-Ingenium/anomalytics/blob/trunk/docs/examples/extreme_anomaly_df_analysis.ipynb)
* [Battery Water Level Analysis - Time Series](https://github.com/Aeternalis-Ingenium/anomalytics/blob/trunk/docs/examples/battery_water_level_analysis.ipynb)
### Anomaly Detection via the `Detector` Instance
1. Import `anomalytics` and initialise our time series of 100_002 rows:
```python
import anomalytics as atics
df = atics.read_ts("./ad_impressions.csv", "csv")
df.head()
```
```shell
datetime xandr gam adobe
0 2023-10-18 09:01:00 52.483571 71.021131 35.681915
1 2023-10-18 09:02:00 49.308678 73.651996 60.347246
2 2023-10-18 09:03:00 53.238443 65.690813 48.120805
3 2023-10-18 09:04:00 57.615149 80.944393 59.550775
4 2023-10-18 09:05:00 48.829233 76.445099 26.710413
```
2. Initialize the needed detector object. Each detector utilises a different statistical method for detecting anomalies. In this example, we'll use POT method and a high anomaly type. Pay attention to the time period that is directly created where the `t2` is 1 by default because "real-time" always targets the "now" period hence 1 (sec, min, hour, day, week, month, etc.):
```python
pot_detector = atics.get_detector(method="POT", dataset=ts, anomaly_type="high")
print(f"T0: {pot_detector.t0}")
print(f"T1: {pot_detector.t1}")
print(f"T2: {pot_detector.t2}")
pot_detector.plot(ptype="line-dataset-df", title=f"Page Impressions Dataset", xlabel="Minute", ylabel="Impressions", alpha=1.0)
```
```shell
T0: 42705
T1: 16425
T2: 6570
```
3. The purpose of using the detector object instead the standalone is to have a simple fix detection flow. In case you want to customize the time window, we can call the `reset_time_window()` to reset `t2` value, even though that will beat the purpose of using a detector object. Pay attention to the period parameters because the method expects a percentage representation of the distribution of period (ranging 0.0 to 1.0):
```python
pot_detector.reset_time_window(
"historical",
t0_pct=0.65,
t1_pct=0.25,
t2_pct=0.1
)
print(f"T0: {pot_detector.t0}")
print(f"T1: {pot_detector.t1}")
print(f"T2: {pot_detector.t2}")
pot_detector.plot(ptype="hist-dataset-df", title="Dataset Distributions", xlabel="Distributions", ylabel="Page Impressions", alpha=1.0, bins=100)
```
```shell
T0: 65001
T1: 25001
T2: 10000
```
4. Now, we can extract exceedances by giving the expected `q`uantile:
```python
pot_detector.get_extremes(0.95)
pot_detector.exeedance_thresholds.head()
```
```shell
xandr gam adobe datetime
0 58.224653 85.177029 60.362306 2023-10-18 09:01:00
1 58.224653 85.177029 60.362306 2023-10-18 09:02:00
2 58.224653 85.177029 60.362306 2023-10-18 09:03:00
3 58.224653 85.177029 60.362306 2023-10-18 09:04:00
4 58.224653 85.177029 60.362306 2023-10-18 09:05:00
```
5. Let's visualize the exceedances and its threshold to have a clearer understanding of our dataset:
```python
pot_detector.plot(ptype="line-exceedance-df", title="Peaks Over Threshold", xlabel="Minute", ylabel="Page Impressions", alpha=1.0)
```
6. Now that we have the exceedances, we can fit our data into the chosen distribution, in this example the "Generalized Pareto Distribution". The first couple rows will be zeroes which is normal because we only fit data that are greater than zero into the wanted distribution:
```python
pot_detector.fit()
pot_detector.fit_result.head()
```
```shell
xandr_anomaly_score gam_anomaly_score adobe_anomaly_score total_anomaly_score datetime
0 1.087147 0.000000 0.000000 1.087147 2023-11-17 00:46:00
1 0.000000 0.000000 0.000000 0.000000 2023-11-17 00:47:00
2 0.000000 0.000000 0.000000 0.000000 2023-11-17 00:48:00
3 0.000000 1.815875 0.000000 1.815875 2023-11-17 00:49:00
4 0.000000 0.000000 0.000000 0.000000 2023-11-17 00:50:00
...
```
7. Let's inspect the GPD distributions to get the intuition of our pareto distribution:
```python
pot_detector.plot(ptype="hist-gpd-df", title="GPD - PDF", xlabel="Page Impressions", ylabel="Density", alpha=1.0, bins=100)
```
8. The parameters are stored inside the detector class:
```python
pot_detector.params
```
```shell
{0: {'xandr': {'c': -0.11675297447288158,
'loc': 0,
'scale': 2.3129766056305603,
'p_value': 0.9198385927065513,
'anomaly_score': 1.0871472537998},
'gam': {'c': 0.0,
'loc': 0.0,
'scale': 0.0,
'p_value': 0.0,
'anomaly_score': 0.0},
'adobe': {'c': 0.0,
'loc': 0.0,
'scale': 0.0,
'p_value': 0.0,
'anomaly_score': 0.0},
'total_anomaly_score': 1.0871472537998},
1: {'xandr': {'c': 0.0,
'loc': 0.0,
'scale': 0.0,
'p_value': 0.0,
'anomaly_score': 0.0},
'gam': {'c': 0.0,
'loc': 0.0,
'scale': 0.0,
'p_value': 0.0,
...
'scale': 0.0,
'p_value': 0.0,
'anomaly_score': 0.0},
'total_anomaly_score': 0.0},
...}
```
9. Last but not least, we can now detect the extremely large (high) anomalies:
```python
pot_detector.detect(0.95)
pot_detector.detection_result
```
```shell
16425 False
16426 False
16427 False
16428 False
16429 False
...
22990 False
22991 False
22992 False
22993 False
22994 False
Name: detected data, Length: 6570, dtype: bool
```
10. Now we can visualize the anomaly scores from the fitting with the anomaly threshold to get the sense of the extremely large values:
```python
pot_detector.plot(ptype="line-anomaly-score-df", title="Anomaly Score", xlabel="Minute", ylabel="Page Impressions", alpha=1.0)
```
11. Now what? Well, while the detection process seems quite straight forward, in most cases getting the details of each anomalous data is quite tidious! That's why `anomalytics` provides a comfortable method to get the summary of the detection so we can see when, in which row, and how the actual anomalous data look like:
```python
pot_detector.detection_summary.head(5)
```
```shell
row xandr gam adobe xandr_anomaly_score gam_anomaly_score adobe_anomaly_score total_anomaly_score anomaly_threshold
2023-11-28 12:06:00 59225 64.117135 76.425925 47.772929 21.445759 0.000000 0.000000 21.445759 19.689885
2023-11-28 12:25:00 59244 40.513415 94.526021 65.921644 0.000000 19.557962 2.685337 22.243299 19.689885
2023-11-28 12:45:00 59264 52.362039 54.191719 79.972860 0.000000 0.000000 72.313273 72.313273 19.689885
2023-11-28 16:48:00 59507 64.753203 70.344142 42.540168 32.543021 0.000000 0.000000 32.543021 19.689885
2023-11-28 16:53:00 59512 35.912221 52.572939 75.621003 0.000000 0.000000 22.199505 22.199505 19.689885
```
12. In every good analysis there is a test! We can evaluate our analysis result with "Kolmogorov Smirnov" 1 sample test to see how far the statistical distance between the observed sample distributions to the theoretical distributions via the fitting parameters (the smaller the `stats_distance` the better!):
```python
pot_detector.evaluate(method="ks")
pot_detector.evaluation_result
```
```shell
column total_nonzero_exceedances stats_distance p_value c loc scale
0 xandr 3311 0.012901 0.635246 -0.128561 0 2.329005
1 gam 3279 0.011006 0.817674 -0.140479 0 3.852574
2 adobe 3298 0.019479 0.161510 -0.133019 0 6.007833
```
13. If 1 test is not enough for evaluation, we can also visually test our analysis result with "Quantile-Quantile Plot" method to observed the sample quantile vs. the theoretical quantile:
```python
# Use the last non-zero parameters
pot_detector.evaluate(method="qq")
# Use a random non-zero parameters
pot_detector.evaluate(method="qq", is_random=True)
```
### Anomaly Detection via Standalone Functions
You have a project that only needs to be fitted? To be detected? Don't worry! `anomalytics` also provides standalone functions as well in case users want to start the anomaly analysis from a different starting points. It is more flexible, but many processing needs to be done by you. LEt's take an example with a different dataset, thistime the water level Time Series!
1. Import `anomalytics` and initialise your time series:
```python
import anomalytics as atics
ts = atics.read_ts(
"water_level.csv",
"csv"
)
ts.head()
```
```shell
2008-11-03 06:00:00 0.219
2008-11-03 07:00:00 -0.041
2008-11-03 08:00:00 -0.282
2008-11-03 09:00:00 -0.368
2008-11-03 10:00:00 -0.400
Name: Water Level, dtype: float64
```
2. Set the time windows of t0, t1, and t2 to compute dynamic expanding period for calculating the threshold via quantile:
```python
t0, t1, t2 = atics.set_time_window(
total_rows=ts.shape[0],
method="POT",
analysis_type="historical",
t0_pct=0.65,
t1_pct=0.25,
t2_pct=0.1
)
print(f"T0: {t0}")
print(f"T1: {t1}")
print(f"T2: {t2}")
```
```shell
T0: 65001
T1: 25001
T2: 10000
```
3. Extract exceedances and indicate that it is a `"high"` anomaly type and what's the `q`uantile:
```python
pot_thresholds = get_threshold_peaks_over_threshold(dataset=ts, t0=t0, "high", q=0.90)
pot_exceedances = atics.get_exceedance_peaks_over_threshold(
dataset=ts,
threshold_dataset=pot_thresholds,
anomaly_type="high"
)
exceedances.head()
```
```shell
2008-11-03 06:00:00 0.859
2008-11-03 07:00:00 0.859
2008-11-03 08:00:00 0.859
2008-11-03 09:00:00 0.859
2008-11-03 10:00:00 0.859
Name: Water Level, dtype: float64
```
4. Compute the anomaly scores for each exceedance and initialize a params for further analysis and evaluation:
```python
params = {}
anomaly_scores = atics.get_anomaly_score(
exceedance_dataset=pot_exceedances,
t0=t0,
gpd_params=params
)
anomaly_scores.head()
```
```shell
2016-04-03 15:00:00 0.0
2016-04-03 16:00:00 0.0
2016-04-03 17:00:00 0.0
2016-04-03 18:00:00 0.0
2016-04-03 19:00:00 0.0
Name: anomaly scores, dtype: float64
...
```
5. Inspect the parameters:
```python
params
```
```shell
{0: {'index': Timestamp('2016-04-03 15:00:00'),
'c': 0.0,
'loc': 0.0,
'scale': 0.0,
'p_value': 0.0,
'anomaly_score': 0.0},
1: {'index': Timestamp('2016-04-03 16:00:00'),
...
'c': 0.0,
'loc': 0.0,
'scale': 0.0,
'p_value': 0.0,
'anomaly_score': 0.0},
...}
```
6. Detect anomalies:
```python
anomaly_threshold = get_anomaly_threshold(
anomaly_score_dataset=anomaly_scores,
t1=t1,
q=0.90
)
detection_result = get_anomaly(
anomaly_score_dataset=anomaly_scores,
threshold=anomaly_threshold,
t1=t1
)
detection_result.head()
```
```shell
2020-03-31 19:00:00 False
2020-03-31 20:00:00 False
2020-03-31 21:00:00 False
2020-03-31 22:00:00 False
2020-03-31 23:00:00 False
Name: anomalies, dtype: bool
```
7. For the test, kolmogorov-smirnov and qq plot are also accessible via standalone functions, but the params need to be processed so it only contains a non-zero parameters since there are no reasons to calculate a zero 😂
```python
nonzero_params = []
for row in range(0, t1 + t2):
if (
params[row]["c"] != 0
or params[row]["loc"] != 0
or params[row]["scale"] != 0
):
nonzero_params.append(params[row])
ks_result = atics.evals.ks_1sample(
dataset=pot_exceedances,
stats_method="POT",
fit_params=nonzero_params
)
ks_result
```
```shell
{'total_nonzero_exceedances': [5028], 'stats_distance': [0.0284] 'p_value': [0.8987], 'c': [0.003566], 'loc': [0], 'scale': [0.140657]}
```
8. Visualize via qq plot:
```python
nonzero_exceedances = exceedances[exceedances.values > 0]
visualize_qq_plot(
dataset=nonzero_exceedances,
stats_method="POT",
fit_params=nonzero_params,
)
```
### Sending Anomaly Notification
We have anomaly you said? Don't worry, `anomalytics` has the implementation to send an alert via E-Mail or Slack. Just ensure that you have your email password or Slack webhook ready. This example shows both application (please read the comments 😎):
1. Initialize the wanted platform:
```python
# Gmail
gmail = atics.get_notification(
platform="email",
sender_address="my-cool-email@gmail.com",
password="AIUEA13",
recipient_addresses=["my-recipient-1@gmail.com", "my-recipient-2@web.de"],
smtp_host="smtp.gmail.com",
smtp_port=876,
)
# Slack
slack = atics.get_notification(
platform="slack",
webhook_url="https://slack.com/my-slack/YOUR/SLACK/WEBHOOK",
)
print(gmail)
print(slack)
```
```shell
'Email Notification'
'Slack Notification'
```
2. Prepare the data for the notification! If you use standalone, you need to process the `detection_result` to become a DataFrame with `row`, ``
```python
# Standalone
detected_anomalies = detection_result[detection_result.values == True]
anomalous_data = ts[detected_anomalies.index]
standalone_detection_summary = pd.DataFrame(
index=anomalous.index.flatten(),
data=dict(
row=[ts.index.get_loc(index) + 1 for index in anomalous.index],
anomalous_data=[data for data in anomalous.values],
anomaly_score=[score for score in anomaly_score[anomalous.index].values],
anomaly_threshold=[anomaly_threshold] * anomalous.shape[0],
)
)
# Detector Instance
detector_detection_summary = pot_detector.detection_summary
```
1. Prepare the notification payload and a custome message if needed:
```python
# Email
gmail.setup(
detection_summary=detection_summary,
message="Extremely large anomaly detected! From Ad Impressions Dataset!"
)
# Slack
slack.setup(
detection_summary=detection_summary,
message="Extremely large anomaly detected! From Ad Impressions Dataset!"
)
```
2. Send your notification! Beware that the scheduling is not implemented since it always depends on the logic of the use case:
```python
# Email
gmail.send
# Slack
slack.send
```
```shell
'Notification sent successfully.'
```
3. Check your email or slack, this example produces the following notification via Slack:
# Reference
* Nakamura, C. (2021, July 13). On Choice of Hyper-parameter in Extreme Value Theory Based on Machine Learning Techniques. arXiv:2107.06074 [cs.LG]. https://doi.org/10.48550/arXiv.2107.06074
* Davis, N., Raina, G., & Jagannathan, K. (2019). LSTM-Based Anomaly Detection: Detection Rules from Extreme Value Theory. In Proceedings of the EPIA Conference on Artificial Intelligence 2019. https://doi.org/10.48550/arXiv.1909.06041
* Arian, H., Poorvasei, H., Sharifi, A., & Zamani, S. (2020, November 13). The Uncertain Shape of Grey Swans: Extreme Value Theory with Uncertain Threshold. arXiv:2011.06693v1 [econ.GN]. https://doi.org/10.48550/arXiv.2011.06693
* Yiannis Kalliantzis. (n.d.). Detect Outliers: Expert Outlier Detection and Insights. Retrieved [23-12-04T15:10:12.000Z], from https://detectoutliers.com/
# Wall of Fame
I am deeply grateful to have met and guided by wonderful people who inspired me to finish my capstone project for my study at CODE university of applied sciences in Berlin (2023). Thank you so much for being you!
* Sabrina Lindenberg
* Adam Roe
* Alessandro Dolci
* Christian Leschinski
* Johanna Kokocinski
* Peter Krauß
Raw data
{
"_id": null,
"home_page": "",
"name": "anomalytics",
"maintainer": "",
"docs_url": null,
"requires_python": ">=3.10",
"maintainer_email": "",
"keywords": "anomaly,anomaly detection,statistics,mathematics,software engineering,data science,data analyst",
"author": "",
"author_email": "Nino Lindenberg <aeternalisingenium@proton.me>",
"download_url": "https://files.pythonhosted.org/packages/2e/c0/b0edadd7439a228e8095aa519b64ecb37d92fdf3dc52e56155efcd65576f/anomalytics-0.2.2.tar.gz",
"platform": null,
"description": "<h1 align=center><strong>Anomalytics</strong></h1>\n\n<h3 align=center><i>Your Ultimate Anomaly Detection & Analytics Tool</i></h3>\n\n<p align=\"center\">\n <a href=\"https://app.codecov.io/gh/Aeternalis-Ingenium/anomalytics/tree/trunk\" >\n <img src=\"https://codecov.io/gh/Aeternalis-Ingenium/anomalytics/graph/badge.svg?token=eC84pMmUz8\"/>\n </a>\n <a href=\"https://results.pre-commit.ci/latest/github/Aeternalis-Ingenium/anomalytics/trunk\">\n <img src=\"https://results.pre-commit.ci/badge/github/Aeternalis-Ingenium/anomalytics/trunk.svg\" alt=\"pre-commit.ci status\">\n </a>\n <a href=\"https://github.com/psf/black\">\n <img src=\"https://img.shields.io/badge/code%20style-black-000000.svg\" alt=\"Code style: black\">\n </a>\n <a href=\"https://pycqa.github.io/isort/\">\n <img src=\"https://img.shields.io/badge/%20imports-isort-%231674b1?style=flat&labelColor=ef8336\" alt=\"Imports: isort\">\n </a>\n <a href=\"#\">\n <img src=\"https://img.shields.io/badge/mypy-checked-blue\" alt=\"mypy checked\">\n </a>\n <a href=\"https://github.com/Aeternalis-Ingenium/anomalytics/actions/workflows/build.yaml\">\n <img src=\"https://github.com/Aeternalis-Ingenium/anomalytics/actions/workflows/build.yaml/badge.svg\" alt=\"CI - Build\">\n </a>\n <a href=\"https://github.com/Aeternalis-Ingenium/anomalytics/actions/workflows/code-quality.yaml\">\n <img src=\"https://github.com/Aeternalis-Ingenium/anomalytics/actions/workflows/code-quality.yaml/badge.svg\" alt=\"CI - Code Quality\">\n </a>\n <a href=\"https://github.com/Aeternalis-Ingenium/anomalytics/actions/workflows/test.yaml\">\n <img src=\"https://github.com/Aeternalis-Ingenium/anomalytics/actions/workflows/test.yaml/badge.svg\" alt=\"CI - Automated Testing\">\n </a>\n <a href=\"https://github.com/Aeternalis-Ingenium/anomalytics/blob/trunk/LICENSE\">\n <img src=\"https://img.shields.io/badge/License-MIT-yellow.svg\" alt=\"License: MIT\">\n </a>\n <a href=\"https://github.com/Aeternalis-Ingenium/anomalytics/blob/trunk/README.md\">\n <img src=\"https://img.shields.io/badge/docs-passing-brightgreen.svg\" alt=\"Documentation\">\n </a>\n <a href=\"https://pypi.org/project/anomalytics/\">\n <img src=\"https://img.shields.io/badge/PyPi-v0.2.1-blue.svg\" alt=\"PyPi\">\n </a>\n</p>\n\n## Introduction\n\n`anomalytics` is a Python library that aims to implement all statistical methods for the purpose of detecting any sort of anomaly e.g. extreme events, high or low anomalies, etc. This library utilises external dependencies such as:\n\n- [Pandas 2.1.1](https://pandas.pydata.org/)\n- [NumPy 1.26.0](https://numpy.org/)\n- [SciPy 1.11.3](https://scipy.org/)\n- [Matplotlib 3.8.2](https://matplotlib.org/)\n- [Pytest-Cov 4.1.0.](https://pytest-cov.readthedocs.io/en/latest/)\n- [Black 23.10.0](https://black.readthedocs.io/en/stable/)\n- [Isort 5.12.0](https://pycqa.github.io/isort/)\n- [MyPy 1.6.1](https://mypy.readthedocs.io/en/stable/)\n- [Bandit 1.7.5](https://bandit.readthedocs.io/en/latest/)\n\n`anomalytics` supports the following Python's versions: `3.10.x`, `3.11.x`, `3.12.0`.\n\n## Installation\n\nTo use the library, you can install as follow:\n\n```shell\n# Install without openpyxl\n$ pip3 install anomalytics\n\n# Install with openpyxl\n$ pip3 install \"anomalytics[extra]\"\n```\n\nAs a contributor/collaborator, you may want to consider installing all external dependencies for development purposes:\n\n```shell\n# Install bandit, black, isort, mypy, openpyxl, pre-commit, and pytest-cov\n$ pip3 install \"anomalytics[codequality,docs,security,testcov,extra]\"\n```\n\n## Use Case\n\n`anomalytics` can be used to analyze anomalies in your dataset (both as `pandas.DataFrame` or `pandas.Series`). To start, let's follow along with this minimum example where we want to detect extremely high anomalies in our dataset.\n\nRead the walkthrough below, or the concrete examples here:\n* [Extreme Anomaly Analysis - DataFrame](https://github.com/Aeternalis-Ingenium/anomalytics/blob/trunk/docs/examples/extreme_anomaly_df_analysis.ipynb)\n* [Battery Water Level Analysis - Time Series](https://github.com/Aeternalis-Ingenium/anomalytics/blob/trunk/docs/examples/battery_water_level_analysis.ipynb)\n\n### Anomaly Detection via the `Detector` Instance\n\n1. Import `anomalytics` and initialise our time series of 100_002 rows:\n\n ```python\n import anomalytics as atics\n\n df = atics.read_ts(\"./ad_impressions.csv\", \"csv\")\n df.head()\n ```\n ```shell\n\n datetime\t xandr\t gam\t adobe\n 0\t2023-10-18 09:01:00\t52.483571\t71.021131\t35.681915\n 1\t2023-10-18 09:02:00\t49.308678\t73.651996\t60.347246\n 2\t2023-10-18 09:03:00\t53.238443\t65.690813\t48.120805\n 3\t2023-10-18 09:04:00\t57.615149\t80.944393\t59.550775\n 4\t2023-10-18 09:05:00\t48.829233\t76.445099\t26.710413\n ```\n\n2. Initialize the needed detector object. Each detector utilises a different statistical method for detecting anomalies. In this example, we'll use POT method and a high anomaly type. Pay attention to the time period that is directly created where the `t2` is 1 by default because \"real-time\" always targets the \"now\" period hence 1 (sec, min, hour, day, week, month, etc.):\n\n ```python\n pot_detector = atics.get_detector(method=\"POT\", dataset=ts, anomaly_type=\"high\")\n\n print(f\"T0: {pot_detector.t0}\")\n print(f\"T1: {pot_detector.t1}\")\n print(f\"T2: {pot_detector.t2}\")\n\n pot_detector.plot(ptype=\"line-dataset-df\", title=f\"Page Impressions Dataset\", xlabel=\"Minute\", ylabel=\"Impressions\", alpha=1.0)\n ```\n ```shell\n T0: 42705\n T1: 16425\n T2: 6570\n ```\n\n \n\n3. The purpose of using the detector object instead the standalone is to have a simple fix detection flow. In case you want to customize the time window, we can call the `reset_time_window()` to reset `t2` value, even though that will beat the purpose of using a detector object. Pay attention to the period parameters because the method expects a percentage representation of the distribution of period (ranging 0.0 to 1.0):\n\n ```python\n pot_detector.reset_time_window(\n \"historical\",\n t0_pct=0.65,\n t1_pct=0.25,\n t2_pct=0.1\n )\n\n print(f\"T0: {pot_detector.t0}\")\n print(f\"T1: {pot_detector.t1}\")\n print(f\"T2: {pot_detector.t2}\")\n\n pot_detector.plot(ptype=\"hist-dataset-df\", title=\"Dataset Distributions\", xlabel=\"Distributions\", ylabel=\"Page Impressions\", alpha=1.0, bins=100)\n ```\n ```shell\n T0: 65001\n T1: 25001\n T2: 10000\n ```\n\n \n\n4. Now, we can extract exceedances by giving the expected `q`uantile:\n\n ```python\n pot_detector.get_extremes(0.95)\n pot_detector.exeedance_thresholds.head()\n ```\n ```shell\n xandr\t gam\t adobe\t datetime\n 0\t58.224653\t85.177029\t60.362306\t2023-10-18 09:01:00\n 1\t58.224653\t85.177029\t60.362306\t2023-10-18 09:02:00\n 2\t58.224653\t85.177029\t60.362306\t2023-10-18 09:03:00\n 3\t58.224653\t85.177029\t60.362306\t2023-10-18 09:04:00\n 4\t58.224653\t85.177029\t60.362306\t2023-10-18 09:05:00\n ```\n\n5. Let's visualize the exceedances and its threshold to have a clearer understanding of our dataset:\n\n ```python\n pot_detector.plot(ptype=\"line-exceedance-df\", title=\"Peaks Over Threshold\", xlabel=\"Minute\", ylabel=\"Page Impressions\", alpha=1.0)\n ```\n\n \n\n6. Now that we have the exceedances, we can fit our data into the chosen distribution, in this example the \"Generalized Pareto Distribution\". The first couple rows will be zeroes which is normal because we only fit data that are greater than zero into the wanted distribution:\n\n ```python\n pot_detector.fit()\n pot_detector.fit_result.head()\n ```\n ```shell\n xandr_anomaly_score gam_anomaly_score adobe_anomaly_score\ttotal_anomaly_score\t datetime\n 0\t 1.087147\t 0.000000 0.000000\t 1.087147\t2023-11-17 00:46:00\n 1\t 0.000000\t 0.000000 0.000000\t 0.000000\t2023-11-17 00:47:00\n 2\t 0.000000\t 0.000000 0.000000\t 0.000000\t2023-11-17 00:48:00\n 3\t 0.000000\t 1.815875 0.000000\t 1.815875\t2023-11-17 00:49:00\n 4\t 0.000000\t 0.000000 0.000000\t 0.000000\t2023-11-17 00:50:00\n ...\n ```\n\n7. Let's inspect the GPD distributions to get the intuition of our pareto distribution:\n\n ```python\n pot_detector.plot(ptype=\"hist-gpd-df\", title=\"GPD - PDF\", xlabel=\"Page Impressions\", ylabel=\"Density\", alpha=1.0, bins=100)\n ```\n\n \n\n8. The parameters are stored inside the detector class:\n\n ```python\n pot_detector.params\n ```\n ```shell\n {0: {'xandr': {'c': -0.11675297447288158,\n 'loc': 0,\n 'scale': 2.3129766056305603,\n 'p_value': 0.9198385927065513,\n 'anomaly_score': 1.0871472537998},\n 'gam': {'c': 0.0,\n 'loc': 0.0,\n 'scale': 0.0,\n 'p_value': 0.0,\n 'anomaly_score': 0.0},\n 'adobe': {'c': 0.0,\n 'loc': 0.0,\n 'scale': 0.0,\n 'p_value': 0.0,\n 'anomaly_score': 0.0},\n 'total_anomaly_score': 1.0871472537998},\n 1: {'xandr': {'c': 0.0,\n 'loc': 0.0,\n 'scale': 0.0,\n 'p_value': 0.0,\n 'anomaly_score': 0.0},\n 'gam': {'c': 0.0,\n 'loc': 0.0,\n 'scale': 0.0,\n 'p_value': 0.0,\n ...\n 'scale': 0.0,\n 'p_value': 0.0,\n 'anomaly_score': 0.0},\n 'total_anomaly_score': 0.0},\n ...}\n ```\n\n9. Last but not least, we can now detect the extremely large (high) anomalies:\n\n ```python\n pot_detector.detect(0.95)\n pot_detector.detection_result\n ```\n ```shell\n 16425 False\n 16426 False\n 16427 False\n 16428 False\n 16429 False\n ...\n 22990 False\n 22991 False\n 22992 False\n 22993 False\n 22994 False\n Name: detected data, Length: 6570, dtype: bool\n ```\n\n10. Now we can visualize the anomaly scores from the fitting with the anomaly threshold to get the sense of the extremely large values:\n\n ```python\n pot_detector.plot(ptype=\"line-anomaly-score-df\", title=\"Anomaly Score\", xlabel=\"Minute\", ylabel=\"Page Impressions\", alpha=1.0)\n ```\n\n \n\n11. Now what? Well, while the detection process seems quite straight forward, in most cases getting the details of each anomalous data is quite tidious! That's why `anomalytics` provides a comfortable method to get the summary of the detection so we can see when, in which row, and how the actual anomalous data look like:\n\n ```python\n pot_detector.detection_summary.head(5)\n ```\n ```shell\n row\t xandr\t gam\t adobe\txandr_anomaly_score\tgam_anomaly_score\tadobe_anomaly_score\ttotal_anomaly_score\tanomaly_threshold\n 2023-11-28 12:06:00\t 59225\t64.117135\t76.425925\t47.772929\t 21.445759\t 0.000000\t 0.000000\t 21.445759\t 19.689885\n 2023-11-28 12:25:00\t 59244\t40.513415\t94.526021\t65.921644\t 0.000000\t 19.557962\t 2.685337\t 22.243299\t 19.689885\n 2023-11-28 12:45:00\t 59264\t52.362039\t54.191719\t79.972860\t 0.000000\t 0.000000\t 72.313273\t 72.313273\t 19.689885\n 2023-11-28 16:48:00\t 59507\t64.753203\t70.344142\t42.540168\t 32.543021\t 0.000000\t 0.000000\t 32.543021\t 19.689885\n 2023-11-28 16:53:00\t 59512\t35.912221\t52.572939\t75.621003\t 0.000000\t 0.000000\t 22.199505\t 22.199505\t 19.689885\n ```\n\n12. In every good analysis there is a test! We can evaluate our analysis result with \"Kolmogorov Smirnov\" 1 sample test to see how far the statistical distance between the observed sample distributions to the theoretical distributions via the fitting parameters (the smaller the `stats_distance` the better!):\n\n ```python\n pot_detector.evaluate(method=\"ks\")\n pot_detector.evaluation_result\n ```\n ```shell\n column\ttotal_nonzero_exceedances\tstats_distance\tp_value\t c\tloc\t scale\n 0\t xandr\t 3311\t 0.012901\t0.635246 -0.128561\t 0\t 2.329005\n 1\t gam\t 3279\t 0.011006\t0.817674 -0.140479\t 0\t 3.852574\n 2\t adobe\t 3298\t 0.019479\t0.161510 -0.133019\t 0\t 6.007833\n ```\n\n13. If 1 test is not enough for evaluation, we can also visually test our analysis result with \"Quantile-Quantile Plot\" method to observed the sample quantile vs. the theoretical quantile:\n\n ```python\n # Use the last non-zero parameters\n pot_detector.evaluate(method=\"qq\")\n\n # Use a random non-zero parameters\n pot_detector.evaluate(method=\"qq\", is_random=True)\n ```\n\n \n\n### Anomaly Detection via Standalone Functions\n\nYou have a project that only needs to be fitted? To be detected? Don't worry! `anomalytics` also provides standalone functions as well in case users want to start the anomaly analysis from a different starting points. It is more flexible, but many processing needs to be done by you. LEt's take an example with a different dataset, thistime the water level Time Series!\n\n1. Import `anomalytics` and initialise your time series:\n\n ```python\n import anomalytics as atics\n\n ts = atics.read_ts(\n \"water_level.csv\",\n \"csv\"\n )\n ts.head()\n ```\n ```shell\n 2008-11-03 06:00:00 0.219\n 2008-11-03 07:00:00 -0.041\n 2008-11-03 08:00:00 -0.282\n 2008-11-03 09:00:00 -0.368\n 2008-11-03 10:00:00 -0.400\n Name: Water Level, dtype: float64\n ```\n\n2. Set the time windows of t0, t1, and t2 to compute dynamic expanding period for calculating the threshold via quantile:\n\n ```python\n t0, t1, t2 = atics.set_time_window(\n total_rows=ts.shape[0],\n method=\"POT\",\n analysis_type=\"historical\",\n t0_pct=0.65,\n t1_pct=0.25,\n t2_pct=0.1\n )\n\n print(f\"T0: {t0}\")\n print(f\"T1: {t1}\")\n print(f\"T2: {t2}\")\n ```\n ```shell\n T0: 65001\n T1: 25001\n T2: 10000\n ```\n\n3. Extract exceedances and indicate that it is a `\"high\"` anomaly type and what's the `q`uantile:\n\n ```python\n pot_thresholds = get_threshold_peaks_over_threshold(dataset=ts, t0=t0, \"high\", q=0.90)\n pot_exceedances = atics.get_exceedance_peaks_over_threshold(\n dataset=ts,\n threshold_dataset=pot_thresholds,\n anomaly_type=\"high\"\n )\n\n exceedances.head()\n ```\n ```shell\n 2008-11-03 06:00:00 0.859\n 2008-11-03 07:00:00 0.859\n 2008-11-03 08:00:00 0.859\n 2008-11-03 09:00:00 0.859\n 2008-11-03 10:00:00 0.859\n Name: Water Level, dtype: float64\n ```\n\n4. Compute the anomaly scores for each exceedance and initialize a params for further analysis and evaluation:\n\n ```python\n params = {}\n anomaly_scores = atics.get_anomaly_score(\n exceedance_dataset=pot_exceedances,\n t0=t0,\n gpd_params=params\n )\n\n anomaly_scores.head()\n ```\n ```shell\n 2016-04-03 15:00:00 0.0\n 2016-04-03 16:00:00 0.0\n 2016-04-03 17:00:00 0.0\n 2016-04-03 18:00:00 0.0\n 2016-04-03 19:00:00 0.0\n Name: anomaly scores, dtype: float64\n ...\n ```\n\n5. Inspect the parameters:\n\n ```python\n params\n ```\n ```shell\n {0: {'index': Timestamp('2016-04-03 15:00:00'),\n 'c': 0.0,\n 'loc': 0.0,\n 'scale': 0.0,\n 'p_value': 0.0,\n 'anomaly_score': 0.0},\n 1: {'index': Timestamp('2016-04-03 16:00:00'),\n ...\n 'c': 0.0,\n 'loc': 0.0,\n 'scale': 0.0,\n 'p_value': 0.0,\n 'anomaly_score': 0.0},\n ...}\n ```\n\n6. Detect anomalies:\n\n ```python\n anomaly_threshold = get_anomaly_threshold(\n anomaly_score_dataset=anomaly_scores,\n t1=t1,\n q=0.90\n )\n detection_result = get_anomaly(\n anomaly_score_dataset=anomaly_scores,\n threshold=anomaly_threshold,\n t1=t1\n )\n\n detection_result.head()\n ```\n ```shell\n 2020-03-31 19:00:00 False\n 2020-03-31 20:00:00 False\n 2020-03-31 21:00:00 False\n 2020-03-31 22:00:00 False\n 2020-03-31 23:00:00 False\n Name: anomalies, dtype: bool\n ```\n\n7. For the test, kolmogorov-smirnov and qq plot are also accessible via standalone functions, but the params need to be processed so it only contains a non-zero parameters since there are no reasons to calculate a zero \ud83d\ude02\n\n ```python\n nonzero_params = []\n\n for row in range(0, t1 + t2):\n if (\n params[row][\"c\"] != 0\n or params[row][\"loc\"] != 0\n or params[row][\"scale\"] != 0\n ):\n nonzero_params.append(params[row])\n\n ks_result = atics.evals.ks_1sample(\n dataset=pot_exceedances,\n stats_method=\"POT\",\n fit_params=nonzero_params\n )\n\n ks_result\n ```\n ```shell\n {'total_nonzero_exceedances': [5028], 'stats_distance': [0.0284] 'p_value': [0.8987], 'c': [0.003566], 'loc': [0], 'scale': [0.140657]}\n ```\n\n8. Visualize via qq plot:\n\n ```python\n nonzero_exceedances = exceedances[exceedances.values > 0]\n\n visualize_qq_plot(\n dataset=nonzero_exceedances,\n stats_method=\"POT\",\n fit_params=nonzero_params,\n )\n ```\n\n### Sending Anomaly Notification\n\nWe have anomaly you said? Don't worry, `anomalytics` has the implementation to send an alert via E-Mail or Slack. Just ensure that you have your email password or Slack webhook ready. This example shows both application (please read the comments \ud83d\ude0e):\n\n1. Initialize the wanted platform:\n\n ```python\n # Gmail\n gmail = atics.get_notification(\n platform=\"email\",\n sender_address=\"my-cool-email@gmail.com\",\n password=\"AIUEA13\",\n recipient_addresses=[\"my-recipient-1@gmail.com\", \"my-recipient-2@web.de\"],\n smtp_host=\"smtp.gmail.com\",\n smtp_port=876,\n )\n\n # Slack\n slack = atics.get_notification(\n platform=\"slack\",\n webhook_url=\"https://slack.com/my-slack/YOUR/SLACK/WEBHOOK\",\n )\n\n print(gmail)\n print(slack)\n ```\n ```shell\n 'Email Notification'\n 'Slack Notification'\n ```\n\n2. Prepare the data for the notification! If you use standalone, you need to process the `detection_result` to become a DataFrame with `row`, ``\n\n ```python\n # Standalone\n detected_anomalies = detection_result[detection_result.values == True]\n anomalous_data = ts[detected_anomalies.index]\n standalone_detection_summary = pd.DataFrame(\n index=anomalous.index.flatten(),\n data=dict(\n row=[ts.index.get_loc(index) + 1 for index in anomalous.index],\n anomalous_data=[data for data in anomalous.values],\n anomaly_score=[score for score in anomaly_score[anomalous.index].values],\n anomaly_threshold=[anomaly_threshold] * anomalous.shape[0],\n )\n )\n\n # Detector Instance\n detector_detection_summary = pot_detector.detection_summary\n\n ```\n\n1. Prepare the notification payload and a custome message if needed:\n\n ```python\n # Email\n gmail.setup(\n detection_summary=detection_summary,\n message=\"Extremely large anomaly detected! From Ad Impressions Dataset!\"\n )\n\n # Slack\n slack.setup(\n detection_summary=detection_summary,\n message=\"Extremely large anomaly detected! From Ad Impressions Dataset!\"\n )\n ```\n\n2. Send your notification! Beware that the scheduling is not implemented since it always depends on the logic of the use case:\n\n ```python\n # Email\n gmail.send\n\n # Slack\n slack.send\n ```\n ```shell\n 'Notification sent successfully.'\n ```\n\n3. Check your email or slack, this example produces the following notification via Slack:\n\n \n\n# Reference\n\n* Nakamura, C. (2021, July 13). On Choice of Hyper-parameter in Extreme Value Theory Based on Machine Learning Techniques. arXiv:2107.06074 [cs.LG]. https://doi.org/10.48550/arXiv.2107.06074\n\n* Davis, N., Raina, G., & Jagannathan, K. (2019). LSTM-Based Anomaly Detection: Detection Rules from Extreme Value Theory. In Proceedings of the EPIA Conference on Artificial Intelligence 2019. https://doi.org/10.48550/arXiv.1909.06041\n\n* Arian, H., Poorvasei, H., Sharifi, A., & Zamani, S. (2020, November 13). The Uncertain Shape of Grey Swans: Extreme Value Theory with Uncertain Threshold. arXiv:2011.06693v1 [econ.GN]. https://doi.org/10.48550/arXiv.2011.06693\n\n* Yiannis Kalliantzis. (n.d.). Detect Outliers: Expert Outlier Detection and Insights. Retrieved [23-12-04T15:10:12.000Z], from https://detectoutliers.com/\n\n# Wall of Fame\n\nI am deeply grateful to have met and guided by wonderful people who inspired me to finish my capstone project for my study at CODE university of applied sciences in Berlin (2023). Thank you so much for being you!\n\n* Sabrina Lindenberg\n* Adam Roe\n* Alessandro Dolci\n* Christian Leschinski\n* Johanna Kokocinski\n* Peter Krau\u00df\n",
"bugtrack_url": null,
"license": "MIT License Copyright (c) 2023 Nino Lindenberg Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the \"Software\"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ",
"summary": "The ultimate anomaly detection library.",
"version": "0.2.2",
"project_urls": {
"documentation": "https://github.com/Aeternalis-Ingenium/anomalytics/blob/trunk/README.md",
"repository": "https://github.com/Aeternalis-Ingenium/anomalytics"
},
"split_keywords": [
"anomaly",
"anomaly detection",
"statistics",
"mathematics",
"software engineering",
"data science",
"data analyst"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "e4679bb9fbf852dee936c607dbabe1dce0b0fb958ed38aed799ea713e97d85b8",
"md5": "9f24fec68bc2276eff681997333d4412",
"sha256": "ada5a1f5da7e55c6dfcd64e2c3a994504ed5c08827bf0f7ab25ef53e65b488f3"
},
"downloads": -1,
"filename": "anomalytics-0.2.2-py3-none-any.whl",
"has_sig": false,
"md5_digest": "9f24fec68bc2276eff681997333d4412",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.10",
"size": 49917,
"upload_time": "2023-12-21T10:34:31",
"upload_time_iso_8601": "2023-12-21T10:34:31.940903Z",
"url": "https://files.pythonhosted.org/packages/e4/67/9bb9fbf852dee936c607dbabe1dce0b0fb958ed38aed799ea713e97d85b8/anomalytics-0.2.2-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "2ec0b0edadd7439a228e8095aa519b64ecb37d92fdf3dc52e56155efcd65576f",
"md5": "1b9a21c58052171ed79b32df05b1f52c",
"sha256": "4b14a50b97ea465edf2e406e19e28fe17b659a65e9f34b97c32160e967450048"
},
"downloads": -1,
"filename": "anomalytics-0.2.2.tar.gz",
"has_sig": false,
"md5_digest": "1b9a21c58052171ed79b32df05b1f52c",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.10",
"size": 42091,
"upload_time": "2023-12-21T10:34:33",
"upload_time_iso_8601": "2023-12-21T10:34:33.209822Z",
"url": "https://files.pythonhosted.org/packages/2e/c0/b0edadd7439a228e8095aa519b64ecb37d92fdf3dc52e56155efcd65576f/anomalytics-0.2.2.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-12-21 10:34:33",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "Aeternalis-Ingenium",
"github_project": "anomalytics",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"requirements": [],
"lcname": "anomalytics"
}
