FHR-File-Converter

This is the fhr file converter, it can convert fhr inbetween json, fasta, microdata, and fasta header. If you would like a detailed specification of fhr, see FHR-Specification

Installation

You can intall the FHR file converter via pypi:

bash pip install fhr

You can also install the FHR file converter and its dependencies using Poetry (by first downloading the repo or release):

bash poetry install

Usage

Commnand line Usage

Using FHR on the command line:

bash fhr-convert <input>.<yaml|json|fasta|html> <output>.<yaml|json|fasta|html>

Detailed Usage:

``` usage: fhr-convert [-h] [--version]

Convert from one FHR supported file type to another

positional arguments: input followed by output

optional arguments: -h, --help show this help message and exit --version show program's version number and exit

positional input and output files input files can be one of: .yml .fasta - fasta contining a fhr header .html - html containing microdata

output files can be one of:
    <output>.yml
    <output>.fasta - fasta output type will be made as a fasta header without sequences
    <output>.html  - microdata output type will be made into generic html output

```

Validating an FHR file on command line

bash fhr-validate <input>.<yaml|json|fasta|html>

Detailed Usage:

``` usage: fhr-validate [-h] [--version]

Validate a fhr containing file

positional input and output files input files can be one of: .yml .fasta - fasta contining a fhr header .html - html containing microdata ```

As such validating a yaml file named "important_genome.fhr.yml" would be:

fhr-validate important_genome.fhr.yml

Other FHR Tools

FHR has several other command line tools:

• fhr_fasta_combine - combine a fhr header in any serialization with an existing fasta file
• fhr_fasta_strip - remove a fhr header out of a fasta file
• fhr_fasta_validate - check an fhr containing fasta against its checksum
• fhr_gfa_combine - combine a fhr header in any serilaization with an existing gfa file
• fhr_gfa_strip - remove an fhr header our of a gfa file
• fhr_gfa_validate - check an fhr containing gfa against its checksum

Using FHR in Python

To use FHR libabry in Python

```python

from fhr import fhr file = open("example.yaml") data = fhr() data.inputyaml(file.read()) data.outputfasta() ";~schema: https://raw.githubusercontent.com/FFRGS/FFRGS-Specification/main/fhr.json\n;~schemaVersion: 1\n;~genome: Bombas huntii\n;~version: 0.0.1\n;~author:;~ name:Adam Wright\n;~ url:https://wormbase.org/resource/person/WBPerson30813\n;~assembler:;~ name:David Molik\n;~ url:https:/david.molik.co/person\n;~place:;~ name:PBARC\n;~ url:https://www.ars.usda.gov/pacific-west-area/hilo-hi/daniel-k-inouye-us-pacific-basin-agricultural-research-center/\n;~taxa: Bombas huntii\n;~assemblySoftware: HiFiASM\n;~physicalSample: Located in Freezer 33, Drawer 137\n;~dateCreated: 2022-03-21\n;~instrument: ['Sequel IIe', 'Nanopore']\n;~scholarlyArticle: https://doi.org/10.1371/journal.pntd.0008755\n;~documentation: Built assembly from... \n;~identifier: ['gkx10242566416842']\n;~relatedLink: ['https/david.molik.co/genome']\n;~funding: some\n;~reuseConditions: public domain\n" ```

Checksums

The FHR stores checksums, allowing the FASTA header of the reference genome to contain the checksum for the FASTA file without the header.

To utilize the checksum, strip the FASTA header:

bash cat example.fasta | grep -E -v '^;~\s?checksum' > example.check.fasta

To strip the checksum:

bash cat example.fasta | grep -E ';~\s?checksum' | sed 's/^;~checksum://g' | sed '/\'//g'

Docker Support

You can also run the FHR file converter in a Docker container. To build the Docker image:

bash docker build -t fhr-file-converter .

And then run the Docker container:

bash docker run -it --rm fhr-file-converter

Running Code Quality Checks

Ensuring code quality is crucial for maintaining a healthy and sustainable codebase. The following tools help enforce coding standards and best practices:

isort

isort is a tool that sorts Python imports alphabetically within each section and separated by a blank line. It ensures consistent import styles across your project.

