<#C062H82UCRG|> (soon to be) first release metro m...
# metro-maps
j
#C062H82UCRG (soon to be) first release metro map proposal - biggest challenge is the high level of parallelisation, and I didn't want to do the horrible intricate thing I did with taxprofiler again, so went with a new system, thus the experiment zoom in boxes (a la Sarek) Comments and criticism gratefully received 🙏
👌 3
m
The zoom in is not clear. Can you make it two lines to another square like in microscope figures
👍 1
j
I tried a variant of that before but it got in the way of the label on the main line... I'll have a think
Unless you have an idea?
m
sarek style, make an arrow
👀 1
and put database building on the big square
same for preprocessing
do you really need a postprocessing box?
But I like it
j
More like that? I don't like putting the labels against the box - what I might do is give them numbers: e.g.
2. Database Building
and put the number in the grey box
(I would also maybe pull the zoom in boxes closerto the main line a tad)
metro-map-diagram_v3.png
😍 1
m
Nah, still no clear connection. What if you make the nodes in the shape of inserts. Also, if you just want to avoid showing the parallelisation, I don't get the first and last insert. They are just confusing, in the context imo.
👍 2
j
So more of a square icon rather than round for the station icon? Fair enough, can replace section 1/2 with just the main line icons instead. Was sort of trying to future proof as I know that in the future definitely will be adding additional preprocessing steps
👍🏻 1
metro-map-diagram_v4.png
@mashehu?
Like so?
Another variant I randomly just thought: larger square node:
m
I would put
(amino acid)
on the right hand side, similar to
(nucleotide)
. But I feel like a legend for the lines' color might be more helpful
💯 1
I like that you simplified the metro map and removed the pre-processing and post-preprocessing boxes
👍 1
and instead of branching out for Bracken and tar, how about having some optional stations?
(But I agree it's clearer with branching out)
j
image.png
Orrrrr
m
what's the red line?
j
image.png
and instead of branching out for Bracken and tar, how about having some optional stations?
I prefer to minimise number of special objects, and want to go for things that are as inituive aspossible (without algend)
(so like you I find it clearer with the branching)
m
I still don't understand the red line without a legend
j
I added it to the legned!
m
oh
sorry, missed it
j
😬
m
I was looking at another image
j
image.png
uh oh here it comes
furious typing
m
I would separate yellow and blue line before the building node. It is confusing otherwise to not see them together in the zoomed in.
m
In sarek, we have this 🔍 on the part to be zoomed in to show the details
m
But I like the zoom indicator now, looks a lot clearer how it is connected.
j
I would separate yellow and blue line before the building node. It is confusing otherwise to not see them together in the zoomed in.
To be fair, they don't have to be entirely separated, they are actually all in the same subworkflow, it's just the input files are different...
I can try putting them together, wait
image.png
image.png
For a little more balance
m
Yes, a lot better. The last white arrow isn't centered correctly
m
a bit more spaces in between the blue and yellow lines?
j
a bit more spaces in between the blue and yellow lines?
Where?
Throughout the whole thing?
m
no, just between the blue stacks of lines and the yellow lines
j
image.png
m
I like it
j
image.png
Slightly improved balance
m
I don't like the white arrows much
j
Why so?
m
I also think they might not be necessary and just add noise. It is a quite clear left-right info stream.
m
I think just an arrow as entry and a line as end would be enough
j
image.png
m
Isn't there a red line missing in the zoom in?
j
I guess technically yes, but it's used across most tools
(except KMCP)
But I guess I could add something for that
Actuaylly no
image.png
I guess this would be betteR:
m
I find it confusing
j
Find which confusing?
m
the red line
It's coming vertically in the zoom, but diagonally in the actual map
j
(assuming done poperly):