Native Instruments Firmware
Ottavia Delamar
Native Instruments recently released version 2.2 software for the MASCHINE family. This new version unlocks the touch sensitivity of the eight knobs beneath the hi-res displays on MASCHINE STUDIO, making the knobs respond instantly to touch, and opening context-sensitive menus, on the displays for faster browsing for sounds and instruments, intuitive routing, and accelerated workflow.
MASCHINE STUDIO requires a firmware update to enable support for this new v2.2 feature. A new dedicated application, Device Updater, maybe be downloaded from the NI site to handle this firmware update process.
Being music makers ourselves, we love geeking out on all things gear. From the tweakiest techniques to the biggest ideas, our experts work hard to constantly supply inSync with a steady stream of helpful, in-depth demos, reviews, how-tos, news, and interviews. With over 28,000 articles and counting, inSync is your FREE resource for breaking news, reviews, demos, interviews, and more.
Historically, instruments logged large amounts of data internally, encoded in proprietary binary formats, so special software to read files in those formats was required. With the advent of more storage in smaller packages, instrument developers have started to output the data in American Standard Code for Information Interchange (ASCII) files. The software we use has evolved over time to accommodate these changes. The section below follows the same order as the instrument description section.
Disclaimer
The following instrument-specific processing descriptions represent instruments and workflows that were in place from before the original version of this publication (2008) through version 2.0 (2016). Since then, the Coastal and Marine Hazards and Resources Program (CMHRP) has begun evolving these data-processing workflows and making them more consistent throughout the CMHRP. Presently this effort is in the transitional phase. Links to latest processing code and workflow descriptions can be found at the Oceanographic Time-Series Data Collection overview page.
Data from ADCPs are processed using the ADCP Toolbox, a collection of MATLAB routines written at the USGS Woods Hole Coastal and Marine Science Center (WHCMSC), described in Cot and others (2005). We compare data from the four beams in pairs for symmetry and check for high-intensity reflection indicative of fish or other beam obstructions. "Bad" values are masked both manually and automatically and, where possible, a three-beam solution is used to fill in gaps caused by one compromised beam. Averages replace short-duration spikes in the data, with pad values replacing bad data points to maintain timebase consistency. Profiles are trimmed at the surface (6 percent of depth) using software provided by the manufacturer. However, bins that are out of the water at low tide are retained during higher tides to retain the full tidal range. We remove data collected by the instrument before and after the deployment using the instrument's tilt and compass data to define when the tripod was stably settled on the ocean floor. Finally, we rotate the data to compensate for magnetic variation from true north at the site and convert from the beam coordinates recorded by the ADCP into earth coordinates. Processed versions of these data files are stored in EPIC-compliant netCDF files.
The WHCMSC commonly configures ADCPs to collect wave data simultaneously with current data. The software provided by manufacturer is used to split the raw file and compute the wave statistics and spectra. MATLAB programs written at WHSC are used subsequently to create EPIC-compliant netCDF files from the individual waves file. The waves processing software is described in Sullivan and others (2006).
The V is the new version of the ADCP, and it can output processed, calibrated data in ASCII or MATLAB .mat format, so a different form of processing and conversion software is currently under development. The manufacturer also provides processing software that is being evaluated as a replacement for our current (2016) processing method.
The software to read the raw burst files from the Vector and output the data in a form similar to ADV data is under development. Since the orientation sensors are in the housing, and because the head can be mounted in any orientation, the transformation from head x, y, z to Cartesian coordinates may not be possible simply by rotating. The principal component method is being evaluated as an alternate method of analysis.
Binary files logged by ADVs and PCADPs are processed using a series of MATLAB routines in the Hydratools toolbox developed at the USGS WHSC (Martini and others, 2007). The ADV and PCADP both employ burst sampling at high frequency to characterize the water flow, so these data types have one time series for each burst logged, and each file contains as many bursts as were logged during the deployment. Statistics, including mean and standard deviation, maxima, minima, and medians are computed on the bursts as part of the initial conversion from binary to EPIC-compliant netCDF and stored in a separate file.
In some ADVs, the instrument firmware from SonTek had a faulty Digital Signal Processing (DSP) chip that corrupted part, but not all, of the data from many bursts. Other sources of data degradation included fouling and flow obstacles such as seaweed and animals. To handle data flaws and retain as much viable data as possible, a system to vary the cutoff for minimum beam correlation and maximum standard deviation across each burst was developed to use with software for flagging bad sections. Small data gaps are interpolated over and larger sections of unusable data are replaced with pad values to maintain the timebase. Spikes in pressure and range to seabed data and obviously faulty records are replaced with the fill value. After questionable data records are treated, the raw velocities are rotated into east-north-up coordinates, and the mean and standard deviation statistics are recalculated and data are low-pass filtered. Separate files are written for raw burst data and for time series of the averaged statistics of the bursts. The mean current velocities in the statistics files are comparable to the current data from mechanical current meters.
The data are offloaded in several binary files. Processing software was developed and employed to read the instrument files and convert the raw data to east, north and up in EPIC-compliant netCDF files.
Software provided by Sea-Bird Electronics (SeaSoft) is used to validate the raw data and compute salinity from time series of temperature and conductivity measurements recorded by Sea-Bird sensors. Water density is ordinarily computed from the temperature, salinity, and pressure measurements. Transmissometers and fluorometers are commonly logged by the SeaCATs and MicroCATs, so other variables may be present. Data processed with SeaSoft are stored in ASCII files so the final step is conversion to EPIC-compliant netCDF using a program called asc2epic.
The data from these instruments are stored in column-delimited ASCII files in scientific units. Software to read the raw data and write EPIC-compliant netCDF output files was developed and is employed. Calibrations are applied internally. Custom programs to read the ASCII files and write EPIC-compliant netCDF were developed.
The SonTek Hydra datalogger converts raw OBS voltage measurements to counts with a 14-bit analog-digital converter. A linear conversion is used to convert counts back to volts so the data can be calibrated to sediment concentration using laboratory-derived calibration coefficients. After the point at which biological fouling significantly degrades the returns, data are replaced with the fill value. The OBS data are stored in the file with other data from the instrument that logged it (either an ADV or PCADP).
The data from these instruments are stored in column-delimited ASCII files in counts. Software to read the raw data, apply the calibrations for that sensor, convert to scientific units, and then write EPIC-compliant netCDF output files was developed and is employed.
The Sontek Hydra dataloggers also log transmissometer data in counts, so a linear conversion is necessary to convert counts to volts. The SeaCAT, however, logs the raw voltage, so no conversion is required. The transmissometer data can also be presented either as percent light transmission (from 0 to 100, where 0 indicates complete occlusion). Beam attenuation coefficients (units of m-1) were computed from the light transmission observations as -4(ln(T/100)), where T is percent light transmission over a beam length of 0.25 meters. The beam attenuation coefficient is linearly proportional to the concentration of suspended material in the water if the particles are of uniform size and composition (Moody and others, 1987). However, the size of the particles in the water changes with time, especially during resuspension events; therefore, the beam attenuation measurements must be interpreted with care. The processed data are usually stored in the file with other data from the logger to which the transmissometer was connected (MIDAS, ADV, PCADP, or SeaCAT).
Aquatec ABS raw data are logged in a set of binary files and processed with a MATLAB-based toolbox that truncates files to include in-water times only, flags questionable points, and transforms the data to netCDF format. The ABS data are not subject to the normal conversion to scientific units and quality-control procedures because calibration protocols are not yet in place. When in doubt, we prefer to preserve all samples rather than remove potentially useful data. These data are distributed as provisional.
LISST raw data are extracted from the logger and stored in the native format. Sequoia Scientific Inc., the manufacturer, supplies processing software. Calibration methods and additional software for working with the data and converting to netCDF are under development at WHCMSC; and until they are completed, the raw data may be distributed as provisional.
c80f0f1006