# Killed during operation of calculix **URL:** \ **Category:** Uncategorized\ **Created:** [July 4, 2023, 6:58am UTC](https://calculix.discourse.group/t/killed-during-operation-of-calculix/1724 "2023-07-04T06:58:29Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Phonix](https://avatars.discourse-cdn.com/v4/letter/p/e274bd/32.png) [@Phonix](https://calculix.discourse.group/u/Phonix)\ **Post date:** [July 4, 2023, 6:58am UTC](https://calculix.discourse.group/t/killed-during-operation-of-calculix/1724/1 "2023-07-04T06:58:29Z")
When I was running calculix in linux system, my program was forced to end because of the killed in the process, was it caused by calculix or was it caused by insufficient memory? (killed at the end, no other error message.) ---
**Author:** ![vicmw](https://avatars.discourse-cdn.com/v4/letter/v/6de8d8/32.png) [@vicmw](https://calculix.discourse.group/u/vicmw)\ **Post date:** [July 4, 2023, 10:49am UTC](https://calculix.discourse.group/t/killed-during-operation-of-calculix/1724/2 "2023-07-04T10:49:24Z")
That is how it responds to too big of a model. I don’t think you can really not have enough memory though. It also crashes like that for when using certain combinations of features. ---
**Author:** ![rsmith](https://yyz2.discourse-cdn.com/free1/user_avatar/calculix.discourse.group/rsmith/32/1684_2.png) [@rsmith](https://calculix.discourse.group/u/rsmith)\ **Post date:** [July 5, 2023, 8:58pm UTC](https://calculix.discourse.group/t/killed-during-operation-of-calculix/1724/3 "2023-07-05T20:58:10Z")
When running the simulation, keep an eye on the amount of memory used. Most desktop environments and window manager can show that. Also check the return value of `ccx`, with e.g. `echo $?` ---
**Author:** ![Phonix](https://avatars.discourse-cdn.com/v4/letter/p/e274bd/32.png) [@Phonix](https://calculix.discourse.group/u/Phonix)\ **Post date:** [July 6, 2023, 1:08am UTC](https://calculix.discourse.group/t/killed-during-operation-of-calculix/1724/4 "2023-07-06T01:08:19Z")
what is meaning of too big of a model? The size of my model is 2m\*3m.And I only used nlgeom and \*restart, read. I’m giving all three directions to each node, is that what’s causing the memory to crash? ---
**Author:** ![Phonix](https://avatars.discourse-cdn.com/v4/letter/p/e274bd/32.png) [@Phonix](https://calculix.discourse.group/u/Phonix)\ **Post date:** [July 6, 2023, 1:11am UTC](https://calculix.discourse.group/t/killed-during-operation-of-calculix/1724/5 "2023-07-06T01:11:14Z")
Since I am using calculix to solve the fluid-structure coupling problem, when I run my program, whether it is the fluid part or calculix, %MEM accounts for 90% or more, which indicates that it is caused by excessive memory consumption? So what’s the solution other than replacing a computer with more memory to do the calculations? And how to check the return value？ ---
**Author:** ![vicmw](https://avatars.discourse-cdn.com/v4/letter/v/6de8d8/32.png) [@vicmw](https://calculix.discourse.group/u/vicmw)\ **Post date:** [July 6, 2023, 2:17am UTC](https://calculix.discourse.group/t/killed-during-operation-of-calculix/1724/6 "2023-07-06T02:17:21Z")
Sorry, by too big, I mean too many DOFs and connectivity between them. If it’s over a few hundred thousand nodes, it could be trouble. But you can’t really run out of memory because the OS will use the disk and it’ll just go slowly. So it’s probably more like the limitations of the CCX build or solver option you’re using. There’s an ILP64 version somewhere that’s good for big model. Also maybe PastiX? ---
**Author:** ![Phonix](https://avatars.discourse-cdn.com/v4/letter/p/e274bd/32.png) [@Phonix](https://calculix.discourse.group/u/Phonix)\ **Post date:** [July 6, 2023, 2:31am UTC](https://calculix.discourse.group/t/killed-during-operation-of-calculix/1724/7 "2023-07-06T02:31:44Z")
I always thought it was the cause of insufficient memory, but I also killed myself when I used a supercomputer calculation just now, so far I don’t know what to do. ---
**Author:** ![Phonix](https://avatars.discourse-cdn.com/v4/letter/p/e274bd/32.png) [@Phonix](https://calculix.discourse.group/u/Phonix)\ **Post date:** [July 6, 2023, 2:39am UTC](https://calculix.discourse.group/t/killed-during-operation-of-calculix/1724/8 "2023-07-06T02:39:02Z")
this is my code first: \*INCLUDE, INPUT=Node.msh \*INCLUDE, INPUT=Element.nam \*INCLUDE, INPUT=Elset.nam \*INCLUDE, INPUT=fixed1.nam \*Material, Name=Material \*Elastic 46500000, 0.35 \*Density 700 \*Shell section, Elset=Elall, Material=Material, Offset=0 0.001 \*Restart, Write \*Step, Nlgeom, Inc=1000 \*DYNAMIC 0.001,0.01 \*Boundary fixed1,1,6,0 \*Cload Nall,1,0.0 Nall,2,0.0 Nall,3,0.0 \*Node file U \*End step second: \*Restart, Read \*Step, Nlgeom, Inc=1000 \*DYNAMIC,DIRECT 0.08,4 \*Boundary 1,1,6,0 3,1,6,0 6,1,6,0 7,1,6,0 9,1,6,0 12,1,6,0 \*Cload, op=New \*Dload, op=New \*Cload \*INCLUDE, INPUT=force.txt \*Node file U \*End step There are about 2800 nodes in total,and 5000+ triangle。 The force.txt file contains the forces for each node in each direction. Can you help me see if I have any obvious mistakes here? Or is there anything that could be improved? ---
**Author:** ![vicmw](https://avatars.discourse-cdn.com/v4/letter/v/6de8d8/32.png) [@vicmw](https://calculix.discourse.group/u/vicmw)\ **Post date:** [July 6, 2023, 5:20am UTC](https://calculix.discourse.group/t/killed-during-operation-of-calculix/1724/9 "2023-07-06T05:20:06Z")
I can’t see anything wrong with it. You can isolate the cause of the problem by removing things until it works. That’s my common troubleshooting technique for mysterious failures. Doesn’t seem nearly enough nodes for memory to be an issue at all. No idea why it would be 90% used. ---
**Author:** ![Phonix](https://avatars.discourse-cdn.com/v4/letter/p/e274bd/32.png) [@Phonix](https://calculix.discourse.group/u/Phonix)\ **Post date:** [July 6, 2023, 6:46am UTC](https://calculix.discourse.group/t/killed-during-operation-of-calculix/1724/10 "2023-07-06T06:46:24Z")
I have this prompt in the process of running, do you know how to modify this? You are using an executable made on Tue Jul 4 16:39:43 CST 2023 \*INFO: restart file yezizz.rin has been opened for reading. it was created with CalculiX Version 2.20 The numbers below are estimated upper bounds number of: nodes: 365457 elements: 5528 one-dimensional elements: 0 two-dimensional elements: 5528 integration points per element: 9 degrees of freedom per node: 3 layers per element: 1 distributed facial loads: 0 distributed volumetric loads: 0 concentrated loads: 68760 single point constraints: 401952 multiple point constraints: 672202 terms in all multiple point constraints: 717490345 tie constraints: 0 dependent nodes tied by cyclic constraints: 0 dependent nodes in pre-tension constraints: 0 sets: 4 terms in all sets: 33452 materials: 1 constants per material and temperature: 2 temperature points per material: 1 plastic data points per material: 0 orientations: 5528 amplitudes: 2 data points in all amplitudes: 2 print requests: 0 transformations: 0 property cards: 0 \*ERROR in u\_calloc: error allocating memory variable=nodempc, file=ccx\_2.20.c, line=272, num=-2142496261, size=4 ---
**Author:** ![vicmw](https://avatars.discourse-cdn.com/v4/letter/v/6de8d8/32.png) [@vicmw](https://calculix.discourse.group/u/vicmw)\ **Post date:** [July 6, 2023, 8:46am UTC](https://calculix.discourse.group/t/killed-during-operation-of-calculix/1724/11 "2023-07-06T08:46:02Z")
A lot of those messages can be hard to interpret. Not sure what error allocating memory really means, nor the “upper bounds” of MPCs/nodes/etc. I tend to ignore the content of a lot of those messages and just delete things to find out what’s causing the problem. ---
**Author:** ![JuanP74](https://avatars.discourse-cdn.com/v4/letter/j/b5a626/32.png) [@JuanP74](https://calculix.discourse.group/u/JuanP74)\ **Post date:** [July 6, 2023, 6:31pm UTC](https://calculix.discourse.group/t/killed-during-operation-of-calculix/1724/12 "2023-07-06T18:31:14Z")
> [@Phonix](#): > > multiple point constraints: 672202 > terms in all multiple point constraints: 717490345 I’d say the problem is related to this…check your MPCs > \*ERROR in u\_calloc: error allocating memory > variable=nodempc, file=ccx\_2.20.c, line=272, num=-2142496261, size=4 ---
**Author:** ![jbr](https://avatars.discourse-cdn.com/v4/letter/j/ecccb3/32.png) [@jbr](https://calculix.discourse.group/u/jbr)\ **Post date:** [July 8, 2023, 1:46am UTC](https://calculix.discourse.group/t/killed-during-operation-of-calculix/1724/13 "2023-07-08T01:46:41Z")
This seems like a very high value: 717,490,345 ---
**Author:** ![jbr](https://avatars.discourse-cdn.com/v4/letter/j/ecccb3/32.png) [@jbr](https://calculix.discourse.group/u/jbr)\ **Post date:** [July 8, 2023, 1:48am UTC](https://calculix.discourse.group/t/killed-during-operation-of-calculix/1724/14 "2023-07-08T01:48:16Z")
I agree with you @JuanP74… It must be related to the expansion of the 2D elements and the associated MPCs. Can you expand these elements to solids and apply proper boundary conditions? ---
**Author:** ![Phonix](https://avatars.discourse-cdn.com/v4/letter/p/e274bd/32.png) [@Phonix](https://calculix.discourse.group/u/Phonix)\ **Post date:** [July 8, 2023, 4:55am UTC](https://calculix.discourse.group/t/killed-during-operation-of-calculix/1724/15 "2023-07-08T04:55:19Z")
This is the result of running \*restart,read many times, as shown in the two inp files I mentioned earlier. How can I check the MPC you mentioned? I don’t know much about it. ---
**Author:** ![Phonix](https://avatars.discourse-cdn.com/v4/letter/p/e274bd/32.png) [@Phonix](https://calculix.discourse.group/u/Phonix)\ **Post date:** [July 8, 2023, 4:58am UTC](https://calculix.discourse.group/t/killed-during-operation-of-calculix/1724/16 "2023-07-08T04:58:08Z")
I’m actually using the shell section in 3D, and the element is S3. I can’t turn it into solid section at the moment, so don’t I have any other solution? ---
**Author:** ![JuanP74](https://avatars.discourse-cdn.com/v4/letter/j/b5a626/32.png) [@JuanP74](https://calculix.discourse.group/u/JuanP74)\ **Post date:** [July 8, 2023, 8:20am UTC](https://calculix.discourse.group/t/killed-during-operation-of-calculix/1724/17 "2023-07-08T08:20:52Z")
with the info available is difficult to figure out. They’re created automatically for CCX shells (search for **knots** in the manual) but considering the number of elements I can´t imagine why there are so many in your model. You should check your model first in a different solution sequence (e.g. static) and see how it goes. ---
**Author:** ![Phonix](https://avatars.discourse-cdn.com/v4/letter/p/e274bd/32.png) [@Phonix](https://calculix.discourse.group/u/Phonix)\ **Post date:** [July 8, 2023, 9:42am UTC](https://calculix.discourse.group/t/killed-during-operation-of-calculix/1724/18 "2023-07-08T09:42:19Z")
You can look at the two inp files I mentioned earlier, the first inp file only runs one piece, and then the second inp file is run every time the force-txt file is updated, and it took about dozens of times to run the second inp file before this error occurred. Is it because many times \*restart, read caused by the number of elements accumulated a lot? ---
**Author:** ![JuanP74](https://avatars.discourse-cdn.com/v4/letter/j/b5a626/32.png) [@JuanP74](https://calculix.discourse.group/u/JuanP74)\ **Post date:** [July 8, 2023, 11:57am UTC](https://calculix.discourse.group/t/killed-during-operation-of-calculix/1724/19 "2023-07-08T11:57:02Z")
Check the output evolution from the first restart analysis to see if it makes sense ---
**Author:** ![jbr](https://avatars.discourse-cdn.com/v4/letter/j/ecccb3/32.png) [@jbr](https://calculix.discourse.group/u/jbr)\ **Post date:** [July 8, 2023, 1:39pm UTC](https://calculix.discourse.group/t/killed-during-operation-of-calculix/1724/20 "2023-07-08T13:39:37Z")
Can you try expanding the mesh using gmsh or something similar? Just to avoid the expansion part. [Next page](https://calculix.discourse.group/t/killed-during-operation-of-calculix/1724.md?page=2)