<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">This has happened to me a lot with one of my datasets, although always during class2D jobs (I am assuming it didn’t happen to me during class3D because at that stage I had already discarded the problematic particles). As I understand it, it is more likely to happen if your autopicking picked a lot of "junk". Using stricter settings for autopicking might help.<div class=""><br class=""></div><div class="">The way I got rid of this error was to do a particle sorting right after extraction, and then select only the good particles. It can be difficult to tell the difference between good and bad particles, but after sorting if you look at the bad end you might be able to visually recognize obvious autopicking junk even with the very low contrast of the raw micrographs. Doing this consistently prevented the error from happening, but I am not very happy with this solution because I am sure I also threw away valid particles in the process.</div><div class=""><br class=""></div><div class="">I wish relion would be able to automatically flag these problematic particles, ignore them during the current classification, and at the end provide a file listing them so the user can discard them from the dataset for subsequent jobs (this would require the "Select" job type to be able to do subtractions between two star files: subtract the flagged particles from the initial set of particles). That would be much more sensible and much less frustrating than the current behavior of crashing the job (I wasted so many hours of computer time because of this error…), and would make class2D an even better way of "cleaning" a dataset.<br class=""><div class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br class="Apple-interchange-newline">Guillaume</div></div></div></div>
</div>
<div><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class="">On Mar 26, 2018, at 15:17, Vishaka Santosh <<a href="mailto:vs4p@virginia.edu" class="">vs4p@virginia.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hey, I know this issue has been asked recently, but I was wondering if anyone had any idea as to how to resolve this. I received this error when attempting to run 3D auto-refine in Relion: <br clear="all" class=""><div class=""><br class="">Dumped data: error_dump_pdf_orientation, error_dump_pdf_orientation and error_dump_unsorted.<br class="">slave 3 encountered error: ERROR: <br class="">No orientation was found as better than any other.<br class=""><br class="">A particle image was compared to the reference and resulted in all-zero<br class="">weights (for all orientations). This should not happen, unless your data<br class="">has very special characteristics. This has historically happened for some <br class="">lower-precision calculations, but multiple fallbacks have since been <br class="">implemented. Please report this error to the relion developers at <br class=""><br class=""> <a href="http://github.com/3dem/relion/issues" class="">github.com/3dem/relion/issues</a> <br class=""> <br class="">File: /programs/x86_64-linux/relion/2.1_cu8.0/src/gpu_utils/<a href="http://cuda_ml_optimiser.cu/" class="">cuda_ml_optimiser.cu</a> line: 1710<br class=""><br class=""></div><div class="">Does anyone have any idea as to what might cause this and any fixes?<br class=""></div><div class=""><br class="">-- <br class=""><div class="gmail_signature">Vishaka Santosh<div class=""><div class="">UVA Class of 2011, BS in Chemistry with a specialization in Biochemistry</div></div><div class="">VCU Class of 2013, MS in Biochemistry </div></div>
</div></div>
_______________________________________________<br class="">3dem mailing list<br class=""><a href="mailto:3dem@ncmir.ucsd.edu" class="">3dem@ncmir.ucsd.edu</a><br class="">https://mail.ncmir.ucsd.edu/mailman/listinfo/3dem<br class=""></div></blockquote></div><br class=""></div></div></body></html>