Skip to content

Conversation

@tpoliaw
Copy link
Collaborator

@tpoliaw tpoliaw commented Feb 12, 2025

{ts_hms} for HourMinuteSecond, eg 142117
{ts_ymd} for YearMonthDay, eg 20250221

There is scope for the year in the visit to not match the year in the timestamp
if run exactly at midnight on NYD. If this is deemed likely enough to be an
issue, we can duplicate the timestamp into the VisitPaths as well as the
ScanPaths.

@DiamondJoseph
Copy link
Contributor

There's a shutdown over new years, so I don't think we should worry about running scans during it

@tpoliaw
Copy link
Collaborator Author

tpoliaw commented Jun 16, 2025

And even if they were it would be one hell of a coincidence to trigger the discrepancy. The date for the visit should really come from the visit information anyway.

{ts_hms} for HourMinuteSecond, eg 142117
{ts_ymd} for YearMonthDay, eg 20250221
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants