-
Notifications
You must be signed in to change notification settings - Fork 1
Remove serialem code and revise context determination #632
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
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #632 +/- ##
==========================================
+ Coverage 32.98% 33.31% +0.33%
==========================================
Files 90 90
Lines 11151 11130 -21
Branches 1470 1462 -8
==========================================
+ Hits 3678 3708 +30
+ Misses 7340 7295 -45
+ Partials 133 127 -6 🚀 New features to boost your workflow:
|
…text' function, as it conflicts with some of the metadata determindation logic for SPA and Tomo
…iles; the loading of the 'analyse_created_directories' key should not be needed
…text of CLEM files; removed the corresponding mocks in the test
…ntext, and more files that can
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.
@stephen-riggs , I've added example files for the CLEM workflow to the analyser test, and have realised that the logic for the CLEM workflow can be optimised, as some of it conflicts with the conditions you've put in place for the SPA and Tomo files. I've also merged the main
branch into this one so that ISPyB gets installed correctly.
Could you verify that the contents of murfey.client.analyser
are as you intended after resolving merge conflicts?
The SerialEM code has never been used, and if we want to support SerialEM in future it would be better to redo it. This removes all code relating to it.
Also improves and tests the determination of the context in the analyser.
There are some potential difficulties with distinguishing data and metadata. The biggest problem is mdoc files which appear with the same name in both folders.