LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

VI Scripting pseudo-code

Hello there.

I was thinking of making a text based scripting library that can be accessed via Python with the task to compile a LabVIEW vi to a kind of pseudo-code text based scripting language.
The first proof of concept would then be to generate an identical copy of that VI from that pseudo code in a python environment.
Not by using the copy function, but by re-building it from scratch using the pseudo-code script.
Additional I would like to explore how AI tools can work on that code (a text based language) to  adapt the diagram, where the object locations in the diagram, and wire routing, location, proportions etc, define programming style context.
That style context is the most interesting part, it's the connection between the strict code functionality and the personalized human perception model.

It is a thought experiment to allow the community to play around and experiment with AI potential where the graphical environment is not a disadvantage for AI but delivers an advantage.
(beside the Nigel initiatives of NI itself, which cannot use the full community potential)

Although the programming style doesn't seem to have functional benefits, it could bring AI generated code closer to the human by respecting the human style that makes use of the graphical presentation style to improve clarity depending on the developer's preference.
Representing the programming style into pseudo-code could then be a topic open to the community that could open up a world of innovation that is not possible in other text-based programming languages.

And who knows, this might open up a new added-value of using LabVIEW above text-based languages. After all: Wouldn't it be crazy to leave the graphical programming concept just because the current baby-AI's are not grown up yet?

(I hope I don't cross any propriarity boundries with this concept)

0 Kudos
Message 1 of 6
(310 Views)

I can't imagine anyone actually wanting to do that.

0 Kudos
Message 2 of 6
(234 Views)

Never too late for a surprise 🙂
I did some tests today in an attempt to retrieve all VI attributes generally with a script. There I stumbled on a few difficulties. First is to get Array types decoded readible from a variant without knowing the exact type at start. Another small issue is that some properties crash LabVIEW when called, no error nothing. This means that automating the saving of all available properties is no option (without workarounds).

Anyway, I can't imagine that here are no initiatives yet of developers wanting to play around with AI driven scripting from a platform of choice..

What brought me there is that I use scripting to make code from templates for our testing platform. Making those LV based scripting tools takes quite some time. I'm searching for a way speed up those initiatives.

0 Kudos
Message 3 of 6
(184 Views)

Which VI properties crash LabVIEW?

0 Kudos
Message 4 of 6
(164 Views)
0 Kudos
Message 5 of 6
(161 Views)

@Andre_FR wrote:


Anyway, I can't imagine that here are no initiatives yet of developers wanting to play around with AI driven scripting from a platform of choice..


There are. You can see this, for example, although it seems to have been removed at the request of NI. I would guess that was because it was using stuff they don't want out there (maybe because it's dangerous, or because they don't want people doing things parallel to their own AI service).


___________________
Try to take over the world!
0 Kudos
Message 6 of 6
(61 Views)