Add a recipe for kyber

[martin-g]

Describe your pull request here

---

Please read the guidelines for Bioconda recipes before opening a pull request (PR).

General instructions

• If this PR adds or updates a recipe, use "Add" or "Update" appropriately as the first word in its title.
• New recipes not directly relevant to the biological sciences need to be submitted to the conda-forge channel instead of Bioconda.
• PRs require reviews prior to being merged. Once your PR is passing tests and ready to be merged, please issue the @BiocondaBot please add label command.
• Please post questions on Gitter or ping @bioconda/core in a comment.

Instructions for avoiding API, ABI, and CLI breakage issues

Conda is able to record and lock (a.k.a. pin) dependency versions used at build time of other recipes.
This way, one can avoid that expectations of a downstream recipe with regards to API, ABI, or CLI are violated by later changes in the recipe.
If not already present in the meta.yaml, make sure to specify run_exports (see here for the rationale and comprehensive explanation).
Add a run_exports section like this:

build:
  run_exports:
    - ...

with ... being one of:

Case	run_exports statement
semantic versioning	{{ pin_subpackage("myrecipe", max_pin="x") }}
semantic versioning (0.x.x)	{{ pin_subpackage("myrecipe", max_pin="x.x") }}
known breakage in minor versions	{{ pin_subpackage("myrecipe", max_pin="x.x") }} (in such a case, please add a note that shortly mentions your evidence for that)
known breakage in patch versions	{{ pin_subpackage("myrecipe", max_pin="x.x.x") }} (in such a case, please add a note that shortly mentions your evidence for that)
calendar versioning	{{ pin_subpackage("myrecipe", max_pin=None) }}

while replacing "myrecipe" with either name if a name|lower variable is defined in your recipe or with the lowercase name of the package in quotes.

Bot commands for PR management

Please use the following BiocondaBot commands:

Everyone has access to the following BiocondaBot commands, which can be given in a comment:

@BiocondaBot please update	Merge the master branch into a PR.
@BiocondaBot please add label	Add the please review & merge label.
@BiocondaBot please fetch artifacts	Post links to CI-built packages/containers. You can use this to test packages locally.

Note that the @BiocondaBot please merge command is now depreciated. Please just squash and merge instead.

Also, the bot watches for comments from non-members that include @bioconda/<team> and will automatically re-post them to notify the addressed <team>.

[martin-g]

Marked as a Draft until wdecoster/kyber#10 is resolved

[martin-g]

@BiocondaBot please fetch artifacts

[BiocondaBot]

Package(s) built are ready for inspection:

Arch	Package	Zip File / Repodata	CI	Instructions
linux-64	kyber-0.6.0-ha6fb395_0.tar.bz2	linux-64.zip	GitHub Actions	show You may also use conda to install after downloading and extracting the zip file. conda install -c ./packages <package name>
osx-64	kyber-0.6.0-hdc87acc_0.tar.bz2	osx-64.zip	GitHub Actions	show You may also use conda to install after downloading and extracting the zip file. conda install -c ./packages <package name>
osx-arm64	kyber-0.6.0-h15efd92_0.tar.bz2	repodata.json	CircleCI	show You may also use conda to install:conda install -c https://output.circle-artifacts.com/output/job/919747d8-b92b-4e34-a7c8-08734d50733b/artifacts/0/tmp/artifacts/packages <package name>
linux-aarch64	kyber-0.6.0-h415ceb9_0.tar.bz2	repodata.json	CircleCI	show You may also use conda to install:conda install -c https://output.circle-artifacts.com/output/job/4a28dbe4-6c88-4632-b18b-6128c12455fa/artifacts/0/tmp/artifacts/packages <package name>

---

Docker image(s) built:

Package	Tag	CI	Install with docker
kyber	0.6.0--ha6fb395_0	GitHub Actions	show Images are in the linux-64 zip file above.gzip -dc images/kyber---0.6.0--ha6fb395_0.tar.gz | docker load

[martin-g]

mgrigorov in 🌐 euler-arm-22 in /tmp/kyber via 🅒 test123 took 11s 
❯ tar xvf kyber-0.6.0-h415ceb9_0.tar.bz2                                                                                                                                                                   (test123) 
info/files
info/test/run_test.sh
info/run_exports.json
info/hash_input.json
info/has_prefix
info/index.json
info/recipe/build.sh
info/paths.json
info/recipe/meta.yaml.template
info/recipe/meta.yaml
info/recipe/conda_build_config.yaml
info/about.json
info/git
info/licenses/THIRDPARTY.yml
bin/kyber

mgrigorov in 🌐 euler-arm-22 in /tmp/kyber via 🅒 test123 
❯ file bin/*                                                                                                                                                                                               (test123) 
bin/kyber: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, stripped

mgrigorov in 🌐 euler-arm-22 in /tmp/kyber via 🅒 test123 
❯ ./bin/kyber --help                                                                                                                                                                                       (test123) 
Tool to create a length-accuracy heatmap from a cram or bam file

Usage: kyber [OPTIONS] --input [<INPUT>...]

Options:
  -i, --input [<INPUT>...]       cram or bam file(s), or use `-` to read a file from stdin with e.g. samtools view -h
  -t, --threads <THREADS>        Number of parallel decompression threads to use [default: 4]
  -o, --output <OUTPUT>          Output file name [default: accuracy_heatmap.png]
  -c, --color [<COLOR>...]       Color used for heatmap [possible values: red, green, blue, purple, yellow]
  -b, --background <BACKGROUND>  Color used for background [default: black] [possible values: black, white]
  -p, --phred                    Plot accuracy in phred scale
      --normalize                Normalize the counts in each bin with a log2
      --ubam                     get reads from ubam file
  -h, --help                     Print help
  -V, --version                  Print version