edwarrick / i13-1-bluesky

I13-1-Bluesky

i13-1-bluesky's Issues

Run demo of existing ptychotomo experiment

With-beam demo of a realistic ptychotomography experiment for project team to aid with definition of interface and high level requirements.

Acceptance criteria

• Demonstrated to EW, HS, KW, TP

Work out how we do Jython scans from pytest

Acceptance Criteria:

• Kaz can outline how this would work in review

Initial runnable version of Bluesky on I13-1

Deploy Panda updates

Panda V3 firmware update deployment and testing

Run demo for Bragg CDI experiment

Proof-of-concept of automated system tests

An initial version of the system testing harness, able to run a suite of test scans in a specified time budget (e.g. 10 minutes).

Acceptance Criteria:

• Demonstration of test harness to project team on I13-1 on machine day.
• All team members understand how to run tests.
• All team members understand how to find out what tests are being run.
• Outline documentation on how to define or modify tests.

Defined switchover mechanism for Bluesky/Malcolm testing

Test we can submit a scan to Malcolm via ActiveMQ

Acceptance Criteria:

-Huw to report this works

Examine what we can discover from ActiveMq about scan outcome

Acceptance criteria:

• Report back in next review what we can discover.

Kubernetes workers for Bluesky

Define common user interface for Ptychotomo and Bragg CDI control

Test arbitrary scans can be submitted via pytest

Acceptance Criteria:

Demo the range of scans that can be submitted to team.

Add I13-1 Bluesky repo

Acceptance Criteria:

• Mechanism defined for linking high level and low level tasks
• Repository exists for core project code and track.

Deploy updated motion system