cramerlab / warp

GNU General Public License v3.0
53 stars 16 forks source link

Automatic unselection of loaded files #31

Closed neumann-emmanuelle closed 4 months ago

neumann-emmanuelle commented 2 years ago

Dear all,

I desperately try to start to analyze my tomography cryo-EM data with Warp collected a few months ago on a Krios in Heidelberg. When I go through the first step, i.e I want to import my data, I correctely enter the path of my files (I am able to see the right number of files to import, through the wheel of the « Processing Status »). But unfortunately, all files deselect by themselves!!

We noticed that in all .xml files generated, the answer to UnselectManual is TRUE. If we change this answer to FALSE , the file is selected and can be processed. 7,171 files have to be processed so how can we fix this problem for all the 7,171 files and why it is so? Do I need to « pre-process » my data before by changing/modifying any subtil parameters?

psimpsonImperial commented 1 year ago

Hi Emmanuelle... did you get to the bottom of this problem, only I see the same thing here at Imperial College London. Select data folder in WarpM, start processing and eer images are automatically deselected during processing?

regards Paul simpson CBEM DoLS ICL

neumann-emmanuelle commented 1 year ago

Hi Paul,

we managed to fix this problem by reinstalling WarpM.

Hope it will solve the problem for you also...

Best regards,

Emmanuelle

Le 29/09/2022 23:39, psimpsonImperial a écrit :

Hi Emmanuelle... did you get to the bottom of this problem, only I see the same thing here at Imperial College London. Select data folder in WarpM, start processing and eer images are automatically deselected during processing?

regards Paul simpson CBEM DoLS ICL

— Reply to this email directly, view it on GitHub https://github.com/cramerlab/warp/issues/31#issuecomment-1262844730, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWU7NKA6HDKZPRKMWOT6CO3WAYEA7ANCNFSM5IYERI2A. You are receiving this because you authored the thread.Message ID: @.***>