-
Notifications
You must be signed in to change notification settings - Fork 628
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
Add config option to control DAG level of detail #3203
Comments
When you say hiding the operator name but leaving an empty node, the DAG structure wouldn't change. Only the label for operator/channels would be hidden, right? |
Right |
Probably a separate effort, but I think we should also be able to collapse subworkflows into single nodes. That would make the DAG actually usable for real workflows. As an example, I generated the Mermaid diagram for rnaseq: It's like looking at the logic diagram of an entire CPU -- hilariously impossible. What you really want is something more coarse-grained by default, that you can optionally make more fine-grained as you need it. A config option called e.g. nf-core/rnaseq is a bit weird because the top-level workflow calls |
LOL. what pipeline is this? |
nf-core rnaseq ! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
See this Slack thread: https://nextflow.slack.com/archives/C02T98A23U7/p1662981608103629
It would be nice for the
dag
config scope to have averbose
option to control whether extra details like channel names and operators are displayed.I should note however that toggling operators is not so trivial. Each operator is a node, so you would need to connect it's inputs to it's outputs. Easy enough to implement, but in cases where an operator has multiple inputs and multiple outputs, you might make things messier than before. So consider hiding the operator name but leaving an empty node to preserve the overall shape of the dataflow.
@mribeirodantas Should be a good issue for you when you have time.
The text was updated successfully, but these errors were encountered: