Graph ideas

[kaitj]

This is great - I've included the example that was generated from the workflow I've been working on.

graph TD
  dwi2response
  dwi2fod
  mtnormalise
  tckgen
  tcksift2
  dwi2response --> dwi2fod
  dwi2response --> dwi2fod
  dwi2fod --> mtnormalise
  dwi2fod --> mtnormalise
  mtnormalise --> tckgen
  tckgen --> tcksift2
  mtnormalise --> tcksift2

It shows basic connectivity of interfaces. At a glance, it is unclear why certain interfaces have multiple connections. A few (simpler) ideas to extend the GraphRunner:

1. Offering different levels of the graph output:
   a. "simple" - just how the interfaces are connected (e.g. 1 connection between each interface).
   b. "detailed" - include file names with each connected
   c. Something in between?
2. Inclusion of tool names (e.g. mrtrix, afni, etc.)

I'll try to add to this as I think of more.

[ReinderVosDeWael]

FYI Github can render mermaid:

graph TD
  subgraph mrtrix
    mtnormalise
    tckgen 
  end

   subgraph pretend_these_are_not_mrtrix
     dwi2response
    dwi2fod
    tcksift2
  end

  dwi2response --> dwi2fod
  dwi2response --> dwi2fod
  dwi2fod --> mtnormalise
  dwi2fod --> mtnormalise
  mtnormalise --> tckgen
  tckgen --> tcksift2
  mtnormalise --> tcksift2

Loading

[nx10]

Maybe also options to add profiler stats like execution time, memory usage, etc. I.e. everything that we could be interested in seeing on a graph

[nx10]

Also there are probably 2 different graphs we would be interested in:

• How programs depend on each other (like above)
• How files depend on each other (i.e. what files are used to create what other files)