Anomaly Detection and Prediction (ADAP) Package
This is a simple example package. You can use GitHub-flavored Markdown to write your content.
| Anomaly type | Type code | Description | Example in the literature and/or alternative terminology | Importance ranking (with respect to time series visualization in this case study) | Potential end-user and application |
|---|---|---|---|---|---|
| Impossible values | A | Values 6666 are highly impossible in compressor sensor data and consider as out of range value of the sensors. | - | Important, but it can be deleted easily using simple rule | - |
| Constant values within the acceptable region for long time period | B | Constant values within the acceptable region for long time period (more than one day) | - | Important can be detected using rate of change | - |
| Large sudden spike | C | The spikes are larger than the surrounding data points but less than 6666. Example one or two values much higher than previous or next values | - | At any point in the time series, used 3 times standard deviation as threshold | - |
| Drift | D | Gradual change in values in positive to zero | - | High priority (Emergency shutdown, ESD) | - |
| Sudden zero | E | Value suddenly shifts in values in positive to zero | - | High priority (Emergency shutdown, ESD) | - |
Table 1: Load current related anomaly types
| Anomaly type | Type code | Description | Example in the literature and/or alternative terminology | Importance ranking (with respect to time series visualization in this case study) | Potential end-user and application |
|---|---|---|---|---|---|
| Impossible values | A | Values 6666 are highly impossible in compressor sensor data and consider as out of range value of the sensors. | - | Important, but it can be deleted easily using simple rule | - |
| Constant values within the acceptable region for long time period | B | Constant values within the acceptable region for long time period (more than one day) | - | Important can be detected using rate of change | - |
| Large sudden spike | C | The spikes are larger than the surrounding data points but less than 6666. Example one or two values much higher than previous or next values | - | At any point in the time series, used 3 times standard deviation as threshold | - |
| Drift | D | Gradual change in values in positive to zero | - | High priority (Emergency shutdown, ESD) | - |
| Sudden zero | E | Value suddenly shifts in values in positive to zero | - | High priority (Emergency shutdown, ESD) | - |
| Step up (sudden shift) | F | Increase the mean while keeping the variance constant | - | High priority (Emergency shutdown, ESD) | - |
| Step down (sudden shift) | G | Decrease the mean while keeping the variance constant | - | Normal, indicate motor flips from OFF to ON | - |
Table 2: Suction pressure related anomaly types
| Anomaly type | Type code | Description | Example in the literature and/or alternative terminology | Importance ranking (with respect to time series visualization in this case study) | Potential end-user and application |
|---|---|---|---|---|---|
| Impossible values | A | Values 6666 are highly impossible in compressor sensor data and consider as out of range value of the sensors. | - | Important, but it can be deleted easily using simple rule | - |
| Constant values within the acceptable region for long time period | B | Constant values within the acceptable region for long time period (more than one day) | - | Important can be detected using rate of change | - |
| Large sudden spike | C | The spikes are larger than the surrounding data points but less than 6666. Example one or two values much higher than previous or next values | - | At any point in the time series, used 3 times standard deviation as threshold | - |
| Drift | D | Gradual change in values in positive to zero | - | High priority (Emergency shutdown, ESD) | - |
| Sudden zero | E | Value suddenly shifts in values in positive to zero | - | High priority (Emergency shutdown, ESD) | - |
| Step up (sudden shift) | F | Increase the mean while keeping the variance constant | - | Normal, indicate motor flips from OFF to ON | - |
| Step down (sudden shift) | G | Decrease the mean while keeping the variance constant | - | High priority (Emergency shutdown, ESD) | - |
Table 2: Discharge pressure related anomaly types
Metadata
Release files for adap 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| adap-0.0.1.tar.gz | 4.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| adap-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.1 kB
Release files / adap-0.0.1.tar.gz
| Download URL | adap-0.0.1.tar.gz |
|---|---|
| Size | 4.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
357f998bc81c5902935a66990abff6c355e3824be4e7b2dc6dc51fdaf7e8d978
|
|
BLAKE2b-256 checksum How to use checksums |
4c9356629208cf30fe8f06c38540c1a73b355e28fa2c90de3b563820d8b4ff58
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.10.1
|
Release files / adap-0.0.1-py3-none-any.whl
| Download URL | adap-0.0.1-py3-none-any.whl |
|---|---|
| Size | 5.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6b5eb9d9b137255b023b721257638b3923464dd9b3eed7a3930336db88b8e56c
|
|
BLAKE2b-256 checksum How to use checksums |
e865060ce469ceb3c228dade875a8e3dfff6a1cad5c0f1156929dab5646ab776
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.10.1
|
Security for adap 0.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.