runner
Analyze multiple files for similarity and/or uniqueness. Finding similarities of works duplicated from one or more part of different works to create a seemingly unique one can be difficult because of different strategies being used, but this can be done better with a software like runner.
Requirements
- Arkivist
pip install arkivist
Usage
Install the latest abero package, upcoming versions might introduce unannounced changes, so a virtual environment is a must have before installation.
pip install -U abero
To integrate abero into your Python codes, check the code snippet below:
import abero
abero.analyze(directory, extension="txt", threshold=80, template=None, skipnames=0, group=0, unzip=0, reset=0)
CLI Usage
# usage: runner [-h] -d directory [-e extension] [-c control] [-t threshold] [-u unzip] [-s skipnames] [-g group] [-r reset]
py runner.py -d "<path_to_files>" -e "txt" -c "<path_to_control_file>" -t 1 -u 1 -s 1 -r 1
-d <path>- Full path of the dirctory containing the files to analyze.-e <txt>- List of allowed file extensions to analyze.-c <*.txt>- Full path of the control file.-t <80>- Threshold level for uniqueness, treats similarity below threshold as unique (1-100; default = 0)-u <0>- Unzip/extract ZIP files (0-1; default = 0)-s <0>- Skip files with common names (0-1; default = 0)-g <1>- Only compare if files contains the same identifier (0-1; default = 1)
Example: student1*_set1*.py >> student2*_set1*.py
-r <0>- Reset analytics before execution (0-1; default = 0)
Control File
Control file contains words or phrases, checked line-by-line, that are deem allowed to be contained in all files to analyzed; therefore, if found on the test files, it will not be flagged as duplicate work.
Features
- Unzip feature
- File comparison
- Threshold levels
- Skip / group compare
- Diff tool, content viewer
Did you know?
The repository name abero was inspired from the words aberrant and runner (Latin), which may mean deviating or being absent.
Metadata
Release files for abero 1.0.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 | Actions |
|---|---|---|---|---|
| abero-1.0.6.tar.gz | 125.4 kB | Without provenance | Details for abero-1.0.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| abero-1.0.6-py3-none-any.whl | Python 3 | none | any | Details for abero-1.0.6-py3-none-any.whl |
Total release size: 133.7 kB
Release files / abero-1.0.6.tar.gz
| Download URL | abero-1.0.6.tar.gz |
|---|---|
| Size | 125.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d0c06e64e4660a86d367c02856a70c9f6a6b9689d5d5bebc394deee490297af2
|
|
BLAKE2b-256 checksum How to use checksums |
65fd227662c4e09bcb68ef635e2c2c47a827fc4433f49651b5de7c705fad7a34
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.7.3 pkginfo/1.7.0 requests/2.24.0 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.9.2
|
Release files / abero-1.0.6-py3-none-any.whl
| Download URL | abero-1.0.6-py3-none-any.whl |
|---|---|
| Size | 8.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
80c9c28dbeadb7833beb5b6c7188e961af983ad22724c8d58c0545904cfa7097
|
|
BLAKE2b-256 checksum How to use checksums |
15c51068f2cb66ced04f2f7e5bb332188f80cb98162c8b98cdd252942c1ef70a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.7.3 pkginfo/1.7.0 requests/2.24.0 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.9.2
|
Security for abero 1.0.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.