OK, I've tried to protect against this situation directly in ProgressBar.py. That is just a timing bubble that pops up to give progress in a task, but in this case the total task time was 0 so it was dividing by 0 to get the percentage of the task that was done. I've put an update in 2.3.0 and it will be fixed automatically in 2.3.1 when I get that done.
Wayne
On 6 Aug 2013, at 18:28, David Langelaan wrote:
> Hello,
>
> Just to add to the pile of e-mails that are coming out today :)
>
>
> I got the following traceback when running pyrpf on a structural ensemble of mine. If instead I select only one of my peak lists to analyze, things work fine. Although looking at the code of the traceback, I doubt it is a peaklist specific issue.
>
> Thanks,
>
> David
>
> Calculating scores and making CCPN validation objects
> Exception in Tkinter callback
> Traceback (most recent call last):
> File "/home/dlangela/Programs/ccpnmr/python2.6/lib/python2.6/lib-tk/Tkinter.py", line 1410, in __call__
> return self.func(*args)
> File "/home/dlangela/Programs/ccpnmr/ccpnmr2.3/python/rutgers/rpf/PyRPF.py", line 800, in runRpf
> progressBar=progressBar)
> File "/home/dlangela/Programs/ccpnmr/ccpnmr2.3/python/rutgers/rpf/PyRPF.py", line 1879, in calcRPF
> peakListM = predictMissingPeaks(peakList, shiftsMissingPeaks, progressBar)
> File "/home/dlangela/Programs/ccpnmr/ccpnmr2.3/python/rutgers/rpf/PyRPF.py", line 2064, in predictMissingPeaks
> progressBar.set(0)
> File "/home/dlangela/Programs/ccpnmr/ccpnmr2.3/python/memops/gui/ProgressBar.py", line 124, in set
> self.update()
> File "/home/dlangela/Programs/ccpnmr/ccpnmr2.3/python/memops/gui/ProgressBar.py", line 95, in update
> p = self.progress/self.total
> ZeroDivisionError: float division
|