Skip to content
This repository has been archived by the owner on Jan 11, 2024. It is now read-only.

access to channel metadata #5

Open
danielhrisca opened this issue Apr 15, 2019 · 6 comments
Open

access to channel metadata #5

danielhrisca opened this issue Apr 15, 2019 · 6 comments

Comments

@danielhrisca
Copy link

Hello, is it planned to have access to channel metadata (user configured name, units, filtering ...) using the streaming spec?

@gatzka
Copy link
Contributor

gatzka commented Apr 23, 2019

Hi!
Not for the moment and it's unlikely that those metadata will make it into the protocol. The unit is probably the only one.

The intention of the streaming protocol is to have all information available to display a correct graph. It's not intended to carry all information how a channel was setup.

@danielhrisca
Copy link
Author

Not for the moment and it's unlikely that those metadata will make it into the protocol. The unit is probably the only one.

I think the user defined name and unit are needed.

Any chance the hbm protocol could also be realeased?

@gatzka
Copy link
Contributor

gatzka commented Apr 23, 2019

I think the user defined name and unit are needed.
Ack.

Any chance the hbm protocol could also be realeased?
No, there are no plans.

May I ask what your intention is? Do want to use the protocol for your own devices or for integrating HBM QuantumX devices into your own software?

@danielhrisca
Copy link
Author

danielhrisca commented Apr 23, 2019

I'm writing and acquisition application to gather data from different source/devices (HBM, NI, generic XCP ..)

Edit: the application is written in Python

@danielhrisca
Copy link
Author

@gatzka

do you have updates regarding this issue?

@danielhrisca
Copy link
Author

ping @gatzka

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants