feat: add stats/strided/dmskmean

[Om-A-osc]

---

type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes. report:

• task: lint_filenames status: passed
• task: lint_editorconfig status: passed
• task: lint_markdown status: passed
• task: lint_package_json status: passed
• task: lint_repl_help status: passed
• task: lint_javascript_src status: passed
• task: lint_javascript_cli status: na
• task: lint_javascript_examples status: passed
• task: lint_javascript_tests status: passed
• task: lint_javascript_benchmarks status: passed
• task: lint_python status: na
• task: lint_r status: na
• task: lint_c_src status: passed
• task: lint_c_examples status: passed
• task: lint_c_benchmarks status: passed
• task: lint_c_tests_fixtures status: na
• task: lint_shell status: na
• task: lint_typescript_declarations status: passed
• task: lint_typescript_tests status: passed
• task: lint_license_headers status: passed
  ---Resolves none.

Description

This pull request adds the @stdlib/stats/strided/dmskmean package.

The package provides a strided masked mean function for double-precision arrays and includes the C implementation, JavaScript interface, ndarray variant, tests, benchmarks, and documentation.

Related Issues

None.

Questions

No.

Other

No.

Checklist

• Read, understood, and followed the contributing guidelines.

AI Assistance

• No

---

@stdlib-js/reviewers

[stdlib-bot]

Hello! Thank you for your contribution to stdlib.

We noticed that the contributing guidelines acknowledgment is missing from your pull request. Here's what you need to do:

1. Please read our contributing guidelines.

2. Update your pull request description to include this checked box:

   - [x] Read, understood, and followed the [contributing guidelines](https://github.com/stdlib-js/stdlib/blob/develop/CONTRIBUTING.md)

This acknowledgment confirms that you've read the guidelines, which include:

• The developer's certificate of origin
• Your agreement to license your contributions under the project's terms

We can't review or accept contributions without this acknowledgment.

Thank you for your understanding and cooperation. We look forward to reviewing your contribution!

[stdlib-bot]

Hello! Thank you for your contribution to stdlib.

We noticed that the contributing guidelines acknowledgment is missing from your pull request. Here's what you need to do:

1. Please read our contributing guidelines.

2. Update your pull request description to include this checked box:

   - [x] Read, understood, and followed the [contributing guidelines](https://github.com/stdlib-js/stdlib/blob/develop/CONTRIBUTING.md)

This acknowledgment confirms that you've read the guidelines, which include:

• The developer's certificate of origin
• Your agreement to license your contributions under the project's terms

We can't review or accept contributions without this acknowledgment.

Thank you for your understanding and cooperation. We look forward to reviewing your contribution!

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
stats/strided/dmskmean	$\color{green}411/411$ $\color{green}+100.00%$	$\color{green}26/26$ $\color{green}+100.00%$	$\color{green}4/4$ $\color{green}+100.00%$	$\color{green}411/411$ $\color{green}+100.00%$

The above coverage report was generated for the changes in this PR.

[kgryte]

This isn't how this particular package should be implemented. Notice how dmean is intended to simply wrap a particular implementation, not include an actual implementation itself. That is intentional.

Ref:

stdlib/lib/node_modules/@stdlib/stats/strided/dmean/lib/ndarray.js

Line 23 in b0950ed

var dmeanpn = require( '@stdlib/stats/strided/dmeanpn' ).ndarray;

Hence, in order for this PR to move forward, the corresponding implementation to be wrapped needs to be added first.

[kgryte]

Right, and just looking at how dmeanpn is implemented, we'd need dmsknsumpw, etc, which are effectively blocked until structured type work is begun.

[Om-A-osc]

Understood. Should I close this pr then ?

[kgryte]

No. It is just blocked until the prerequisites are completed.

[kgryte]

As commented, we need the upstream implementation to be added first.

[kgryte]

You're using ORS which is known to be numerically unstable. This is the reason we use pairwise summation in dmeanpn.