Depending on how frequently you saved frames, the analysis can take several hours. do_dssp is just a wrapper that calls dssp for every frame, dumping a temporary PDB file, running the analysis, and collating the result. It’s very inefficient, especially since it requires disk I/O at every step.
How can I determine/ check how much saved frames for the trajectory input file (.xtc) ?
It’s been over 2 days for my dssp analysis and it’s still in progress. I’m running two 100 ns (2.3 GB data) and two 200 ns (4.8 GB data) at once in separate computers, 62.7 GB and 125.7 GB memory with 12 TB and 6 TB available storage respectively. Do you think it’s reasonable/normal?
There is no reason for do_dssp to take more than a few hours. Several people have reported the same behavior so maybe something is buggy. Try upgrading to 2020.3 and try again.