-
Notifications
You must be signed in to change notification settings - Fork 91
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
SAMPLE
cannot be represented as a DATA_SET
#500
Comments
I’ll need to check the code. I’m not sure if we’ve done a sample as a data set as of yet. It should override he sample category conversion, but I’m not sure what takes precidece. You’re right this is not the behavior desired.
…Sent from my iPad
|
what is the functional or parsing difference between a sample and an event? or are they truely just 'categories'? |
They are just categories, but a sample is fixed as a floating point number where as an event can have a controlled vocabulary or a string value. Representation is handled as a special case when parsing.
I may have inverted the checks on the observation factory method that messed this up. I’ll check tomorrow. The code is fairly complex handling all the type construction and checks.
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was expecting to be able to represent a sample as a dataset, but the agent complains about not being able to convert to a double:
SHDR:
Agent log:
device.xml:
the use case here is a digital twin of a 6-axis robot. the joint angles are provided from the robot.
It seems to work if i change
category="EVENT"
instead ofSAMPLE
. technicallytype="ANGLE"
is not anEVENT
, but the agent doesnt seem to care about that?Is there a better way to model this?
The text was updated successfully, but these errors were encountered: