X___

No comments and couldn't care less whether it is fixed or not.

https://www.fool.com/investing/2023/03/10/who-will-win-the-bidding-war-for-national-instrume/

https://finance.yahoo.com/news/ni-acquires-set-gmbh-accelerate-140000459.html

I am not the one confused by this post, but I have to wonder: with a 17 MB BD and a code complexity of 18.1, maybe considering breaking stuff into subVIs and refactoring is in order? In my case, this tool was helpful in setting priorities: https://www.abcdef.biz/pi_free.htm

I only meant that 2023 Q1 is the first version to officially support Windows 11 and that apparently, the head count in the LabVIEW R&D team is either classified or not to be admitted in public.

There is no need for gut feeling: the simple fact that they are not even trying to hype the future of LabVIEW is speaking volume. We implicitly learn that the LabVIEW team has been gutted or at least not given the means it needs to even keep in sync with OSes (https://www.ni.com/en-us/support/documentation/supplemental/22/ni-product-compatibility-for-microsoft-windows-11-.html). Heck, TestStand and VeriStand themselves, of which I know nothing but understand are where NI is investing its resources, are not Windows 11 ready. As for the rest, I guess you can check the release notes for 2023 Q1 (https://www.ni.com/pdf/manuals/labview-2023-q1-and-drivers.html#examples) to understand that the T's are not even crossed anymore, since the examples for this version are apparently to be found in the \LabVIEW 2022\examples directory... I am not sure it is fun to work at SpaceX, but I doubt there is much feeling of exhilaration at LabVIEW R&D nowadays...

And the saga continues... https://www.reuters.com/markets/deals/national-instruments-picks-fortive-keysight-challengers-emersons-bid-sources-2023-03-03/

Seriously: it's over (it actually starts at 54 mins in).

My bad, it does not scramble elements 😞 Busy on the side dealing with a lab flood doesn't help with focus...

Well, you are sorting the array before removing the elements to filter. If I don't care about the array order, I can use a set, which should to things quicker by design.

This is messing up with the elements order in the original array though

What are your respective experiences with Python and LabVIEW? It seems that you are more proficient in the former than in the latter. If so, looking at built-in examples might help (Help>>FInd Examples). Answer 1: the way the Python node is designed requires a function to call in your script. You can have several functions in a script, but you would have to call the Python node repeatedly, one function call at a time, or those functions would have to call each other within the script. Not that this is what you are asking for, but that might clarify the node's intent. Your first snapshot doesn't show any node output. If you want to get something back into LabVIEW, that is missing. If I understand what you are trying to do, you would want your Python function to return something like an array containing your image. Answer 2: the easiest way would be to use a Picture control to display the image array returned by the Python node. More expensive (the toolkit is not free) would be to use the Vision Development Module, which in addition to a more advanced control, would offer a number of utilities to manipulate the image. HTH

Some of the earlier patents (still listed in Help>>Patents...) have long expired. The latest is dated 2014.

I was puzzled by that statement and since I am unable to do anything more demanding at this time, I checked the job offers at NI. There are 4 sites: Texas, Costa-Rica, Hungary, Malaysia. Most of the software-related postings appear to be API and driver related. I would be surprised that any of the frontend software is developed outside a tight-knit group in Austin (especially because NI is not an open source software developer, where delocalization is the rule).

Simple: to be understood by and be able to share code with others in academia. I have a few options: python, MATLAB, Mathematica, possibly C/C++ but certainly not LabVIEW. I dabble in all other languages, but in terms of cost and adoption, the choice is easy. I understand that for automation and delivering slick UI to paying customers it might not cut it, but if Emerson drops it, everyone will have to reconsider their options. As far as I am concerned, the writing has been on the wall a long time ago as far as LabVIEW was concerned. What saddens me the most is that its graphical paradigm hasn't percolated (much) in other languages (Node-Red and some other experiments being rare and not-so-impressive exceptions).

I don't know about that. For me multithreading works when all my cores usage are maxed out. I see that in both LabVIEW code and Python code.

I wonder whether Emerson knows that, and if so, what their logical conclusion will be moving forward. I mean, I have no doubt what they will decide.

My bad, I did not fully fleshed my proposal to Jeff K. I did not mean to rewrite LabVIEW in Python, but import some of the graphical concepts of LabVIEW into Python. Here is it: develop a Python module that allows representing python code graphically. The execution parallelism implemented in LabVIEW would probably be the trickiest part, but I am not sure I would require it initially. And implement some type and syntax checking breaking the "diagrams" at edit time rather than at compile/runtime (typos is what I hate in text-based languages).

You mean that sentence: I am not sure he means LabVIEW when he thinks "new technologies". After all that is more the purview of Colonel Kodosky... Who probably wouldn't mind a few extra 100 million dollars for... what about spinning off G and funding an open source project making a graphical Python-based LabVIEW?

That's maybe because, according to Reuters (https://www.reuters.com/markets/deals/emerson-makes-76-bln-bid-ni-corp-2023-01-17/), (company with a green and blue-themed website too...). So, their interest is probably not in supporting the development of a niche software that once pretended to be the programming language to run them all (or did it?) but is certainly not anymore. A lot of people at NI should probably get busy updating their profiles and checking job offers, if they had not been thinking of it after AQ's departure... BTW, I don't quite understand your previous argument that cofounders having a majority of shares would oppose a sale? Why would they not try to get as much money out of the sale and leave their families/heirs with a comfortable fortune to spend the rest of their lives?

I see...nothing. In any case, they already have taken Ni's color(s). Or is it the opposite? And as far as their slogan: "Go Boldly", this will be easy to merge with NI's: "Go boldly and engineer ambitiously... for twice the price!".

What software does Emerson have?

If I had wanted to be ironical, I would have typed LabVIEW 2023 Q5. And twitted it!

They are trying their best to snap NI at a bargain price, knowing full well that the picture will completely change when LabVIEW 2023 Q4 will be released, instantly doubling the value of NI share price.

https://finance.yahoo.com/news/ni-appoints-cfo-140000382.html