Hyperspectral Browser

A browser for hyperspectral datasets.

The data must be saved as a 3D wave, with x and y representing spatial coordinates and waveform spectroscopic or time-series data stored in the z dimension. The browser provides a user interface to efficiently view spectra at different pixel locations or to average spectra over a region of interest.

To generate a dataset for testing, execute hyperspec#demo() from the commandline.

Note that the color scale for line profile maps is autoscaled to the visible data range, and does not correspond to the values shown on the scale bar for the map view of one plane. To resize the graph subwindows, place the mouse cursor between the plots; when the cursor switches to a double-headed arrow,  click-and-drag to resize.

Related project: For fitting baselines to large collections of spectra, the fast fitting project provides a user interface for setting up multithreaded baseline fitting.

Project Details

Current Project Release

Hyperspec IGOR.8.00.x-1.40

Release File: Hyperspec140_0.zip (41.82 KB)
Version: IGOR.8.00.x-1.40
Version Date:
Version Major: 1
Version Patch Level: 40
OS Compatibility: Windows Mac-Intel
Release Notes:

Adds more path profiling options, restores Igor 8 compatibility

View All Releases

OK. This looks so cool that I want to run out and collect hyperspectra just to use it!!!

As you may have surmised, my three recent project releases were motivated by working with infrared hyperspectra generated by a focal plane array detector. I hope though that parts of this work will be more generally useful for Igor Pro users who work with spatially-resolved spectroscopic data. In version 1.01 I've added a demo function for testing the interface: execute hyperspec#demo() from the command line to generate some fake data.

That looks very nice. I wish this project had been around when I was still working with hyperspectral data. The selection of regions is very elegant.

Perhaps it would also be good if the exported spectra could retain the original wave and range as a note. Otherwise there is a risk that this might be forgotten.

And is there a reason why the exported wave is Single Float 32 bit (and not Double Float 64 bit)? Information may be lost here.

These issues are addressed in version 1.03. The precision of exported waves is now the same as that of the input data. When an output wave represents a pixel selected with the crosshair cursor or a rectangular region selected with the marquee, the range is saved in the wave's note. If you select a collection of pixels, draw a ROI using the UI, or use drawing layer shapes to select a region of interest, the output wave's note contains the name of the input wave + 'masked region'.

If you downloaded this project prior to version 1.30 to test under Windows, I suggest trying version 1.30 or later, in which Windows compatibility is significantly improved.

Forum

Support

Gallery

Igor Pro 9

Learn More

Igor XOP Toolkit

Learn More

Igor NIDAQ Tools MX

Learn More