Open MJJoyce opened 3 years ago
Our current time encoding for handler start() functions isn't properly encoding the start / end datetimes passed.
start()
datetimes
For example, RAF.start has the following: https://github.com/NASA-AMMOS/AIT-DSN/blob/master/ait/dsn/sle/raf.py#L155
RAF.start
if start_time is None: start_invoc['rafStartInvocation']['startTime']['undefined'] = None else: start_time = struct.pack('!HIH', (start_time - common.CCSDS_EPOCH).days, 0, 0) start_invoc['rafStartInvocation']['startTime']['known']['ccsdsFormat'] = start_time
We should be pulling out the rest of the start_time attributes values instead of setting those to 0. The same is happening with end_time.
start_time
end_time
This likely affects both RAF and RCF. Need to scrub both and check.
Our current time encoding for handler
start()
functions isn't properly encoding the start / enddatetimes
passed.For example,
RAF.start
has the following: https://github.com/NASA-AMMOS/AIT-DSN/blob/master/ait/dsn/sle/raf.py#L155We should be pulling out the rest of the
start_time
attributes values instead of setting those to 0. The same is happening withend_time
.This likely affects both RAF and RCF. Need to scrub both and check.