 |
 |
 |
 |
 |
 |
||
 |
 |
 |
 |
 |
| 5 | 1/1 | 返回列表 |
| 查看: 1436 | 回復(fù): 2 | |||
| 當(dāng)前只顯示滿足指定條件的回帖，點(diǎn)擊這里查看本話題的所有回帖 | |||
蔡鋒同學(xué)金蟲 (小有名氣)
|
[求助]
請問下計(jì)算時(shí)出現(xiàn)這些問題是什么原因
|
||
|
在用Castep進(jìn)行優(yōu)化時(shí)出現(xiàn)了下面這兩種錯誤。請問下原因是什么呢？ 1. Convergence failed when doing finite basis set correction. 2. Error in geom_get_forces - electronic_minimisation of current_cell failed 求指點(diǎn) |
回復(fù)此樓» 猜你喜歡
299求調(diào)劑
已經(jīng)有8人回復(fù)
-
一志愿北京理工大學(xué)本科211材料工程294求調(diào)劑
已經(jīng)有6人回復(fù)
-
300求調(diào)劑，材料科學(xué)英一數(shù)二
已經(jīng)有8人回復(fù)
-
招收生物學(xué)/細(xì)胞生物學(xué)調(diào)劑
已經(jīng)有5人回復(fù)
-
070305高分子化學(xué)與物理 304分求調(diào)劑
已經(jīng)有7人回復(fù)
-
289求調(diào)劑
已經(jīng)有13人回復(fù)
-
一志愿哈爾濱工業(yè)大學(xué)材料與化工方向336分
已經(jīng)有9人回復(fù)
-
081200-11408-276學(xué)碩求調(diào)劑
已經(jīng)有6人回復(fù)
-
調(diào)劑求院校招收
已經(jīng)有5人回復(fù)
-
調(diào)劑310
已經(jīng)有8人回復(fù)
» 本主題相關(guān)價(jià)值貼推薦，對您同樣有幫助:
- 計(jì)算時(shí)出現(xiàn)這個(gè)問題怎么解決？
已經(jīng)有5人回復(fù)
- 計(jì)算原子磁矩時(shí)出現(xiàn)對稱性問題
已經(jīng)有7人回復(fù)
- [Materials-studio] [求助] 計(jì)算結(jié)束出現(xiàn)了這個(gè)問題 是什么原因呢 非常著急
已經(jīng)有7人回復(fù)
- vasp5.2編譯完成沒有問題，但是在運(yùn)行時(shí)出現(xiàn)killed by signal 11，請問是什么原因？
已經(jīng)有4人回復(fù)
- 【求助完畢】集群上用vasp計(jì)算ELF有ELFCAR而沒有DOSCAR是啥問題？
已經(jīng)有15人回復(fù)
- 【求助】用castep計(jì)算合金phonons老出錯的原因是什么？
已經(jīng)有10人回復(fù)
- 【求助】aspen 閃蒸計(jì)算出現(xiàn)這個(gè)問題是怎么回事
已經(jīng)有6人回復(fù)
- 【求助】用CASTEP計(jì)算的時(shí)候出現(xiàn)問題
已經(jīng)有11人回復(fù)
- 【求助】在MS中用CASTEP做計(jì)算時(shí)出現(xiàn)問題
已經(jīng)有13人回復(fù)
|
本帖內(nèi)容被屏蔽 |
3樓2021-05-23 22:11:15
gkf高
木蟲 (著名寫手)
世界和平
- 應(yīng)助: 61 (初中生)
- 貴賓: 0.074
- 金幣: 1905.8
- 散金: 3018
- 紅花: 55
- 沙發(fā): 126
- 帖子: 2865
- 在線: 252小時(shí)
- 蟲號: 1418268
- 注冊: 2011-09-26
- 性別: GG
- 專業(yè): 凝聚態(tài)物性 II ：電子結(jié)構(gòu)
【答案】應(yīng)助回帖
★ ★
感謝參與，應(yīng)助指數(shù) +1
賀儀: 金幣+2, 謝謝參與討論 2012-04-04 23:24:28
感謝參與，應(yīng)助指數(shù) +1
賀儀: 金幣+2, 謝謝參與討論 2012-04-04 23:24:28
|
常見錯誤及解決方法 CASTEP Error abort handling An abnormal or premature exit from a CASTEP run can have three causes. 1. CASTEP has detected an error of some kind and chosen to perform a controlled abort of the run. This may occur if 1. There is a syntax or other error in your input files 2. some condition has occurred during the run which prevents it from continuing. This might be a check on the validity of the physics assumptions or a computational constraint.c) 3. CASTEP has requested an action of the operating system (via the Fortran run-time library) which has returned a failure status to CASTEP 2. The operating system has chosen to terminate the CASTEP run and killed it. In a batch system this may be because it exceeded some system resource or queue cputime limit. 3. There is a bug in CASTEP and the process, or one of the parallel processes has terminated with a "segmentation violation" or "bus error" signal (UNIX and Linux) or "access violation" (windows). When trying to understand the cause of the error it is important to work out which of the above three cases has occurred. In case (1) CASTEP always writes a (hopefully) explanatory error message into one of its stderr files. The have names of the form parallel process issued the error message (always 0001 for a serial run). They are deleted on a normal end-of-run exit. If any of these files contains an informational message that proves that CASTEP chose a contro lled abort. If on the other hand all of the empty that proves that the running CASTEP processes were killed externally, either because of an operating system action (case 2) or a bug (case 3). Further diagnosis: Cases (2) and (3) To understand these cases you should look at the logfiles written by the batch job manager (if you are using one) which should contain some information on the reason for aborting the run. These can sometimes be verbose and cryptic; it is usually best to study the output logs of a successful run and to look for differences. You may well have to ask your systems staff to interpret these for you. A further indication of an external abort is the presence of "core" files, which are dumped on a signal. These can sometimes be useful to a guru in further diagnosis of a bug. Running out of memory This is such a common error with plane-wave calcu lations that it merits a section of its own. HEAP Memory exceeded If any of the .nnnn.err files contain the messages * Error in allocating /variable/ in /function/ (CASTEP versions <= 4.0.1) * Out of RAM for /variable/ in /function/ (CASTEP versions >= 4.1) this means that CASTEP requested some memory from the operating system (using Fortran's ALLOCATE statement) and the request was denied, usually because available memory has been exhausted. After checking that your input settings do not contain an error, your options are 1. to use some of CASTEP's memory-saving options eg set parameter OPT_STRATEGY=MEMORY (or OPT_STRATEGY_BIAS to 0 or -3) and PAGE_WVFNS=-1 or PAGE_WVFNS=/max-size/ 2. to find a computer with more memory to run on, (or go to your local computer shop, buy and install some additional memory) 3. If on a parallel system, increase the number of processors for the job. This way the total memory needed will be distributed over a larger number of processes, and the requirement per processor will be smaller STACK Memory exceeded Due to a design limitation of linux and most unix and microsoft operating systems, there is another "memory exceeded" condition which can not be trapped by CASTEP. This occurs when the stack memory is exhausted, and the result is the process is killed with a "segmentation fault" on unix/linux. This is harder to diagnose, but be aware that there are O/S-enforced stack limits which might be much smaller than the physical memory in the system. Google for process stack limits stacksize for more information. the shell command ulimit -s unlimited can be used to increase stack size (bash shells). CASTEP error messages explained It is intended that the error messages CASTEP writes to the as possible self-explanatory. Unfortunately it is not always possible to give useful "end-user" explanations. Here are some commonly encountered abort messages with some explanation. * ERROR: cell_read - failure to open freeform cell file /filename/ * Error model_continuation: Failed to open file /filename/ CASTEP was unable to open the input files for the run specified on the command line, probably because there is no file of that name. Check your command lines and input files. * Error in allocating /variable/ in /function/ (CASTEP versions <= 4.0.1) * Out of RAM for /variable/ in /function/ (CASTEP versions >= 4.1) This common error means that CASTEP ran out of memory. See section "Running out of memory" for more information * Error reading wavefunction coefficients from file in wave_read_all_ser/par This or similar messages means that CASTEP was attempting to read a continuation file but the read failed. This is commonly because the .check file is truncated or corrupt. The wavefunction coefficients are fairly far down the file, after the parameters and cell data, and if the read got that far before failing, it is likely that the file was truncated. This can happen if the previous CASTEP run crashed or was killed while writing the .check file. Check to see if the file size is consistent with any similar .check files you may have. * Trapped SIGINT or SIGTERM. Exiting... (CASTEP versions <= 4.0.1) This message is generated by an otherwise useless signal handler in earlier versions of CASTEP. It means that CASTEP was killed by an external signal. Diagnosis should proceed as for major case (3) * Error check_elec_ground_state : electronic_minimisation of initial cell failed. * Error calculate_finite_basis : Convergence failed when doing finite basis set correction. * Error in /subroutine/ - electronic_minimisation of current_cell failed Any of these messages means that the SCF convergence loop did not converge in in the maximum allowed number of iterations. If you read the end of the .castep file it ought to be obvious whether the run only just failed to converge. In that case specifying a larger value of MAX_SCF_CYCLES in the .param file ought to work. But sometimes it is apparent that the energy is unlikely ever to converge, for example it may oscillate, or be decr easing linearly and slowly. This may indicate that the system is in a poorly-bonded or co-ordinated state, and it's best to ask advice if you don't know how to preceed. * Error in parameters_restore: missing END_GENERAL This can occur on a continuation run where the .check file used for restart is incompatible with the version of CASTEP you are using. We aim for nearly full compatibility, but there are always exceptions. |
2樓2012-04-04 22:27:18
| 最具人氣熱帖推薦 [查看全部] | 作者 | 回/看 | 最后發(fā)表 | |
|---|---|---|---|---|
|
[考研] 一志愿211 初試270分 求調(diào)劑 +8 | 谷雨上岸 2026-03-23 | 9/450 |
|
|---|---|---|---|---|
|
[考研] 一志愿鄭州大學(xué)，080500學(xué)碩，總分317分求調(diào)劑 +5 | 舉個(gè)栗子oi 2026-03-24 | 6/300 |
|
|
|
[考研] 本科新能源科學(xué)與工程，一志愿華理能動285求調(diào)劑 +7 | AZMK 2026-03-28 | 11/550 |
|
|
|
[考研] 本科新能源科學(xué)與工程，一志愿華理能動285求調(diào)劑 +3 | AZMK 2026-03-27 | 5/250 |
|
|
|
[考研] 329求調(diào)劑 +6 | 星野? 2026-03-26 | 6/300 |
|
|
|
[考研] 347求調(diào)劑 +3 | 山頂見α 2026-03-25 | 3/150 |
|
|
|
[考研] 317求調(diào)劑 +6 | 十閑wx 2026-03-24 | 6/300 |
|
|
|
[考研] 291求調(diào)劑 +15 | hhhhxn.. 2026-03-23 | 21/1050 |
|
|
|
[考研] 277跪求調(diào)劑 +5 | 1915668 2026-03-27 | 9/450 |
|
|
|
[考研] 一志愿上海理工能源動力（085800）310分求調(diào)劑 +3 | zhangmingc 2026-03-27 | 4/200 |
|
|
|
[考研] 求調(diào)劑 +3 | 劉柯@ 2026-03-24 | 4/200 |
|
|
|
[考研] 0703化學(xué)338求調(diào)劑！ +6 | Zuhui0306 2026-03-26 | 7/350 |
|
|
|
[考研] 材料與化工304求B區(qū)調(diào)劑 +3 | 邱gl 2026-03-26 | 6/300 |
|
|
|
[考研] 334分 一志愿武理 材料求調(diào)劑 +4 | 李李不服輸 2026-03-26 | 4/200 |
|
|
|
[考研] 一志愿河工大 081700 276求調(diào)劑 +4 | 地球繞著太陽轉(zhuǎn) 2026-03-23 | 4/200 |
|
|
|
[考研] 332求調(diào)劑 +6 | 032500 2026-03-25 | 6/300 |
|
|
|
[考研] 334分 一志愿武理-080500 材料求調(diào)劑 +4 | 李李不服輸 2026-03-25 | 4/200 |
|
|
|
[考研] 347求調(diào)劑 +4 | L when 2026-03-25 | 4/200 |
|
|
|
[考研] 求調(diào)劑 +3 | 李李不服輸 2026-03-25 | 3/150 |
|
|
|
[論文投稿] 急發(fā)核心期刊論文 +3 | 賢達(dá)問津 2026-03-23 | 5/250 |
|