You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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`?
I found a peculiar bug in
extra_data.tests.mockdata.base
while creating new virtual sources for EXtra tests. When theRUN
keys are created inDeviceBase.write_control
, thedims
symbol from the last iteration ofCONTROL
keys is used asRUN
keys cannot even define their own dimension and hence are assumed to be scalar.EXtra-data/extra_data/tests/mockdata/base.py
Line 73 in 6a889bc
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 theextra_run_keys
tuple`?@takluyver
The text was updated successfully, but these errors were encountered: