mudinthewater

Woraround is to set ZONE and localtime simlink to /usr/share/zoneinfo/UTC, or set ZONE to just UTC and use either UTC or Etc/UTC.

Okay decided to take another look at this: System still the same: contents of /etc/sysconfig/clock: > ZONE="Etc/UTC" > UTC="true" /etc/localtime -> /usr/share/zoneinfo/Etc/UTC So by default our Zone is "Etc/UTC". Note...

@akhenry please tell me they're not trying to punt their adaptation issues to the MCT team rather than fix their broken adaptation

It's unclear if the /latest uri could fulfill this functionality, or if further influxdb intergration is needed.

Yeah this is a big pain in the ass for me on the serving side as well @akhenry. Looking at an example of a timestamp we'd have to be dealing...

@akhenry hate to bump such an old topic, but what would it take to switch to microseconds from milliseconds in MCT?

Poked at this some more and suggest updating the vue implementation to this: ``` compositionPathContainsId(domainObjectToFind) { if (!domainObjectToFind.composition) { return false; } return domainObjectToFind.composition.some((compositionIdentifier) => { return this.openmct.objects.areIdsEqual(compositionIdentifier, this.domainObject.identifier); });...

@scottbell If you're looking for a way to categorize Events, the AMMOS repo does a pretty decent job with its EVRs views: https://github.com/NASA-AMMOS/openmct-mcws/tree/main/src/evrView  Then on the view side everything...

If you wanted to simulate that last view in MCT, what you'd do is assign a regular channel and a numerical value to each EVR level, e.g. FATAL = 6,...

Another potential idea - what if we could zoom on the time-strip's time thing at the top?  That's perfectly correlated with the range on the entire time strip, and...