Description Kevin Rice 2009-09-10 22:59:58 BST
ByteOrderList is not valid for container and is part of the BinaryEncoding
element.
Ignore or remove from future version.
Even message support is need in XTCE. Adding an EventSet to TelemetryMetaData would be an appropriate location.
Description Kevin Rice 2007-10-22 21:09:15 BST
CheckWindow has no way to vary window size based on context
Description Kevin Rice 2008-05-28 21:45:18 BST
In EntryList, a containerRef that's to an abstract container has special
meaning. perhaps it warrants it own entry to clear up the semantics.
Description Kevin Rice 2008-05-28 21:35:39 BST
CustomAlgorithm which appears in many places in the schema should be a
namereference to AlgorithmSet. To enforce the proper semantics the Ref should
"name" which algorithm type it referes to such as "InputAlgorithmRef" or
"InputOutputAlgorithmRef", etc...
After jaxb runs on the current XTCE 1.2 (after ballot 28) schema. The following methods show weaknesses in the schema type hierarchy (below). It's been shown they schema types can be meaningfully tweaked and these items will map cleanly. It also suggest but is not clear the order of the items in some the lists may not be enforced. for two of the items below this would be bad. this is conjecture however.
>> ArgumentInputSetType.java: public List<Object> getInputParameterInstanceRefOrInputArgumentInstanceRef() {
>> InputSetType.java: public List<Object> getInputParameterInstanceRefOrConstant() {
>> ParameterSetType.java: public List<Object> getParameterOrParameterRef() {
>>
>> ArgumentComparisonCheckType.java: public List<JAXBElement<?>> getRest() {
>> ComparisonCheckType.java: public List<JAXBElement<?>> getRest() {
>> MathOperationCalibratorType.java: public List<JAXBElement<?>> getValueOperandOrThisParameterOperandOrOperator() {
>> MetaCommandSetType.java: public List<JAXBElement<?>> getMetaCommandOrMetaCommandRefOrBlockMetaCommand() {
>>
The reworked XTCE 1.2 from the proposed BitBucket schema has additional checksums (also hashes) and a new XOR element. In addition, there is a missing @parameterRef that should appear to specify the parameter that holds the value. Some systems do not store that so it can be optional.
A mask alarm applies to numerics and enums – although usage in floats is discouraged. It defines 16-states which map 1 to 1 with values (say 1-16), it's a 16-bit mask – each bit is either a care or don't care. If set to 1, it's a care bit. If the value associated with that bit appears, it is in alarm. If the mask bit is set to 0, it's a don't care bit – and the value associated with it will not trip an alarm. When used with enums it's almost like an enum alarm list,except the states can go "past" the range of values given in the enum list itself. For example, suppose an enum had the values of OPEN=1, SHUT=2. The mask could be 0xfffffffc - as one and two are allowed and valid. And any other value would be in alarm. Because there's only two enum values and each of these is green but any other value is read, it is hard to completely simulate this alarm with the enum alarm list. It's possible to use a condition perhaps in this one example but the current syntax requires the enum alarm list. Further transferring this information through to another party will be hard in that case. Reported by JPL.
Description Kevin Rice 2007-10-22 21:37:38 BST
AbsoluteTimeParameterType do not have alarm elements associated with it. In
the current schema this may be by design – an example of a usage for an
alarming absolute time could be helpful. JWST claims to alarm on occurrences
of reverse time which in fact would probably be a packet ordering issue.
Description Kevin Rice 2007-10-22 21:04:10 BST
Move Alarms outside of Type area. Alarms may change a lot and it may be easier
to have them set in the Parameter area, further alarms and calibrators, as well
as the time types reference Parameters directly which seems inconsistent with
them being in types.
C-S/CNES
Ludovic Faure
XTCE alarms are associated with data types and come in a default and context set form. A variety of alarm types are associated with each data type, some specific to it (such enum alarms). However this is too restrictive to meet the needs of many of organizations. Specifically the following is requested: allow set of alarms without a required context by data type. Original reporter is JPL.
Added specific support for reed-solomon and turbo encoding, among others in the stream set. Reported by JPL.
A gap entry is an addressing mechanism to move the address pointer relative or absolutely as specified in the gap entry. This is an alternate approach to XTCE's location in container element. Reported by JPL.
The IndirectParameterRefEntry is a clever construct that has the potential to be useful, although I am not aware of anyone who has used it.
I suggest that we consider removing it because it is a limited case of the more general case solved by the IncludeCondition element. The IncludeCondition can provide this functionality and a lot more. As a result, this element is effort for implementers that doesn't add anything really "new". In addition, it leaves a case where the need is addressed in more than 1 way - which is generally not the best idea.
Description Kevin Rice 2007-10-22 21:11:43 BST
Message, IncludeCondition and BaseContainer do similar things and should be
unified
Comment 1 Kevin Rice 2007-10-22 21:21:03 BST
Message, IncludeCondition and BaseContainer do similar things and should be
unified
Description Kevin Rice 2007-10-22 21:48:47 BST
Some organizations wish to capture counts to units on the telemetry side & then
units to counts on command side (often called reverse or inverse calibrators).
In some cases they may wish to both for various reasons, often in testing
scenarios to validate their operation calibration. XTCE does not provide an
easy way to mark a calibrator as either 'reverse' or 'forward'.
Description Kevin Rice 2008-03-04 22:57:09 GMT
Expand NameReference concept to allow specifying items in precise locations
such as TelemetryMetaData, CommandMetaData, etc...
Description Kevin Rice 2008-05-28 21:39:55 BST
RestrictionCriteria seems incorrect for commands. the value checked are
inserted to form the command, operators seem a little strange, maybe only '=='
makes sense, etc...
Allow for local argument types to be defined in MetaCommand, helps avoid collisions with arguments in other commands of the same name but different properties.
Absolute and Relative time should have a "baseType" similar to the other scalar data types. This is probably an oversight.
I am not sure that this attribute makes sense in the String data type definitions. The character encoding (@encoding) element really should capture the knowledge here, but there could be a nuance I am unsure about.
Check on this in the committee meeting. Propose to remove the attribute.
Reported by Michel Sibon of Thales. There is a spelling error of the word "Agument" in RelativeTimeArgumentType in XTCE 1.2 proposed. It has been present for some time because it is also reflected in the xtcetools schema file that was based on an early XTCE 1.2 releae schema.
<element name="RelativeTimeAgumentType" type="xtce:RelativeTimeArgumentType">
<annotation>
<documentation xml:lang="en">Describe an argument type that has an engineering/calibrated value in the form of a duration in time.</documentation>
</annotation>
</element>
The text above is from the RTF report version of the file.
Description Kevin Rice 2008-05-28 21:41:50 BST
OCL is an OMG standard that adds a constraint language to UML or any model.
It's related to RestrictionCriteria. Would a specific XTCE Algorithm for OCL
be useful?
A switch entry is similar to the switch/case statement provided in most programming languages, and would improve upon the include condition currently found in XTCE. Reported by JPL.
Variables are local values created from bit/sub-bits specified in the entry list of container. They are similar to parameters but exist only within the scope of the container they are defined – they are of type integer. Reported by JPL.
The annotation below would be better served as an optional attribute with the specified format as the default. From a telemetry stantpd this would be interpreted as optional display info, and from an argument standpt the user input string format. "Used to contain an absolute time. Contains an absolute (to a known epoch) time. Use the [ISO 8601] extended format CCYY-MM-DDThh:mm:ss where "CC" represents the century, "YY" the year, "MM" the month and "DD" the day, preceded by an optional leading "-" sign to indicate a negative number. If the sign is omitted, "+" is assumed. The letter "T" is the date/time separator and "hh", "mm", "ss" represent hour, minute and second respectively. Additional digits can be used to increase the precision of fractional seconds if desired i.e. the format ss.ss... with any number of digits after the decimal point is supported. "
Outside of the SpaceSystem and systemName, a general mechanism for categorizing @name elements into one or groups is needed. Reported by JPL.