FAQ - Frequently Asked Questions


 Browse FAQ      Browse Documentation Wiki   movie Browse EigenGuide Videos
SearchSearch for Keyword(s):

Issue:

    Do any PLS_Toolbox functions conflict with the Mathworks Toolboxes?

Possible Solutions:

    There are several files in PLS_Toolbox which are named the same as files in Mathwork's toolbox products. When such conflicts exist, Matlab will only be able to use the file located earliest in the Matlab Path (type "pathtool" to view and edit the Matlab path). In the case of such conflicts, you can switch between which file is used by editing the path and moving the desired folder (i.e. toolbox) to above the conflicting folder.

    Question: How do I know if I have this problem? Check this related FAQ item.

    The following conflicts have been identified between PLS_Toolbox function and Mathworks' toolboxes. Note that although the functions are named the same, the action of the functions are not usually the same.

    Statistics Toolbox Conflicts



    The following PLS_Toolbox files exist in the Statistics Toolbox:
        boxplot.m
        cluster.m
        clusterdemo.m
        crossval.m
        dendrogram.m
        gline.m
        kstest.m
        mdscale.m
        pca.m
        range.m
        ridge.m
        signtest.m

    Also note that the Statistics Toolbox contains an object named the dataset object which conflicts with Eigenvector's DataSet object. You can only use one of the two objects at any one time. If you wish to use the Mathworks' dataset object instead of the Eigenvector object, you must first move PLS_Toolbox to the bottom of the path (or remove it completely), then type the command:

     clear classes

    Note that this command will clear all variables from memory, but this is the only way to switch between the Eigenvector and Mathworks' DataSet objects.

    Other Conflicts



    The following PLS_Toolbox file exists in the Communications Toolbox:
        encode.m

    The following PLS_Toolbox file exists in the Control System Toolbox:
        gram.m


Still having problems? Check our documentation Wiki or try writing our helpdesk at helpdesk@eigenvector.com