-
Notifications
You must be signed in to change notification settings - Fork 9
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.
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
Output related questions #109
Comments
Hi Jens, Thanks for reaching out. So the layout file was designed to be easily readable by Raptor to build the index rather than for users to interpret. The Now to the hierarchy. The
Let's look at an easy example
This means there is only a single level. File 1 is split into two technical bins (TB), namely TB-0 and TB-1. Thus file2, who is only stored in a single bin, is stored in TB-3. Next example
Now there are two levels. I hope this is helpful? Then you can probably parse the layout.
Which information are you interested in? Maybe I'll add a |
Hi Svenja, thanks for your quick reply and shedding light on the output. I was just playing around with the HIBF. I used the entire viral refseq and computed a layout with chopper but was stuck because I did not understand the structure of the HIBF that would result when building it with raptor. I'm currently thinking about applying your approach for my tools as well. Maybe a better documentation would suffice for the beginning ;-) |
Hi Jens, I'll work on the documentation! We are currently thinking about how we could move the HIBF to seqan3 s.t. the data structure is available without chopper/raptor. Best, |
Hi,
I have some questions regarding the output of chopper layout. I tried to calculate the layout for the viral refseq and got the following header lines as part of the output
As far as I can see, these are all merged bins, but what does
max_bin_id
refer to? And how can I infer the topology of the hierarchy from the output?How can I interpret the
BIN_INDICES
andNUMBER_OF_BINS
columns?Cheers
Jens
The text was updated successfully, but these errors were encountered: