Closed dasari123 closed 11 years ago
mferrero
commented
11 years ago Hi Dasari. Can you show us the content of the following files in the build directory:
pytriqs/Solvers/HybridizationExpansion/test/SingleSiteBethe_output.errand
pytriqs/Solvers/HybridizationExpansion/test/SingleSiteBethe_outputThis will help to figure what the problem is. Thanks!
dasari123
commented
11 years ago Hi mferrero,
The following is the content of pytriqs/Solvers/HybridizationExpansion/test/SingleSiteBethe_output.err in the triqs_build directory.
Starting on 1 Nodes at : 2013-02-23 10:12:00.430900 Average sign: 1 * The MPI_Barrier() function was called before MPI_INIT was invoked. * This is disallowed by the MPI standard. *\ Your MPI job will now abort. [test:16562] Local abort before MPI_INIT completed successfully; not able to aggregate error messages, and not able to guarantee that all other processes were killed!
The below text is the content of pytriqs/Solvers/HybridizationExpansion/test/SingleSiteBethe_output in the triqs_build directory.
------ Node : 0 -------- Iteration Number = 1
Optional parameters defined to their default values: *Global_Moves -> [] Description : A list of global moves
*Fitting_Frequency_Start -> 50 Description : Frequency at which the fit starts
*Record_Statistics_Configurations -> False Description : (Expert only) Get the kink length statistics
*Quantum_Numbers_Selection -> <function
*Use_F -> False Description : (Expert only) Compute F
*Nmax_Matrix -> 100 Description : Initial size of the determinant matrices
*Keep_Full_MC_Series -> False Description : (Expert only) Store the Green's function for later analysis
*Measured_Operators -> {} Description : A dict of operators that will be averaged de : 0 -------- Iteration Number = 1
Optional parameters defined to their default values: *Global_Moves -> [] Description : A list of global moves
*Fitting_Frequency_Start -> 50 Description : Frequency at which the fit starts
*Record_Statistics_Configurations -> False Description : (Expert only) Get the kink length statistics
*Quantum_Numbers_Selection -> <function
*Use_F -> False Description :
*N_Frequencies_Accumulated -> 100 Description : Number of frequencies to accumulate
*Time_Accumulation -> False Description : Do we accumulate in imaginary-time?
*Random_Seed -> 34788 Description : Seed for the random generator
*Eta -> 0.0 Description : (Expert only) Value of eta, the minimum value of the det
*Legendre_Accumulation -> True Description : Do we accumulate in legendre?
*Proba_Move -> 1.0 Description : Probability to move operators
*Proba_Insert_Remove -> 1.0 Description : Probability to insert/remove operators
*Measured_Time_Correlators -> {} Description : A dict of operators, whose time correlations are to be measured
Hamiltonian with Eps0 term : 2.5 C^(up,1)C(up,1)C^(down,1)C(down,1) - 1.25 C^(up,1)C(up,1) - 1.25 C^(down,1)C(down,1) Inv Fourier done
1%; 2%; 3%; 4%; 5%; 6%; 7%; 8%; 9%; 10%; 11%; 12%; 13%; 14%; 15%; 16%; 17%; 18%; 19%; 20%; 21%; 22%; 23%; 24%; 25%; 26%; 27%; 28%; 29%; 30%; 31%; 32%; 33%; 34%; 35%; 36%; 37%; 38%; 39%; 40%; 41%; 42%; 43%; 44%; 45%; 46%; 47%; 48%; 49%; 50%; 51%; 52%; 53%; 54%; 55%; 56%; 57%; 58%; 59%; 60%; 61%; 62%; 63%; 64%; 65%; 66%; 67%; 68%; 69%; 70%; 71%; 72%; 73%; 74%; 75%; 76%; 77%; 78%; 79%; 80%; 81%; 82%; 83%; 84%; 85%; 86%; 87%; 88%; 89%; 90%; 91%; 92%; 93%; 94%; 95%; 96%; 97%; 98%; 99%;
Acceptance rate for all moves: Move set INSERT: 0.362024 Move Insert0: 0.362065 Move Insert1: 0.361984 Move set REMOVE: 0.36177 Move Remove0: 0.361572 Move Remove1: 0.361968 Move Move C Delta: 0.434462
Simulation lasted: 14 seconds Total measures: 5000 measures Average sign: (1,0)
Thanks and With regards, Dasari.
parcollet
commented
11 years ago Hi, Looks like an MPI pb. what does : dpkg -l |grep openmpi return ? Do you have every package listed in 1) of http://ipht.cea.fr/triqs/doc/user_manual/install/Ubuntu.html ? PS : We are also using 12.04, so it must be a missing package ... Olivier
mferrero
commented
11 years ago For comparison here are all the mpi-related packages that show up in my dpkg -l. You might want to check that they all appear in your dpkg -l too:
libopenmpi-dev
libopenmpi1.3
openmpi-bin
openmpi-checkpoint
openmpi-common
mpi-default-devHi,
This is the screened output of sudo dpkg -l | grep openmpi command. I checked whether the above mentioned files are appearing in dpkg -l or not. I found all files. No problem.
ii libopenmpi-dev 1.4.3-2.1ubuntu3 high performance message passing library -- header files ii libopenmpi1.3 1.4.3-2.1ubuntu3 high performance message passing library -- shared library ii openmpi 1.6.3-3 A powerful implementaion of MPI ii openmpi-bin 1.4.3-2.1ubuntu3 high performance message passing library -- binaries ii openmpi-checkpoint 1.4.3-2.1ubuntu3 high performance message passing library -- checkpoint support ii openmpi-common 1.4.3-2.1ubuntu3 high performance message passing library -- common files
Thanks, Dasari.
dasari123
commented
11 years ago Hi,
I installed all necessary libraries. You can see it below.
sudo apt-get install cmake git g++ libgfortran3 gfortran openmpi-bin openmpi-common openmpi-checkpoint libopenmpi-dev libblas-dev liblapack-dev libfftw3-dev libgmp-dev hdf5-tools libhdf5-serial-dev python-h5py libboost1.48-all-dev python-dev python-numpy python-scipy python-virtualenv python-matplotlib
Reading package lists... Done
Building dependency tree
Reading state information... Done
g++ is already the newest version.
gfortran is already the newest version.
git is already the newest version.
libblas-dev is already the newest version.
libfftw3-dev is already the newest version.
libgfortran3 is already the newest version.
libgmp-dev is already the newest version.
liblapack-dev is already the newest version.
python-dev is already the newest version.
python-numpy is already the newest version.
hdf5-tools is already the newest version.
libboost1.48-all-dev is already the newest version.
libhdf5-serial-dev is already the newest version.
libopenmpi-dev is already the newest version.
openmpi-bin is already the newest version.
openmpi-checkpoint is already the newest version.
openmpi-common is already the newest version.
python-h5py is already the newest version.
python-matplotlib is already the newest version.
python-scipy is already the newest version.
python-virtualenv is already the newest version.
cmake is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 111 not upgraded.
Thanks, Dasari.
mferrero
commented
11 years ago Hi! Maybe this has nothing to do with the problem, but your dpkg -l command shows a:
ii openmpi 1.6.3-3 A powerful implementaion of MPII think this is not part of the standard Ubuntu 12.04. I'm not sure it doesn't conflict with the other openmpi components (1.4.3). Can you try to remove it to see if it makes a difference?
dasari123
commented
11 years ago Hi mferrero,
I installed that package(openmpi 1.6.3-3) manually for other purpose. That is not in the standard path also. Removing that package may be create a more problems. Is it necessary to remove that package?
Thanks, Dasari.
parcollet
commented
11 years ago You have indeed - Found MPI_CXX: /usr/local/lib/libmpi_cxx.so;/ /usr/local ... while on my 12.04, I have /usr/lib/openmpi/lib/libmpi_cxx.so So I guess that you compile against this non std package. Not a pb for TRIQS, but a serious one for boost, if you use the installed one. (boost::mpi is compiled for the default version...) Did you use the option to compile boost from the source ? (I mean -DBOOST_SOURCE_DIR = ...., with the latest e..g boost 1.53)
dasari123
commented
11 years ago Hi,
I removed the manually installed openmpi1.6.3-3. Again I started installation of triqs. All files passed test(100%). You can see the output result. Still I have a problem with tutorials.
118/118 Test #118: HubbardI ......................... Passed 0.93 sec
100% tests passed, 0 tests failed out of 118
Total Test time (real) = 64.78 sec
These are the contents of installation directory. bin include lib share
contents of bin directory is:: dmftproj ipytriqs ipytriqs_notebook pytriqs contents of include directory is:: triqs contents of share directory is:: triqs contents of lib directory is:: libtriqs.so python2.7
I think I missed some python modules and c++ modules(According to triqs website).
I export the path of bin, then I run the below python script: ipytriqs my_script.py
from pytriqs.Base.GF_Local import GFBloc_ImFreq, iOmega_n, inverse
g = GFBloc_ImFreq(Indices = [1], Beta = 50, NFreqMatsubara = 1000, Name = "imp") g <<= inverse( iOmega_n + 0.5 )
from pytriqs.Base.Plot.MatplotlibInterface import oplot oplot(g, '-o', x_window = (0,10))
I got an error like this:
Traceback (most recent call last):
File "
All my libraries are default.
Thanks, Dasari.
tayral
commented
11 years ago Hi Dasari, Have you installed ipython? If not, could you try easy_install ipython This should solve your problem with ipytriqs.
For the ipython notebook, you can take a look at http://ipython.org/ipython-doc/dev/install/install.html#installnotebook to see all the dependencies.
Cheers Le 25/02/13 08:55, dasari123 a écrit :
Hi,
I removed the manually installed openmpi1.6.3-3. Again I started installation of triqs. All files passed test(100%). You can see the output result. Still I have a problem with tutorials.
118/118 Test #118: HubbardI ......................... Passed 0.93 sec
100% tests passed, 0 tests failed out of 118
Total Test time (real) = 64.78 sec
These are the contents of installation directory. bin include lib share
contents of bin directory is:: dmftproj ipytriqs ipytriqs_notebook pytriqs contents of include directory is:: triqs contents of share directory is:: triqs contents of lib directory is:: libtriqs.so python2.7
I think I missed some python modules and c++ modules(According to triqs website).
I export the path of bin, then I run the below python script: ipytriqs my_script.py
Import the Green's functions
from pytriqs.Base.GF_Local import GFBloc_ImFreq, iOmega_n, inverse
Create the Matsubara-frequency Green's function and initialize it
g = GFBloc_ImFreq(Indices = [1], Beta = 50, NFreqMatsubara = 1000, Name = "imp") g <<= inverse( iOmega_n + 0.5 )
from pytriqs.Base.Plot.MatplotlibInterface import oplot oplot(g, '-o', x_window = (0,10))
I got an error like this:
Traceback (most recent call last): File "", line 3, in ImportError: No module named IPython
All my libraries are default.
Thanks, Dasari.
— Reply to this email directly or view it on GitHub https://github.com/TRIQS/TRIQS/issues/108#issuecomment-14019618.
dasari123
commented
11 years ago Hi,
I installed ipython and ipython notebook. I am not getting anything means it is not writing any output either error or graphs.
I used this command : ipytriqs my_script.py
Nothing comes in the folder. It didn't write error also.
I used ls -ltr in my test folder, then It showing
total 4
-rw-r--r-- 1 root root 375 Feb 25 03:53 my_script.py
I didn't see 4 files. I don't know what happend?
Thanks, Dasari.
tayral
commented
11 years ago Hi, Could you try
ipytriqs -i my_script.py --pylab
? If your script is supposed to plot something, it should work with this command.
Cheers
Le 25/02/13 10:19, dasari123 a écrit :
Hi,
I installed ipython and ipython notebook. I am not getting anything means it is not writing any output either error or graphs.
I used this command : ipytriqs my_script.py Nothing comes in the folder. It didn't write error also. I used ls -ltr in my test folder, then It showing
total 4 -rw-r--r-- 1 root root 375 Feb 25 03:53 my_script.py
I didn't see 4 files. I don't know what happend?
Thanks, Dasari.
— Reply to this email directly or view it on GitHub https://github.com/TRIQS/TRIQS/issues/108#issuecomment-14021798.
dasari123
commented
11 years ago Hi tayral,
i.e I need to try myself.
Thanks, Dasari.
dasari123
commented
11 years ago Hi,
I used a following command at the terminal to run the python script: ipytriqs -i my_script.py --pylab.
(1) I saw the picture(greens function) on my screen. When I closed the picture I didn't get my prompt back. It may be silly question for you. But I am new for this language(python). I used ctrt+c, ctrl+q and some unix commands. It didn't work. Could you please tell me how to get the prompt back.
(2) Why my script is not working with ipytriqs my_script.py command ? Any idea.
(3)Did I have all the libraries when I installed triqs?( It seems to me I missed some c++ libraries). I showed it in my previous mail.
(4)Now can I go through all the tutorials? (installation ok or not)
$ ipytriqs -i my_script.py --pylab
Python 2.7.3 (default, Aug 1 2012, 05:14:39) Type "copyright", "credits" or "license" for more information.
IPython 0.13.1 -- An enhanced Interactive Python. ? -> Introduction and overview of IPython's features. %quickref -> Quick reference. help -> Python's own help system. object? -> Details about 'object', use 'object??' for extra details.
Welcome to pylab, a matplotlib-based Python environment [backend: TkAgg]. For more information, type 'help(pylab)'.
In [1]:
What I want to type at In[1]?
Please help me?
Thanks and with regards, Dasari.
tayral
commented
11 years ago Hi Dasari, Your installation sems to be fine. I guess the best thing to do if you want to use pytriqs/ipytriqs is to look at any python/ipython tutorial. By the way, 1) pytriqs is virtually the same thing as python (it just sets sets the correct paths for you) 2) ipytriqs, likewise, is the same thing as ipython
Have you tried ctrl+D to close python/ipython? This is what one usually does.
You can definitely go through the tutorials (but to understand them you need to understand the python syntax; there are very good tutorials on the web).
Cheers
Le 25/02/13 14:53, dasari123 a écrit :
Hi,
I used a following command at the terminal to run the python script: ipytriqs -i my_script.py --pylab.
(1) I saw the picture(greens function) on my screen. When I closed the picture I didn't get my prompt back. It may be silly question for you. But I am new for this language(python). I used ctrt+c, ctrl+q and some unix commands. It didn't work. Could you please tell me how to get the prompt back.
(2) Why my script is not working with ipytriqs my_script.py command ? Any idea.
(3)Did I have all the libraries when I installed triqs?( It seems to me I missed some c++ libraries). I showed it in my previous mail.
(4)Now can I go through all the tutorials? (installation ok or not)
$ ipytriqs -i my_script.py --pylab
Python 2.7.3 (default, Aug 1 2012, 05:14:39) Type "copyright", "credits" or "license" for more information.
IPython 0.13.1 -- An enhanced Interactive Python. ? -> Introduction and overview of IPython's features. %quickref -> Quick reference. help -> Python's own help system. object? -> Details about 'object', use 'object??' for extra details.
Welcome to pylab, a matplotlib-based Python environment [backend: TkAgg]. For more information, type 'help(pylab)'.
In [1]:
What I want to type at In[1]?
Please help me?
Thanks and with regards, Dasari.
— Reply to this email directly or view it on GitHub https://github.com/TRIQS/TRIQS/issues/108#issuecomment-14026964.
dasari123
commented
11 years ago Hi,
I will go through the python tutorial and triqs tutorial in the triqs webpage.
Is it possible to run the triqs with command line instead of python interface.
Thanks, Dasari.
aeantipov
commented
11 years ago Hi, Dasari.
Last question is a topic of a different subject. TRIQS itself doesn't provide any binary executables, so strictly speaking, you can't run TRIQS from shell.
However, if you get into more details of python, you will probably want to try the argparse python module. It allows to use python script with shell arguments, e.g. python ./my_script.py --T=0.1 .... These values then can be used for running triqs tools.
Andrey.
dasari123
commented
11 years ago Thanks.
parcollet
commented
11 years ago Hi, This discussion is now unrelated to the title : Test do not fail. hence I close this issue.
Hi,
I am Dasari. I am trying to install triqs on my laptop(Ubuntu 12.04, 64 bit). Before install the triqs I installed all prerequisite by following the triqs installation web page. I issued a command cmake with installation directory name and source directory. You can see the screened output of cmake command.
-- Installation directory is /home/dasari/Desktop/triqs/triqs -- The C compiler identification is GNU -- The CXX compiler identification is GNU -- The Fortran compiler identification is GNU -- Check for working C compiler: /usr/bin/gcc -- Check for working C compiler: /usr/bin/gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working Fortran compiler: /usr/bin/gfortran -- Check for working Fortran compiler: /usr/bin/gfortran -- works -- Detecting Fortran compiler ABI info -- Detecting Fortran compiler ABI info - done -- Checking whether /usr/bin/gfortran supports Fortran 90 -- Checking whether /usr/bin/gfortran supports Fortran 90 -- yes -- DYNAMIC Built -- CMAKE_GENERATOR: Unix Makefiles -- CMAKE_CL_64: -- Build type: Release -- Looking for rpc/rpc.h -- Looking for rpc/rpc.h - found -- Looking for stdarg.h -- Looking for stdarg.h - found -- Looking for sys/stat.h -- Looking for sys/stat.h - found -- Looking for sys/systeminfo.h -- Looking for sys/systeminfo.h - not found -- Looking for sys/types.h -- Looking for sys/types.h - found -- Looking for unistd.h -- Looking for unistd.h - found -- Looking for windows.h -- Looking for windows.h - not found -- Looking for C++ include valarray -- Looking for C++ include valarray - found -- Found MPI_C: /usr/local/lib/libmpi.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libm.so;/usr/lib/x86_64-linux-gnu/librt.so;/usr/lib/x86_64-linux-gnu/libnsl.so;/usr/lib/x86_64-linux-gnu/libutil.so;/usr/lib/x86_64-linux-gnu/libm.so;/usr/lib/x86_64-linux-gnu/libdl.so -- Found MPI_CXX: /usr/local/lib/libmpi_cxx.so;/usr/local/lib/libmpi.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libm.so;/usr/lib/x86_64-linux-gnu/librt.so;/usr/lib/x86_64-linux-gnu/libnsl.so;/usr/lib/x86_64-linux-gnu/libutil.so;/usr/lib/x86_64-linux-gnu/libm.so;/usr/lib/x86_64-linux-gnu/libdl.so -- Found MPI_Fortran: /usr/local/lib/libmpi_f90.so;/usr/local/lib/libmpi_f77.so;/usr/local/lib/libmpi.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libm.so;/usr/lib/x86_64-linux-gnu/librt.so;/usr/lib/x86_64-linux-gnu/libnsl.so;/usr/lib/x86_64-linux-gnu/libutil.so;/usr/lib/x86_64-linux-gnu/libm.so;/usr/lib/x86_64-linux-gnu/libdl.so -- MPI compiler was /usr/local/bin/mpicxx -- Falling back to CMake provied LAPACK/BLAS detection. -- Looking for Fortran sgemm -- Looking for Fortran sgemm - found -- Looking for include files CMAKE_HAVE_PTHREAD_H -- Looking for include files CMAKE_HAVE_PTHREAD_H - found -- Looking for pthread_create in pthreads -- Looking for pthread_create in pthreads - not found -- Found Threads: TRUE -- A library with BLAS API found. -- A library with BLAS API found. -- Looking for Fortran cheev -- Looking for Fortran cheev - found -- A library with LAPACK API found. -- Found FFTW: /usr/lib/libfftw3.so -- Found HDF5: debug;/usr/lib/libhdf5_hl.so;/usr/lib/libhdf5.so;/usr/lib/x86_64-linux-gnu/libpthread.so;/usr/lib/x86_64-linux-gnu/libz.so;/usr/lib/x86_64-linux-gnu/libm.so;/usr/lib/libhdf5_cpp.so;optimized;/usr/lib/libhdf5_hl.so;/usr/lib/libhdf5.so;/usr/lib/x86_64-linux-gnu/libpthread.so;/usr/lib/x86_64-linux-gnu/libz.so;/usr/lib/x86_64-linux-gnu/libm.so;/usr/lib/libhdf5_cpp.so -- HDF5 version found is 1.8.4-patch1 in /usr/include -- Python interpreter /usr/bin/python -- Python interpreter ok : version 2.7.3 -- PYTHON_INCLUDE_DIRS = /usr/include/python2.7 -- PYTHON_NUMPY_INCLUDE_DIR = /usr/lib/python2.7/dist-packages/numpy/core/include -- PYTHON_SITE_PKG = /usr/lib/python2.7/dist-packages -- PYTHON_LIBRARY = /usr/lib/python2.7/config/libpython2.7.so -- PYTHON_EXTRA_LIBS =-lssl -lcrypto -lssl -lcrypto -L/usr/lib -lz -lpthread -ldl -lutil -- PYTHON_LINK_FOR_SHARED = -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions -- Numpy include in /usr/lib/python2.7/dist-packages/numpy/core/include -- HDF5_LIBRARIES = debug;/usr/lib/libhdf5_hl.so;/usr/lib/libhdf5.so;/usr/lib/x86_64-linux-gnu/libpthread.so;/usr/lib/x86_64-linux-gnu/libz.so;/usr/lib/x86_64-linux-gnu/libm.so;/usr/lib/libhdf5_cpp.so;optimized;/usr/lib/libhdf5_hl.so;/usr/lib/libhdf5.so;/usr/lib/x86_64-linux-gnu/libpthread.so;/usr/lib/x86_64-linux-gnu/libz.so;/usr/lib/x86_64-linux-gnu/libm.so;/usr/lib/libhdf5_cpp.so -- Triqs general lib detection ( but boost ) -- Adding definitions -D_LARGEFILE_SOURCE;-D_LARGEFILE64_SOURCE;-D_FILE_OFFSET_BITS=64;-D_BSD_SOURCE;-D_FORTIFY_SOURCE=2 -- Adding include /usr/local/include;/usr/include;/usr/include/python2.7;/usr/lib/python2.7/dist-packages/numpy/core/include -- Adding libs /usr/local/lib/libmpi_cxx.so;/usr/local/lib/libmpi.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libm.so;/usr/lib/x86_64-linux-gnu/librt.so;/usr/lib/x86_64-linux-gnu/libnsl.so;/usr/lib/x86_64-linux-gnu/libutil.so;/usr/lib/x86_64-linux-gnu/libm.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/liblapack.so;/usr/lib/libblas.so;/usr/lib/x86_64-linux-gnu/libpthread.so;debug;/usr/lib/libhdf5_hl.so;/usr/lib/libhdf5.so;/usr/lib/x86_64-linux-gnu/libpthread.so;/usr/lib/x86_64-linux-gnu/libz.so;/usr/lib/x86_64-linux-gnu/libm.so;/usr/lib/libhdf5_cpp.so;optimized;/usr/lib/libhdf5_hl.so;/usr/lib/libhdf5.so;/usr/lib/x86_64-linux-gnu/libpthread.so;/usr/lib/x86_64-linux-gnu/libz.so;/usr/lib/x86_64-linux-gnu/libm.so;/usr/lib/libhdf5_cpp.so;/usr/lib/python2.7/config/libpython2.7.so -- Adding library dir -- Python modules will be installed in /home/dasari/Desktop/triqs/triqs/lib/python2.7/dist-packages/pytriqs -- Boost root dir: -- You are not using mkl -- cblas header found at /usr/include -- Found CBLAS: /usr/include -- Found Git: /usr/bin/git -- Git hash 0ff670c0509e1d4977c1f657df5f8bd65a4d5153 -- Git branches :
-- \ WARNING ** -- Wien2k users : after installation of TRIQS, copy the files from -- /home/dasari/Desktop/triqs/triqs/share/triqs/Wien2k_SRC_files/SRC_templates -- to your Wien2k installation WIENROOT/SRC_templates (Cf documentation). -- This is not handled automatically by the installation process.
-- Preparing optional python module CTHyb -- Preparing python module CTHyb -- Making pytriqs/Solvers/HybridizationExpansion/pytriqs_Solver_HybridizationExpansion.py -- Preparing the various scripts -- Configuring done -- Generating done -- Build files have been written to: /home/dasari/Desktop/triqs/triqs_build
I don't have any problem at the time of configure. Then I went for build the triqs. I got an 100% build also. Below I am just showing screened output of 100% build(end lines only). Again no problem with triqs up to here.
[100%] Building CXX object pytriqs/Solvers/HybridizationExpansion/CMakeFiles/_pytriqs_Solver_HybridizationExpansion.dir/C++/MC.cpp.o [100%] Building CXX object pytriqs/Solvers/HybridizationExpansion/CMakeFiles/_pytriqs_Solver_HybridizationExpansion.dir/C++/QMC_wrap.cpp.o Linking CXX shared module _pytriqs_Solver_HybridizationExpansion.so [100%] Built target _pytriqs_Solver_HybridizationExpansion
Now I issued a command make test. The following is the output(end lines only).
113/118 Test #113: dos1 ............................. Passed 2.80 sec Start 114: Wien2kconvert 114/118 Test #114: Wien2kconvert .................... Passed 0.62 sec Start 115: Umat 115/118 Test #115: Umat ............................. Passed 0.13 sec Start 116: SingleSiteBethe 116/118 Test #116: SingleSiteBethe .................._Failed 15.34 sec Start 117: CDMFT_4_sites 117/118 Test #117: CDMFT_4_sites ...................._Failed 24.40 sec Start 118: HubbardI 118/118 Test #118: HubbardI ......................... Passed 0.75 sec
98% tests passed, 2 tests failed out of 118
Total Test time (real) = 48.87 sec
The following tests FAILED: 116 - SingleSiteBethe (Failed) 117 - CDMFT_4_sites (Failed)
" I didn't understand why single site Bethe and CDMFT_4 site failed test".
Without worrying much about test failure, I issued a command make install. I got python libraries in the installation directory/lib and executables in bin directory also. But I didn't get c++ libraries in the lib of installation directory.
Could please help me to solve this problem?
Thanks and with regards, Dasari.