Argument Components - Identification and Classification
This package provides a command line tool to find MajorClaims, Claims, and Premises on argumentative essays, as defined by Stab and Gurevych in their 2017 paper.
Inference
The tool AC-IaC takes one or more text files and finds MajorClaims, Claims, and Premises on them.
The results are returned in Brat-Standoff-Format.
If a directory is provided to the tool, it will recursively find all txt files in that and all the sub-directories.
This input structure will then be rebuilt in the output.
For the inference, a trained model needs to be provided.
I may have the correct models available on Hugging-Face under my username Theoreticallyhugo, which you could use for quick and dirty testing.
However, for proper use you need to train your own model, using the tool AC-IaC-train, as described in the training section.
If you want to test how the files would be structured in the ouput, you can use the dry option.
Training
The tool AC-IaC-train uses the original dataset of essays, annotated by Stab and Gurevych to train the models needed for inference.
Use AC-IaC-train -h to learn about the arguments that can be used.
use for inference
You always need to specify and ouput path, which will house the model files. If you have a Hugging-Face account, you can upload the models to Hugging-Face repos. This is recommended. If you don't want the models to be uploaded, set the corresponding option. Per default this tool will train both models, but it can be instructed to train just one of them.
use for validation
The tool supports setting a seed, the number of epochs, and running 5-fold-cross-validation. The evaluation data can be found in the output directory. The default number of epochs should always be good for use with inference.
dev-structure
- command_line.py is the entry point for the module.
AC-IaCandAC-IaC-trainpoint to the functionsinferenceandtrain_wrapperrespectively. - ./inference/ is the directory that houses everything inference related
- ./training/ is the directory that houses everything training related
Metadata
Release files for AC-IaC 1.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 | |
|---|---|---|---|---|
| ac_iac-1.0.1.tar.gz | 27.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ac_iac-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 67.1 kB
Release files / ac_iac-1.0.1.tar.gz
| Download URL | ac_iac-1.0.1.tar.gz |
|---|---|
| Size | 27.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cbb3813244f188681e58eaa6a6769630dd41865706a186f1b2a30decff1bbd2d
|
|
BLAKE2b-256 checksum How to use checksums |
419965de524a6830a2c4a798d322f7d61cde90fbb269ebdc28e4a930403dcf2c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.8.17
|
Release files / ac_iac-1.0.1-py3-none-any.whl
| Download URL | ac_iac-1.0.1-py3-none-any.whl |
|---|---|
| Size | 39.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3afe3bfb6b4418519c75d2197e923df9cccf8eefc047e259304fae30e4a1c56c
|
|
BLAKE2b-256 checksum How to use checksums |
b59d94df896e532746b22083e5e4f9c6bc766dbd1d6b4aa62dd626ceb38ffd99
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.8.17
|
Security for AC-IaC 1.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.