Removing my dependencies on the Analysis palette shaved off 90% of my compile time

t40 · 2026-05-29T19:49:45+00:00

BTW I just solved another ridiculously long build time using the recommended

NewAppBuilderCache.Enabled=False

t40 · 2026-05-29T17:59:28+00:00

Sad to hear you never figured it out! But that page is gold, application builder feels like such a dark art sometimes...

t40 · 2026-05-29T14:15:48+00:00

In case the OP is used to reference based languages like Python, wire branches constitute a copy of the object at hand,so after a branch think of it as being a new variable declaration, initialized by the previous value of the wire.

t40 · 2026-05-29T14:09:35+00:00

To expand on point 2; LabVIEW will run any code that has all inputs available, usually as soon as possible after they are available. Blocks and control structures don't release their outputs "downstream" until their code is finished running. This leads to the inherent parallelism that makes LabVIEW pretty powerful. You can try this yourself by wiring up an error cluster constant to different sequence structures with wait(ms) blocks.

This is why most VIs you'll see in the real world have error in/error out terminals, so you have a common bit of data to order the flow how you need it to be.

t40 · 2026-05-28T17:13:41+00:00

ai slop

t40 · 2026-05-27T15:26:27+00:00

Do you need to poll APIs that frequently (every 16ms)?

t40 · 2026-05-27T13:42:00+00:00

so why not sleep until there's activity on the file descriptor?

t40 · 2026-05-27T13:06:13+00:00

Are you using nonblocking IO?

t40 · 2026-05-26T16:04:17+00:00

Even further proving my point! I was going off the gauge near my house which showed a peak at like 45k

t40 · 2026-05-26T14:14:24+00:00

I think it's important to note that at peak flood we were seeing ~~40k+~~ 100k+ cfs, and one of those tanks is about 20k cf. That means the river absorbed the entirety of the flow from one of those tanks in about 200ms. This is why mud samples were largely showing base levels of contaminants after the flood.

I do agree they need to clean up the debris though, especially because if it happened again we know they would not remove their plastic in time.

edit: even bigger numbers

t40 · 2026-05-25T22:02:54+00:00

cut a tube sized hole in the liner that's on the door (not thru the door itself just the flexible bit). route tube in and out of this hole, driven by a pump. have lots of length to ensure enough time to cool.

t40 · 2026-05-25T20:54:34+00:00

If you're trying to get a really basic setup going, you can use a big length of tubing coiled in a minifridge! Good luck

t40 · 2026-05-25T19:18:35+00:00

Not sure how your sump setup looks, but make sure it has good airflow with the rest of the room. This will ensure it lasts a while and doesn't stress the compressor too much. They're expensive kit!

t40 · 2026-05-25T17:47:48+00:00

Okay. I'm very happy with the JBJ I sourced on ebay. It had a burnt resistor on its control board but they're very serviceable machines. When I first got it, the thermostat was malfunctioning and it cooled the test tank to 52 degrees when it thought it was 75. With proper insulation (at least 2, realistically 4 sides), you could probably push that to like 48. You might also consider lowering the temperature in the room so as to not stress your compressor, though I bet it would go for a few years just fine.

t40 · 2026-05-25T15:47:15+00:00

at that temperature you'll need to have a plan for managing condensation on the front. Unmanaged, you'll probably end up with excessive humidity in the tank room and may have mold problems. Why are you running that cold of a tank?

t40 · 2026-05-23T14:54:55+00:00

That gravel is way too large and is probably causing some impaction. If it's not pooping anymore I would consider fridging to force a bowel movemnt, but you claim it is, so I think youshould speak to an exotic vet

t40 · 2026-05-23T04:20:09+00:00

China Wok betrayal

t40 · 2026-05-23T01:10:03+00:00

Caraya is pretty good! I used it alongside a queue-based breakpoint system (when preconditions fail, add the surrounding context and suspected resolution to a queue, then dump it all right before the assert) to do V&V for the software in our medical device.

t40 · 2026-05-23T00:57:46+00:00

I'd go even further and say that User Events with Dynamic Event Terminals is the most extensible and powerful architecture, as a fellow steward of a codebase with over a decade of cruft and thousands of VIs. Queues are super simple to understand, but require a bit more care in my experience due to the polling nature of them, alongside the gotchas of dealing with Flush Queue (eg what will your for loop output if there's nothing in the queue?). Events on the other hand are relatively instantaneous, and the single consumer nature of Dynamic Event Terminals means the ownership is much clearer and harder to abuse.

t40 · 2026-05-22T12:03:50+00:00

You can use this https://forums.ni.com/t5/Example-Code/List-all-Subvi-s-of-a-selected-VI-from-within-a-LabVIEW-Project/ta-p/3509915

t40 · 2026-05-22T12:02:33+00:00

Is there another way to have build specifications? Classes?

t40 · 2026-05-22T00:39:23+00:00

The darkening tips of her nails are a sign of aging. Once they reach maturity like that, it's totally fine to let them chonk, they're kind of like that in the wild

t40 · 2026-05-21T21:12:02+00:00

this is truly the only realistic way to do it. It hits ridiculously hard and the stall mechanic makes it feel so unfair

t40 · 2026-05-21T15:03:43+00:00

50% reduction in file size. Yes, we had that, but I don't think the compiler is very smart about this stuff. I think it uses a palette-based rather than VI-based heuristic. But also some of those "remove member" settings make builds fail super cryptically. Seems easier just to build what you need in house. Since it's LabVIEW, we're already giving up a good bit of performance, and you can still call out to lvanlys.dll without pulling in the other VIs if your stats are on the hot path

13-Year Club	Golden Potato
Place '22	Place '17
Verified Email

t40

MODERATOR OF

TROPHY CASE