Evolutionary Dataset Optimisation
A library for generating artificial datasets through evolution.
The edo library provides an evolutionary algorithm that optimises any real-valued function over a subset of the space of all possible datasets that we call Evolutionary Dataset Optimisation. The output of the algorithm is a bank of effective datasets for which the provided function performs well that can then be studied.
The applications of this method are varied but an important and relevant one is in learning an algorithm’s strengths and weaknesses.
When determining the quality of an algorithm, the standard route is to run the comparable algorithms on a finite set of existing (or newly simulated) datasets and calculating some metric. The algorithm(s) with the smallest value of this metric are chosen to be the best performing.
An issue with this approach is that it pays little regard to the reliability and quality of the datasets being used, which begs the question: what makes a dataset “good” for an algorithm? Or, why is it that an algorithm performs well on some datasets but not others?
By passing the objective function of the algorithm to the edo.DataOptimiser class, questions like these can be answered by studying the properties of the resultant datasets. Beyond that, a combination of objective functions could be used to determine how an algorithm performs against any number of other algorithms. A comprehensive description of the evolutionary algorithm and an examplar case study is available at https://doi.org/10.1007/s10489-019-01592-4.
Installation
The edo library requires Python 3.6+ and is pip-installable:
$ python -m pip install edo
To install from source then clone the GitHub repo:
$ git clone https://github.com/daffidwilde/edo.git $ cd edo $ python setup.py install
A command line tool has been developed to make using edo for larger experiments easier: https://github.com/daffidwilde/edolab
Publications and documentation
Full documentation for the library is available at https://edo.readthedocs.io.
An article on the theory behind the algorithm has been published:
Wilde, H., Knight, V. & Gillard, J. Evolutionary dataset optimisation: learning algorithm quality through evolution. Appl Intell 50, 1172-1191 (2020). https://doi.org/10.1007/s10489-019-01592-4
Citation instructions
Citing the library
Please use the following to cite the library:
@misc{edo-library,
author = {{The EDO library developers}},
title = {edo: <RELEASE TITLE>},
year = <RELEASE YEAR>,
doi = {<DOI INFORMATION>},
url = {http://doi.org/<DOI INFORMATION>}
}
To check the relevant details (i.e. RELEASE TITLE, RELEASE YEAR and DOI NUMBER) head to the library’s Zenodo page:
Citing the paper
If you wish to cite the paper, then use the following:
@article{edo-paper,
title = {Evolutionary dataset optimisation: learning algorithm quality
through evolution},
author = {Wilde, Henry and Knight, Vincent and Gillard, Jonathan},
journal = {Applied Intelligence},
year = 2020,
volume = 50,
pages = {1172--1191},
doi = {10.1007/s10489-019-01592-4},
}
Contributing to the library
Contributions are always welcome whether they come in the form of providing a fix for a current issue, reporting a bug or implementing an enhancement to the library code itself. Pull requests (PRs) will be reviewed and collaboration is encouraged.
To make a contribution via a PR, follow these steps:
Make a fork of the GitHub repo and clone your fork locally:
$ git clone https://github.com/<your-username>/edo.git
Install the library in development mode. If you use Anaconda, there is a conda environment file (environment.yml) with all of the development dependencies:
$ cd edo $ conda env create -f environment.yml $ conda activate edo-dev $ python setup.py develop
Make your changes and write tests to go with them. Ensure that they pass and you have 100% coverage:
$ python -m pytest --cov=edo --cov-fail-under=100 tests
Push to your fork and open a pull request.
Metadata
Release files for edo 0.3.6
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 | |
|---|---|---|---|---|
| edo-0.3.6.tar.gz | 30.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| edo-0.3.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 53.6 kB
Release files / edo-0.3.6.tar.gz
| Download URL | edo-0.3.6.tar.gz |
|---|---|
| Size | 30.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7489c2c90da2ab350bfbebea533afff8ee4c6a364aabc80d51fe835411c9253e
|
|
BLAKE2b-256 checksum How to use checksums |
1cff7014894ed1e4c0c23c31d31ea03a4daa66603091723d2d02b6236d9eedd8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.2.0.post20200714 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.8.3
|
Release files / edo-0.3.6-py3-none-any.whl
| Download URL | edo-0.3.6-py3-none-any.whl |
|---|---|
| Size | 23.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
41319427e21a34808ccb624c1730cd36725847f3d87d2fb5de60ab0f3f9e3395
|
|
BLAKE2b-256 checksum How to use checksums |
d23fe5c98b7304540899037b479bb02466561c0b9e16c87ab773b99b979468cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.2.0.post20200714 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.8.3
|
Security for edo 0.3.6
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.