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

samples from samplesheet.yml are not reported #92

Closed
oliverdrechsel opened this issue Mar 26, 2021 · 3 comments · Fixed by #93
Closed

samples from samplesheet.yml are not reported #92

oliverdrechsel opened this issue Mar 26, 2021 · 3 comments · Fixed by #93
Assignees
Labels
enhancement New feature or request

Comments

@oliverdrechsel
Copy link
Collaborator

This might be an issue with an older version (analyses was run end of February).

Samples that are given in the samplesheet.yml and yield no reads in demultiplexing are not reported in output. this may lead to missing information in tracking samples further downstream.

could you add the information of lacking reads in a report.csv or similar?

@replikation
Copy link
Owner

  • should be doable if a sample input file is provided.

@replikation replikation added the enhancement New feature or request label Mar 26, 2021
@hoelzer
Copy link
Collaborator

hoelzer commented Mar 27, 2021

  • should be doable if a sample input file is provided.

Yes exactly, we would specifically need this in case a sample sheet is provided. It would be sufficient to add samples missing in the final output (bc/ no consensus was constructed) to the report (HTML, XLSX, {C,T}SV) - e.g. a row that just has the ID and all other columns are 'NA' or something like 'No consensus reconstructed due to low read amount'.

I was thinking about how to add this but I think w/ some channel magic you are faster, @replikation ? :)

@RaverJay
Copy link
Collaborator

On it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants