Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fastcs eiger support #528
Fastcs eiger support #528
Changes from all commits
d14f194
eca5850
2c4d509
aebc98c
0078df2
9df23f2
c19ccca
7c2d990
6574add
a650bbe
76ad527
ca69c77
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After #405 then there will be a
prepare
method on the controller that takes aTriggerInfoT
so this prepare method will become unnecessary. For now this is correct though.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where did you get this number from? If from the manual then please can you provide a reference?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As soon as PVI datastructures are published over PVA then this file will drastically change to something like:
It will also only need to include the signals that are needed at static analysis time, at runtime then all the extras (like
beam_centre_x
, etc) will be filled in automatically.This will also mean that the class structure and ophyd attribute names will have to exactly match those in PVI.
For this reason I suggest we do this soon, and @GDYendell is going to start looking at this now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Eventually all these signals will be needed at static analysis time. I have added in all the ones that we need to re-implement what we currently have on the
ophyd
eiger
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PVI structures will be added in DiamondLightSource/FastCS#54
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gilesknap I wonder if this can be achieved with
docker-compose
or similar, so we can run it up either in the CI or locally in exactly the same way?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't want to hold this up on the CI stuff, which could get fiddly so made #531