-
Notifications
You must be signed in to change notification settings - Fork 47
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
Reading configuration of devices in a run doesn't work with tiled server #820
Comments
So we narrowed it down a little, I had a mismatch between the datatype reported in noisy_det.noise.describe()
--> {'noisy_det_noise': {'source': 'SIM:noisy_det_noise',
'dtype': 'integer',
'shape': [],
'enum_strs': ('none', 'poisson', 'uniform')}}
det.noise.read()
--> {'noisy_det_noise': {'value': 'uniform', 'timestamp': 1727074877.150907}} And if there is a single mismatch, db[-1].primary.config['motor'].read() # this returns config data
db[-1].primary.config['det'].read() # this fails Further investigation:But after fixing the mismatch in my code, reading Example:So if a Signal similar to this one is present reading the config data from tiled fails. await gas_dosing.massflow_contr1.status.describe()
--> {'gas_dosing-massflow_contr1-status': {
'source': 'localhost:10800:gas_dosing:massflow_contr1:status',
'dtype_str': '|V408',
'dtype_descr': "[('f0', '<i8'), ('f1', '<U100')]",
'dtype': 'array',
'shape': []}
}
await gas_dosing.massflow_contr1.status.read()
--> {'gas_dosing-massflow_contr1-status': {'value': array((100, 'at target'), dtype=[('f0', '<i8'), ('f1', '<U100')]),
'timestamp': 1727076275.2028334}} Note: |
Thanks @Bilchreis. It may be next week until we properly follow up, as several of us are at a conference this week. Two immediate thoughts:
|
@danielballan So i think I found the issue: [("name", "U10"), ("age", "i4"), ("weight", "f4")] When I put leading to this type error:
I guess the |
Thanks @Bilchreis! Would you give this branch a try and check that it fully addresses the issue? If so we can add a unit test. |
Hmm, now I get this shape mismatch, when accessing the data:
I am not sure why the reported shape suddenly is (2,3). when i make an api-call to
|
This issue seems somewhat similar to #745
Expected Behavior
With databroker backed by intake I am able to access the configuration parameters of devices like this:
This gives an xarray of device configuration parameters. I would like the same functionality using a databroker with a tiled server like this:
Current Behavior
I get the following error when I try to access the config data:
Possible Solution
Steps to Reproduce (for bugs)
Context
I want to use the data inside the configuration parameters to populate a Nexus File . Similarly to the Issue #745 the data is still accessible under:
Your Environment
The text was updated successfully, but these errors were encountered: