Athan
Athan
@Daniel777y Yes, this would be useful. Note, however, that you'll want to accommodate older Node.js environments not supporting the `options` object (and hence `recursive`). You can consult https://github.com/isaacs/node-mkdirp, but note...
Yes, I think that makes sense.
Use FreeBSD v12.2.0. Our `log1p` probably needs to be updated, as I imagine that the `fdlibm` implementation is somewhat out-of-date.
@gunjjoshi Yes, feel free to go ahead and create `roundf`. Now that `round` has a C implementation, this should hopefully be more straightforward.
@headlessNode A couple of links: - Non-moving version: https://github.com/stdlib-js/stdlib/tree/develop/lib/node_modules/%40stdlib/stats/incr/kurtosis. - Example of moving implementation where we calculate the moving variance: https://github.com/stdlib-js/stdlib/tree/develop/lib/node_modules/%40stdlib/stats/incr/mvariance - Non-moving version for calculating the variance: https://github.com/stdlib-js/stdlib/blob/develop/lib/node_modules/%40stdlib/stats/incr/variance/lib/main.js As...
@headlessNode Yes, that is correct. It may be straightforward to implement, but IIRC can be a little tricky getting the update equations into a nice form amenable to a single-pass...
You may; TBH, I am not sure. I'd need to do the R&D. I suggest consulting the reference literature linked to in the `incr/kurtosis` package and starting from there.
Yes, it may be quite likely you'd need to derive the update equations yourself. IIRC, I remember sitting down with pen and paper when originally implementing kurtosis and skewness.
For reference, we could alternatively have the signature be ```c rempio2( const double x, double *y1, double *y2 ); ``` Where `y1` and `y2` are pointers for storing output values....
This has now been implemented. Closing...