Project Releases

Prevent bugging out on too small datasets when trying to pixelate them. We now enforce a minimum number of data points. And if it then even fails, we just return the non-resampled bricklet.

• Port to Igor Pro 8.0
• Require Windows 10
• Port to 64-bit
• Upgrade to XOP Toolkit 8.01
• Compile against Vernissage 2.4.1 SDK and switch to Visual Studio 2013
• Add new bricklet types and view codes from Vernissage 2.4

• Fix encoding of metadata/text waves for IP7. These now hold unicode encoded text for IP7 and the local ANSI codepage encoded text for IP6. Text waves loaded with an old version of this XOP can be fixed with setting the encoding of text waves to the local ANSI codepage. For example on this authors computer the line SetWaveTextEncoding 3, 16, metadata_00002 fixes the issue.


• Upgrade to XOP Toolkit 7.01

Raise XOP version.

Raise XOP version.

• Upgrade to XOP Toolkit 6.40


• Add support for Vernissage 2.3 in addition to 2.2









 
•  
•  
•  
•  
•  
•  
•  

Changes since 0.24.beta2:

Only preload data if data cache is enabled

Bugfix: Don't create Down/ReDown waves for Up/ReUp-only measurement
The bug is present since forever. The erroneously created waves had
garbage data, the Up/ReUp waves were not affected and had valid data.

Major bugfix: Fix incorrect data in VolumeCITS traces ReUp and ReDown
* Re data starts xAxisForwardBlockSize further away.
* The result from this bug is that the contents of ReUp and ReDown where
taken from Up and Down traces and flipped.
* The bug is present since forever.
* The regression tests revealed that really only ReUp and ReDown waves are
affected.

MFR Basic GUI:
* Correctly remember the open result file after opening it and not only after closing it.
* Use a unique notebook name for the bug report notebook
* Only update startBrickletID and endBrickletID from "check for new bricklets" if it suceeded.
* Initialize some more variables to sane defaults
* Limit brickletID boxes to the range 1 <-> inf

MFR XOP user:
* Upgrade to Vernissage 2.2
* Move the result set loading into its own thread
This allows to call SpinProcess() in the main thread and thus
does not block the GUI.
* Add support for calibrationinfo in bricklet metadata
* Always sort the bricklet metadata entries dependentBricklets, referencedBricklets and brickletSeries
* Add support for loading bricklet data/metadata using multiple threads
* Support loading of data with ramp reversal:
* Suffix RampFwd/RampBwd
* 1D SPS
* 3D VolumeCITS
- Bricklets with ramp reversal enabled and the old code did produce incorrect waves.
* 3D bricklet conversion Error out on unexpected table sets
* Add resampling support for 1D data using Decimation by omission using the
Igor operation Resample
* Add free/total memory in bug report template
* Reduce memory consumption for bricklet metadata considerably
* Add git commit of the last change to the bug report template
* Add new variable MFR_MatrixFileReaderMagic for advanced debugging
* Proper Unicode to ANSI, aka wstring to string, conversion using the functions from the Vernissage API

MFR XOP internal:
* Code cleanup
* extend class Wave to allow an arbitrary suffix
* Add Boost include (currently version 1.55)
* Use smartptr from boost
* check return value of MDSetDimensionLabel
* Switch to CBString from bstrlib for the bricklet metadata as it decreases the memory consumption by 30%

Regression Tests:
* minor enhancements for the utility diff function
* Add detailed tests for VolumeCITS data using the new magic options
* Create new reference data sets

code cleanup
check if the datafolder, which can be passed to various operations, really exists
S_waveNames now holds paths relative to the dfref/current data folder. This prevents inconsistencies with free data folders passed as dfref

code cleanup
enhanced regression tests

Compile against final Vernissage header
minor code cleanup
remove old and unused files

• major code cleanup and minor bug fixes
• require Vernissage 2.1 (to be more precise T2.1-7 or above)
• upgraded XOP toolkit from 6.01 to 6.02
• added support for new API functions
• hardcode the name of the help file, this allows the user to rename the XOP
• remove all trailing backslashes from dirPath, this gives more consistent results for MFR_GetResultFileName
• only remember the last used path for the Dialog in MFR_OpenResultFile if it exists
• only copy valid content for 1D bricklets (relevant only for I(t) spectra introduced with Matrix 3.1)

Updated the shipped vcredist package

Upgraded XOP toolkit from 6.0 to 6.01
Added a static build configuration

Bug Fixes:
*fix a off-by-one error, now the min/max data in the wave note should always be correct. This
bug has also the potential to crash the application and/or modify other
unrelated data (aka a wild pointer was fixed).
*fix metadata vector resizing, this lowers the memory consumption for cached
meta data.

Other stuff:
*Compiled against Vernissage SDK 2.0-1 (no user visible changes)
*major code cleanup and reorganization
*add much more documentation, now every function and class is documented
*split operationsinterface.cpp into multiple files, one file for each operation
*split the utils.* stuff into utils_generic.*, utils_bricklet.* and utils_xop.*
*be more precise about the axis table sets (no user visible change)
*added regression testing suite, the reference data is due to its size (> 4GB) not attached but of course available on request

constant data must be transformed differently from raw to physical values (this is a corner case with very little practical impact)

add a new wave note entry named traceDirection (this is much safer than parsing the wave name)

add meta data key dataComment.count which holds the number of datacomments of the bricklet. Without any datacomments this value is 0.

minor code cleanup

sync the documented error codes and the ones we return in operationsinterface.cpp

the error code NON_EXISTENT_BRICKLET was removed
and accordingly the igor structure errorCode has also been changed

rename the key resultFilePath to resultDirPath in the wave notes and in the result file meta data wave

better error message wording

fix a stupid bug which caused the tablesets for 3D data to be interpreted wrong
_Only_ applies to the case where the number of points is different in x and y direction for Grid spectroscopy data

initial public release