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

Threshold for bounded/unbounded TFs ? #262

Closed
matteozoia4 opened this issue Apr 11, 2024 · 2 comments
Closed

Threshold for bounded/unbounded TFs ? #262

matteozoia4 opened this issue Apr 11, 2024 · 2 comments
Labels

Comments

@matteozoia4
Copy link

Dear TOBIAS providers,

I have noticed to loose positive binding sites (after TOBIAS analysis) of TFs that we know (through ChIP-seq analysis) to be actually binding regions within our input.
-> I am working with snATAC-seq .bam files using JASPAR2024 TFBMs PWMs.

  1. What can I do (adjusting a specific threshold during a given step in the pipeline?) to get/improve the footprinting analysis closest to the biology of the tissue?

Kind regards,

MZ

@hschult
Copy link
Collaborator

hschult commented Apr 18, 2024

Hi @matteozoia4 and thank you for using TOBIAS.

I need more information to give a definitive answer for example the TOBIAS call would be a good start.
However, as you are using snATAC-seq data sparsity might be the issue. TOBIAS relies on the Tn5-cutsites to predict footprints, where a footprint is defined as a small area with less cutsites flanked by areas containing more cutsites (see our wiki) as such a certain amount of Tn5-cutsites and subsequently read coverage is needed to reliably predict footprints. For bulk ATAC, which TOBIAS was designed for, this is usually not an issue, however analysing at cell-level often does not provide enough cutsites and therefore may not see some of the footprints.
A possible workaround would be to create "pseudobulks" by combining your .bam files into one .bam per group (cell type, condition, etc.) and running TOBIAS with these files but keep the number of cells per group in mind, small groups could still suffer from data sparsity.

I hope this answers your questions.

Best wishes,
Hendrik

Copy link

No activity for at least 30 days. Marking issue as stale. Stale issues are closed after one week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants