FindDQE

Hello, I have been using FindDQE to test the DQE for XF416 camera on our TEM. However, when I input the mrc file, it could not read the corresponding NX,NY,NZ.

The output is as follows:

  Input image with pointer silhouette
image-95.mrc
   image-95.mrc
 
 Opening MRC/CCP4 file for READ...
 File      : image-95.mrc
  WARNING: NO MACHINE STAMP
 NX, NY, NZ: ******************
 Min, max  :     0.000000       0.7724490E-39
 Mean, RMS :     462.0021        0.000000    
 
  ERROR: Image must be 2D

Hi, I am a new user of FindDQE. When I was running sample data, I found a huge difference of MTF compared to provided result. When I was testing DE12, it even gave a DQE near 3.0, so I would like to ask what can be the source of this error? The parameter I input was the same to the .com file provided.

Thanks in advance.

Haoyang

Hi,

I find you have a new version of findDQE (FindDQE_150706) and try to compile it in linux system. Fistly, I install intel MKL (l_mkl_2018.1.163.tgz), and then compile the findDQE program according your source code. But I have these errors like below:

========================
/opt/intel/mkl/lib/intel64/libmkl_core.a(mkl_aa_fw_locking_HOST.o): In function `mkl_aa_fw_global_trylock':
mkl_aa_fw_locking.c:(.text+0x18): undefined reference to `pthread_mutex_trylock'

Hi there,

I am really sorry to open another topic about F3 overdose in EC mode but the other one got no reply and I am really keen on getting FindDQE (v1.06) working.

Let me first say that I had absolute no problem in measuring the DQE in linear mode. For EC mode, I have measured a total dose of 40 e/A2 both in EPU and Falcon Image Reference Manager. The dose measurements I got from the two tools match perfectly. However, when I run FindDQE the DQE goes well above 1.0.

Could it be the counts multiplier? How do I calculate a correct one?

Hi,

I am doing some things that involve running findDQE on several cameras and have a question. The J Str Bio paper says that the program can work on a pair of images and use them to estimate the noise power spectrum. I have assumed that this means a pair of images with the beam stop in place, but that's not totally clear. I have not yet tried this option with findDQE but I collected images that I think I can use.

I ran FindDQE on a beamstop image taken by Falcon3 counting mode (dose rate = 0.92e/p/s, total dose = 55e). The DQE goes above 1. The output is attached. Is there anything abnormal?

Hi,

EM users

In Ruskin et al., 2013 there is data on the TVIPS F416 camera MTF at 120 and 200 kV
and I am wondering if files with these curves are available that can be used
in various programs, such as RELION, to correct ones 3D maps from data collected on a home
instrument.

thanks,

C Akey
Prof.

I recorded images on a FEI TF20 at 200 kV on a K2 Summit (model XP). In counting mode, the DQE plots are equal to or better than the comparable curves posted at http://grigoriefflab.janelia.org/dqedata (see attached). But, when I tried super-resolution mode, the DQE curves are much worse (see attached). Here is how I recorded the pointer images, and the values I entered into FindDQE:

-Direct alignments updated.
-Although it doesn't, of course, affect the size of the pointer image, magnification was set to a typical magnification we use for recording images.

Dear All,

I would like to use FindDQE software to calculate MTF and DQE but it does not work on my computer! Does FindDQE work also on 64-bit operating system?

Thanks in advance.

Kind Regards

Brahim