Skip to content
  • Home
  • Recent
Collapse
Brand Logo
CRYSTAL23
Latest v1.0.1
Tutorials Try the Demo Get a License
Tutorials Try the Demo Get a License Instagram
  1. Home
  2. CRYSTAL
  3. Geometry Optimisations
  4. CLSEGV **** NOT PAIRING AT K
MSSC2026 Summer School: Registration is now open!

14-18 Sep 2026, London (UK)

Early Bird fee available until 8 May

CLSEGV **** NOT PAIRING AT K

Scheduled Pinned Locked Moved Geometry Optimisations
2 Posts 2 Posters 37 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • Alexanderundefined Offline
    Alexanderundefined Offline
    Alexander
    wrote last edited by
    #1

    Hello,

    I get this error after optimising the geometry of one of solid solution structures:

    [SYMMETRY ALLOWED INTERNAL DEGREE(S) OF FREEDOM: 6
    TOTAL NUMBER OF PARTNERS = 2
    NUMBER OF THE FIRST COMPONENT = 2
    STAR VECTOR = 1
    IRREDUCIBLE REPRESENTATION = 1
    ERROR **** CLSEGV **** NOT PAIRING AT K = 7
    ----------------------------------------------------------------]

    The optimization starts as expected, but after reaching convergence criteria and going for FINALRUN calculations stops. Using obtained geometry for OPTGEOM restart or FREQCALC results in this error. All other 8 solid solutions were optimized smoothly.

    CrTaO4_SIC4_FREQ.out
    CrTaO4_SIC4.f34
    CrTaO4_SIC4.out

    1 Reply Last reply
    0
    • fbodoundefined Offline
      fbodoundefined Offline
      fbodo
      wrote last edited by
      #2

      Hi Alexander,
      I took a look into your calculations and I performed a few tests on them.

      As you said, the calculation seems to break at the end of the optimization as it enters in the FINALRUN. This is because when you perform a geometry optimization the bielectronic integrals are indexed based on the starting geometry and they are kept the same throughout the entire optimization process to avoid any numerical instabilities. With FINALRUN active, the code performs a new indexing that in your case leads to the issue you observed.

      Working a bit with the OPTGEOM input you gave us I found two possible workarounds:

      • You can either deactivate the FINALRUN option, and if you feel safer you can perform a second optimization on the geometry you obtain
      [...]
      OPTGEOM
      FINALRUN
      0
      END
      [...]
      
      • An alternative option is instead to increase the TOLINTEG used in the optimization, and, in this case, I didn't encounter any issue using
      [...]
      TOLINTEG
      10 10 10 10 20
      [...]
      

      For both cases I have attached an output below
      opt_finalrun.out
      opt_tolinteg.out

      Filippo Bodo
      Department of Chemistry, Southern Methodist University, Dallas , TX, USA
      Dipartimento di Chimica, Università degli Studi di Torino, Torino, Italy
      https://github.com/Filo3dg

      1 Reply Last reply
      1

      Powered by Crystal Solutions
      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Home
      • Recent