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
1ff78fa4
Commit
1ff78fa4
authored
14 years ago
by
Aaron
Browse files
Options
Downloads
Patches
Plain Diff
Fixed bug in processing BED files in coverageBed using the Open/Get/Close idiom.
Open and Close were omitted by mistake.
parent
bcd7d9f4
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
src/coverageBed/coverageBed.cpp
+3
-1
3 additions, 1 deletion
src/coverageBed/coverageBed.cpp
with
3 additions
and
1 deletion
src/coverageBed/coverageBed.cpp
+
3
−
1
View file @
1ff78fa4
...
...
@@ -58,7 +58,8 @@ void BedCoverage::CollectCoverageBed() {
int
lineNum
=
0
;
// current input line number
BED
a
,
nullBed
;
BedLineStatus
bedStatus
;
_bedA
->
Open
();
// process each entry in A
bedStatus
=
_bedA
->
GetNextBed
(
a
,
lineNum
);
while
(
bedStatus
!=
BED_INVALID
)
{
...
...
@@ -69,6 +70,7 @@ void BedCoverage::CollectCoverageBed() {
}
bedStatus
=
_bedA
->
GetNextBed
(
a
,
lineNum
);
}
_bedA
->
Close
();
// report the coverage (summary or histogram) for BED B.
ReportCoverage
();
...
...
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