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 option for separating out technical replicates #17

Open
nboley opened this issue May 24, 2016 · 4 comments
Open

Add option for separating out technical replicates #17

nboley opened this issue May 24, 2016 · 4 comments

Comments

@nboley
Copy link
Collaborator

nboley commented May 24, 2016

  • PCR duplicate should happen on each technical replicate
  • The the bams should be merged with a RG assignment atatched
    • we should allow the user to specify custom read group meta data
@chrisprobert
Copy link
Member

@nboley: Just to clarify: a technical replicate here is a unique sample/lane combination? So a library sequenced on multiple lanes has a technical replicate for each sample in each lane?

@akundaje
Copy link
Contributor

I think it's dangerous to do excessive inference from read names etc.
Platforms or conventions often change and then all of this breaks down.
Best to have users be explicit about what tech reps, lanes, bioreps and
adapter sequences.
On May 24, 2016 4:57 PM, "Chris Probert" [email protected] wrote:

@nboley https://github.com/nboley: Just to clarify: a technical
replicate here is a unique sample/lane combination? So a library sequenced
on multiple lanes has a technical replicate for each sample in each lane?


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#17 (comment)

@chrisprobert
Copy link
Member

@akundaje Yeah, I think some type of sample sheet to specify parameters for all replicates would be a good solution, perhaps combined with automated sanity checking (e.g. if the user-specified adapter sequence is clearly wrong).

@akundaje
Copy link
Contributor

Agreed
On May 24, 2016 5:07 PM, "Chris Probert" [email protected] wrote:

@akundaje https://github.com/akundaje Yeah, I think some type of sample
sheet to specify parameters for all replicates would be a good solution,
perhaps combined with automated sanity checking (e.g. if the user-specified
adapter sequence is clearly wrong).


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#17 (comment)

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

3 participants