ryanlayer / giggle

Interval data structure
MIT License
224 stars 29 forks source link

Problem indexing multiple bed files #35

Closed mvdbeek closed 6 years ago

mvdbeek commented 6 years ago

Hi there,

I can't manage to index more than 1 file. I am trying this with a single-line bed file like this:

chr2L   450388  451555
$ giggle index -o test_idx9  -i a.bed.gz b.bed.gz
Indexed 1 intervals.

(a.bed.gz is a copy of b.bed.gz, but only 1 interval seems to be indexed) Consequently the same thing happens when I try to index a directory full of sorted and bgzip'ed bed files.

Is there anything I'm doing wrong ? I'm working off the master branch, but the docker container also seems to have the same issue. Any help would be much appreciated.

ryanlayer commented 6 years ago

put those bed files in their own directory, then use a wildcard to pass in the path.

mkdir bed_files mv a.bed.gz b.bed.gz bed_files giggle index -o test_idx9 -i "bed_files/*.bed.gz" -s -f

On Tue, Apr 17, 2018 at 10:26 AM, Marius van den Beek < notifications@github.com> wrote:

Hi there,

I can't manage to index more than 1 file. I am trying this with a single-line bed file like this:

chr2L 450388 451555

$ giggle index -o test_idx9 -i a.bed.gz b.bed.gz Indexed 1 intervals.

(a.bed.gz is a copy of b.bed.gz, but only 1 interval seems to be indexed:) Consequently the same thing happens when I try to index a directory full of sorted and bgzip'ed bed files.

Is there anything I'm doing wrong ? I'm working off the master branch, but the docker container also seems to have the same issue. Any help would be much appreciated.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ryanlayer/giggle/issues/35, or mute the thread https://github.com/notifications/unsubscribe-auth/AAlDUXQxVhNj7fwc6TAglszOZHAgHmEqks5tphfJgaJpZM4TYpE2 .

-- Ryan Layer

mvdbeek commented 6 years ago

Thanks, the quotes made the difference here. I guess it'd be more intuitive if those weren't required, but now I see it in the readme as well.