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

how to "merge" ? #1

Open
zdWang04 opened this issue Dec 17, 2024 · 2 comments
Open

how to "merge" ? #1

zdWang04 opened this issue Dec 17, 2024 · 2 comments

Comments

@zdWang04
Copy link

Hello,

I recently encountered a problem while using your software. I would like to analyze paired-end sequencing data, but I noticed that the parameter section only supports single-end sequencing. For paired-end sequencing, it seems that I need to run the program separately and then merge the results. What would be the best way to perform this "merging"? For example, should I use intersection, union, or another method?

Thank you!

@rna-editing1
Copy link
Owner

You are right; analyzing stranded, paired-end data is not supported out of the box.
As a workaround you can analyze the *_1.fastq and *_2.fastq individually:

  • Align these fastq files separately to obtain one bam file per fastq file.
  • Identify each file's strandedness/library type (manually in a genome browser or automatically via tools like salmon or how_we_are_stranded_here).
  • Organize and group your bam files by identified library type.
  • Run LoDEI for all files with identical library type.
  • Filter results according to your q-value threshold.
  • Merge the results, e.g., by using bamtools intersect.

There is no right or wrong when deciding between an intersection or a union. However, an intersection seems helpful in only keeping window regions covered in both result files.

@zdWang04
Copy link
Author

zdWang04 commented Jan 8, 2025

You are right; analyzing stranded, paired-end data is not supported out of the box. As a workaround you can analyze the *_1.fastq and *_2.fastq individually:

  • Align these fastq files separately to obtain one bam file per fastq file.
  • Identify each file's strandedness/library type (manually in a genome browser or automatically via tools like salmon or how_we_are_stranded_here).
  • Organize and group your bam files by identified library type.
  • Run LoDEI for all files with identical library type.
  • Filter results according to your q-value threshold.
  • Merge the results, e.g., by using bamtools intersect.

There is no right or wrong when deciding between an intersection or a union. However, an intersection seems helpful in only keeping window regions covered in both result files.

thanks for your replying!

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