[ENH]: SVG writing module to visualise the YAML pipeline #315

New issue

Open

opened 2024-03-27 10:32:44 +00:00 by LeSasse · 1 comment

LeSasse commented

2024-03-27 10:32:44 +00:00

(Migrated from github.com)

Are you requiring a new dataset or marker?

I understand this is not a marker or dataset request

Which feature do you want to include?

I have prototyped a little command line tool to visualise junifer pipelines from the YAML specification as an SVG file. As discussed with @fraimondo we can make this part of junifer if the consensus is that this is desirable.

The tool uses as dependencies:

https://svgwrite.readthedocs.io/en/latest/ which is NOT active
https://pygments.org/ for syntax highlighting

These dependencies and therefore the svg tool can probably best be made optional.

In addition, where and how should it be implemented in junifer and what should the UI look like (i.e. as an additional command etc.)?

How do you imagine this integrated in junifer?

perhaps as an additional command

Do you have a sample code that implements this outside of junifer?

see https://github.com/LeSasse/junigraph

Anything else to say?

No response

### Are you requiring a new dataset or marker? - [X] I understand this is not a marker or dataset request ### Which feature do you want to include? I have prototyped a little command line tool to visualise junifer pipelines from the YAML specification as an SVG file. As discussed with @fraimondo we can make this part of junifer if the consensus is that this is desirable. The tool uses as dependencies: * https://svgwrite.readthedocs.io/en/latest/ which is NOT active * https://pygments.org/ for syntax highlighting These dependencies and therefore the svg tool can probably best be made optional. In addition, where and how should it be implemented in junifer and what should the UI look like (i.e. as an additional command etc.)? ### How do you imagine this integrated in junifer? perhaps as an additional command ### Do you have a sample code that implements this outside of junifer? ```shell see https://github.com/LeSasse/junigraph ``` ### Anything else to say? _No response_

LeSasse commented

2024-03-27 10:40:57 +00:00

(Migrated from github.com)

As an alternative approach that I personally prefer, I would propose to simply curate a list of external junifer-related tools in the documentation. The advantage would be less maintenance-overhead for junifer direct, for tools that aren't really necessary to junifer's core functionality but are "nice to have".