Source: NASA ( Kevin Rice)
Perhaps this is more about discussion first but a language/implementation (& version?) attribute would help custom algorithm be useful – and perhaps resolvable by your code.
For example, since most of the implementations of xtce are java – there are many jvm languages that could run as embedded "script" through the custom algorithm – if we but only knew which one to run!
For example so called "space python" could be run on jython…
We use gradle at work, and I'm so used to it forking of JVMs in other languages to do things – I'm thinking, let's give it a go! (we use a plugin that is in written python and is run by gradle on as jython on another jvm)
Reported: XTCE 1.2 — Thu, 9 Jul 2020 19:39 GMT
Updated: Tue, 1 Dec 2020 00:50 GMT
XTCE13 — CustomAlgorithm needs a language/implementation field
- Key: XTCE13-111
- OMG Task Force: XML Telemetric & Command Exchange Format 1.3 (XTCE) RTF