Badges
| fair-software.eu recommendations | |
|---|---|
| (1/5) code repository | |
| (2/5) license |
| (4/4) checklist | |
| howfairis |
|
| Other best practices | |
| Static analysis |
|
| Coverage |
|
| Documentation |
|
| GitHub Actions | |
| Build |
|
| Citation data consistency |
|
| SonarCloud |
|
| MarkDown link checker |
|
| How to install | |
| pypi |
|
| bioconda |
|
How to use rcx_tk
rcx-tk package provides tools to process the metadata or alkane files.
On the input, the user is expected to supply a path to the metadata/alkane file in tsv/csv/xls/xlsx file. The file is then converted to a dataframe which is further processed. The main steps are:
- columns rearrangement
- validation of the file names
- validation that the
injectionNumbercolumn is of integer type - derivation of new metadata:
sampleName,sequenceIdentifier,sampleIdentifierandlocalOrder
Finally, the processed dataframe is saved into user-defined location.
Installation
To install rcx_tk from GitHub repository, do:
git clone git@github.com:RECETOX/rcx-tk.git
cd rcx-tk
poetry install
The main functions are process_metadata_file and process_alkane_ri_file.
The tool can be run using subcommands in the command-line interface, either by python3 or poetry:
python3 -m rcx_tk sequence <path-to-input-data> <path-to-output-data>
python3 -m rcx_tk alkanes <path-to-input-data> <path-to-output-data>
python3 -m rcx_tk msdial <path-to-input-data> <path-to-output-data> [mz_tol_ppm]
poetry run rcx_tk sequence <file-path-to-input-data> <file-path-to-output-data>
poetry run rcx_tk alkanes <file-path-to-input-data> <file-path-to-output-data>
poetry run rcx_tk msdial <file-path-to-input-data> <file-path-to-output-data> [mz_tol_ppm]
Documentation
The project is documented here.
Contributing
If you want to contribute to the development of rcx_tk, have a look at the contribution guidelines.
Credits
This package was created with Cookiecutter and the NLeSC/python-template.
Metadata
Release files for rcx-tk 0.3.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 | |
|---|---|---|---|---|
| rcx_tk-0.3.1.tar.gz | 10.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rcx_tk-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.2 kB
Release files / rcx_tk-0.3.1.tar.gz
| Download URL | rcx_tk-0.3.1.tar.gz |
|---|---|
| Size | 10.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ed27c08b972ec2783177355db981468563211970c6031a9611664bb98df3fc55
|
|
BLAKE2b-256 checksum How to use checksums |
e939feee22c3fddee3782d1f092d2363940b648fbd953ca1d32141034bd51f49
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.4.1 CPython/3.11.0 Linux/6.17.0-1015-azure
|
Release files / rcx_tk-0.3.1-py3-none-any.whl
| Download URL | rcx_tk-0.3.1-py3-none-any.whl |
|---|---|
| Size | 10.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d4c9489b817a06dcde78d1fd178e8461c2ade76c5af05cc607c6bbdbced37eb7
|
|
BLAKE2b-256 checksum How to use checksums |
2139a3babeba8ed00d02a320f7aec379e36a829c3229d658dc9e177abe49a422
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.4.1 CPython/3.11.0 Linux/6.17.0-1015-azure
|
Security for rcx-tk 0.3.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.