Appion

One possibility is to put them in

if self.debug:

An example of this is in normalizeCTF:

                if self.res80 < 6 and self.conf3010 < 0.3:
                        print(numpy.around(confdata[:15],3))
                        apDisplay.printError("confendence below 0.3 and resolution better than 6A")

This is to avoid false positive fits. What it needs to do is return None or something, so it is does upload the values to the database.

I initially put the crash in, because it usually meant something was wrong with the program.

There are many places that does this in the same module. Do you suggestt me to go through them one by one ? You should be better in judging which should be fatal. In addition, I start this issue to bounce ideas on how to make it possible to have both needs meet.

Okay, I see what you mean.

I am okay with adding self.debug flag, my test suite runs apCtf on 1000's of images looking for these fails and I do not reach them, so I like to know when they occur. Of course, I do not have time to work on any fix at the moment.

1d14cf39 add to self.debug failure when conf 30/10 failed to give back a number from scipy. The actually except happens when it is inserted to database.

Most problems come from images with defocus close to zero and from phase plate data. WIth -0.5 um defocus that I use with phase plate, ctfdisplay fails to create graph about 90% of the time.