compile error in new version of findDQE
Forums
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'
/opt/intel/mkl/lib/intel64/libmkl_core.a(mkl_aa_fw_load_orsl_lite_lib_HOST.o): In function `mkl_aa_fw_load_orsl_lite_lib':
mkl_aa_fw_load_orsl_lite_lib.c:(.text+0xb9): undefined reference to `dlopen'
mkl_aa_fw_load_orsl_lite_lib.c:(.text+0xd4): undefined reference to `dlsym'
mkl_aa_fw_load_orsl_lite_lib.c:(.text+0xf2): undefined reference to `dlsym'
mkl_aa_fw_load_orsl_lite_lib.c:(.text+0x110): undefined reference to `dlsym'
mkl_aa_fw_load_orsl_lite_lib.c:(.text+0x12e): undefined reference to `dlsym'
/opt/intel/mkl/lib/intel64/libmkl_core.a(load_library_HOST.o): In function `mkl_ueaa_prv_load_backend_lib':
load_library.c:(.text+0x1cd): undefined reference to `dlopen'
load_library.c:(.text+0x1ef): undefined reference to `dlvsym'
load_library.c:(.text+0x218): undefined reference to `dlvsym'
load_library.c:(.text+0x241): undefined reference to `dlvsym'
load_library.c:(.text+0x26a): undefined reference to `dlvsym'
load_library.c:(.text+0x293): undefined reference to `dlvsym'
/opt/intel/mkl/lib/intel64/libmkl_core.a(load_library_HOST.o):load_library.c:(.text+0x2bc): more undefined references to `dlvsym' follow
collect2: error: ld returned 1 exit status
Makefile.inc:16: recipe for target 'finddqe' failed
make: *** [finddqe] Error 1
==========================
These errors are not happen in your previous version (when I install the MKL, findDQE can compile successfully). So what difference between the two versions and how to compile the new version?
Another question is how to use the findDQE program and decide the right parameters to run it. Do you have the tutorials like this: how to use the suitable parameters to get the right results. What parameters we must pay more attention.
I am very sorry but we cannot
I am very sorry but we cannot provide support for these types of problems. Please use the pre-compiled version if possible. If the old version of the program works, please use the old version. The old version uses slower FFTs but should otherwise work fine. For instruction on how to use the program, please read the associated paper.
new question
In reply to I am very sorry but we cannot by niko
Thank you for your help! I understand it. I have another question. When I run findDQE program, it will generate a output image, residual image. The image size of this image is different with original image, and the brightness is also different. What is the residual image means? Is it a measurement to tell us that the results are right?
Yes, the residual image
In reply to new question by xufbit
Yes, the residual image should not show any strong features, such as the edges of the pointer you used to collect the image. The size of the image is smaller than the original image as some of the area outside the pointer are cut away for speed and algorithmic reasons.
the function of residual image?
In reply to Yes, the residual image by niko
So what is its role? What information can we get from this image, which the findDQE program output it. My question is that like DQE and MTF, we can use them to measure the image quality. But I don't know the function of residual image.
If you see strong features in
In reply to the function of residual image? by xufbit
If you see strong features in the residual image, the fit of the pointer edge is not good and DQE measurements may not be accurate.
Same Compilation error encountered
In reply to new question by xufbit
Hi xufbit,
I am a new user to FindDQE and I have encountered the same problem compiling the newer version, may I ask if you have solved it(and how)?
Thank you in advance.
Haoyang Ni