LabVIEW
CLA code snippet review
I'm finding I don't have quite enough time to finish the CLA practice test. However, I think I set up a good framework and have plenty of examples for API communications.
With that said, do you think I will get away with what I have pictured? Throwdown a blank VI with tags, put the blank VI in the correct location architecturally.
@UnholyPenguin wrote:
I'm finding I don't have quite enough time to finish the CLA practice test. However, I think I set up a good framework and have plenty of examples for API communications.
With that said, do you think I will get away with what I have pictured? Throwdown a blank VI with tags, put the blank VI in the correct location architecturally.
If I'm not mistaken, the CLA test doesn't need to contain working code; the emphasis is on having a sound architecture. Personally I'd include terminate.vi in the dataflow to avoid race conditions. It may not matter if it executes before or after the case structure with your current code, but if someone modifies something so it does matter, you may have issues that are so subtle that it will take some intensive t-shooting to figure out because sometimes it will work and sometimes it won't. This code is fairly fragile because of that.
@billko wrote:
@UnholyPenguin wrote:
I'm finding I don't have quite enough time to finish the CLA practice test. However, I think I set up a good framework and have plenty of examples for API communications.
With that said, do you think I will get away with what I have pictured? Throwdown a blank VI with tags, put the blank VI in the correct location architecturally.
If I'm not mistaken, the CLA test doesn't need to contain working code; the emphasis is on having a sound architecture. Personally I'd include terminate.vi in the dataflow to avoid race conditions. It may not matter if it executes before or after the case structure with your current code, but if someone modifies something so it does matter, you may have issues that are so subtle that it will take some intensive t-shooting to figure out because sometimes it will work and sometimes it won't. This code is fairly fragile because of that.
Yes good point, I should have made the flow clear, and probably just pulled everything in that case down into that VI. Full panic mode lol
