-
Notifications
You must be signed in to change notification settings - Fork 12
Add ability to move scintillator in to beam for i04 #1583
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
Merged
Merged
Changes from all commits
Commits
Show all changes
23 commits
Select commit
Hold shift + click to select a range
f209271
Add scint into beam + change Enum to be be more descriptive compared …
srishtysajeev 1efa5fd
Get rid of Enum change as this has to match what the PV is expecting
srishtysajeev 5b747e2
Add comments for what In and Out mean for the scint
srishtysajeev f61d124
small change
srishtysajeev 542db18
add tests for scint in
srishtysajeev 05453f9
get rid of comment!
srishtysajeev 512a942
make changes to scintillator.py from comments
srishtysajeev aa826be
make changes from comments to test_scintillator.py
srishtysajeev ba13e02
fix typo
srishtysajeev 9d71e54
make all functions hidden
srishtysajeev ec986c0
Change current_pos to a tuple because it was causing lint failing in …
srishtysajeev c5be74b
Add opencv docs
srishtysajeev 2aaf02f
fix: add awaits
srishtysajeev fb5f26c
Better mock the aperture scatterguard
DominicOram 01d6f02
fix: fix tests by changing expected type of current_pos in _check_pos…
srishtysajeev 21b3eca
refactor: change error message so it's not specific to just out
srishtysajeev 4ac32ae
fix: check if already In before attempting to move scint
srishtysajeev ebd1f6c
add test
srishtysajeev d4a74c1
fix: tests
srishtysajeev 5fd13a6
Merge branch 'main' into 1567_move_scintillator_to_beam
DominicOram 7d9e676
remove whitespace
srishtysajeev 9479360
Merge branch 'main' into 1567_move_scintillator_to_beam
srishtysajeev 78ba2f0
Merge branch 'main' into 1567_move_scintillator_to_beam
DominicOram File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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.
Is self._aperture_scatterguard().selected_aperture.get_value(), what we want here? I noticed that sometimes the error gives out Large or Small rather than an actual position - is that expected, and should I be testing that the correct error message is outputted?
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.
That's correct, the positions it can have are Large/Medium/Small