Acos

Applicability

Function Usage

Performs element-wise arccosine computation using the following formula:

Prototype

• Pass the temporary space through the sharedTmpBuffer input parameter.
  • All or part of the source operand tensors are involved in computation.

    1 2	template <typename T, bool isReuseSource = false> __aicore__ inline void Acos(const LocalTensor<T>& dstTensor, const LocalTensor<T>& srcTensor, const LocalTensor<uint8_t>& sharedTmpBuffer, const uint32_t calCount)

  • All source operand tensors are involved in computation.

    1 2	template <typename T, bool isReuseSource = false> __aicore__ inline void Acos(const LocalTensor<T>& dstTensor, const LocalTensor<T>& srcTensor, const LocalTensor<uint8_t>& sharedTmpBuffer)

• Allocate the temporary space through the API framework.
  • All or part of the source operand tensors are involved in computation.

    1 2	template <typename T, bool isReuseSource = false> __aicore__ inline void Acos(const LocalTensor<T>& dstTensor, const LocalTensor<T>& srcTensor, const uint32_t calCount)

  • All source operand tensors are involved in computation.

    1 2	template <typename T, bool isReuseSource = false> __aicore__ inline void Acos(const LocalTensor<T>& dstTensor, const LocalTensor<T>& srcTensor)

Due to the complex mathematical computation involved in the internal implementation of this API, additional temporary space is required to store intermediate variables generated during computation. The temporary space can be passed by developers through the sharedTmpBuffer input parameter or allocated through the API framework.

• When the sharedTmpBuffer input parameter is used for passing the temporary space, the tensor serves as the temporary space. In this case, the API framework is not required for temporary space allocation. This enables developers to manage the sharedTmpBuffer space and reuse the buffer after calling the API, so that the buffer is not repeatedly allocated and deallocated, improving the flexibility and buffer utilization.
• When the API framework is used for temporary space allocation, developers do not need to allocate the space, but must reserve the required size for the space.

If sharedTmpBuffer is used, developers must allocate space for the tensor. If the API framework is used, developers must reserve the temporary space. To obtain the size of the temporary space (BufferSize) to be reserved, use the API provided in GetAcosMaxMinTmpSize.

Parameters

Returns

None

Restrictions

• The value range of the input source data is [-1, 1]. If the input is not within the range, the output is invalid.
• The source operand address must not overlap the destination operand address.
• The address of sharedTmpBuffer must not overlap the addresses of the source operand and destination operand.
• For details about the operand address alignment requirements, see General Address Alignment Restrictions.

Example

For a complete example, see Acos operator sample.

1
2
3
4
5

// dstLocal: tensor for storing the computation result
// srcLocal: input tensor involved in computation
// sharedTmpBuffer: temporary buffer for storing intermediate variables during complex internal computation
// The input tensor length is 1,024, the input data type of the operator is half, and the number of actually computed data elements is 512.
AscendC::Acos(dstLocal, srcLocal, sharedTmpBuffer, 512);

1
2
3

// The first and last values are special.
Input (srcLocal): [0.000000 0.001000 0.002000 ... 0.252000 0.253000 -1.000000 1.000000]
Output (dstLocal): [1.570796 1.569796 1.568796 ... 1.316050 1.315016 3.141593 0.000000]