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.

Sign up for GitHub

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

Jump to bottom

Why use all peaks rather than output peaks from function FindNode to run Cicero? #3

Open
JoanDu2017 opened this issue Jun 9, 2022 · 1 comment
Open

Why use all peaks rather than output peaks from function FindNode to run Cicero? #3

JoanDu2017 opened this issue Jun 9, 2022 · 1 comment

Comments

@JoanDu2017
Copy link

Hi, I used your pipeline to analyze my own data. I have a problem that why you used all peaks to run Cicero rather than the output peak list from the function FindNode?
@xmuhuanglab
Copy link
Owner

Hi, I used your pipeline to analyze my own data. I have a problem that why you used all peaks to run Cicero rather than the output peak list from the function FindNode?

We've already tested the co-accessibility results of all peaks and the output peak list from the function FindNode, and the results are similar. To save the computational resource, we used all peaks to calculate the co-accessibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JoanDu2017 @xmuhuanglab