cryosparc version is v4.6.2
cryosparcm log app
cryosparcm joblog P17 J10
The first remove pick action cost too much time and prevent other remove action to be done.
It need to know what happend between got remove pick and done remove_pick.
@gaorongchao Please can you post
- Outputs of these commands on the CryoSPARC master computer
uname -a free -h - The full URL that in the web browser’s address bar when you access the CryoSPARC web app (why?)
-
uname -a
Linux gpu6 3.10.0-1160.36.2.el7.x86_64 #1 SMP Wed Jul 21 11:57:15 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux -
free -h
total used free shared buff/cache available
Mem: 503G 12G 87G 19M 404G 490G
Swap: 31G 1.2G 30G -
Full URL
http://172.22.96.148:39000/browse/P17-W1-J*#job(P17-J10)
When use http://localhost:39000/browse/P17-W1-J*#job(P17-J10)
The problem is still exist
Is there any solution?
The first time picks are edited (added or removed), all picks are written out to disk to make sure progress is not lost. Writing to disk happens again after every addition or removal of picks, unless it was already done less than 10 seconds ago.
The observed lag can be explained by the writing of large sets of particles to disk.
How many particles particles were input to the job?