Function Use Statistics: Difference between revisions

From Eigenvector Research Documentation Wiki
Jump to navigation Jump to search
imported>Jeremy
(Created page with "Some versions of PLS_Toolbox and Solo contain a feature which allows you to contribute anonymous "Function Use" information to the Eigenvector Research developers team. This info...")
 
imported>Jeremy
No edit summary
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
Some versions of PLS_Toolbox and Solo contain a feature which allows you to contribute anonymous "Function Use" information to the Eigenvector Research developers team. This information is ONLY used to help us better understand which features are most used and, therefore, where our development effort is best spent in making your experience better.
Some versions of PLS_Toolbox and Solo allow you to contribute anonymous "Feature Use" information to the Eigenvector Research development team. This information is ONLY used to help us better understand which features are most used and, therefore, where our development effort is best spent in improving our tools.


===Opt-In===
===Opt-In===


This feature is completely "opt-in" meaning that it will '''NOT''' collect or send any information unless you explicitly tell it that you want to participate. Once you've been asked once, it will not ask you again (unless you clear all program settings, for example, if you uninstall and re-install from scratch.) But under no circumstances will it ever send use information unless you have explicitly told it you want to do so.
This feature is completely "opt-in" meaning that it will '''NOT''' collect or send any information unless you explicitly tell it that you want to participate. Once you've been asked once, it will not ask you again (unless you clear all program settings, for example, if you uninstall and re-install from scratch.) Under no circumstances will it ever send use information unless you have explicitly told it you want to do so.


===What Information Is '''Not''' Collected?===
This feature has no impact on performance of the software. If it cannot file a report, it will simply discard the information.
 
It can be disabled (and re-enabled) through the Help menu in the Workspace Browser or the Analysis window.
 
===What Information Is Not Collected?===


The information collected by this feature '''includes absolutely NO information about:''' your data, you, your computer, your company/affiliated organization, your location, your IP address, your Eigenvector Research account or license number, nor any other personally-identifiable information.
The information collected by this feature '''includes absolutely NO information about:''' your data, you, your computer, your company/affiliated organization, your location, your IP address, your Eigenvector Research account or license number, nor any other personally-identifiable information.


===What Information '''Is''' Collected?===
===What Information Is Collected?===


This feature counts the number of times you execute "high-level" functions in the software and combines this with the product name (e.g. "PLS_Toolbox", "Solo", "Solo+MIA") and version number, and whether the given product is running with an expiring "Demo" license code. This information is periodically sent to Eigenvector Research (e.g. every 30 minutes) along with a completely random "session" code which allows combining all the submissions from that given session of using the software. The session key changes randomly each time you start up the software and can only be used to assure that all your use information is correctly accumulated for that session.
The report includes the number of times you made use of particular features in the software and combines this count with the product name (e.g. "PLS_Toolbox", "Solo", "Solo+MIA"), version number, and whether the given product is running with an expiring "Demo" license code. This information is periodically sent to Eigenvector Research (e.g. every 30 minutes) along with a random code allowing the system to combine the reports.
 
You have the '''OPTION''' to also submit reports with a random anonymous "user" code which will help us understand how individual users make user of the software. Even when this feature is enabled, your submissions will '''always''' be anonymous in that we can and will never connect any use information with a given physical end-user. This code is simply used to aggregate multiple sessions together with a given installation of the software.


===Example Report===
===Example Report===
Line 19: Line 21:
Below is an example of a report collected by one of the Eigenvector Research staff during a short period of time:
Below is an example of a report collected by one of the Eigenvector Research staff during a short period of time:


       user: ''
       cumulative: 152
    session: '7K11NUCBT27EUQAMF2LTFVJXY'
      peakfindgui: 12
    product: 'PLS_Toolbox'
  plotgui_toolbar: 11
    version: '7.0.3'
      drop_parse: 2
    isdemo: 0
      figbrowser: 13
 
        evrimodel: 2
This information is followed by the actual "use" information:
          explode: 22
 
        analysis: 30
          cumulative: 58
      pca_guifcn: 4
                pca: 6
            auto: 1
                auto: 3
          normset: 1
            normset: 1
  wlsbaselineset: 3
      wlsbaselineset: 3
      wlsbaseline: 1
        wlsbaseline: 1
        baseline: 1
            baseline: 1
    poissonscale: 1
        poissonscale: 1
          flucut: 1
              flucut: 1
          emscorr: 1
          evrimodel: 1
           mdcheck: 8
           evriscript: 1
              pca: 6
            mdcheck: 8
      evriscript: 1
          pcaengine: 3
        pcaengine: 3
       residuallimit: 2
    residuallimit: 2
              scale: 8
       choosecomp: 2
          plotscores: 2
      modelcache: 3
      plotscores_pca: 2
      plotscores: 2
    knnscoredistance: 4
  plotscores_pca: 2
        inheritimage: 1
knnscoredistance: 2
           figbrowser: 2
    inheritimage: 1
            plotgui: 1
            mplot: 2
        classmarkers: 2
           plotgui: 2
        peakfindgui: 2
          evritip: 3
    plotgui_toolbar: 2
    classmarkers: 1
        plotloads: 2
            scale: 2

Latest revision as of 16:19, 17 April 2013

Some versions of PLS_Toolbox and Solo allow you to contribute anonymous "Feature Use" information to the Eigenvector Research development team. This information is ONLY used to help us better understand which features are most used and, therefore, where our development effort is best spent in improving our tools.

Opt-In

This feature is completely "opt-in" meaning that it will NOT collect or send any information unless you explicitly tell it that you want to participate. Once you've been asked once, it will not ask you again (unless you clear all program settings, for example, if you uninstall and re-install from scratch.) Under no circumstances will it ever send use information unless you have explicitly told it you want to do so.

This feature has no impact on performance of the software. If it cannot file a report, it will simply discard the information.

It can be disabled (and re-enabled) through the Help menu in the Workspace Browser or the Analysis window.

What Information Is Not Collected?

The information collected by this feature includes absolutely NO information about: your data, you, your computer, your company/affiliated organization, your location, your IP address, your Eigenvector Research account or license number, nor any other personally-identifiable information.

What Information Is Collected?

The report includes the number of times you made use of particular features in the software and combines this count with the product name (e.g. "PLS_Toolbox", "Solo", "Solo+MIA"), version number, and whether the given product is running with an expiring "Demo" license code. This information is periodically sent to Eigenvector Research (e.g. every 30 minutes) along with a random code allowing the system to combine the reports.

Example Report

Below is an example of a report collected by one of the Eigenvector Research staff during a short period of time:

      cumulative: 152
     peakfindgui: 12
 plotgui_toolbar: 11
      drop_parse: 2
      figbrowser: 13
       evrimodel: 2
         explode: 22
        analysis: 30
      pca_guifcn: 4
            auto: 1
         normset: 1
  wlsbaselineset: 3
     wlsbaseline: 1
        baseline: 1
    poissonscale: 1
          flucut: 1
         emscorr: 1
         mdcheck: 8
             pca: 6
      evriscript: 1
       pcaengine: 3
   residuallimit: 2
      choosecomp: 2
      modelcache: 3
      plotscores: 2
  plotscores_pca: 2
knnscoredistance: 2
    inheritimage: 1
           mplot: 2
         plotgui: 2
         evritip: 3
    classmarkers: 1
       plotloads: 2
           scale: 2