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

Ill-Defined Behavior When Over-Defining Parameters #233

Open
jacobson3 opened this issue Nov 21, 2022 · 0 comments
Open

Ill-Defined Behavior When Over-Defining Parameters #233

jacobson3 opened this issue Nov 21, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@jacobson3
Copy link
Contributor

The custom device allows messages with parameters which overlap other parameters. This can be useful if you are receiving information as you can print both the "parameterized" and "raw" data simultaneously and both VS channels are simply reading from the same data source. However, if you over-define data that you are transmitting you end up with two parameter channels which are both supposed to write to the same hardware buffer. This behavior is ill-defined and the custom device should probably throw some configuration error if the parameters aren't being defined correctly.

Zip attached with BC and RT parameter/hardware xml files. Relevant XML below.

params.zip

@jacobson3 jacobson3 added the enhancement New feature or request label Nov 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant