Add EMPIAR 11618 experimental recon#1361
Conversation
4b38252 to
bd2a43d
Compare
|
Using the non-legacy preprocessing seems to give up about 0.5A in this configuration so I went with that. Probably in the future it can improve. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #1361 +/- ##
========================================
Coverage 90.87% 90.87%
========================================
Files 135 135
Lines 14678 14678
========================================
Hits 13339 13339
Misses 1339 1339 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
[skip ci]
[skip ci]
bd2a43d to
80b9f0b
Compare
80b9f0b to
34006d1
Compare
|
Github having some issues, will return to restart these later. This code diff doesn't actually run in anything other than the doc build so the CI should go through normally .... |
GH appears healthier today. Restarted. |
|
Going to merge this in just to keep the PR area tidy. We can tweak it before the next release if any concerns. |
Adds gallery example for EMPIAR 11618 recon.
The data for this is clean enough that we can use the randomized class selection to avoid the expensive entire class average set generation. Raw data to recon volume with 1 A100 GPU is taking about 2 hours and about 20A at 129 pixels.
I did try using various preprocessing techniques. While most were slightly faster preprocessing, they all had decreased recon accuracy in my (limited) testing runs.
Most of my runs were at 50 neighbors per class average. I'm currently testing with 100 as written here and will decide based on the FSC and visuals what to initially recommend before proofreading and opening up for review.