Our current configuration has the following structure:
modules:
....
cfe_es:
#telemetry and telecommanding data
...
cf:
#telemetry and telecommanding data
In XTCE generated by auto-yamcs we get the expected structure:
<SpaceSystem:cfe>
#telemetry and telecommanding data
</SpaceSystem:cfe>
<SpaceSystem:cf>
#telemetry and telecommanding data
</SpaceSystem:cf>
The XTCE is what we expect; cfe and cfe_es are completely separate namespaces independent of each other.
However, when YAMCS parses the XTCE it looks like this on the YAMCS webapp:
<SpaceSystem:cfe>
#telemetry and telecommanding data
<SpaceSystem:cf>
#telemetry and telecommanding data
</SpaceSystem:cf>
</SpaceSystem:cfe>
The namespaces are nested, but this is incorrect; it is not what is defined on XTCE. This needs further investigation, but I highly suspect that the YAMCS webapp is globbing(using regex such "*") and it thinks that anything starting with cf* should be inside the "cf" folder. While, so far, this has not caused issues with sending telemetry or telecommanding, it is unexpected behavior that we should address.
Our current configuration has the following structure:
In XTCE generated by auto-yamcs we get the expected structure:
The XTCE is what we expect; cfe and cfe_es are completely separate namespaces independent of each other.
However, when YAMCS parses the XTCE it looks like this on the YAMCS webapp:
The namespaces are nested, but this is incorrect; it is not what is defined on XTCE. This needs further investigation, but I highly suspect that the YAMCS webapp is globbing(using regex such "*") and it thinks that anything starting with cf* should be inside the "cf" folder. While, so far, this has not caused issues with sending telemetry or telecommanding, it is unexpected behavior that we should address.