https://nf-co.re logo
Join Slack
Powered by
Metromap question: Is this too confusing?
# help
n
Metromap question: Is this too confusing?
image.png
e
The colors legend would help see if it's confusing 😄
But I like it
n
The color map is essentially based on the datatypes: pink: ONT read, blue: HiFI read; green HiC read, red genomic short read; black: fasta file, grey: reference genome, dark-grey: reference annotation
But I am not sure if this actually is a good way to do it. I could draw every possible path through the pipeline, but i think this would be extremely confusing since there are many paths
By datatype i obviously mean format
j
I would say yes from the point of view tis that it is much too cramped
Stretch it A4
)landscape)
e
Artist's choice I guess, always depend on the complex parts of each pipeline. But there should be a legend explaining that black is a mix for more than one input channel or something. And I guess hte grey colors that jump from pink and blue also need an explanation
j
But I have a feeling also it might be too much detail?
Does a user really need ALL that infoi?
n
I made the pink/blue output that was grey black (since it was inconsistent with the legend I made up)
j
And also I think readability is not helping because everything out of scale: the logo is much too big, as are the file icons
a
It feels intuitive to me in terms of detail/layout but agree with James that it needs to have more space
👍 1
I would also leave off the reference genome
j
So it's just blows your eyes out in detail compressed into a single space
n
Really hard for me to know which info the user needs since it is all obvious to me 😉
I also wanted to make it a bit explicit which inputs are needed for which parts / subworkflows
👍 1
a
Really hard for me to know which info the user needs since it is all obvious to me 😉
I sincerely understand your pain here
My personal take is that you don't need to list/show reference data files in the pipeline diagram (unless it were a specific reference handling pipeline of course!) but typically just the "user generated" inputs
n
Making it wider and less cramped is probably a good idea, I usually create these left -> right and then i run out of space the closer I get the right
but the reference (if used) has to be provided by the user
j
Remember we live in the wonderful world of abstract intetnet, you don't need to be constrained by ISO paper dimensions 😉
n
But it has to scale from phone to gaming monitor 😢
j
Phone?!
😂 1
n
Tiny tablet?
j
Pepole can scrolly scrolly in that case, make it top down 😉
n
I guess there could be t->d mermaid gitgraph for the phone users
👍 1
Thanks for the feedback
j
But otherwise, I think your main issue is just space, let it breath (less abrupt curves etc), have more in balance, it actually will work quite well
m
I would also try to get the lines as straight as possible, makes it easier to follow and looks less chaotic (my first impression was that i was looking at a bomb defuser training kit 😁)
👍 1
n
So regarding the space, more like this?
image.png
for the curves I am not really sure what to do, I realize that there are parts where it looks kind of confusing, but I guess this is also related to the fact that there is no "correct way" through the pipeline and users may decide to stuff something into another thing (thats what the scaffold thing is supposed to reflect), or not
j
Tha'ts already better yes, less overtwhelming
I would argue you can make logo half the size or 75% the size, icons can still go smaller
And just make it wider, don't restrict yourself to a square 😉
And make sure things are aligned properly, and reduce the reliance of curly-wurly self-drawn lines too
Like that is unnsecesasry
As is this:
m
for the curves, try to make them as parallel as possible and with as little curves as possible. and no wobbly lines please
this 2
original tube maps often have fixed angles for their lines, try to stick to that as well
👍 1
n
Ok, thanks!
Open in Slack
PreviousNext
Powered by