This release serves to document the re-addition of LaserTRAM-profiler to the dashboard now using the `lasertram` API. It previously had been relatively dead in the water and not functioning, however to maintain backwards compatibility with old laser-quad data outputs as well as improve flexibility of dealing with different experiment types, it has been added back in. Similar to LaserTRAM spot, it uses `lasertram` under the hood so the inputs and outputs for both are identical and seamlessly integrate into LaserCalc.
To reduce the computational load on storing data in the browser, it is recommended to process only a few or one line of spots at a time in LaserTRAM-profiler, then strap their outputs together to be used in LaserCalc.
**Full Changelog**: https://github.com/jlubbersgeo/laserTRAM-DB/compare/2.0.0...v2.1.0