Log-distance-measures

Latest version: v2.1.0

Safety actively analyzes 723217 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 2

2.1.0

Changelog


4d66266 - Add Remaining Time Distribution distance measure (RTD) to measure the remaining cycle time of already-started cases (David Chapela de la Campa)

2.0.2

Changelog


f9fff7c - Refactor to avoid Pandas FutureWarning(s) (David Chapela de la Campa)
60d8a2a - Update README.md (David Chapela de la Campa)

2.0.1

Changelog


2f712d8 - Update workflow (upload artifact v4) (David Chapela de la Campa)
d635938 - Release 2.0.1 - Update dependencies and README.md (David Chapela de la Campa)

2.0.0

Changelog


c321319 - Release 2.0.0 - with Circadian Workforce and Work in Progress (David Chapela de la Campa)
8828f86 - [InfSys] - Adapt ELS.py script and include new Workforce metric (David Chapela de la Campa)

1.1.0

Changelog


5004c56 - Reimplement "Work in Progress" to measure the distance with 1-WD or EMD We are interested in penalizing not only the differences in the mass distribution but their distance, similarly to other metrics, because it's not the same to estimate the same WiP displaced 2h than 10h. (David Chapela de la Campa)
c11fef0 - Fix normalization of the measured distances When normalizing a measured distance, if the maximum observed value is 0 (all observations are in the first bin of the "histogram"), set the measured distance as normalized value instead of 0. Wasserstein will return 0 because if all observations are in the same bin in both "histograms", the PDFs are the same. EMD will return a difference if there's a difference in mass (desired). (David Chapela de la Campa)
3712a8d - Refactor Circadian Workforce to compute the average of active workers per hour and day of the week Realized that if we only aggregate the number of active workers, the same simulation scenario (w.r.t. the resource model) having a duration of 4 months vs 2 months (for example, because of different activity durations) would result in two very different workforces. Our aim is to compare the weekly workforce of one log with another, so by computing the average we mitigate this error. (David Chapela de la Campa)

1.0.3

Changelog


8c0aabb - Update patch version (David Chapela de la Campa)
be31a0b - Merge remote-tracking branch 'origin/main' (David Chapela de la Campa)
f60cec6 - Implement circadian workforce measure and tests Circadian workforce measures the number of distinct resources that were observed in each hour of each day of the week. For example, number of distinct resources registering an event on each Monday at 3 PM. Then aggregates (by summing up) all the observations of Mondays at 3 PM. Finally, it computes the EMD for each day of the week, where each hour is a bin. (David Chapela de la Campa)
4aa261f - Add PyPI link to README.md. Closes 14 (Ihar Suvorau)

Page 1 of 2

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.