Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Delivery not in line with current procedure #3948

Closed
RasmusBurge-CG opened this issue Nov 18, 2024 · 0 comments
Closed

Bug: Delivery not in line with current procedure #3948

RasmusBurge-CG opened this issue Nov 18, 2024 · 0 comments

Comments

@RasmusBurge-CG
Copy link
Contributor

Describe the bug

Sample with an application other than PAZ should not be delivered if the required amount of reads is not reached.

In this case sterlingmacaque sample ACC16176A14, among others, was delivered to Caesar but the threshold is 75% for this app-tag.

To Reproduce
Steps to reproduce the behavior:

  1. Look at a ticket with a non PAZ app-tag, see if there are samples with less than 75% reads. Look if that sample is in Caesar.

A clear and concise description of what you expected to happen.
Screenshot 2024-11-18 at 11 21 07

Expected behavior

The files should not be delivered. They will be re-sequenced to reach the required amount of reads, and then be delivered.

Additional context
Add any other context about the problem here.

@RasmusBurge-CG RasmusBurge-CG changed the title Bug: Bug: Delivery not in line with current procedure Nov 18, 2024
@karlnyr karlnyr removed the Bug label Nov 21, 2024
@karlnyr karlnyr closed this as not planned Won't fix, can't repro, duplicate, stale Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants