You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The `N` and stride parameters determine which elements in the input strided array are accessed at runtime. For example, to scale every other value in `zx` by `za`,
59
+
The `N` and stride parameters determine which elements in the input strided array are accessed at runtime. For example, to scale every other value in `x` by `alpha`,
60
60
61
61
```javascript
62
62
var Complex128Array =require( '@stdlib/array/complex128' );
63
63
var Complex128 =require( '@stdlib/complex/float64/ctor' );
The function has the following additional parameters:
118
118
119
-
-**offsetX**: starting index for `zx`.
119
+
-**offsetX**: starting index for `x`.
120
120
121
121
While [`typed array`][mdn-typed-array] views mandate a view offset based on the underlying buffer, the offset parameter supports indexing semantics based on a starting index. For example, to scale every other value in the input strided array starting from the second element,
122
122
123
123
```javascript
124
124
var Complex128Array =require( '@stdlib/array/complex128' );
125
125
var Complex128 =require( '@stdlib/complex/float64/ctor' );
#### zscal.Module.prototype.ndarray( N, zap, zxp, sx, ox )
230
230
231
-
Scales values from `zx` by `za` using alternative indexing semantics.
231
+
Scales values from `x` by `alpha` using alternative indexing semantics.
232
232
233
233
<!-- eslint-disable node/no-sync -->
234
234
@@ -301,7 +301,7 @@ The function has the following additional parameters:
301
301
302
302
## Notes
303
303
304
-
- If `N <= 0`, `zx` is left unchanged.
304
+
- If `N <= 0`, `x` is left unchanged.
305
305
- This package implements routines using WebAssembly. When provided arrays which are not allocated on a `zscal` module memory instance, data must be explicitly copied to module memory prior to computation. Data movement may entail a performance cost, and, thus, if you are using arrays external to module memory, you should prefer using [`@stdlib/blas/base/zscal`][@stdlib/blas/base/zscal]. However, if working with arrays which are allocated and explicitly managed on module memory, you can achieve better performance when compared to the pure JavaScript implementations found in [`@stdlib/blas/base/zscal`][@stdlib/blas/base/zscal]. Beware that such performance gains may come at the cost of additional complexity when having to perform manual memory management. Choosing between implementations depends heavily on the particular needs and constraints of your application, with no one choice universally better than the other.
306
306
-`zscal()` corresponds to the [BLAS][blas] level 1 function [`zscal`][zscal].
0 commit comments