Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
B
bedtools2
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
External wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
R3
legacy
bedtools2
Commits
214906b3
Commit
214906b3
authored
12 years ago
by
Aaron
Browse files
Options
Downloads
Patches
Plain Diff
update FAQ
parent
daee6e90
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/content/faq.rst
+30
-0
30 additions, 0 deletions
docs/content/faq.rst
with
30 additions
and
0 deletions
docs/content/faq.rst
+
30
−
0
View file @
214906b3
...
@@ -103,3 +103,33 @@ To display the help for a specific tool (e.g., ``bedtools shuffle``), use:
...
@@ -103,3 +103,33 @@ To display the help for a specific tool (e.g., ``bedtools shuffle``), use:
-n Report the number of BED entries that were merged.
-n Report the number of BED entries that were merged.
- Note: "1" is reported if no merging occurred.
- Note: "1" is reported if no merging occurred.
====================
Issues with output
====================
------------------------------------------------------------------------
I *know* there are overlaps, but none are reported. What might be wrong?
------------------------------------------------------------------------
There are two common causes of this problem. The first cause is non-obvious
differences in the way chromosomes are named in files being compared.
For example, "1" is not the same as "chr1" just as " chr1" is not the same
as "chr1". Secondly, users often copy files from a Windows machine to a UNIX
machine. This causes issues because Windows uses two bytes to represent
the end of a line (``\r\n``) whereas the UNIX convention uses a single byte
(``\n``). If your files don't conform to the UNIX convention, you will have
problems. One can convert files from Windows to UNIX with
the following command:
.. code-block:: bash
perl -i -p -e 's/\r\n/\n/g;' file.windows > file.unix
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment