ashaw596

@justbuchanan would know more about the original RRT implementation basis, but this paper goes into BiRRts https://arxiv.org/pdf/1703.08944.pdf The full trajectory planning(path planning plus velocities/acceleration) method we use is a variation...

This can be seen when retrieving ModificationTime from mailitems from outlook

Sorry the bug is that it's not being correctly converted. It's giving the time as UTC, but it's actually only correct if interpreted in your local time zone On Wed,...

Please consider reopening the issue. @mhammond

Hmm here is the code I'm using rn to demonstrate. Let me take a look at that. It might be just outlook pywin32 API related. ``` import datetime from win32com.client...

It is giving the modification time in the local timezone, but claiming it's UTC which is incorrect.

Yeah whoops missed that part of you message. Could just be outlook

Hmm so this test does fail. ``` def testNoTimeZone(self): self.check( datetime( year=2000, month=12, day=25, microsecond=500000, ) ) ``` I'm guessing that it doesn't support no time zone currently?

Oh I think I get it. So the return type from outlook is fundamentally without a time zone. It's a little confusing since if I understand correctly the datetime object...

Hmm. I was looking through the code. So is that only used in the final training? It looks like its only called in _fixed_layer.