feat: add Orthanq wrappers for hla and virus applications

[huzuner]

QC

• I confirm that:

For all wrappers added by this PR,

• there is a test case which covers any introduced changes,
• input: and output: file paths in the resulting rule can be changed arbitrarily,
• either the wrapper can only use a single core, or the example rule contains a threads: x statement with x being a reasonable default,
• rule names in the test case are in snake_case and somehow tell what the rule is about or match the tools purpose or name (e.g., map_reads for a step that maps reads),
• all environment.yaml specifications follow the respective best practices,
• the environment.yaml pinning has been updated by running snakedeploy pin-conda-envs environment.yaml on a linux machine,
• wherever possible, command line arguments are inferred and set automatically (e.g. based on file extensions in input: or output:),
• all fields of the example rules in the Snakefiles and their entries are explained via comments (input:/output:/params: etc.),
• stderr and/or stdout are logged correctly (log:), depending on the wrapped tool,
• temporary files are either written to a unique hidden folder in the working directory, or (better) stored where the Python function tempfile.gettempdir() points to (see here; this also means that using any Python tempfile default behavior works),
• the meta.yaml contains a link to the documentation of the respective tool or command,
• Snakefiles pass the linting (snakemake --lint),
• Snakefiles are formatted with snakefmt,
• Python wrapper scripts are formatted with black.
• Conda environments use a minimal amount of channels, in recommended ordering. E.g. for bioconda, use (conda-forge, bioconda, nodefaults, as conda-forge should have highest priority and defaults channels are usually not needed because most packages are in conda-forge nowadays).

[fgvieira]

Don't have any experience with orthanq but, from the command line, it seems that it could make more sense to have candidates\hla and cadidates\virus, no?

It seems candidates\hla uses a temp folder; can you use the tmpdir resource?

[huzuner]

Don't have any experience with orthanq but, from the command line, it seems that it could make more sense to have candidates\hla and cadidates\virus, no?

It seems candidates\hla uses a temp folder; can you use the tmpdir resource?

Yes that could make sense aswell. But I was thinking of putting everything related to the each application in one folder, to make the navigation within the usage easier. Therefore the commands are as follows:

orthanq candidates hla
orthanq preprocess hla
orthanq call hla

and

orthanq candidates virus
orthanq preprocess virus
orthanq call virus

also could you eloborate more regarding the temp usage?

Thank you for all the reviewing :)

[fgvieira]

From what I can see in the docs, it seems that the tool has three subcommands and hla/virus is an option. If so, I'd organize the wrapper the same way as (e.g.) samtools (orthanq/candidates, orthanq/preprocess, and orthanq/call) with hla/virus as a parameter.
However, since orthanq is developed by @johanneskoester lab, I think it would be nice to hear from him.

If the program supports a temp folder, then it would be nice if the wrappers would take care of it. For example, as in:

snakemake-wrappers/bio/samtools/sort/wrapper.py

Lines 25 to 30 in f0b638a

	with tempfile.TemporaryDirectory() as tmpdir:
	tmp_prefix = Path(tmpdir) / "samtools_sort"
	shell(
	"samtools sort {samtools_opts} -m {mem_per_thread_mb}M {extra} -T {tmp_prefix} {snakemake.input[0]} {log}"
	)