Quantcast
Channel: Recent posts
Viewing all 190 articles
Browse latest View live

how to install pydaal without mysql

$
0
0

Hi:

I want to install pydaal. When it compile the source code _data_management__db.cpp and say from

#include <data_management/data_source/mysql_feature_manager.h> it can not find <sql.h> in daal/include/data_management/data_source/mysql_feature_manager.h

Of course, because I do not install mysql in my computer, so there is no sql.h in my computer. Actually, I use postgresql as my database, so mysql_feature_manager is completely useless to me. I want to ask how to install pydaal without mysql


SEGFAULT in mkl_dcoomv() on Xeon Phi

$
0
0

I keep getting segmentation faults within mkl_dcoomv() function from MKL invoked in a native mode program on Xeon Phi (KNC). The code works well on the host (Haswell) as well as with the CSR strorage format (mkl_dcsrmv()) instead of COO. So, the problem happens only with the combination of COO an MIC.

In a debugger, I got the following error message:

Catchpoint -1 (signal SIGSEGV), 0x00007ffff514cc8a in mkl_spblas_lp64_dcoo0ng__c__mvout_mic () from /apps/all/imkl/2017.0.098-iimpi-2017.00-GCC-5.4.0-2.26/mkl/lib/mic/libmkl_intel_thread.so

The MKL and compiler versions are both 2017.

The code can be found here.

Any hints?

Compile errors of mpif90 for a MPI Fortran with FFTW3 code

$
0
0

I have a fortran code using MPI and calling FFTW3. It can be successfully compiled by the command mpiifort. But when I try to use mpif90, it gives errors like:

fftwtest_fwd.f90:(.text+0x2a6): undefined reference to `fftw_mpi_init'
fftwtest_fwd.f90:(.text+0x2e7): undefined reference to `fftw_mpi_local_size_2d_f03'
fftwtest_fwd.f90:(.text+0x2f7): undefined reference to `fftw_alloc_complex'
fftwtest_fwd.f90:(.text+0x46e): undefined reference to `fftw_mpi_plan_dft_2d_f03'
fftwtest_fwd.f90:(.text+0x630): undefined reference to `fftw_mpi_execute_dft'
fftwtest_fwd.f90:(.text+0x937): undefined reference to `fftw_destroy_plan'
fftwtest_fwd.f90:(.text+0x93c): undefined reference to `fftw_mpi_cleanup'
fftwtest_fwd.f90:(.text+0x948): undefined reference to `fftw_free'

I compile the code using my laptop, the parallel studio xe 2017 has been installed.

However, when I use mpiffort and mpif90 compile the same code on a server of my organization, everything is good. Could someone give me directions? Thank you very much.

Intel® DAAL 2017 Update 2 is now available

$
0
0

Intel® DAAL 2017 Update 2 was just released. Here are What's New in this release:

  • Lots of improvements for the neural networks API:
    • Added the transposed convolution layer
    • Added the reshape layer
    • Extended interface of loss softmax cross-entropy layer to support input tensors of arbitrary dimensions
    • Added sigmoid cross-entropy criterion
    • Added truncated Gaussian initializer for tensors
    • Extended support for distributed computing by adding the objective function with pre-computed characteristics
    • Improved performance of neural network layers used in topologies such as AlexNet
  • Added more samples to demonstrate the usage of this library. You can find and download the latest samples from: Intel® Data Analytics Acceleration Library Code Samples

Intel® Data Analytics Acceleration Library 2018 Beta Release Notes

$
0
0

This document provides a general summary of new features and important notes about the Intel® Data Analytics Acceleration library (Intel® DAAL) software product. Please see the following links to the online resources and documents for the latest information regarding Intel DAAL:

·         Intel® DAAL Product Page

·         Intel® DAAL 2018 Installation Guide

·         Intel® DAAL 2018 System Requirements

Links to documentation, help, and code samples can be found on the main Intel DAAL product page. For technical support visit the Intel DAAL technical support forum and review the articles in the Intel DAAL knowledge base.

Please register your product using your preferred email address. This helps Intel recognize you as a valued customer in the support forum and insures that you will be notified of product updates. You can read Intel's Online Privacy Notice Summary if you have any questions regarding the use of your email address for software product registration.

What's New in Intel® DAAL 2018 Beta

  • A new documentation page that better organizes a new API References Manual and a new Developer Guide.
  • Introduced API modifications to streamline library usage and enable consistency across functionality. 
  • Introduced support for Decision Tree for both classification and regression. The feature includes calculation of Gini index and Information Gain for classification, and mean squared error (MSE) for regression split criteria, and Reduced Error Pruning.
  • Introduced support for Decision Forest for both classification and regression. The feature includes calculation of Gini index for classification, variance for regression split criteria, generalization error, and variable importance measures such as Mean Decrease Impurity and Mean Decrease Accuracy.
  • Introduced support for varying learning rate in the Stochastic Gradient Descent algorithm for neural network training.
  • Performance improvements in various neural network layers used in AlexNet and other topologies. 

