####Use Case
When you want to merge two arff files with Weka, it gives you 2 options as merging and appending. Appending uses for merging two arff files which have exactly same headers. And merging option uses for merging attributes for same instances. But sometimes we need append arff files and their headers. So imagine you have 2 arff files which have same attributes(but different headers) and different instances.
1.arff, 30 instances
----------------------------------
@relation 1.arff
..
@attribute weather {rainy, sunny}
..
2.arff, 40 instances
----------------------------------
..
@attribute weather {cloudly}
..
merged.arff, 70 instances
---------------------------------
..
@attribute weather {rainy, sunny, cloudly]
..
####Usage
$ mergearff [1.arff] [2.arff] [merged.arff]
####Installation
$ [sudo] pip install mergearff
1 maintainer
Metadata
1 maintainer
Release files for mergearff 1.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 | Actions |
|---|---|---|---|---|
| mergearff-1.1.tar.gz | 2.1 kB | Without provenance | Details for mergearff-1.1.tar.gz |
Release files / mergearff-1.1.tar.gz
| Download URL | mergearff-1.1.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
55557cd7ca7942ca7cb417107384552ce8c0319efb393f304daab5c87fec9344
|
|
BLAKE2b-256 checksum How to use checksums |
70f6496cb7955ff9880555d61baab43bba7e0b6c84c83f89aa56832eba13e447
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for mergearff 1.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.
