nf-core / nf-core/clipseq

Test and integarte peak input from peakcallers other then pureclip

Open
#137 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Nextflow
Stars
26
Forks
43
PR merge metrics
No merged PRs in 30d

Description

We need to check if bindingSiteFinder is ok with the input from the other peak callers or if we need to change something to read them in

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by examining bindingSiteFinder's current input expectations and the outputs produced by the other peak callers. Compare those formats and determine whether each caller's output can be consumed as-is; done means the supported inputs are tested and any required changes are identified and verified.

Written by the indexing model from the issue text.

Assessment

Domain
bioinformatics
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.