Author Topic: Error message from ESCF  (Read 6877 times)

slackenerny

  • Jr. Member
  • **
  • Posts: 12
  • Karma: +0/-0
Error message from ESCF
« on: April 13, 2008, 11:27:59 am »
When running ESCF to determine the spectrum of a compound, it ends with:

Quote
Iteration IRREP Converged      Max. Euclidean
                 roots          residual norm

    1       a        0        4.298597583587716D-02

    2       a        0        2.181993990032693D-02

    3       a        0        5.948377383707624D-03

    4       a        0        1.766785396957421D-03


 Allocation failure for MO-vector scratch arrays in <respon>


 MODTRACE: no modules on stack

  abnormal termination
 escf ended abnormally
 escf ended abnormally
program stopped.

And I can't quite make a sense out of it... Any further explanations?

best wishes!
« Last Edit: April 14, 2008, 10:08:23 am by slackenerny »

christof.haettig

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 258
  • Karma: +0/-0
    • Hattig's Group at the RUB
Re: Error message from ESCF
« Reply #1 on: April 15, 2008, 03:03:19 pm »
You should send a bug report to the TURBOMOLE support desk.

doguapo

  • Jr. Member
  • **
  • Posts: 14
  • Karma: +0/-0
Re: Error message from ESCF
« Reply #2 on: July 29, 2010, 11:15:00 pm »
I'm having an error message too with escf.  I'm running through the tutorial and trying to run a tddft calculation on pentahelicene radical anion - the RIDFT ran fine (b-p86 functional and sVP basis).  when trying to run escf, i have the following error message, after running interactively for around 30 seconds or so:
"
Iteration IRREP Converged  Max. Euclidean
                     roots          residual norm

MODTRACE: no modules on stack

Reference state is non-real unstable
escf ended abnormally
"
any suggestions?  Thanks!

uwe

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 426
  • Karma: +0/-0
Re: Error message from ESCF
« Reply #3 on: August 06, 2010, 09:15:23 pm »
Hi,

slackenerny:

it might be a little bit too late for an answer, but perhaps it helps other users: Allocation failures are in almost all cases caused by memory problems. Either your memory was not sufficient on that machine (or another big job was running at the same time), or your user limits are such that you are not allowed to use as much memory as you expect. Check with ulimit -a or see the post:

http://www.turbo-forum.com/index.php?topic=23.0

doguapo:

This has been discussed several times in this forum. If you enter the string 'unstable' in the Search field on this web site, you will find some posts about it. dimi gave several really helpful answers.

Regards,

Uwe