If you guys get "STOP 1 " message or an error like "Error in routine readpp (1): file C:\Users\manas\.burai\.pseudopot/Fe.pbe-nd-rrkjus.UPF not found" in the output file, then it is because of the wrong path/address of Pseudopotential provided in the pseudo_dir attribute of input file. You can use pseudo_dir = '.' in the input file instead. Download the updated input files here: www.bragitoff.com/wp-content/uploads/2020/07/QE_Sample_Input_Files.zip
@kamalgurnani9244 жыл бұрын
My 'bin' folder is empty, why is that happening? Can anyone help me?
@suleimanbashiradamu4 жыл бұрын
Thank you very much for this video. You are one of the best tutors that I will always recommend.
@dr.vijayakumar32592 ай бұрын
I am unable to activate the materials API search option in BURAI
@alexderak86764 жыл бұрын
Hi, I have a problem in the last part when we copy the pw.x and i run the test. There is a message STOP 1 and in the output file say "Error in routine readpp (1): file C:\Users\manas\.burai\.pseudopot/Fe.pbe-nd-rrkjus.UPF not found" Could you help me?
@PhysWhiz4 жыл бұрын
Use the address of the PP for your PC. This is where I stored the PP--->>. C:\Users\manas\.burai You should use the address corresponding to your PC.
@anilrai7734 Жыл бұрын
Sir bin folder didn't install in my laptop. It got crashed giving error =could not find namelist and control
@hakimaouhenou8622 жыл бұрын
please can you help me , I don't have file of calculation for starting to calcul DFT byQE
@jeevaraj23273 жыл бұрын
No such file or directory error after make pw command, how to solve it
@م.م.خالدعبداللهنجم2 жыл бұрын
How can i install qe on windows? please could you help me i cant do that
@sayanjitb2 жыл бұрын
For my case make pw command r make all, none of them are working. It is showing Makefile:9:make.inc: No such file or directory make: *** No rule to make target 'make.inc'. stop. please help me out. TIA
@anilrai7734 Жыл бұрын
make pw command didn't work in my terminal sir.. There is warning= nonexistent include durectory
@SAJALPHYS2 жыл бұрын
Sir when I'm giving this command 'make all' showing the following error: sajal@sajal-Acer-one-14-Z422:~/qe-7.0-ReleasePack/qe-7.0$ make all Command 'make' not found, but can be installed with: sudo apt install make # version 4.2.1-1.2, or sudo apt install make-guile # version 4.2.1-1.2 Please help.
@wenusarasatheekshana17382 жыл бұрын
install make in given versions
@PhysWhiz2 жыл бұрын
Sorry for the late reply. But the solution is in the error itself. You need to install 'make'. Run this in the terminal sudo apt-get install --reinstall make
@collectorsspace5 жыл бұрын
thank you so much for this video !!
@baharulislamlaskar045 жыл бұрын
Dear Sir, I'm looking forward to knowing from you about how to install quantum espresso (in parallel) on an Ubuntu platform.
@ManasSharma075 жыл бұрын
Next tutorial will be about that
@baharulislamlaskar045 жыл бұрын
I would be really grateful to you then!
@PhysWhiz5 жыл бұрын
Sorry for being late. But I just uploaded a tutorial for that. You can check it out here: kzbin.info/www/bejne/aIGke3qog82NeJo Essentially you just need to install openmpi somehow.
@baharulislamlaskar045 жыл бұрын
Thank you very much, Sir!
@mjggrandgeneration63244 жыл бұрын
@@ManasSharma07 r u working on quantum espresso?
@abhishekagarwal42663 жыл бұрын
I am trying to install fortran compiler but i am facing problems. My linux is boss linux 6.1
@wenusarasatheekshana17382 жыл бұрын
configure: error: Fortran could not compile .f90 files what is the solution of this error? thank u in advance
@동진쎄미켐-v5w3 жыл бұрын
i installed it as you teach. but i only can use MPI but not openMP. what shall I install more?
@jodieryngnga77314 жыл бұрын
i also face" stop 1" in the terminal when i copy pw.x . i don't understand when you mention use the corresponding address in the previous comment
@PhysWhiz4 жыл бұрын
Could you please write down the complete error. In a previous comment they mention that the error is because of the wrong address of Pseudopotential provided in the pseudo_dir attribute of input file. This is because the address was corresponding to what it was on my PC but won't work for others like you. If that is the error you got then maybe you can try by using this updated set of input files: www.bragitoff.com/wp-content/uploads/2020/07/QE_Sample_Input_Files.zip This should definitely work.
@anujsingh24304 жыл бұрын
After running scf.in it's showing STOP1 and in scf.out it's showing "Error in routine postproc(1)"
@sidhivinayakmmallya16222 жыл бұрын
Nothing to be done for pw kya kren?
@bgphysics94754 жыл бұрын
What is minimum configuration (computational hardware) requirement for electronic structural calculation like Ferrites and magnetic materials using Quantum Espresso?
@ravtepdav3 жыл бұрын
thank you so much Do you know how can I open now QE if I already install it? I am new in these thing of Ubuntu:(
@othoncampos10695 жыл бұрын
4:41 Here, the syntax "build-essential" for Fortran compiler also works.
@bhavikthacker58253 жыл бұрын
I want your help to install quantum espresso
@SkanderTALEBHACINE5 жыл бұрын
Thanks alot , but where is the Sample Files to test installation? there is no such file above?! thanks again
@PhysWhiz5 жыл бұрын
I'm sorry for forgetting to add the link to that. I've now added the link in the description. www.bragitoff.com/wp-content/uploads/2019/05/QE_Sample_Input_Files.zip
@comprehensivemathsscience12174 жыл бұрын
Useful
@priyambadaaiswarya18313 жыл бұрын
Instead of writing make pw. ..I tried it by using make all command but after installation when I tried to run one example from examples folder it shows that mpirun: not found Kindly help me out
@PhysWhiz3 жыл бұрын
Because mpirun is an independent command that enable parallel computing. It is possible that you may not have it installed. First verify that your bin folder has the quantum espresso executables lile pw.x, etc. The try to run pw.x inputfile > outputfile Make sure that you run the above command from the directory where you have the input file. If this works then we can try to discuss abiut how to install mpirun.
@PhysWhiz3 жыл бұрын
Also as you can see in the title above, this video only explains serial compilation. For parallel compilation refer to this video kzbin.info/www/bejne/aIGke3qog82NeJo The command to install mpirun is given in the description of the linked video
@priyambadaaiswarya18313 жыл бұрын
@@PhysWhiz ok thanks Sir
@priyambadaaiswarya18313 жыл бұрын
@@PhysWhiz sir I tried to run one example but it shows error in routine check_tempdir(1) cannot be created or accessed
@PhysWhiz3 жыл бұрын
Can you paste the contents of the input file here
@ajazulhaq5514 Жыл бұрын
Sir how to install it on hpc linux cluster
@PhysWhiz Жыл бұрын
Same procedure, but I recommend you follow my other tutorial to compile QE with parallelizations
@tarifulazam29945 жыл бұрын
Your video goes blank after 15:45
@PhysWhiz5 жыл бұрын
Fixed
@sahirmalik8594 жыл бұрын
Sir what is this file which you run program please tell me
@shubha29054 жыл бұрын
Hello Sir I'm getting this error "/home/physics1/qe-6.5/bin/pw.x: error while loading shared libraries: libmkl_scalapack_lp64.so: cannot open shared object file: No such file or directory". How can i resolve it?? Please help!
@PhysWhiz4 жыл бұрын
Try this command source compilervars.sh intel64
@shubha29054 жыл бұрын
@@PhysWhiz in bashrc file
@PhysWhiz4 жыл бұрын
You can first try to just run it in the terminal. If it works then you can add it to the bashrc.
@shubha29054 жыл бұрын
@@PhysWhiz After adding the location of compilervars.sh in bashrc, I'm getting an error "/home/physics1/qe-6.5/bin/pw.x: error while loading shared libraries: libmkl_gf_lp64.so: cannot open shared object file: No such file or directory ".
@shubha29054 жыл бұрын
I have made following changes in make.inc file, Please have a look! # make.inc. Generated from make.inc.in by configure. # compilation rules .SUFFIXES : .SUFFIXES : .o .c .f .f90 # most fortran compilers can directly preprocess c-like directives: use # $(MPIF90) $(F90FLAGS) -c $< # if explicit preprocessing by the C preprocessor is needed, use: # $(CPP) $(CPPFLAGS) $< -o $*.F90 # $(MPIF90) $(F90FLAGS) -c $*.F90 -o $*.o # remember the tabulator in the first column !!! .f90.o: $(MPIF90) $(F90FLAGS) -c $< # .f.o and .c.o: do not modify .f.o: $(F77) $(FFLAGS) -c $< .c.o: $(CC) $(CFLAGS) -c $< # Top QE directory, useful for locating libraries, linking QE with plugins # The following syntax should always point to TOPDIR: TOPDIR = $(dir $(abspath $(filter %make.inc,$(MAKEFILE_LIST)))) # if it doesn't work, uncomment the following line (edit if needed): # TOPDIR = /home/physics1/qe-6.5 # DFLAGS = precompilation options (possible arguments to -D and -U) # used by the C compiler and preprocessor # To use libxc (v>=3.0.1), add -D__LIBXC to DFLAGS # See include/defs.h.README for a list of options and their meaning # With the exception of IBM xlf, FDFLAGS = $(DFLAGS) # For IBM xlf, FDFLAGS is the same as DFLAGS with separating commas # MANUAL_DFLAGS = additional precompilation option(s), if desired # BEWARE: it does not work for IBM xlf! Manually edit FDFLAGS MANUAL_DFLAGS = DFLAGS = -D__DFTI -D__MPI -D__SCALAPACK FDFLAGS = $(DFLAGS) $(MANUAL_DFLAGS) # IFLAGS = how to locate directories with *.h or *.f90 file to be included # typically -I$(TOPDIR)/include -I/some/other/directory/ # the latter contains .e.g. files needed by FFT libraries # for libxc add -I/path/to/libxc/include/ IFLAGS = -I$(TOPDIR)/include -I$(TOPDIR)/FoX/finclude -I$(TOPDIR)/S3DE/iotk/include/ -I/opt/intel/mkl/include # MOD_FLAG = flag used by f90 compiler to locate modules MOD_FLAG = -I # BASEMOD_FLAGS points to directories containing basic modules, # while BASEMODS points to the corresponding module libraries # Each Makefile can add directories to MODFLAGS and libraries to QEMODS BASEMOD_FLAGS= $(MOD_FLAG)$(TOPDIR)/iotk/src \ $(MOD_FLAG)$(TOPDIR)/Modules \ $(MOD_FLAG)$(TOPDIR)/FFTXlib \ $(MOD_FLAG)$(TOPDIR)/LAXlib \ $(MOD_FLAG)$(TOPDIR)/UtilXlib \ $(MOD_FLAG)$(TOPDIR)/FoX/finclude # Compilers: fortran-90, fortran-77, C # If a parallel compilation is desired, MPIF90 should be a fortran-90 # compiler that produces executables for parallel execution using MPI # (such as for instance mpif90, mpf90, mpxlf90,...); # otherwise, an ordinary fortran-90 compiler (f90, g95, xlf90, ifort,...) # If you have a parallel machine but no suitable candidate for MPIF90, # try to specify the directory containing "mpif.h" in IFLAGS # and to specify the location of MPI libraries in MPI_LIBS MPIF90 = mpif90 F90 = gfortran CC = cc F77 = gfortran # GPU architecture (Kepler: 35, Pascal: 60, Volta: 70 ) GPU_ARCH= # CUDA runtime (Pascal: 8.0, Volta: 9.0) CUDA_RUNTIME= # CUDA F90 Flags CUDA_F90FLAGS= # C preprocessor and preprocessing flags - for explicit preprocessing, # if needed (see the compilation rules above) # preprocessing flags must include DFLAGS and IFLAGS CPP = cpp CPPFLAGS = -P -traditional -Uvector $(DFLAGS) $(IFLAGS) # compiler flags: C, F90, F77 # C flags must include DFLAGS and IFLAGS # F90 flags must include MODFLAGS, IFLAGS, and FDFLAGS with appropriate syntax CFLAGS = -O3 $(DFLAGS) $(IFLAGS) F90FLAGS = $(FFLAGS) -x f95-cpp-input $(FDFLAGS) $(CUDA_F90FLAGS) $(IFLAGS) $(MODFLAGS) FFLAGS = -O3 -g # compiler flags without optimization for fortran-77 # the latter is NEEDED to properly compile dlamch.f, used by lapack FFLAGS_NOOPT = -O0 -g # compiler flag needed by some compilers when the main program is not fortran # Currently used for Yambo FFLAGS_NOMAIN = # Linker, linker-specific flags (if any) # Typically LD coincides with F90 or MPIF90, LD_LIBS is empty # for libxc, set LD_LIBS=-L/path/to/libxc/lib/ -lxcf90 -lxcf03 -lxc LD = mpif90 LDFLAGS = -g LD_LIBS = # External Libraries (if any) : blas, lapack, fft, MPI # If you have nothing better, use the local copy via "--with-netlib" : # BLAS_LIBS = /your/path/to/espresso/LAPACK/blas.a # BLAS_LIBS_SWITCH = internal BLAS_LIBS = -L/opt/intel/mkl/lib/intel64 -lmkl_gf_lp64 -lmkl_sequential -lmkl_core BLAS_LIBS_SWITCH = external # If you have nothing better, use the local copy via "--with-netlib" : # LAPACK_LIBS = /your/path/to/espresso/LAPACK/lapack.a # LAPACK_LIBS_SWITCH = internal # For IBM machines with essl (-D__ESSL): load essl BEFORE lapack ! # remember that LAPACK_LIBS precedes BLAS_LIBS in loading order LAPACK_LIBS = LAPACK_LIBS_SWITCH = external SCALAPACK_LIBS = -lmkl_scalapack_lp64 -lmkl_blacs_openmpi_lp64 # nothing needed here if the the internal copy of FFTW is compiled # (needs -D__FFTW in DFLAGS) FFT_LIBS = # HDF5 HDF5_LIBS = FOX_LIB = -L$(TOPDIR)/FoX/lib -lFoX_dom -lFoX_sax -lFoX_wxml -lFoX_common\ -lFoX_utils -lFoX_fsys FOX_FLAGS = # For parallel execution, the correct path to MPI libraries must # be specified in MPI_LIBS (except for IBM if you use mpxlf) MPI_LIBS = # IBM-specific: MASS libraries, if available and if -D__MASS is defined in FDFLAGS MASS_LIBS = # CUDA libraries CUDA_LIBS= CUDA_EXTLIBS = # ar command and flags - for most architectures: AR = ar, ARFLAGS = ruv AR = ar ARFLAGS = ruv # ranlib command. If ranlib is not needed (it isn't in most cases) use # RANLIB = echo RANLIB = ranlib # all internal and external libraries - do not modify FLIB_TARGETS = all LIBOBJS = $(TOPDIR)/clib/clib.a $(TOPDIR)/iotk/src/libiotk.a LIBXC_LIBS = QELIBS = $(CUDA_LIBS) $(SCALAPACK_LIBS) $(LAPACK_LIBS) $(FOX_LIB) $(FFT_LIBS) $(BLAS_LIBS) $(MPI_LIBS) $(MASS_LIBS) $(HDF5_LIBS) $(LIBXC_LIBS) $(LD_LIBS) # wget or curl - useful to download from network WGET = wget -O # Install directory - "make install" copies *.x executables there PREFIX = /usr/local Am I doing right or not?? Please help!!!