Stream: connectathon mgmt
Topic: DevDays16 - Profiling
Michel Rutten (Nov 15 2016 at 16:51):
To all participants of the DevDays 2016 profiling track, here you can download the exercises for the profiling workshop: http://bit.ly/2gdKQb2
Michel Rutten (Nov 16 2016 at 11:07):
Note: The initial Forge BETA release has a bug concerning slicing, so you cannot use it to complete Exercise 4. I've just deployed an update that fixes the bug. If you've already downloaded the Forge BETA release, then please re-download the ZIP file (the size of the new ZIP file is 5.663.142 bytes) and extract in place, overwriting the existing binaries. And if you find any other bugs, please let me know!
Michel Rutten (Nov 17 2016 at 11:12):
We will be doing a Profiling break out session today after lunch in The Muhammad starting at 13:30. We will demonstrate the use of Forge and Simplifier. Everybody is welcome to join!
Michel Rutten (Nov 17 2016 at 12:21):
Correction: David Hay will kick off the profiling break out session in the Richard at 13:30 with a demo of the ClinFhir profiling tool. After about an hour I will take over and demo Forge & Simplifier. All are invited!
David Hay (Nov 17 2016 at 12:31):
and welcome!
Christian Jeppesen (Nov 17 2016 at 12:56):
moved
Brian Reinhold (Nov 20 2016 at 15:03):
In the Furore profiling tool, how would a specify a conditional where if it is done, it shall be done this way but it does not have to be done. In my case I am thinking of slicing an identifier which is an array. There shall be one set of codes that is always present. However, one may also use the Bluetooth address as an additional identifier if the device is a BT device. However, if one chooses to add this identifier, it shall be done as specified.
I know how to write this in standard normative text, but how is it done in profiling. My guess is as follows.
Slice the identifier.
The discriminator is the system
The first identifier is 1...1
the system is the IEEE urn
the value is an EUI-64 system id
The second identifier is 0...1 but the fields in the identifier are defined.
the system is some BT urn (though I don't know what that is yet)
the value is the BT address
The third identifier is 0...1 but the fields in the identifier are defined.
the system is some USB urn (though I don't know what that is yet)
the value is the VID and PID numbers
Brian Reinhold (Nov 20 2016 at 15:07):
Okay i wanted to delete this entirely and make a new topic but that didn't work either. So now there is a bunch of crap that all looks like one topic. It ain't!
Brian Reinhold (Nov 20 2016 at 15:17):
Where does one obtain 'system' values. For example I know that the system specifying IEEE 11073 is urn:
urn:iso:std:iso:11073:10101
Where would I get these for Bluetooth MAC addresses and USB pid and vid identifiers? Do they even exist?
Grahame Grieve (Nov 20 2016 at 16:36):
bluetooth: this is what we talked about before:
{
"use":"official",
"system":"http://ietf.org/eui-48",
"value":"00:3E:42:FF:B2:01",
"assigner":{
"reference":"Bluetooth SIG"
}
}
Grahame Grieve (Nov 20 2016 at 16:36):
I don't think we've ever talked about USB identifiers before
Thomas Tveit Rosenlund (Nov 21 2016 at 13:31):
@Michel Rutten Did you manage to fix the bug that the beta Forge tool did not save changes, unless you forced it?
Michel Rutten (Nov 21 2016 at 14:11):
@Thomas Tveit Rosenlund not yet. This week we will try to fix (most of) the bugs that we found during the DevDays. Then we will publish an official new release, which will be announced via Zulip. Stay tuned...
Thomas Tveit Rosenlund (Nov 22 2016 at 07:49):
@Michel Rutten Great, looking forward to it!
Last updated: Apr 12 2022 at 19:14 UTC
