Skip to content

Investigate allowing different templating per detector vs per run for the start document path provider #899

Closed as not planned
Closed as not planned
Investigate allowing different templating per detector vs per run for the start document path provider#899
Labels
deferredNot needed yetenhancementNew feature or request

Description

@abbiemery
abbiemery
opened on Apr 4, 2025

There is a desire to allow different detectors within a run to have differently structured file names. Currently the start document path provider allows for a custom template to be provided, but it applies the same across all detectors in a run. We should investigate how we could differentiate between detectors for this templating

Acceptance Criteria

  • Know if this is possible within blueapi
  • If there are few options, have the implementations drafted out so a discussion can be had about the desired direction

Activity

  1. abbiemery
    added
    enhancementNew feature or request
    spikeIssue to investigate scope/feasilibilty/technology etc. of how to do something
    on Apr 4, 2025

  2. callumforrester commented on Apr 11, 2025

    @callumforrester
    callumforrester
    on Apr 11, 2025
    Contributor

    So currently we are allowing people to insert "template": "blah-blah-{detector}" into the start document, could instead have

    "template": {
    "default": "blah-blah-{detector}",
    "my-special-detector": "{detector}-blah-blah"
}

  3. abbiemery commented on Feb 25, 2026

    @abbiemery
    abbiemery
    on Feb 25, 2026
    ContributorAuthor

    There is a proof-of-concept PR in numtracker to support this but as the detector templating in numtracker is not used yet, this can be deferred for now.

    DiamondLightSource/numtracker#103

  4. abbiemery
    closed this as completedon Feb 25, 2026
  5. abbiemery
    added
    deferredNot needed yet
    and removed
    spikeIssue to investigate scope/feasilibilty/technology etc. of how to do something
    on Feb 25, 2026
  6. abbiemery
    closed this as not plannedon Feb 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    deferredNot needed yetenhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions