Developer Reference for Intel® oneAPI Math Kernel Library for Fortran

ID 766686
Date 3/22/2024
Public
Document Table of Contents

vslConvNewTaskX/vslCorrNewTaskX

Creates a new convolution or correlation task descriptor for multidimensional case and assigns source data to the first operand vector.

Syntax

status = vslsconvnewtaskx(task, mode, dims, xshape, yshape, zshape, x, xstride)

status = vsldconvnewtaskx(task, mode, dims, xshape, yshape, zshape, x, xstride)

status = vslcconvnewtaskx(task, mode, dims, xshape, yshape, zshape, x, xstride)

status = vslzconvnewtaskx(task, mode, dims, xshape, yshape, zshape, x, xstride)

status = vslscorrnewtaskx(task, mode, dims, xshape, yshape, zshape, x, xstride)

status = vsldcorrnewtaskx(task, mode, dims, xshape, yshape, zshape, x, xstride)

status = vslccorrnewtaskx(task, mode, dims, xshape, yshape, zshape, x, xstride)

status = vslzcorrnewtaskx(task, mode, dims, xshape, yshape, zshape, x, xstride)

Include Files

  • mkl.fi, mkl_vsl.f90

Input Parameters

Name

Type

Description

mode

INTEGER

Specifies whether convolution/correlation calculation must be performed by using a direct algorithm or through Fourier transform of the input data. See Table "Values of mode parameter" for a list of possible values.

dims

INTEGER

Rank of user data. Specifies number of dimensions for the input and output arrays x, y, and z used during the execution stage. Must be in the range from 1 to 7. The value is explicitly assigned by the constructor.

xshape

INTEGER, DIMENSION(*)

Defines the shape of the input data for the source array x. See Data Allocation for more information.

yshape

INTEGER, DIMENSION(*)

Defines the shape of the input data for the source array y. See Data Allocation for more information.

zshape

INTEGER, DIMENSION(*)

Defines the shape of the output data to be stored in array z.See Data Allocation for more information.

x

REAL*8 for real data in double precision flavors,

COMPLEX*8 for complex data in single precision flavors,

COMPLEX*16 for complex data in double precision flavors

REAL(KIND=4), DIMENSION (*) for real data in single precision flavors,

REAL(KIND=8), DIMENSION (*) for real data in double precision flavors,

COMPLEX(KIND=4), DIMENSION (*) for complex data in single precision flavors,

COMPLEX(KIND=8), DIMENSION (*) for complex data in double precision flavors

Pointer to the array containing input data for the first operand vector.See Data Allocation for more information.

xstride

INTEGER, DIMENSION(*)

Strides for input data in the array x.

Output Parameters

Name

Type

Description

task

INTEGER*4 task(2) for vslscorrnewtaskx, vsldcorrnewtaskx, vslccorrnewtaskx, vslzcorrnewtaskx

TYPE(VSL_CONV_TASK) for vslsconvnewtaskx, vsldconvnewtaskx, vslcconvnewtaskx, vslzconvnewtaskx

TYPE(VSL_CORR_TASK) for vslscorrnewtaskx, vsldcorrnewtaskx, vslccorrnewtaskx, vslzcorrnewtaskx

VSLCorrTaskPtr* for vslsCorrNewTaskX, vsldCorrNewTaskX, vslcCorrNewTaskX, vslzCorrNewTaskX

Pointer to the task descriptor if created successfully or NULL pointer otherwise.

status

INTEGER

Set to VSL_STATUS_OK if the task is created successfully or set to non-zero error code otherwise.

Description

Each vslConvNewTaskX/vslCorrNewTaskX constructor creates a new convolution or correlation task descriptor with the user specified values for explicit parameters. The optional parameters are set to their default values (see Table "Convolution and Correlation Task Parameters").

Unlike vslConvNewTask/vslCorrNewTask, these routines represent the so called X-form version of the constructor, which means that in addition to creating the task descriptor they assign particular data to the first operand vector in array x used in convolution or correlation operation. The task descriptor created by the vslConvNewTaskX/vslCorrNewTaskX constructor keeps the pointer to the array x all the time, that is, until the task object is deleted by one of the destructor routines (see vslConvDeleteTask/vslCorrDeleteTask).

Using this form of constructors is recommended when you need to compute multiple convolutions or correlations with the same data vector in array x against different vectors in array y. This helps improve performance by eliminating unnecessary overhead in repeated computation of intermediate data required for the operation.

The parameters xshape, yshape, and zshape define the shapes of the input and output data provided by the arrays x, y, and z, respectively. Each shape parameter is an array of integers with its length equal to the value of dims. You explicitly assign the shape parameters when calling the constructor. If the value of the parameter dims is 1, then xshape, yshape, and zshape are equal to the number of elements read from the arrays x and y or stored to the array z. Note that values of shape parameters may differ from physical shapes of arrays x, y, and z if non-trivial strides are assigned.

The stride parameter xstride specifies the physical location of the input data in the array x. In a one-dimensional case, stride is an interval between locations of consecutive elements of the array. For example, if the value of the parameter xstride is s, then only every sth element of the array x will be used to form the input sequence. The stride value must be positive or negative but not zero.