If you run into troubles, it is always a good habit to report the following information:
  • the way build.mrcc was invoked
  • the output of build.mrcc
  • compiler version (for example: ifort -V, gfortran -v)
  • blas/lapack versions
  • as well as gcc and glibc versions

as well as the value of the relevant environmental variables, such OMP_NUM_THREADS, etc.

This information helps us a lot when figuring out what is going on with your compilation :)

ldfzvec: number of arguments in dft_core call does not match with definition

  • i.s.ger
  • Topic Author
  • Offline
  • New Member
  • New Member
More
4 weeks 1 day ago #1479 by i.s.ger
Hello!

I've looked through MRCC source code and I've found that call dft_core in ldfzvec.f90 does not match with definition of dft_core in dft.f.

In one of the versions of MRCC (I do not know exactly which, but not older that MRCC 2023), dft_core has definition:
./dft.f:2:      subroutine dft_core(nbasis,nal,nbe,focka,fockb,moa,mob,grfile,
./dft.f-3-     $dcore,iout,exc,dft,minpfile,scftype,ifltln,maxcor,imem,imem1,
./dft.f-4-     $icore,verbosity,dero,grad,route,densa,densb,nstate,mult,chfx,
./dft.f-5-     $istore,g2ab,vint2ab,lldenscorr,ifb_loc,nvirta,nvirtb,dfnbasis)

at ldfzvec, it is called as:
./ldfzvec.f90:1162:  call dft_core(nbasis,nal,nbe,dcore(ixca),dcore(ixcb),dcore(imoa),dcore(imob), &
./ldfzvec.f90-1163-    scrfile4,dcore,iout,exc,dft,minpfile,iscft,ifltln,maxcor,imem,imem1,icore,  &
./ldfzvec.f90-1164-    0,0,dcore,route,dcore(idens),dcore(idensb),1,1,chfx,0)

The following args are not defined there:
,g2ab,vint2ab,lldenscorr,ifb_loc,nvirta,nvirtb,dfnbasis)

Igor


 

Please Log in or Create an account to join the conversation.

Time to create page: 0.037 seconds
Powered by Kunena Forum