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

add CRAM input handling #41

Open
alkaZeltser opened this issue Feb 3, 2024 · 4 comments
Open

add CRAM input handling #41

alkaZeltser opened this issue Feb 3, 2024 · 4 comments

Comments

@alkaZeltser
Copy link
Collaborator

CRAM formatted inputs require some modifications of the pipeline:

  1. PipeVal requires access to the reference file used for CRAM compression.
  2. CollectHsMetrics requires access to the reference fasta and index files.
@alkaZeltser
Copy link
Collaborator Author

@yashpatel6 any thoughts regarding PipeVal handling? Is there a way to provide it a reference file through the pipeline?

@yashpatel6
Copy link
Contributor

I think the way forward will be to generalize the PipeVal process used within Nextflow to allow additional inputs and options

@alkaZeltser
Copy link
Collaborator Author

I think the way forward will be to generalize the PipeVal process used within Nextflow to allow additional inputs and options

Sorry I don't understand, are you recommending changes to the external PipeVal tool independent of pipeline-targeted-coverage or are you recommending changes internal to pipeline-targeted-coverage, e.g. modifying this code?

@yashpatel6
Copy link
Contributor

I mean the Nextflow process we have for PipeVal (ie. the one being imported here: https://github.com/uclahs-cds/pipeline-targeted-coverage/blob/f3a5959d24538b445f83b1438786a2b9e92f13b8/main.nf#L6) needs to be generalized to allow for additional options

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