Jump to content

X___

Members
  • Posts

    307
  • Joined

  • Last visited

  • Days Won

    20

X___ last won the day on April 29

X___ had the most liked content!

2 Followers

Profile Information

  • Gender
    Not Telling

LabVIEW Information

  • Version
    LabVIEW 2021
  • Since
    1995

Recent Profile Visitors

4,225 profile views

X___'s Achievements

Enthusiast

Enthusiast (6/14)

  • Conversation Starter Rare
  • Reacting Well Rare
  • First Post Rare
  • Collaborator Rare
  • Dedicated Rare

Recent Badges

69

Reputation

  1. The relative difference between the two appears to decrease with the size of the array, suggesting this is an initialization step (sanity checks) issue. On my machine: N | no String Conversion | with String Conversion | -------------------------------------------------------------- 10 | 750 ns | 400 ns | 100 | 700 ns | 1000 ns | 1000 | 5600 ns | 5100 ns | So approximately 300 ns more for the no String Conversion case, which becomes a negligible difference for large array. I would argue that large arrays are more common in this type of conversion tasks, but this is interesting to know regardless. I would also argue that there are vastly more irritating oldies in the LabVIEW code base that would deserve attention, but we know how that flies in Austin.
  2. I would find this related post kinda funny: https://forums.ni.com/t5/LabVIEW/how-to-associate-a-license-with-my-NI-account/td-p/4256133 if a colleague of mine had not reported the exact same problem of a suddenly expiring permanent license (for the 2021 Vision Development runtime). The response she got was "they are refusing to reactivate it or even explain why it was deactivated in the first place". It looks like a class action lawsuit in the making. Any lawyers reading this?
  3. 13 years later, this is still not documented in LabVIEW. And since in the meantime the Matlab node has also changed, you now need to reate a little "ClearAll.m" Matlab helper script that contains: function ClearAll() clear functions end and call it before your node of interest when developing...
  4. It took me a handful of calls before I found one person who was willing to take up the case. It's been such a long time since I got some really helpful support from NI that I am starting to believe in a miracle (I forgot to mention that I was provided temporary activation codes for the different computers and software packages I needed to work. Those expire in a couple of weeks, so I may end up with a complete meltdown again). If that guys quits on me or is fired, I am afraid I am running out of options. I guess what saves NI from having my university on their neck is that no-one is pretty much using LabVIEW anymore? Meanwhile NI is offering $100 for 1-on-1 Teams calls for users to help them improve their docs and publishes a roadmap with two columns: soon and later. The ambition is bursting at the seams...
  5. Update on "disappearing" permanent license. Well, there is at least one helpful person at NI, and I was lucky enough to find him... Long story short (this has been going on since my last post on the topic, more than 2 weeks ago) NI screwed up internally (or, a possibility that was cautiously hinted at, the licensing code is buggy) and voided our permanent license. After (presumably) some testing, they haven't been able to fix the problem and offered me to: 1) exceptionally issue a new permanent license number that will replace our voided one. 2) escalate the issue to the R & D team to figure it out (the hint I was referring to). I chose 1 after having strongly suggested they go for 2) anyway, as I (we) can't be the only one affected. It also turned out that they screwed up our license renewal (i.e. the migration to an annual academic subscription license) and gave our Department a quote for a one month (!) license, soon to expire. I don't really care about that one, as I have no intention to upgrade, but just sayin'... There is truly something rotten in the State of Denmark.
  6. You have two very similar threads on this forum, which makes it difficult to have a linear discussion: https://lavag.org/topic/22489-let%E2%80%99s-make-deep-learning-easy-with-haibal-library-on-labview/#comment-142891 We all agree that graphical programming has tons of advantages over pages of text code. However, most of us hate to be arm-twisted in having to pay annually for new versions of a language that fixes bug at a snail pace (if ever), release features that take 2 to 3 versions to work as advertised, and is offering abysmal level of technical support (and the list of recriminations could go on and on). Your toolkit looks truly amazing, but I would argue that you are not alone in having invested massive amount of time and effort in G-code. Yet, some of us who have, have come to the conclusion that we cannot reasonably tie our work to NI's whim and suicidal plans for LabVIEW. I have decided to migrate as fast as I can to Python. I'd argue that someone who is willing to do so (migrate to Python) will find the resources to master the basics of DL in Python, not mentioning that you'll have to keep running to stay on top of the new developments in the field with your toolkit. How you can hope to do that for free is a mystery to me. As I said, admirable, but a tad idealistic... Sorry for being he bearer of bad news, but "un homme averti en vaut deux", as the French say.
  7. To tell you the truth, right now I am feeling owned for not being able to open LabVIEW 2021 SP1 after having installed it in December 2021 under a "permanent" Academic License (idem for the Vision Development Module). I am being told there never was such a thing as a permanent academic license. Oh yeah? So why can I open my LabVIEW 2019 SP1 and LabVIEW 2018 SP1 versions installed with the same license number on the same machine? I forgot to say that another NI employee I was talking with today (I talked with three, not including the Newark guy) told me that this was impossible because an academic license was only supposed to allow using the latest version of LabVIEW. Needless to say, she had nothing to answer to my explaining what I just said in the previous sentence (that is that I was running TWO old versions simultaneously). So far, I haven't talked to a single NI employee who seemed to really know what they were talking about. It's absolutely all downhill and I have absolutely zero trust in this company. Stock is doing great though, so the smokescreen and psychedelics are doing wonders.
  8. BTW, if someone still believe that a debug and deployment license will allow them to develop software, they need to wake up or prove that this is the case. According to the NI home employees (and beyond, see below) I talked to, that is not the case. For LabVIEW, for Vision Development Module, etc. True, these are PERMANENT licenses, but you can't do much with them. The funny part is that a guy from Newark (the company that distributed NI product, to which NI sales transferred me to get additional information - this gets better by the hour) tried to explained to me that with a debug and deployment license, you cannot develop new code, but you can debug and fix a released executable (exe file). I asked him how that would work and then thanked him very much. đŸ˜­
  9. I wished I could be as excited as this deserves, but with the abysmal transformation of NI in a money machine making it impossible to get support for something as simple re-activating a permanent license, I am on my way to Python...
  10. As part of their 100-year of "Engineer Ambitiously" TM "at your speed", NI has in fact implemented a very clever strategy to motivate people from migrating away from their products: make permanent license re-activatable every year and make the reactivation process completely opaque or downright impossible. The idea is that after a few frustrating phone calls ending in the connecting ending in prolonged silence after an attempted "transfer" with tech support, you are supposed to give up and write off 25+ years of code development using a desperately closed and outdated language to finally embrace the open source Now tech support is working from home, so they are probably free to decide that they won't pick up calls, or maybe the call routing system at NI is hopelessly rotten (dropped calls appear to be systematic), but this problems would not exist in the first place if permanent licenses were really what their name indicate. This is not just me saying that: https://lavag.org/topic/22538-labview-activation-issues/ I am not in a mood or position to file a lawsuit, but this is erring on the side of commercial deception...
  11. I thought that was the first... at least according to popular secular tradition: link I guess this is the old question of which one came first of the hen and the egg...
  12. Actually the original is quite possibly funnier: Oh, and there is a second version of it: and even a Wikipedia page with very interesting background information: https://en.wikipedia.org/wiki/Turbo_encabulator
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.