-
Notifications
You must be signed in to change notification settings - Fork 1
Read and insert tomography atlas and search map locations #616
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
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #616 +/- ##
==========================================
+ Coverage 31.86% 32.38% +0.52%
==========================================
Files 90 92 +2
Lines 10762 11095 +333
Branches 1422 1460 +38
==========================================
+ Hits 3429 3593 +164
- Misses 7215 7377 +162
- Partials 118 125 +7 🚀 New features to boost your workflow:
|
tieneupin
left a comment
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.
Looks good overall!
|
With the latest changes, the test workflow now runs on the incompatible tomo dataset, with the missing values replaced with inaccurate arbitrary ones. This should be safe to merge. |
Connects to DiamondLightSource/python-murfey#616 The location and ID of the search map for a tomogram will be send in the alignment message, and this inserts those into ispyb with the tomogram.
Registers the locations of SearchMaps and BatchPositions for tomography data collection.
This requires reading the SearchMap.dm and .xml files, and the BatchPositionsList.xml, plus finding the atlas in the Session.dm
The logic for converting from stage coordinates to pixel positions is non-trivial and does not work perfectly.
For the Krios microscopes with FALCON and K3_FLIPX cameras it appears to give reasonably accurate values (with some ambiguity over whether "zero" is top-left or bottom-left which may need fixing), but for the Talos with K3_FLIPY it does not currently work.
The Murfey database has a new table for SearchMaps and the TiltSeries table now has positions. For ispyb the SearchMaps are inserted as GridSquares. TiltSeries location inserts will be done as part of the em-tomo-align recipe.