Closed emgre closed 5 years ago
My understanding is TimeAccuracyKind is a 5 bit integer 0..31 for the values below, where for example the enum T0 has the integer value of 7
On Wednesday, August 14, 2019, 11:00:14 AM MDT, Émile Grégoire <notifications@github.com> wrote:
Closes #57. gooseStructure: # GOOSE structure definition
[...]
A:
net:
cVal:
q:
quality-field-type: mapped
name: "A.q"
quality-mapping-type: copy
template-id: default-quality
t:
timestamp-field-type: mapped
name: "A.t"
time-quality-name: "A.tq"
quality-mapping-type: constant
template-id: default-time-quality
When a quality is mapped, you need to specify the following things:
name: The name that appears in gooseStructure (must be a bitstring), where the value will be written to.
quality-mapping-type: Enumeration specifying how the value is obtained.
template-id (only for constant and constant_if_absent): ID of the template used.
When a timestamp is mapped, you can specify the following things:
name: The name that appears in gooseStructure (must be a time type) where the timestamp value (not the quality!) will be written to.
time-quality-name: The name that appears in gooseStructure (must be a bitstring) where the timestamp quality will be written to.
quality-mapping-type: Enumeration specifying how the value is obtained.
template-id (only for constant and constant_if_absent): ID of the template used.
The constant templates are defined at the top of the YAML. You give each of them an unique ID and assign the different values.
❓ @larrylackey: I don't know how to map the TimeAccuracyKind into the bitstring. Do you have info on that?
You can view, comment on, or merge this pull request online at:
https://github.com/openenergysolutions/openfmb.adapters/pull/62
Commit Summary
File Changes
Patch Links:
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
Good, I added it.
@emgre Need to rebase. Same thing, need the determinism.
Done.
Closes #57.
When a quality is mapped, you need to specify the following things:
name
: The name that appears ingooseStructure
(must be a bitstring), where the value will be written to.quality-mapping-type
: Enumeration specifying how the value is obtained.copy
: The value will be copied from the OpenFMB proto.constant
: The value will be constant, based on the templatetemplate-id
.constant_if_absent
: If there is a value in the OpenFMB proto, it is used. Otherwise, it uses the constant based on the templatetemplate-id
.template-id
(only forconstant
andconstant_if_absent
): ID of the template used.When a timestamp is mapped, you can specify the following things:
name
: The name that appears ingooseStructure
(must be a time type) where the timestamp value (not the quality!) will be written to.time-quality-name
: The name that appears ingooseStructure
(must be a bitstring) where the timestamp quality will be written to.quality-mapping-type
: Enumeration specifying how the value is obtained.copy
: The value will be copied from the OpenFMB proto.constant
: The value will be constant, based on the templatetemplate-id
.constant_if_absent
: If there is a value in the OpenFMB proto, it is used. Otherwise, it uses the constant based on the templatetemplate-id
.template-id
(only forconstant
andconstant_if_absent
): ID of the template used.The constant templates are defined at the top of the YAML. You give each of them an unique ID and assign the different values.
❓ @larrylackey: I don't know how to map the
TimeAccuracyKind
into the bitstring. Do you have info on that?