Skip to content

Conversation

@Tom-Willemsen
Copy link
Member

Description of work

Fix a warning of the form:

Using UFloat objects with std_dev==0 may give unexpected results.

during fitting. This is caused by lmfit/lmfit-py#999 .

Ticket

n/a

Labels

Add appropriate label(s) to this PR

  • 'bluesky-Semver-Major' - Breaking Change
  • 'bluesky-Semver-Minor' - New feature
  • 'bluesky-bug' - Bug fix
  • 'bluesky-documentation' - Document Changes
  • 'bluesky-ignore-for-release' - Do not show in the release notes

Labels can be found of the right-hand sidebar of this PR once created

Acceptance criteria

  • Pull request title is understandable for a user (e.g. scientist) reading the release notes. The PR title should be a short description of the change from a user perspective.
  • Pull request has appropriate labels for automatic release-notes generation
  • Warning no longer appears

Documentation

n/a

@Tom-Willemsen Tom-Willemsen added the bluesky-bug Back-compatible fixes to existing functionality label Jul 4, 2025
@Tom-Willemsen Tom-Willemsen requested a review from rerpha July 4, 2025 09:14
@rerpha
Copy link
Contributor

rerpha commented Jul 4, 2025

we should take this out once fixed upstream

@rerpha rerpha merged commit 7b8d6b9 into main Jul 4, 2025
13 checks passed
@rerpha rerpha deleted the fix_ufloat_warning branch July 4, 2025 09:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bluesky-bug Back-compatible fixes to existing functionality size/XS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants