Tweak to celltype annotation

[Tobi1kenobi]

Modifications:

• Added parameter to enable or disable printing of celltypist probabilities per sample and annotation. This cuts down on file usage in yascp runs with hundreds of samples and many models
• Modified celltype merge input to take a TSV with filenames rather than print filenames to a terminal command which broke with many models and samples
• Fixed merging of celltype models when using yascp fetch full_name_inputs.tsv file by making the string splitting more flexible.

Notes:

• Celltype merge TSVs save as a result rather than in the hashed work directory because of issues printing to a file that was in the current work dir. Files could be deleted within the nextflow process but as it stands, are not.
• Merging of celltype models should work with full_names_inputs.tsv and original sample_ids but the latter is untested. Also untested is on multiplexed samples.
• I believe a bug still exists when submitting multiple samples with the same sanger_sample_id e.g. resequenced samples. For celltype annotation I think Azimuth is broken for these samples whilst celltypist and keras work the normalisation may be done within sanger_sample_id rather than within each sequenced sample. tl;dr sample duplicates not handled well

[github-actions]

Markdown linting is failing

To keep the code consistent with lots of contributors, we run automated code consistency checks.
To fix this CI test, please run:

• Install markdownlint-cli
  • On Mac: brew install markdownlint-cli
  • Everything else: Install npm then install markdownlint-cli (npm install -g markdownlint-cli)
• Fix the markdown errors
  • Automatically: markdownlint . --fix
  • Manually resolve anything left from markdownlint .

Once you push these changes the test should pass, and you can hide this comment 👍

We highly recommend setting up markdownlint in your code editor so that this formatting is done automatically on save. Ask about it on Slack for help!

Thanks again for your contribution!

[github-actions]

YAML linting is failing

To keep the code consistent with lots of contributors, we run automated code consistency checks.
To fix this CI test, please run:

• Install yaml-lint
  • Install npm then install yaml-lint (npm install -g yaml-lint)
• Fix the markdown errors
  • Run the test locally: yamllint $(find . -type f -name "*.yml" -o -name "*.yaml")
  • Fix any reported errors in your YAML files

Once you push these changes the test should pass, and you can hide this comment 👍

We highly recommend setting up yaml-lint in your code editor so that this formatting is done automatically on save. Ask about it on Slack for help!

Thanks again for your contribution!