←back to thread

896 points tux3 | 6 comments | | HN request time: 1.061s | source | bottom
1. russdill ◴[] No.43546583[source]
Anyone who did undergrad lab work around 2000ish might throw in some comment about lab view software and the number of times it crashes and loses all your data
replies(3): >>43547595 #>>43548534 #>>43550235 #
2. ◴[] No.43547595[source]
3. ptsneves ◴[] No.43548534[source]
2000s? My university's wind tunnel instrumentation was mostly LabView.
replies(1): >>43551401 #
4. wholinator2 ◴[] No.43550235[source]
Lmao my entire undergraduate physics program is still entirely labview instruments.
5. russdill ◴[] No.43551401[source]
It's been around a very long time and continues to be relevant. It's just a window in time where it was feasible to have a graphical application made on labview to be accessible to undergrads crossing over with such a thing being quite unstable.
replies(1): >>43556430 #
6. immibis ◴[] No.43556430{3}[source]
I once wrote A* in LabVIEW for a robot.

It was a competition sponsored by National Instruments, so the code was supposed to be in LabVIEW. Another person wanted to write it as a C plugin, but I thought that was cheating.

There's A* built into LabVIEW, but it's for completely generic graphs so it takes a lot longer to run. The rewrite brought it from about 10 seconds to compute a path, down to about 0.5 seconds.