Archive for the ‘Data Handling’ Category
Monster Panel V
8
History requires a chart, right? Wrong. In Part I, recall from the requirements that we want : — A chart, showing the history of 1-4 channels. The history can be the last 30 seconds, or the last 30 hours, or various lengths in
Needle in the Haystack
Finding the best answer is not always straightforward. Scientists are not programmers. Repeat that after me: scientists are not programmers. It’s not their fault; it’s just a lack of proper training. If you are implementing some algorithm given you by a scientist, it’s important to
Beware Simplicity
Simpler ≠ faster : you still have to know what happens “under the hood”. If you read the post about en masse operations, you might remember that I pointed out that you should know what is happening behind the scenes. Here is a particular case
Operations en Masse
The things that I used to do… En masse is a French term meaning “as a whole” or “all together”; treating a group of something as a single unit. LabVIEW has the ability to treat arrays this way, which can greatly reduce your workload.
Delays, delays, delays
Can’t you signals just work together? Usually, in a data acquisition program, all the signals you measure are “live”, meaning they represent the current conditions at the time they are sampled. However, in some cases you might have some signals which are not live, but
Hybrid Data Files
Combine BINARY and DATALOG files for the best of both worlds. In LabVIEW, there are three kinds of files: TEXT files. Ordinary text, stored in human-readable form, with spaces and line feeds, etc. BINARY files. Raw information stored as machine-readable information. A 32-bit integer is
Contact Info
207-593-8109
Culverson Software
184 Lakeview Drive
Rockland, ME 04841
General questions:
Accounts/billing questions:
