Firefly and PC GAMESS-related discussion club



Learn how to ask questions correctly


Re^3: CASSCF/MCQDPT input files questions

sanya
sanya@photonics.ru


>This part I find a bit confusing, perhaps because we're talking about both states and roots. From what I understand, both WSTATE (in $DET) and KSTATE (in $MCQDPT) refer to roots, whereas NSTATE (in $DET) refers to CI states. I assume that when you speak of "no less than 10 states", you are talking about NSTATE in $DET (NSTATE=10 or higher).

No, no! I was talking about KSTATE. In fact, I see no difference between roots (solutions of CI equations) and states (linear combinations of Slater determinants on optimized orbitals with the corresponding CI coefficients) at CASSCF stage. In MCQDPT, the CI roots included in the effective Hamiltonian are corrected in the second order of perturbation theory (which includes their mixing, reordering, etc.). Therefore, PT-corrected states may go far from the initial CASSCF states (CI roots).

NSTATE in $DET ($DRT) defines how many states (CI roots) we want to calculate. WSTATE defines the states whose densities are averaged to obtain the optimized orbitals (state-averaged CASSCF). I.e., if you need the ground and lowest excited state, WSTATE(1)=1.,1. NSTATE is always greater or equal to WSTATE. The number of states in the active space is just the number of all possible excitations from occupied active orbitals to unoccupied ones; this number grows dramatically with the size of the active space. The program prints the number of CSFs (for GUGA) or determinants (for ALDET), this equals the number of states in the active space and may range from 4 (for CAS(2,2)) to several millions and even more.

NSTATE from $DET or $DRT as well as WSTATE is not used by MCQDPT routine. MCQDPT uses only optimized orbitals (which depend on both NSTATE and WSTATE). KSTATE defines the effective Hamiltonian (which appears at the MCQDPT stage). It is the size of the effective Hamiltonian that should be large enough to obtain sensible results. For two states (ground and first excited state), it should include no less than 10 states (KSTATE=1,1,1,1,1,1,1,1,1,1).

>Having that said, I would like to provide the following hypothetical case to see if I got the point: the cyclization of hexatriene to cyclohexadiene. This is a 6-electron pericyclic reaction, so CASSCF(6,6) would be a good active space for this. May I ask you to comment on the following input sections which I would use for such a case? (BTW, I do understand that for bigger systems it is better to run the CASSCF part parallel and the MCQDPT part multithreaded in two separate runs).

CASSCF(6,6) is a minimum active space for this system. If possible, it is advisable to add some extra orbitals (usually, pi) for better description of the active orbitals. Anyway, if you face problems (poor convergence, different starting MOs leading to different CASSCF solutions, some orbitals initially included in the active space being missing after iterations, etc.), first try to expand the active space.

Some more points about WSTATE. WSTATE(1)=1.,0.,... defines a pure state-specific CASSCF for the ground state. But if you want to perform a state-specific CASSCF for the first excited state, WSTATE(1)=0.,1. may cause problems. In such cases, it is advisable to set WSTATE(1)=0.1,1.0 to perform an "almost state-specific" CASSCF for the excited state (and, correspondingly, WSTATE(1)=1.0,0.1 for the ground state for consistency). But state-averaged CASSCF (WSTATE(1)=1.,1.) is better.

How many states should be included in WSTATE, is also not so evident. In some cases, CASSCF is not a good approximation. The order of roots may be not quite correct. If all the necessary states are included in the effective Hamiltonian, they'll be corrected by MCQDPT and go into their places. But if some of them are not included in WSTATE (say, the necessary state is #7 and WSTATE included only 4 lowest states), their density is not taken into account in orbital optimization, and these states just fall out of the active space. No state -- nothing to correct. So, for the first run, set NSTATE certainly larger than you'll need in all further calculations (say, 10 instead of 5) and look at all the CI roots. Probably, the state you need is higher than you expect. In further runs, you may set NSTATE as necessary.


[ Previous ] [ Next ] [ Index ]           Tue Oct 19 '10 2:02pm
[ Reply ] [ Edit ] [ Delete ]           This message read 1324 times