Skip to content

Epoch timestamps in SAXSWAXS #383

Closed
Closed

Description

@jpk96

We noticed that the Epoch timestamps in the SAXSWAXS data appear to be offset from their expected values.

I believe the issue may be that the workflow is adding the per-datapoint Epoch value to the start time of the individual scan. However, these Epoch values should instead be referenced to the #E value in the SPEC data file.

In other words, the timestamp for each datapoint should be calculated by adding the recorded Epoch offset to the #E value, rather than to the scan start time.

Tagging @jcrossno-afrl

Activity

  1. added theissue type on Oct 18, 2026
  2. jpk96 commented on Oct 19, 2026

    @jpk96
    CollaboratorAuthor

    For SPEC data files containing multiple #E entries, each scan should use the most recent #E value. This ensures that Epoch offsets are referenced to the correct absolute timestamp, particularly when data collection is resumed in an existing SPEC data file after acquiring data in a different SPEC data file.

  3. added
    in progressCurrently being addressed by developers
    commonRelated to routines in common that are shared over multiple workflows
    on Oct 19, 2026
  4. linked a pull request that will close this issue383 epoch timestamps in saxswaxs #384on Oct 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

commonRelated to routines in common that are shared over multiple workflowshigh priorityHigh priority issuein progressCurrently being addressed by developerssaxswaxsRelated to the saxswaxs workflow

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions