These file formats are used by Imagine Optic
|format / example||purpose||accessibility||remarks|
via WaveView, WaveTune, WaveKit
can be read by user without IO software, using e.g. Matlab
no modification possible without IO software
more information available in documentation of WaveView
stores raw data of wavefront sensor
.himg files are re-interpreted each time according to the cfg. file you provide. You can use the new cfg. file with the old data.
Attention: Tracking data when following changing tilts is currently not saved. In other words, the sensor must be well aligned, or the trimmer function (magic hat) must be used, or the sensor must have a gray pupil, or WaveKit must be used to correct any offset in tilt.
via WaveView, WaveTune, WaveKit
direct access only via SDK (HASO SDK or WaveKit)
|*.pmc||stores shape setting for a deformable mirror||read, write||text file|
|HASO 4000.dat||configuration file for HASO v3.0.x||no user access|
|HASO3_128_GE2_4000.dat||configuration file for WaveView / WaveSuite||no user access|
- In general it's good policy to save raw data in science. That can be done with our *.himg file format, which saves the actual CCD image. However, this is a bit rawer (and much more storage space-hungry) than necessary.
- For a wavefront sensor, saving the slopes is generally a good compromise, because this is still unfiltered data, but much smaller, and also the calibration of the sensor has already been applied to the data at this point. There are even parameters indicating measurements from a double pass. This makes measurement data easily comparable.
Thus, the *.has files contain the raw slopes of the measurement. In addition, pupil & intensity information from the last processing, and other information for wavefront reconstruction is included. Even reference wavefronts (in the form of slops data) can be included together with the operation required to apply this reference. How this data is filtered (to remove tilts, or focus, etc.) is a matter of displaying in WaveView, or of where the file is opened in WaveTune (see expert settings for the target wavefront).
A point of occasional confusion hinges on the question of what exactly is saved, and also, what is loaded when using the corresponding buttons in WaveView, and WaveTune.
- In general the software was conceived following a WYSIWYG approach ("what you see is what you get"), to the limit of still saving the underlying raw data, to make different views (e.g. filtering or not filtering focus) when looking at the data later.
- When saving: That means the raw slopes, a potential reference and all operations to get to the same displayed wavefront are saved. (+pupil, +intensity, +etc.). For example, when you look at the residual wavefront in WaveTune, saving it will save the raw slopes from the measurement, and the target as reference, so that if you open the files in WaveView (our standard viewer, which can be used to analyze all .*has files) you'll only see the residual until you disable the reference, which would show you the actually measured wavefront.
- The files are xml-based, so you can always open them with a text editor such as Notepad++ (or a Matlab/Python script) and look what has been saved inside. Note that following the "keep the data as raw as necessary"-approach you'll not see wavefront estimation data, but only slopes.
- When opening: This is where the confusion might arise. Depending on where you load the file in WaveTune, its information is interpreted accordingly. For example, if you use the expert mode of WaveTune, you can load 3 different files and pick which focus, which tilts, which higher order aberrations you want to use to construct the target.