Closed uniqueg closed 5 months ago
Would something like this work?
This is great - thanks a lot @balajtimate!
The only thing I'm not sure about is the tool names in the blue boxes. What do they signify? Do we use kallisto
to "infer" the library source, STAR for the read orientation and Cutadapt for the 3' adapter sequences?
And perhaps about the pictograms:
Do we use
kallisto
to "infer" the library source, STAR for the read orientation and Cutadapt for the 3' adapter sequences?
Yeah, exactly. Technically, STAR is also used for library type inference when the seq_ids are not present, but for the read orientation it's always used, so for the overview I think it's enough to put it there. If the flow is not obvious, I could put some arrows to indicate it more visibly.
The library type isn't very obvious. Might be better to have something that indicates single vs paired. Not sure what though.
Yeah 😅 Maybe a single and double arrows from the read orientation pictogram, and for that, add another pair of arrows showing the forward read as 2, and reverse as 1?
so perhaps increase the letter sice a bit and then use only one row?
Sure, I'll change that.
Yes, good idea about the library type pictogram.
I would probably put STAR in as well for the type inference, but maybe with a slightly in a lighter blue shade or with a pair of brackets around it? Just for completion.
Also, how is Cutadapt used for the 3' adapter sequence? I thought Rohan implemented some fancy search algorithm for that. Sure Cutadapt isn't just used for polyA tails?
Here is an updated version:
Great! I think you can just attach the SVG file as well here, then close the issue :)
Here is the SVG:
Create high level ("graphical abstract") overview of what HTSinfer does, in vector graphics.