Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix contributed component type mismatches #1714

Merged
merged 2 commits into from
Sep 25, 2024
Merged

Conversation

g5t
Copy link
Contributor

@g5t g5t commented Sep 25, 2024

Fixes #1713 by removing compiler warnings; correct behavior of test instruments not verified.

g5t added 2 commits September 25, 2024 17:21
In the StatisticalChopper_Monitor.comp a `int *` component parameter is
retrieved but was not de-referenced, so the `int **` was inadvertently
assigned to an `int *` parameter.
@g5t g5t requested a review from willend September 25, 2024 15:29
@willend
Copy link
Contributor

willend commented Sep 25, 2024

Meaningful patches @g5t, thanks.

I've run handheld tests with 3.5.1 and the patched components:

  • The Mono instrument seems stable numerically
  • The Statisticalchopper instrument performs differently, but in this case it would (to me) make sense to correct the "Expected output" later

i.e. merge - and I will postfix the test

@willend willend merged commit ee841a9 into McStasMcXtrace:main Sep 25, 2024
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Example instruments give type-mismatch compiler warnings
2 participants