Skip to content
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

Flow-chart UI for VI orchestration #150

Open
linzuzeng opened this issue Jun 23, 2020 · 5 comments
Open

Flow-chart UI for VI orchestration #150

linzuzeng opened this issue Jun 23, 2020 · 5 comments
Labels
GUI Features related to the GUI

Comments

@linzuzeng
Copy link
Member

linzuzeng commented Jun 23, 2020

Maybe we can try node red as VI orchestration UI.
Each VI can be represented as a node in the graph, and the numbers of input channels and output channels can be simply shown as connectors for each VI.

https://nodered.org/
and here is an example
https://www.pjrc.com/teensy/gui/index.html

I found a library for making LabVIEW-like flow charts. Maybe we can consider using it for wiring VIs up, and use the named connectors instead of the globally assigned channel numbers. I put the link in the issues.

But I think we should try it after publishing the paper or find someone who is familiar with JavaScript and GUI development

@gyger
Copy link
Contributor

gyger commented Jun 28, 2020

While I do like the flow, I am against putting Node into the package. It becomes too complicated and bloated. Said that there does not exist a software like this for python or a web-module that can be easily implemented.

@linzuzeng
Copy link
Member Author

No we don't need Node. We only need thier frontend library.

@linzuzeng
Copy link
Member Author

The channel number in ETA was designed as an analogy of the channel number in a real timetagger device. Initially we thought it is nice to give real channels in lower numbers from 0, and leave non-exisiting higher numbers for virtual channels.

However, if we go the LabVIEW-way eventually, we don't need such channel number to connect different VIs together.
We can use diagram with wires instead, and in the state diagram of each VI we only need to refer to the connector name.

The only drawback of the graphical wiring ui is that, it makes * ("catch all") looks like a mess. You will need to connect every channels from time tagged to every VIs, basically. With "catch all" you only need to type one symbol

@gyger
Copy link
Contributor

gyger commented Jun 28, 2020

Ah ok, yeah in that sense splitting of the frontend of their code seems to be an interesting way to go. (I am still dreaming about lab orchestration in the the future, so their such a library would become very handy.

@gyger gyger added the enhancement New feature or request label Jul 7, 2020
@linzuzeng
Copy link
Member Author

https://reactflow.dev/ Seems to be the new cool thing.

Maybe we could use their https://www.npmjs.com/package/react-flow-renderer as an alternative to our existing table-based main GUI.

@linzuzeng linzuzeng changed the title Use node red as VI orchestration UI Flow-chart orchestration UI May 6, 2022
@linzuzeng linzuzeng added GUI Features related to the GUI and removed enhancement New feature or request labels May 6, 2022
@linzuzeng linzuzeng changed the title Flow-chart orchestration UI Flow-chart UI for VI orchestration May 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
GUI Features related to the GUI
Projects
None yet
Development

No branches or pull requests

2 participants