To run isort, use the following command:

bash poetry run isort .

ruff

ruff is a lightweight linter for Python that aims to detect common programming errors, stylistic issues, and code smells. It provides quick feedback on potential issues in your code.

To run ruff, use the following command:

bash poetry run ruff .

black

black is an uncompromising Python code formatter. It reformats entire files in place to ensure a consistent and readable code style. It's opinionated and strives for the smallest diffs possible.

To run black, use the following command:

bash poetry run black .

Running these code quality checks regularly helps maintain a clean and consistent codebase, making it easier to collaborate with others and ensuring code readability and maintainability. These checks are required to pass in order to pull changes into the main branch.

pytest

Make sure you install depedencies first and then run the tests with poetry bash poetry run install poetry run pytest

Citing FHR

Information on Citations of FHR

Citing the Validation Tool

cite the validation tool when directly interacting with the tool or library The APA citation for the FHR validation/converter software is:

Molik, D., & Wright, A. FHR File Converster [Computer software]. https://github.com/FAIR-bioHeaders/FHR-File-Converter

Or in bibtex: bibtex % Citation For FHR Validation/Converter Software @software{FHR_File_Converter, author = {Molik, David and Wright, Adam}, year = {2023}, license = {PDDL-1.0}, title = {{FHR File Converster}}, url = {https://github.com/FAIR-bioHeaders/FHR-File-Converter}, doi = {10.5281/zenodo.6762547} }

Citing the Specification

cite the specification when directly interacting with the specification (pull requests, comments on schema) The APA citation for the FHR specification is:

Molik, D., & Wright, A. FHR Specification [Data set]. https://github.com/FAIR-bioHeaders/FHR-Specification

Or in bibtex: bibtex % Citation For FHR Specification @misc{FHR_Specification, author = {Molik, David and Wright, Adam}, year = {2023}, title = {{FHR Specification}}, url = {https://github.com/FAIR-bioHeaders/FHR-Specification}, doi = {10.5281/zenodo.6762549} }

Citing FHR

The APA citation for the FHR Briefings in Bioinformatics is:

Adam Wright, Mark D Wilkinson, Christopher Mungall, Scott Cain, Stephen Richards, Paul Sternberg, Ellen Provin, Jonathan L Jacobs, Scott Geib, Daniela Raciti, Karen Yook, Lincoln Stein, David C Molik, FAIR Header Reference genome: a TRUSTworthy standard, Briefings in Bioinformatics, Volume 25, Issue 3, May 2024, bbae122, https://doi.org/10.1093/bib/bbae122

Or in bibtex: bibtex % Citation For FHR @article{10.1093/bib/bbae122, author = {Wright, Adam and Wilkinson, Mark D and Mungall, Christopher and Cain, Scott and Richards, Stephen and Sternberg, Paul and Provin, Ellen and Jacobs, Jonathan L and Geib, Scott and Raciti, Daniela and Yook, Karen and Stein, Lincoln and Molik, David C}, title = "{FAIR Header Reference genome: a TRUSTworthy standard}", journal = {Briefings in Bioinformatics}, volume = {25}, number = {3}, pages = {bbae122}, year = {2024}, month = {03}, abstract = "{The lack of interoperable data standards among reference genome data-sharing platforms inhibits cross-platform analysis while increasing the risk of data provenance loss. Here, we describe the FAIR bioHeaders Reference genome (FHR), a metadata standard guided by the principles of Findability, Accessibility, Interoperability and Reuse (FAIR) in addition to the principles of Transparency, Responsibility, User focus, Sustainability and Technology. The objective of FHR is to provide an extensive set of data serialisation methods and minimum data field requirements while still maintaining extensibility, flexibility and expressivity in an increasingly decentralised genomic data ecosystem. The effort needed to implement FHR is low; FHR’s design philosophy ensures easy implementation while retaining the benefits gained from recording both machine and human-readable provenance.}", issn = {1477-4054}, doi = {10.1093/bib/bbae122}, url = {https://doi.org/10.1093/bib/bbae122}, eprint = {https://academic.oup.com/bib/article-pdf/25/3/bbae122/57108923/bbae122.pdf}, }