Skip to content

Fix offline detection_time offset by one inference step - #548

Merged
wbenoit26 merged 2 commits into
ML4GW:devfrom
JunyanX:fix-offset
Oct 5, 2026
Merged

wbenoit26 merged 2 commits into
ML4GW:devfrom
JunyanX:fix-offset

Conversation

@JunyanX

@JunyanX JunyanX commented Oct 5, 2026

Copy link
Copy Markdown

The offline Postprocessor's t0 omitted the 1 / inference_sampling_rate term that online get_time_offset includes, so offline detection times came out one inference step (0.25 s at 4 Hz) early.

The offline Postprocessor's t0 omitted the 1 / inference_sampling_rate
term that online get_time_offset includes, so offline detection times
came out one inference step (0.25 s at 4 Hz) early.

@wbenoit26 wbenoit26 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for catching this!

@wbenoit26

Copy link
Copy Markdown
Contributor

Oh, looks like we had a test based on the wrong offset. Could you fix that as well?

@JunyanX

JunyanX commented Oct 5, 2026

Copy link
Copy Markdown
Author

Yeah, I am working on that

@JunyanX

JunyanX commented Oct 5, 2026

Copy link
Copy Markdown
Author

I think it should be good now

@wbenoit26
wbenoit26 merged commit a21ff00 into ML4GW:dev Oct 5, 2026
7 of 9 checks passed
@JunyanX
JunyanX deleted the fix-offset branch October 6, 2026 15:46
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.

2 participants