HoloPRO Interface and LabView Interface: Difference between pages

From Eigenvector Research Documentation Wiki
(Difference between pages)
Jump to navigation Jump to search
imported>Jeremy
No edit summary
 
imported>Jeremy
No edit summary
 
Line 1: Line 1:
==Introduction==
==Introduction==


Kaiser Optical Systems' HoloPRO software supports calls into either Solo_Predictor (as of v3.2.0.5) or Matlab. The sections below give some background and basic information on using HoloPRO software with Eigenvector Research products. [http://www.kosi.com Contact Kaiser Optical Systems] for more information on interfacing to Matlab or using the Solo_Predictor interfacing options of HoloPRO.
[http://www.ni.com/labview/ National Instruments' LabView software] supports three different interfaces which are compatible with Eigenvector models. Solo_Predictor can be called directly using ActiveX or .NET interfaces. The m-files output by Model_Exporter can be executed natively within LabView, and LabView allows for using PLS_Toolbox by calling directly into Matlab via its ActiveX interface.


==Solo_Predictor Interface==
==Solo_Predictor Interface==
For making predictions using Solo_Predictor, a regression model can be specified and HoloPRO will automatically extract the available information from that model. For best interfacing, it is recommended you build models which include labels on your y-block columns to clearly identify the predicted species.
LabView supports both socket, ActiveX, and .NET interfaces, any of which can be used to connect to Solo_Predictor directly. For details on these interfaces and the methods, see the [[EigenvectorTools]] pages. For assistance with scripting Solo_Predictor, see the [[Solo_Predictor User Guide]].


==Model_Exporter Interface==
==Model_Exporter Interface==
To use Eigenvector Research models which have been exported using Model_Exporter, HoloPRO supports calling into Matlab which can be scripted to return results from the model of interest. The Model_Exporter models can be called directly and do not require any additional software beyond Matlab and HoloPRO.
LabView, if installed with the National Instruments "MathScript" add-on, is configured to work with m-file models which are output by Model_Exporter. In these cases, you do '''not''' need Matlab to implement an exported model. To learn more about using Model_Exporter with LabView, see the [[Model_Exporter User Guide|Model_Exporter User Guide]].


==PLS_Toolbox Interface==
==PLS_Toolbox Interface==
To use Eigenvector models with PLS_Toolbox natively (without using Model_Exporter) HoloPRO's Matlab interface can be used along with custom scripts to return results from the model of interest. For assistance with scripting for these situations, [mailto:helpdesk@eigenvector.com contact our Helpdesk].


====Licensing====
To make predictions with an Eigenvector model from within Matlab, LabView can be configured to call into Matlab and execute a specific script. This script can call PLS_Toolbox commands, as long as PLS_Toolbox is installed along with Matlab. See [[PLS_Toolbox Unattended Configuration]] for details on configuring PLS_Toolbox for use in unattended situations. For assistance with scripting for these situations, [mailto:helpdesk@eigenvector.com contact our Helpdesk].
 
Note that the [http://www.eigenvector.com/software/license_evri.html PLS_Toolbox license] requires that, unless special site licensing arrangements are made, you must obtain a separate PLS_Toolbox license for each instance of any PLS_Toolbox code you wish to deploy. Special licensing options are available. See the [http://www.eigenvector.com Eigenvector Website] for more information.
 
====Configuration====
For best performance, it is recommended that you follow these instructions to configure Matlab and PLS_Toolbox:
 
With Matlab already installed (as per [http://www.mathworks.com The Mathworks installation instructions]), PLS_Toolbox can be copied onto the target computer using any of the available file types as described in the [[Installation|standard installation instructions]]. The primary differences from the standard installation will be that you will create two special files and place these files into the PLS_Toolbox/utilities folder on the target computer:
# Create a text file named '''evrilicense.lic''' and put your license code (available from the [http://download.eigenvector.com Eigenvector Research download page]) as a single line in that file. You can also obtain a evrilicense.lic file from the [mailto:helpdesk@eigenvector.com Eigenvector Helpdesk].
# Create an ''empty'' text file named '''evrinetwork.lic'''. This file will instruct PLS_Toolbox to ignore installation errors and run without warnings (necessary when calling PLS_Toolbox functions from within SiPAT.)

Revision as of 16:54, 21 December 2011

Introduction

National Instruments' LabView software supports three different interfaces which are compatible with Eigenvector models. Solo_Predictor can be called directly using ActiveX or .NET interfaces. The m-files output by Model_Exporter can be executed natively within LabView, and LabView allows for using PLS_Toolbox by calling directly into Matlab via its ActiveX interface.

Solo_Predictor Interface

LabView supports both socket, ActiveX, and .NET interfaces, any of which can be used to connect to Solo_Predictor directly. For details on these interfaces and the methods, see the EigenvectorTools pages. For assistance with scripting Solo_Predictor, see the Solo_Predictor User Guide.

Model_Exporter Interface

LabView, if installed with the National Instruments "MathScript" add-on, is configured to work with m-file models which are output by Model_Exporter. In these cases, you do not need Matlab to implement an exported model. To learn more about using Model_Exporter with LabView, see the Model_Exporter User Guide.

PLS_Toolbox Interface

To make predictions with an Eigenvector model from within Matlab, LabView can be configured to call into Matlab and execute a specific script. This script can call PLS_Toolbox commands, as long as PLS_Toolbox is installed along with Matlab. See PLS_Toolbox Unattended Configuration for details on configuring PLS_Toolbox for use in unattended situations. For assistance with scripting for these situations, contact our Helpdesk.

Retrieved from "https://www.wiki.eigenvector.com/index.php?title=HoloPRO_Interface&oldid=8065"