Product Contents

Intel DAAL can be installed as a part of the following suite:

Intel DAAL consists of one package for both IA-32 and Intel® 64 architectures.

Known Issue

  • Intel DAAL Python API (a.k.a. pyDAAL) is provided as source. When build it on Windows, users may see warning messages. These warning messages do not indicate critical issues and do not affect the library's functionality. 
  • Intel DAAL Python API (a.k.a. pyDAAL) built from the source does not work on OS X* El Capitan (version 10.11). Workaround: Users can get the Intel Distribution of Python as an Anaconda package (http://anaconda.org/intel/), which contains a pre-built pyDAAL that works on OS X* El Capitan.

Technical Support

If you did not register your Intel software product during installation, please do so now at the Intel® Software Development Products Registration Center. Registration entitles you to free technical support, product updates, and upgrades for the duration of the support term.

For information about how to find Technical Support, Product Updates, User Forums, FAQs, tips and tricks, and other support information, please visit https://software.intel.com/en-us/intel-daal-support.

Note: If your distributor provides technical support for this product, please contact them for support rather than Intel.

License Definitions

INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT.

A "Mission Critical Application" is any application in which failure of the Intel Product could result, directly or indirectly, in personal injury or death. SHOULD YOU PURCHASE OR USE INTEL'S PRODUCTS FOR ANY SUCH MISSION CRITICAL APPLICATION, YOU SHALL INDEMNIFY AND HOLD INTEL AND ITS SUBSIDIARIES, SUBCONTRACTORS AND AFFILIATES, AND THE DIRECTORS, OFFICERS, AND EMPLOYEES OF EACH, HARMLESS AGAINST ALL CLAIMS COSTS, DAMAGES, AND EXPENSES AND REASONABLE ATTORNEYS' FEES ARISING OUT OF, DIRECTLY OR INDIRECTLY, ANY CLAIM OF PRODUCT LIABILITY, PERSONAL INJURY, OR DEATH ARISING IN ANY WAY OUT OF SUCH MISSION CRITICAL APPLICATION, WHETHER OR NOT INTEL OR ITS SUBCONTRACTOR WAS NEGLIGENT IN THE DESIGN, MANUFACTURE, OR WARNING OF THE INTEL PRODUCT OR ANY OF ITS PARTS.

Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined." Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. The information here is subject to change without notice. Do not finalize a design with this information.

The products described in this document may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request.

Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order.

Copies of documents which have an order number and are referenced in this document, or other Intel literature, may be obtained by calling 1-800-548-4725, or by visiting Intel's Web Site.

Intel processor numbers are not a measure of performance. Processor numbers differentiate features within each processor family, not across different processor families. See http://www.intel.com/products/processor_number for details.

BlueMoon, BunnyPeople, Celeron, Celeron Inside, Centrino, Centrino Inside, Cilk, Core Inside, E-GOLD, Flexpipe, i960, Intel, the Intel logo, Intel AppUp, Intel Atom, Intel Atom Inside, Intel Core, Intel Inside, Intel Insider, the Intel Inside logo, Intel NetBurst, Intel NetMerge, Intel NetStructure, Intel SingleDriver, Intel SpeedStep, Intel Sponsors of Tomorrow., the Intel Sponsors of Tomorrow. logo, Intel StrataFlash, Intel vPro, Intel Xeon Phi, Intel XScale, InTru, the InTru logo, the InTru Inside logo, InTru soundmark, Itanium, Itanium Inside, MCS, MMX, Moblin, Pentium, Pentium Inside, Puma, skoool, the skoool logo, SMARTi, Sound Mark, Stay With It, The Creators Project, The Journey Inside, Thunderbolt, Ultrabook, vPro Inside, VTune, Xeon, Xeon Inside, X-GOLD, XMM, X-PMU and XPOSYS are trademarks of Intel Corporation in the U.S. and/or other countries.Intel, and the Intel logo are trademarks of Intel Corporation in the U.S. and/or other countries.

*Other names and brands may be claimed as the property of others.

Java is a registered trademark of Oracle and/or its affiliates.

© Copyright 2017, Intel Corporation

Optimization Notice

Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.

Notice revision #20110804

 

Intel® Data Analytics Acceleration Library 2018 Beta Installation Guide

$
0
0

Please see the following links to the online resources and documents for the latest information regarding Intel DAAL:

·         Intel® DAAL Product Page

·         Intel® DAAL 2018 Release Notes

·         Intel® DAAL 2018 Installation Guide

·         Intel® DAAL 2018 System Requirements

These instructions assume a standalone installation of Intel® Data Analytics Acceleration Library (Intel® DAAL). If your copy of Intel® DAAL was included as part of one of our "suite products" (e.g., Intel® Parallel Studio XE) your installation procedure may be different than that described below; in which case, please refer to the readme and installation guides for your "suite product" for specific installation details.

Before installing Intel® DAAL, check the Product Downloads section of Intel® Registration Center to see if a newer version of the library is available. The version listed in your electronic download license letter may not be the most current version available.

The installation of the product requires a valid license file or serial number. If you are evaluating the product, you can also choose the "Evaluate this product (no serial number required)" option during installation.
If you have a previous version of Intel® DAAL installed you do not need to uninstall it before installing a new version. If you choose to uninstall the older version, you may do so at any time.

Note: Installation on 32-bit hosts is no longer supported. However, the 32-bit library continues to exist, and can be used on 64-bit hosts.

Installing Intel® DAAL on Windows* OS

You can install multiple versions of Intel® DAAL and any combination of 32-bit and 64-bit variations of the library on your development system.

These instructions assume you to have an Internet connection. The installation program will automatically download a license key to your system. If you do not have an internet connection, see the manual installation instructions below.

Interactive installation on Windows* OS

  1. If you received the Intel® DAAL product as a download, double-click on the downloaded file to begin.
  2. You will be asked to choose a target directory ("c:\Users\<Username>\Downloads\"  by default) in which the contents of the self-extracting setup file will be placed before the actual library installation begins. You can choose to remove or keep temporarily extracted files after installation is complete. You can safely remove the files in this "downloads"  directory if you need to free up disk space; however, deleting these files will impact your ability to change your installation options at a later time using the add/remove applet, you will always be able to uninstall.)
  3. Click Next when the installation wizard appears.
  4. If you agree with the End User License Agreement, click Next to accept the license agreement.
  5. License Activation Options:
    • If you do have an Internet connection, skip this step and proceed to the next numbered step (below).
    • If you do not have an Internet connection, or require a floating or counted license installation, choose Alternative Activation and click Next; there will be two options to choose from:
      • Activate Offline:  requires a License File.
      • Use a License manager: Floating License activation
  6. Enter your serial number to activate and install the product.
  7. Activation completed. Click Next to continue.
  8. If there is package from another update of Parallel Studio XE installed, you will be able to select update mode on Choose Product Update Mode dialog:
    1. I want to apply this update to the existing version.
      Using this option will result in the original version being replaced by the updated version.
    2. I want to install this update separate from the existing version.
      Using this option will result in the update being installed in a different location, leaving the existing version unchanged.
  9. The Installation Summary dialog box opens to show the summary of your installation options (chosen components, destination folder, etc.). Click Install to start installation (proceed to step 15) or click Customize to change settings. If you select "Customize", follow steps 10-14.Installation summary

  10. In the Architecture Selection dialog box, select the architecture of the platform where your software will run.
  11. In the Choose a Destination Folder dialog box, choose the installation directory. By default, it is C:\Program Files\IntelSWTools. You may choose a different directory. All files are installed into the Intel Parallel Studio XE 2018 subdirectory (if you chose I want to install this update separate from the existing version, all files are installed into the parallel_studio_xe_2018.0.xxx directory, where xxx is the package number).
  12. Package contains components for integration into Microsoft Visual Studio*. You are able to select the Microsoft Visual Studio product(s) for integration on the Choose Integration target dialog box.
  13. If Microsoft Compute Cluster Pack* is present, and the installation detects that the installing system is a member of a cluster, the dialog box will be shown which provides you an option to install the product on all visible  nodes of the cluster or on the current node only(by default installation on all visible nodes is performed).
  14. The Installation Summary dialog box opens to show the summary of your installation options (chosen components, destination folder, etc.). Click Install to start installation.
  15. Click Finish in the final screen to exit the Intel Software Setup Assistant.

Online Installation on Windows* OS

The default electronic installation package for Intel® DAAL for Windows now consists of a smaller installation package that dynamically downloads and then installs packages selected to be installed. This requires a working internet connection and potentially a proxy setting if you are behind an internet proxy. Full packages are provided alongside where you download this online install package if a working internet connection is not available.

Silent Installation on Windows* OS

Silent installation enables you to install Intel® DAAL on a single Windows* machine in a batch mode, without input prompts. Use this option if you need to install on multiple similarly configured machines, such as cluster nodes.

To invoke silent installation:

  1. Go to the folder where the Intel® DAAL package was extracted during unpacking; by default, it is the C:\Program Files\Intel\Download\w_daal_2018.y.xxx folder.
  2. Run setup.exe, located in this folder: setup.exe [command arguments]

If no command is specified, the installation proceeds in the Setup Wizard mode. If a command is specified, the installation proceeds in the non-interactive (silent) mode.

The table below lists possible values of  and the corresponding arguments.

Command

Required Arguments

Optional Arguments

Action

install

output=<file>,
eula={accept|reject}
installdir=<installdir>,
license=<license>,
sn=<s/n>,
log=<log file>

Installs the product as specified by the arguments.

Use the output argument to define the file where the output will be redirected. This file contains all installer's messages that you may need: general communication, warning, and error messages.

Explicitly indicate by eula=accept that you accept the End-user License Agreement.

Use the license argument to specify a file or folder with the license to be used to activate the product. If a folder is specified, the installation program searches for *.lic files in the specified folder. You can specify multiple files/folders by supplying this argument several times or by concatenating path strings with the ";" separator.

Use the sn argument to choose activation of the product through a serial number. This activation method requires Internet connection.

Do not use the sn and license arguments together because they specify alternative activation methods. If you omit both arguments, the installer only checks whether the product is already activated.

Use the log argument to specify the location for a log file. This file is used only for debugging. Support Engineers may request this file if your installation fails.

remove

output=<file>log=<log file>

Removes the product. See the description of the install command for details of the output and log arguments.

repair

output=<file>

log=<log file>

Repairs the existing product installation. See the description of the install command for details of the output and log arguments.

For example, the command line
 setup.exe install -output=C:\log.txt -eula=accept
launches silent installation that prints output messages to the C:\log.txt file.

License File Installation for Windows* OS

If you have an evaluation license and decide to upgrade to a commercial license, you must complete the following steps after obtaining the commercial serial number:

  1. Replace your evaluation license file (.lic file) with the commercial license file you received in the license file directory (the default license directory is "C:\Program Files(x86)\Common Files\Intel\Licenses").
  2. Register the new serial number at https://registrationcenter.intel.com.
  3. Re-installation of Intel® DAAL is not required.

Uninstalling Intel® DAAL for Windows* OS

To uninstall Intel® DAAL, select Add or Remove Programs from the Control Panel and locate the version of Intel® DAAL you wish to uninstall.

Note: Uninstalling Intel® DAAL does not delete the corresponding license file.

Installing Intel® DAAL on Linux* OS

You can install multiple versions of Intel® DAAL and any combination of 32-bit and 64-bit variations of the library on your development system.

These instructions assume you to have an Internet connection. The installation program will automatically download a license key to your system. If you do not have an Internet connection, see the manual installation instructions below.

Interactive installation on Linux* OS

  1. If you received the product as a downloadable archive, first unpack the Intel® DAAL package
    tar -zxvf name_of_downloaded_file
  2. Change the directory (cd) to the folder containing unpacked files.
  3. Run the installation script and follow the instructions in the dialog screens that are presented:
    > ./install.sh
  4. The install script checks your system and displays any optional and critical prerequisites necessary for a successful install. You should resolve all critical issues before continuing the installation. Optional issues can be skipped, but it is strongly recommended that you fix all issues before continuing with the installation.

GUI installation on Linux* OS

If on a Linux* system with GUI support, the installation will provide a GUI-based installation. If a GUI is not supported (for example if running from an ssh terminal), a command-line installation will be provided.

To install Intel® DAAL for Linux* OS  in GUI mode, run shell script (install_GUI.sh).
If a GUI is not supported (for example, if running from an ssh terminal), a command-line installation will be provided.

Silent Installation on Linux* OS

To run the silent install, follow these steps:

  1.  If you received the product as a downloadable archive, first unpack the Intel® DAAL package
    >tar -zxvf name_of_downloaded_file
  2. Change the directory (cd) to the folder containing unpacked files.
  3. Edit the configuration file silent.cfg following the instructions in it:
    1.  Accept End User License Agreement by specifying ACCEPT_EULA=accept instead of default "decline" value;
    2. Specify activation option for the installation.
      • Default option is to use existing license (ACTIVATION_TYPE=exist_lic), please make sure that a working product license file is in place before beginning. The file should be world-readable and located in a standard Intel license file directory, such as /opt/intel/licenses or ~/licenses.
      • To use another way of activation, change the value of ACTIVATION_TYPE variable. You may also need to change the value of ACTIVATION_SERIAL_NUMBER and ACTIVATION_LICENSE_FILE variable for specific activation options.
  4. Run the silent install:
    >./install.sh --silent ./silent.cfg

Tip: You can run install interactively and record all the options into custom configuration file using the following command.
>./install.sh  --duplicate "./my_silent_config.cfg"
After this you can install the package on other machines with the same installation options using
>./install.sh --silent "./my_silent_config.cfg"

License File Installation for Linux* OS

If you have an evaluation license and decide to upgrade to a commercial license, you must complete the following steps after obtaining the commercial serial number:

  1. Replace your evaluation license file (.lic file) with the commercial license file you received in the license file directory (the default license directory is /opt/intel/licenses).
  2. Register the new serial number at https://registrationcenter.intel.com.
  3. Re-installation of Intel® DAAL is not required.

Online Installation on Linux* OS

The default electronic installation package for Intel® DAAL for Linux consists of a smaller installation package that dynamically downloads and then installs packages selected to be installed. This requires a working internet connection and potentially a proxy setting if you are behind an internet proxy. Full packages are provided alongside where you download this online install package if a working internet connection is not available.

Offline Installation on Linux* OS

If the system where Intel® DAAL will be installed disconnected from internet, product may be installed in offline mode.
To install product offline user must provide to installer full path to license file.

License file (.lic file) is included as an attachment to email which sends after purchasing and registration product on IRC. User may request to resend .lic file from IRC. To achieve this go to "My Intel Products" page, select needed update for Intel® DAAL from "Download Latest Update" column. When page with information about selected product update will be opened, click on "Manage" reference in "Licenses" column. When "Manage License" page will be opened, press button "Resend license file to my email".

  1. If product installs in GUI mode: on "Activation options" dialog select "Choose alternative activation" radio button, press "Next" button. On following dialog select "Activate offline" radio button, press "Next" button. On next dialog type full path to license file and press "Next" button.
  2. If product installs in interactive mode: on step 3 "Activation step" select point 4 - "I want to activate by using a license file, or by using Intel(R) Software". On next step choose point 1 - "Activate offline [default]" and type full path to license file.
  3. If product installs in silent mode: in the file silent.cfg set value: license_file for variable: ACTIVATION_TYPE, set full path to license file to variable: ACTIVATION_LICENSE_FILE

Uninstalling Intel® DAAL for Linux* OS

If you installed as root, you will need to log in as root.

To uninstall Intel® DAAL run the uninstall script: <DAAL-install-dir>/uninstall.sh.

Alternatively, you may use GUI mode for uninstall Intel® DAAL for Linux* OS. First, run shell script install_GUI.sh, then select Remove option from menu and press "next" button.

If you installed in the default directory, use:
> /opt/intel/compilers_and_libraries_2017/linux/daal

Uninstalling Intel® DAAL will not delete your license file(s).

Installing Intel® DAAL on macOS*

There are several different product suites available, for example, Intel® Data Analytics Acceleration Library for macOS*, Intel® Parallel Studio XE Composer Edition for C++ macOS*, each including Intel DAAL as one of components. Please read the download web page carefully to determine which product is appropriate for you.

If you will be using Xcode*, please make sure that a supported version of Xcode is installed. If you install a new version of Xcode in the future, you must reinstall the Intel DAAL afterwards.

The installation of the product requires a valid license file or serial number. If you are evaluating the product, you can also choose the “Evaluate this product (no serial number required)” option during installation.

These instructions assume you to have an Internet connection. The installation program will automatically download a license key to your system. If you do not have an Internet connection, see the manual installation instructions below.

Interactive installation on macOS*

  1. If you received the Intel DAAL product as a download, double-click on the downloaded file to begin the installation.
  2. You will be asked to select installation mode. The option Install as root is recommended. Click Next and enter the password. The install wizard will proceed automatically.
  3. If you agree with the End User License Agreement, check the radio button of I accept the terms of the license agreement, and click Next
  4. License Activation Options:
    • Use serial number

      If you do have an Internet connection, skip this step and proceed to the next numbered step (below).

    • Evaluate this product (no serial number required or if you want to activate at a later time).

    • Alternative Activation

      If you do not have an Internet connection, choose Alternative Activation and click Next; there will be two options to choose from:

      • Activate Offline: requires a License File.
      • Use Intel® Software License manager: floating License activation

        Intel® Software License manager
  5. Enter your serial number to activate and install the product.
  6. Activation completed. Click Next to continue.
  7. The Installation Summary dialog box opens to show the summary of your installation options (chosen components, destination folder, etc.). Click Install to start installation (proceed to step 10) or click Customize installation to change settings. If you select "Customize", follow steps 8-10.Installation summary

  8. In the Choose a Destination Folder dialog box, choose the installation directory. By default, it is /opt/intel. But you may choose a different directory. All files are installed into the Intel Parallel Studio XE 2017 subdirectory (by default/opt/intel/compilers_and_libraries_2017/mac/daal).
  9. If you install DAAL from a Parallel Studio XE product, the package contains components for integration into Xcode *. You are able to select the integration to Xcode* on the Choose Integration target dialog box.
  10. The Installation Summary dialog box opens to show the summary of your installation options (chosen components, destination folder, etc.). Click Install to start installation.
  11. Click Finish in the final screen to exit the Intel Software Setup Assistant.

Silent installation on macOS*

Silent installation enables you to install Intel DAAL on a single macOS* machine in a batch mode without input prompts. Use this option if you need to install on multiple similarly configured machines, such as cluster nodes. For information on automated or “silent” install capability, please seehttp://intel.ly/1gcW0Bl

Support of Non-Interactive Custom Installation

Intel DAAL can save user install choices during an ‘interactive’ install in a configuration file that can then be used for silent installs. This configuration file is created when the following option is used from the command line install:

  • export INTEL_SWTOOLS_DUPLICATE_MODE=config_file_name: it specifies the configuration file name. If the full path is specified, the INTEL_SWTOOLS_DOWNLOAD_DIR environment variable is ignored and the installable package is created in the directory with the configuration file.
  • export INTEL_SWTOOLS_DOWNLOAD_DIR=dir_name: optional, it specifies where the configuration file will be created. If this option is omitted, the installation package and the configuration file will be created in the default download directory: /tmp/intel/downloads/<package_id>

License File Installation for macOS*

If you have an evaluation license and decide to upgrade to a commercial license, you must complete the following steps after obtaining the commercial serial number:

  1. Replace your evaluation license file (.lic file) with the commercial license file you received in the license file directory (the default license directory is /opt/intel/licenses).
  2. Register the new serial number at https://registrationcenter.intel.com.
  3. Re-installation of Intel® DAAL is not required.

Uninstalling Intel® DAAL for macOS*

It is not possible to remove the compiler while leaving any of the performance library components installed.

  1. Open the file 
    <install_dir>/parallel_studio_xe_2018.<n>.<pkg>/uninstall.app
  2. Follow the prompts

If you are not currently logged in as root you will be asked for the root password.

Uninstalling Intel® DAAL will not delete your license file(s).

Legal Information

Intel, and the Intel logo are trademarks of Intel Corporation in the U.S. and/or other countries.

*Other names and brands may be claimed as the property of others.

Java is a registered trademark of Oracle and/or its affiliates.

© Copyright 2017, Intel Corporation

Intel® Data Analytics Acceleration Library 2018 Beta System Requirements

$
0
0

Please see the following links to the online resources and documents for the latest information regarding Intel DAAL:

·         Intel® DAAL Product Page

·         Intel® DAAL 2018 Release Notes

·         Intel® DAAL 2018 Installation Guide

·         Intel® DAAL 2018 System Requirements

System Requirements

The Intel® DAAL supports the IA-32 and Intel® 64 architectures. For a complete explanation of these architecture names please read the following article:
Intel Architecture Platform Terminology for Development Tools.

The lists below pertain only to the system requirements necessary to support application development with Intel® DAAL. Please review your compiler (gcc*, Microsoft Visual Studio* or Intel® Compiler Pro) hardware and software system requirements, in the documentation provided with that product to determine the minimum development system requirements necessary to support your compiler product.

Supported Operating Systems

  • Windows 10* 
  • Windows 8*
  • Windows 8.1* 
  • Windows 7* - Note: SP1 is required for use of Intel® AVX instructions
  • Windows Server* 2012 
  • Windows Server* 2016
  • Red Hat* Enterprise Linux* 6 
  • Red Hat* Enterprise Linux* 7 
  • Red Hat Fedora* 25
  • SUSE Linux Enterprise Server* 12
  • SUSE Linux Enterprise Server* 12 SP1
  • Debian* GNU/Linux 8 
  • Ubuntu* 16.04 
  • Ubuntu* 16.10 
  • macOS* 10.12
  • macOS* 10.13

Note: Intel® DAAL is expected to work on many more Linux distributions as well. Let us know if you have trouble with the distribution you use.

Supported C/C++* compilers for Windows* OS:

  • Intel® C++ Compiler 16.0 for Windows* OS
  • Intel® C++ Compiler 17.0 for Windows* OS
  • Intel® C++ Compiler 18.0 for Windows* OS
  • Microsoft Visual Studio* 2013 - help file and environment integration
  • Microsoft Visual Studio* 2015 - help file and environment integration
  • Microsoft Visual Studio* 2017 - help file and environment integration

Supported C/C++* compilers for Linux* OS:

  • Intel® C++ Compiler 16.0 for Linux* OS
  • Intel® C++ Compiler 17.0 for Linux* OS
  • Intel® C++ Compiler 18.0 for Linux* OS
  • GNU Compiler Collection 5.0 and later

Supported C/C++* compilers for macOS*:

  • Intel® C++ Compiler 16.0 for macOS*
  • Intel® C++ Compiler 17.0 for macOS*
  • Intel® C++ Compiler 18.0 for macOS*
  • Xcode* 8
  • Xcode* 9

Supported Java* compilers:

  • Java* SE 7 from Sun Microsystems, Inc.
  • Java* SE 8 from Sun Microsystems, Inc.

Supported Python versions:

  • Intel® Distribution for Python 2.7 (64-bit) for Windows* OS
  • Intel® Distribution for Python 3.5 (64-bit) for Windows* OS
  • Intel® Distribution for Python 2.7 (64-bit) for Linux* OS
  • Intel® Distribution for Python 3.5 (64-bit) for Linux* OS
  • Intel® Distribution for Python 2.7 (64-bit) for macOS*
  • Intel® Distribution for Python 3.5 (64-bit) for macOS*
  • Python* 2.7 (64-bit) for Linux* OS
  • Python* 3.5 (64-bit) for Linux* OS
  • Python* 2.7 (64-bit) for macOS*
  • Python* 3.5 (64-bit) for macOS*

MPI implementations that Intel® DAAL for Windows* OS has been validated against:

MPI implementations that Intel® DAAL for Linux* OS has been validated against:

Database

  • MySQL 5.x
  • KDB+ 3.4

Hadoop* implementations that Intel® DAAL has been validated against:

  • Hadoop* 2.6 and above

Note: Intel® DAAL is expected to work on many more Hadoop* distributions as well. Let us know if you have trouble with the distribution you use.

Spark* implementations that Intel® DAAL has been validated against:

  • Spark* 2.0

Note: Intel® DAAL is expected to work on many more Spark* distributions as well. Let us know if you have trouble with the distribution you use.

API Changes Introduced in Intel® DAAL 2018 Beta

$
0
0

A series of API changes are introduced into Intel® DAAL to improve usability, error handling, and consistency. These changes will start to take effective in Intel DAAL 2018 Beta. The changes discussed below are centered on the C++ API, but similar changes also apply to the Java API and the Python API.

Renaming, addition, and removal of enums

APIBeforeAfter
Error handling
  • Algorithmic classes
    • void compute()
  • Input argument classes
    • void check(...)
  • Result and Partial Result classes
    • void check(...)
    • void allocate(…)
  • Algorithmic classes
    • Status compute()
  • Input argument classes
    • Status check(...)
  • Result and Partial Result classes
    • Status check(...)
    • Status allocate(…)
class Environment
  • static int freeInstance();
  • Method is deprecated
Alternating Least Square initialization
  • One step initialization
  • Two-step initialization to eliminate the need in complex data preparation such as matrix transposing on the user’s side

Alternating Least Square renamings

  • enum Step3LocalCollectionInputId
    • partialModelBlocksToNode
  • Enum Step3LocalCollectionInputId
    • inputOfStep3FromInit
kNN algorithm
  • kdtree_knn_classification_types.h
  • File is removed
k-means initialization in distributed computing mode
  • enum PartialResultId
    • partialClusters
    • partialClustersNumber
  • enum PartialResultId
    • partialCentroids
    • partialClustersNumber is deprecated
K-means namings
  • enum PartialResultId
    • partialGoalFunction
  • enum ResultId
    • goalFunction
  • enum PartialResultId
    • partialObjectiveFunction
  • enum ResultId
    • objectiveFunction
Multi-class classfier Model
  • getTwoClassClassifierModels()
  • Method is deprecated as unsafe
Neural Network training parameter
  • Class Parameter contains batchSize and optimization solver
  • Class Parameter contains optimization solver
  • batchSize is read from parameter of optimization solver
NumericTable
  • void setDictionary( NumericTableDictionary *ddict );
  • virtual void setDictionary( NumericTableDictionary *ddict );
  • virtual void resetDictionary()
  • virtual void setNumberOfColumns(size_t ncol)
  • virtual void setNumberOfRows(size_t nrow)
  • virtual void allocateDataMemory(daal::MemType type = daal::dram)
  • freeDataMemory();
  • All the methods are deprecated
  • One dictionary is associated with NumericTable for the whole life cycle of the respective object; number of attributes can’t be changed
  • Memory allocation by the library is done on the stage of object construction only.
  • Memory deallocation by the library is done on the stage of destruction
NumericTable 
  • resize( nrows ) the method to modify number of feature vectors in the table, involves memory allocation, if necessary. If the memory was allocated by the user, resize() will “forget” about it and allocate another memory
HomogenNumericTable
  • setArray( DataType* const ptr)
  • The method is deprecated as memory management is done at the stage of object construction
AOS Numeric Table
  • void setFeature(size_t idx, size_t offset)
  • void setFeature(size_t idx, size_t offset, data_feature_utils::FeatureType featureType = data_feature_utils::DAAL_CONTINUOUS, size_t categoryNumber=0) Extended API of method to support all types of atteibutes
SOA Numeric Table
  • SOANumericTable( size_t nColumns = 0, size_t nRows = 0 )
  • SOANumericTable( size_t nColumns = 0, size_t nRows = 0, DictionaryIface::FeaturesEqual featuresEqual = DictionaryIface::notEqual ) Manages the case when attributes are equal for further optimizations
Data Dictionary 
  • void setAllFeatures() Add service method to configure the attributes of the datasets to the same type
NumericTable
  • getNumberOfCategories(size_t feature_idx) returns (size_t)-1 when all attribute is continuous, and 2, otheriwse 
  • Range of values returned by the method is extended to support different types of attributes
NumericTable
  • enum AllocationFlag
    • notAllocate
  • enum AllocationFlag
    • doNotAllocate
Tensor
  • enum AllocationFlag
    • notAllocate
  • enum AllocationFlag
    • doNotAllocate
class NumericTableIface
  • enum NormalizationType
    • nonNormalized
    • standardScoreNormalized
  • enum NormalizationType
    • nonNormalized
    • standardScoreNormalized
    • minMaxNormalized
HomogenTensor
  • getSampleTensor(size_t firstDimIndex)
  • Method is deprecated
Algorithms and numeric tables
  • Default type is double
  • Default type is float
Multinomial Naïve Bayes algorithm
  • multinomial_naive_bayes_types.h
  • File is removed
Linear regression algorithm
  • linear_regression_types.h
  • File is removed
Ridge regression algorithm
  • ridge_regression_types.h
  • File is removed
Multi-class classifieralgorithm
  • multi_class_classifier_types
  • File is removed
Neural Networks Topology for training and prediction
  • addNext(layerId1, layerId2);
  • Deprecated
  • Use combination of the available methods for topology object x
  • x.get(layerId1)->addNext(layerId2);
Default data type for algorithms, numeric tables, and data sources 
  • template<typename algorithmFPType = double, Method method = defaultDense>
  • template<typename DataType = double>

class DAAL_EXPORT HomogenNumericTable : public NumericTable

  • template< typename _numericTableType, typename _summaryStatisticsType = double>

class DataSourceTemplate : public DataSource

  • template<typename algorithmFPType = DAAL_ALGORITHM_FP_TYPE, Method method = defaultDense>

DAAL_ALGORITHM_FP_TYPE is float by default

  • template<typename DataType = DAAL_DATA_TYPE>

class DAAL_EXPORT HomogenNumericTable : public NumericTable

DAAL_DATA_TYPE is float by default

  • template< typename _numericTableType, typename _summaryStatisticsType = DAAL_SUMMARY_STATISTICS_TYPE >

class DataSourceTemplate : public DataSource

DAAL_SUMMARY_STATISTICS_TYPE is float by default

 

Methods deprecation 

ClassesMethods deprecated
EnvironmentfreeInstance
Multi-class classifier ModelgetTwoClassClassifierModels
NumericTablesetDictionary, resetDictionary, setNumberOfColumns, setNumberOfRows, allocateDataMemory, freeDataMemory
HomogenNumericTablesetArray
HomogenTensorgetSampleTensor

 

 

 

 

 

 

 

Method signatures change

ClassesBeforeAfter
All algorithmic classesvoid compute( )Status compute( )
All input argument classesvoid check( ... )Status check( ... )
All result and partial result classes

void check( ... )

void allocate( .. )

Status check( ... )

Status allocate( ... )

AOSNumericTablevoid setFeature( size_t idx, size_t offset )vid setFeature( size_t idx, size_t offset, data_feature_utils::FeatureType featureType = data_feature_utils::DAAL_CONTINUOUS, size_t categoryNumber=0 )
SOANumericTableSOANumericTable( size_t nColumns = 0, size_t nRows = 0 )SOANumericTable( size_t nColumns = 0, size_t nRows = 0, DictionaryIface::FeaturesEqual featuresEqual = DictionaryIface::notEqual )
NumericTableThe return value of getNumberOfCategories( size_t feature_idx ) was either (size_t) - 1 when all attributes are continuous, or 1 otherwise.The return value of this method is now extended to support different types of attributes.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

New methods

ClassesNew methods
NumericTablevoid resize( size_t nrows ) - To modify the number of feature vectors in a table.
DataDictionaryvoid setAllFeatures( ... ) - To configure the attributes of the datasets to be the same type.

 

 

 

 

 

 

Other changes

  • Alternating Least Square (ALS) algorithm initialization has been changed from one-step initialization to two-step initialization, to make data preparation easier. For example, users don't have to take matrix transpose on themselves.
  • The Parameter class of the Neural Network training algorithm no longer contains 'batchSize'. The 'batchSize' is now obtained from the corresponding parameter of a optimization solver.  
  • The header file kdtree_knn_classification_types.h is removed.

Can pardiso use the windows virtual memory?

$
0
0

Hi,

I know about the OOC functionality, but if I just want to use the in-core option (iparm(60) = 0), how can I make sure pardiso uses virtual memory (windows 7)? In a large solve with 6 million unknowns, I get the error code -2. After phase 1 I calculate the memory requirement from pardiso as around 30gb, which is more than my available ram, but much less than my available virtual memory. 

Related to this is the following question: what is the exact criterion which causes error code -2?

Best,
Jens

 

Make publicly available the mkl-devel conda package

$
0
0

First, I'd like to congratulate Intel on the awesome initiatives to (1) make MKL freely available through the Community Licensing, (2) develop the super fast Intel Distribution for Python and (3) make it available through Continuum's conda.

There's only one thing that is really missing now: to provide a mkl-devel conda package so that we are able to build other packages that depend on MKL using conda-build locally or on the conda-forge infrastructure.

Continuum already have an internal private mkl-devel package which they use to build their version of numpy and other packages, but they are not able to publish it due to licensing restrictions (despite MKL having a free version already), please see:

https://github.com/ContinuumIO/anaconda-recipes/issues/50

and:

https://github.com/ContinuumIO/anaconda-issues/issues/888

Could Intel make this package available, or provide a way to make it available?

Thanks!

Viewing all 190 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>