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

RUN keys in mockdata must be scalar but use last CONTROL key's dimensions #429

Open
philsmt opened this issue Jul 14, 2023 · 0 comments
Open

Comments

@philsmt
Copy link
Contributor

philsmt commented Jul 14, 2023

I found a peculiar bug in extra_data.tests.mockdata.base while creating new virtual sources for EXtra tests. When the RUN keys are created in DeviceBase.write_control, the dims symbol from the last iteration of CONTROL keys is used as RUN keys cannot even define their own dimension and hence are assumed to be scalar.

(1,) + dims, datatype, data=[value], maxshape=((None,) + dims))

We have not used non-scalar RUN keys before, but they can exist (abstractInterface e.g., something I was meaning to expose). So the proper fix is probably here to introduce a fourth element to the extra_run_keys tuple`?

@takluyver

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

No branches or pull requests

1 participant