GitLab sent out an email today (as I’m writing) about best practices for source code control for collaboration.
GitLab’s five best practices are:
Engineering data that is properly collected will help you make better decisions in the design, integration, and testing stages of your system. Timing and synchronization are a very important aspect of collecting valuable data. Some of these strategies are general purpose, but others and specific to NI DAQmx.
What it is
A regular expression is a sequence of symbols and characters expressing a string or pattern to be searched for within a longer piece of text. It is a strict search code that must find an exact match according to the regular expression used. You can search for words, numbers or symbols. They can be specific words or numbers, or any given word or number. The concept is used in most coding languages and has many uses.
Whether you’re new to LabVIEW or have been around the block the topic of VI reentrancy is an important one especially when dealing with stateful VI’s. In this post we’re going to briefly define the different reentrancy settings and then talk about the dangers of stateful VI’s who have the wrong reentrancy settings or are used in the wrong context. We define a stateful VI as one that stores data within itself from one call to the next. This is done in LabVIEW using shift registers and feedback nodes.
Once upon a time there was a quack named <your name>. Everyday <your name> arrived to work to solve complicated technical problems with their mighty intellect and LabVIEW development skills. These skills, wielded like a sharp sword helped <your name> slay even the toughest of challenging problems. One day, <your name> faced a looming dreadline that threatened impending doom if <your name> could not dispatch of it quickly enough.
Our team is using BitBucket for source code control and the SourceTree app for Windows to interface with our repositories. We've had a couple of small hurdles getting SourceTree to integrate with the LabVIEW diff tool, but here's a solution that's worked for us. (Credit to Paul Lotz on Atlassian's forum, https://community.atlassian.com/t5/Questions/SourceTree-external-diff-path-issue-on-Windows/qaq-p/394740)
As I program in LabVIEW I am surprised by the number of times small bits of code cause large problems. For example, I was working with a large system that communicated with many instruments. I made some changes, tried running the code, and the program locked up! My gut reaction was to blame the LabVIEW development environment or a driver, but in the end I discovered the code I changed caused the hang.