-
Notifications
You must be signed in to change notification settings - Fork 43
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
Different STRAND in the same analysis #47
Comments
If the values are 'yes' or 'reverse' then yes. If some samples were sequenced not strand-specifically, then no. |
The problem is that GTEX control samples are STRAND = no. Does that mean I cannot use them together with my samples that are STRAND = yes? |
And if the above is not possible, do you have any suggestions for what to do? |
And just to clarify - what I mean is not whether it is recommended to combine stranded with unstranded samples -- I know that is not recommended. |
Yes, you can run the pipeline with different strand options, as they are defined for each sample individually. This might lead to batch effects that might or might not be corrected well by the autoencoder. You could either count your samples in a strand unspecific mode or count them strand specifically and evaluate based on the heatmap in the outrider summary, how strong the batch effect is. We would recommend the former, as it minimises known effects. |
Can samples with different STRAND values be used together in the same analysis?
The text was updated successfully, but these errors were encountered: