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

Assess which files should be published #393

Closed
nschcolnicov opened this issue Aug 27, 2024 · 4 comments
Closed

Assess which files should be published #393

nschcolnicov opened this issue Aug 27, 2024 · 4 comments
Assignees

Comments

@nschcolnicov
Copy link
Contributor

nschcolnicov commented Aug 27, 2024

Current version publishes almost every file outputed by the processes. We probably should avoid publishing some of them, but would need a more informed opinion of an end-user or SME on which files to keep.

  • Should we keep bam bai from genomequant in publishdir?
  • Should we keep fastqc_raw and fastqc_trimmed files in publishdir? Only used for building multiqc (zip files), html reports are for user.
  • Should we outuput fastq and bam files?
  • Should we return fasta with their indices?

FYI @atrigila @apeltzer @grst @lpantano

@nschcolnicov nschcolnicov converted this from a draft issue Aug 27, 2024
@apeltzer
Copy link
Member

In general I would be rather keen to publish only relevant information, e.g. metrics and smaller files but no BAM/FASTQ or similar files if not explicity specified by the user. Default should be conservative, e.g. not pushing these files to users.

  • no BAM/BAI
  • keep fastqc (not much data)
  • no fastq/Bams
  • fasta with index I am indifferent

After all, we could make these things configurable, e.g. --save_intermediates or similar and upon that either publish or not.

@lpantano
Copy link
Contributor

agree with this, as far as the user can turn on saving those other files.

@apeltzer
Copy link
Member

apeltzer commented Sep 4, 2024

Sounds like a plan then :)

@atrigila atrigila self-assigned this Sep 16, 2024
@atrigila
Copy link
Contributor

Closed via #429

@github-project-automation github-project-automation bot moved this from In progress to Done in smrnaseq Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

4 participants