Closed S160024 closed 3 years ago
Thank you @S160024 , I'm involving here Relion plugin developers
@S160024 could you provide full output logs, screenshot of protocol parameters used so we could reproduce it? Also, are you running extraction in streaming or not? Also, which relion plugin version are you using?
From the shown error trace, it seems to be in streaming...still will be good to have full logs and parameters.
@S160024 any update on this?
Hi there sorry for the late response.
The full log file is attached. run.log
The parameters used is the coordinates from relion's autopicking LoG output file The micrograph source are from xmipp3-ctf consensus output file. The particle box size is 150 px, with no rescale of particles.
The preprocess parameters are as follows:
the streaming was set as 0 seconds sleep when waiting and 0 batch size.
Thanks, @S160024, we'll try to reproduce it. Could you also attach run.stdout which is more detailed?
Hi @azazellochg , I'm unable to attach it. However, i've uploaded on dropbox and you may access the run.stdout file in the link below.
For me 'relion - particle extraction' is also failing when I try to extract using coordinates from 'relion - auto-picking LoG' in streaming mode
Confirmed as a bug in core extraction protocol
Thanks @azazellochg , have you manage to reproduce it. Since test are passing, I guess there must be a specific condition that makes it fail and test are not covering? I guess we can assign it to us.
I was able to reproduce it in cistem since I copied the relion code from that protocol to cistem picker.
This is definitely fixed.
Usually when running in Relion 3.0, the particles extracted would result in an output file that can be read for 2D classifications. However, in Scipion, there seems to be an error in producing the output file.
Step 2 in Scipion-relion particles extraction failure. The particles extractions was performed properly, however, the output file is not available.
Despite editing the failed process and clicking continue, the error still pops up. Is there a bug issue or is there a coding issue? I'm currently running on Ubuntu Centos 7.