Skip to content

test: migrate stats/base/dists/chi/logpdf to ULP-based assertions - #14839

Draft
kgryte wants to merge 1 commit into
developfrom
kgryte/ulp-chi-logpdf
Draft

test: migrate stats/base/dists/chi/logpdf to ULP-based assertions#14839
kgryte wants to merge 1 commit into
developfrom
kgryte/ulp-chi-logpdf

Conversation

@kgryte

@kgryte kgryte commented Aug 31, 2026

Copy link
Copy Markdown
Member

Resolves a part of #11352.

Description

What is the purpose of this pull request?

This pull request:

The following files are updated:

  • test/test.logpdf.js (was 2.0 * EPS * abs( expected[ i ] )) → 2 ULP
  • test/test.factory.js (was 2.0 * EPS * abs( expected[ i ] )) → 2 ULP
  • test/test.native.js (was 40.0 * EPS * abs( expected[ i ] )) → 2 ULP

ULP bounds

Each bound is the measured minimum. Over the full decimal_decimal.json fixture set (5000 cases), the maximum observed ULP difference against the expected values is 2 for each of the main, factory, and native implementations, attained at x = 0.048002235420554484, k = 2.39848473901088. At 1 ULP, all three implementations fail on that same case; at 0 ULP, six cases fail. The bounds were tightened downward from an initial value of 64 and the suite was run twice at the final value to confirm determinism.

The native add-on was compiled locally (node-gyp rebuild) so that test/test.native.js executes rather than skips; the previous 40.0 * EPS native tolerance turned out to be considerably looser than required, as the C implementation agrees with the JavaScript implementation on this fixture set.

Only test files are touched; no implementation or fixture changes are included.

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

While measuring, I noticed that the native results for this function are sensitive to floating-point contraction: compiling src/main.c with FMA contraction enabled (e.g., -march=native -ffp-contract=fast) raises the maximum observed difference from 2 to 48 ULP. stdlib's binding.gyp builds with -O3 -std=c99 and no -march override, so the 2 ULP bound holds for the add-on as actually built here (verified against the compiled .node), but reviewers may want to confirm on an architecture where FMA contraction is the compiler default (e.g., arm64).

Checklist

Please ensure the following tasks are completed before submitting this pull request.

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of AI assistance?

  • Yes
  • No

If you answered "yes" above, how did you use AI assistance?

  • Code generation (e.g., when writing an implementation or fixing a bug)
  • Test/benchmark generation
  • Documentation (including examples)
  • Research and understanding

Disclosure

If you answered "yes" to using AI assistance, please provide a short disclosure indicating how you used AI assistance. This helps reviewers determine how much scrutiny to apply when reviewing your contribution. Example disclosures: "This PR was written primarily by Claude Code." or "I consulted ChatGPT to understand the codebase, but the proposed changes were fully authored manually by myself.".

This PR was written primarily by Claude Code, running unattended as a scheduled task. It studied previously merged ULP migrations to mirror the established idiom, applied the edits, and searched for the minimum passing ULP bound empirically.


@stdlib-js/reviewers


Generated by Claude Code

Replace relative tolerance comparisons with `isAlmostSameValue` ULP
difference assertions in the `stats/base/dists/chi/logpdf` tests.

Ref: #11352

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UYyqUPEukY4soPWzpgy8RV

---
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: skipped
  - task: lint_markdown_pkg_readmes
    status: na
  - task: lint_markdown_docs
    status: na
  - task: lint_markdown
    status: na
  - task: lint_package_json
    status: na
  - task: lint_repl_help
    status: na
  - task: lint_javascript_src
    status: na
  - task: lint_javascript_cli
    status: na
  - task: lint_javascript_examples
    status: na
  - task: lint_javascript_tests
    status: passed
  - task: lint_javascript_benchmarks
    status: na
  - task: lint_python
    status: na
  - task: lint_r
    status: na
  - task: lint_c_src
    status: na
  - task: lint_c_examples
    status: na
  - task: lint_c_benchmarks
    status: na
  - task: lint_c_tests_fixtures
    status: na
  - task: lint_shell
    status: na
  - task: lint_typescript_declarations
    status: passed
  - task: lint_typescript_tests
    status: na
  - task: lint_license_headers
    status: passed
---
@stdlib-bot stdlib-bot added Statistics Issue or pull request related to statistical functionality. Good First PR A pull request resolving a Good First Issue. labels Aug 31, 2026
@stdlib-bot

Copy link
Copy Markdown
Contributor

Hello! 👋

We've noticed that you've been opening a number of PRs addressing good first issues. Thank you for your interest and enthusiasm!

Now that you've made a few contributions, we suggest no longer working on good first issues. Instead, we encourage you to prioritize cleaning up any PRs which have yet to be merged and then proceed to work on more involved tasks.

Not only does this ensure that other new contributors can work on things and get ramped up on all things stdlib, it also ensures that you can spend your time on more challenging problems. 🚀

For ideas for future PRs, feel free to search the codebase for TODOs and FIXMEs and be sure to check out other open issues on the issue tracker. Cheers!

@stdlib-bot

Copy link
Copy Markdown
Contributor

Coverage Report

Package Statements Branches Functions Lines
stats/base/dists/chi/logpdf $\\color{green}307/307$
$\\color{green}+100.00\\%$
$\\color{green}29/29$
$\\color{green}+100.00\\%$
$\\color{green}4/4$
$\\color{green}+100.00\\%$
$\\color{green}307/307$
$\\color{green}+100.00\\%$

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Good First PR A pull request resolving a Good First Issue. Statistics Issue or pull request related to statistical functionality.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants