Table of Contents
Release Notes
lipi-core-toolkit 2.1
Media & Configuration
Platforms supported
lipi-core-toolkit 2.1 can be installed on any of the following platforms:
► Windows XP Professional edition
► Redhat Enterprise Linux Edition 4.0
► Ubuntu Gutsy Gibbon 7.10
Software Requirements
| Description | Windows XP Profession edition | Linux |
| Extracting the contents of the package | Cabarc sdk (Refer to Appendix for download instructions) | tar |
| Building lipi-core-toolkit code | Microsoft Visual Studio 6.0 with SP6 for VC 6.0, Microsoft Visual C++ 2005 or MsBuild for VC2005 | GCC 3.4.6-9 or above |
| Executing scripts | Perl 5.0 or above (Refer to Appendix for download instructions for Active Perl) |
Release Components
| Component Name | Version No. | Description |
| lipi-core-toolkit2.1-winvc6.0.cab | 2.1 | Binary package for Windows, for VC6.0 |
| lipi-core-toolkit2.1-src.winvc6.0.cab | 2.1 | Source package for Windows, for VC6.0 |
| lipi-core-toolkit2.1-winvc2005.cab | 2.1 | Binary Package for Windows, for VC2005 |
| lipi-core-toolkit2.1-src.winvc2005.cab | 2.1 | Source package for Windows, for VC2005 |
| lipi-core-toolkit2.1-linux.tar.gz | 2.1 | Binary package for Linux |
| lipi-core-toolkit2.1-src.linux.tar.gz | 2.1 | Source package for Linux |
Documentation
New Features in this release
► Writing MDT file in binary mode
In the latest version of core toolkit, a new configuration parameter has been added to the shape recognizer configuration file, which allows the user to select the writing mode for MDT file. In the previous versions, MDT file was always written in ASCII mode.Writing the MDT file in binary mode reduces the file size.
#------------------------------------------------------------------------------- # NNMDTFileOpenMode # Description: This configuration parameter specifies the mode for # opening the mdt file. # # Valid values: ascii, binary # Default Value: ascii #------------------------------------------------------------------------------ NNMDTFileOpenMode=ascii
► Separate Utility classes for platform specific code A new interface LTKOSUtil has been added to core toolkit, which exposes functions for loading/unloading shared libraries. All the platform specific code has been moved to separate files; LTKWindowsUtil for Windows and LTKLinuxUtil for Linux. These classes derive from LTKOSUtil and at run-time, based on the operating system, an instance of the corresponding class is created.
► Logger implemented as a separate shared library
In version 2.1 of core toolkit, logger has been implemented as a separate shared library, loaded by lipiengine at runtime. In case of error loading the logger library, no log messages are recorded.
Note: This change has no impact on end user. The logger behavior remains the same as in the previous versions of the toolkit.
► Support for building VC2005 using MsBuild
lipi-core-toolkit 2.1 provides the MsBuild project file for every module. With this, user can build source code for VC2005 package by using the MsBuild. The earlier version required the user to install Microsoft Visual C++ 2005 for building the source code.
Bugs Fixed
Note: Bug-Ids below are for internal tracking purposes only.
| S No. | Bug Id | Description |
| 1. | LIPTKT-387 | The config values read during training should be stored in the mdt file, so that they can be compared while testing |
| 2. | LIPTKT-389 | LVQ training is taking more time |
| 3. | LIPTKT-455 | Evaluation works on the basis of number of results in the first valid line of the result file and hence fails for non uniform result files |
| 4. | LIPTKT-471 | Error using Preproc routines |
| 5. | LIPTKT-472 | Remove TraceDimension from mdt file header |
| 6. | LIPTKT-473 | The runshaperec application should print -1 for shapes which do not match to any of the prototypes. |
| 7. | LIPTKT-476 | RemoveDuplicatePoints and many other functions in the preprocessing module not working |
| 8. | LIPTKT-478 | Error during deletion of multiple ShapeRecognizers |
| 9. | LIPTKT-479 | SmoothenTraceGroup changes the number of points |
| 10. | LIPTKT-481 | Memory Leaks: LipiEngineModule: The library doesn't export any function for deleting the instance of LipiEngieModule |
| 11. | LIPTKT-482 | Memory Leak in error scenarios. |
| 12. | LIPTKT-485 | filter value for smoothenTraceGroup shall be read from the config file |
| 13. | LIPTKT-363 | Logger to be independent, behavior should be the same irrespective of dll or static lib using the logger. |
| 14. | LIPTKT-448 | Solution for building LipiTk (vc2005) from command line |
| 15. | LIPTKT-475 | All the platform specific code should be moved to separate files |
| 16. | LIPTKT-463 | The mdt file should be written in binary mode |
Limitations and known issues
►Spaces in ink file paths in training/test list files causes error
► Problem statement
The runshaperec.exe reports error if the file paths mentioned in the list files for training or testing contain spaces.
► Workaround
Do not use directory or files names with spaces in them, or (for Windows platforms) use the DOS path instead (e.g. for C:\program files, use "C:\progra~1").
Backward Compatibility
Version 2.1 of core toolkit does not maintain backward compatibility with previous releases of core toolkit.
