# RESTART does not write resutls with ccx\_i8

**URL:** <https://calculix.discourse.group/t/restart-does-not-write-resutls-with-ccx-i8/2572>\
**Category:** Analysis issues\
**Created:** [February 5, 2025, 8:15pm UTC](https://calculix.discourse.group/t/restart-does-not-write-resutls-with-ccx-i8/2572 "2025-02-05T20:15:33Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![Iacobellis88](https://avatars.discourse-cdn.com/v4/letter/i/9de0a6/32.png) [@Iacobellis88](https://calculix.discourse.group/u/Iacobellis88)\
**Post date:** [February 5, 2025, 8:15pm UTC](https://calculix.discourse.group/t/restart-does-not-write-resutls-with-ccx-i8/2572/1 "2025-02-05T20:15:33Z")

</div>

Hello everyone,  
I am using ccx.i8 and I am using RESTART.  
Everything works well, but when the restart simulation(\*RESTART,READ) finishes the frd file has got 1kb. Inside there is not results.  
What could be the issue?  
I am using these cards to lauch my files for i8  
set CCX\_NPROC\_RESULTS=20  
set CCX\_NPROC\_STIFFNESS=20  
set OMP\_NUM\_THREADS=20  
set MKL\_NUM\_THREADS=20  
set MKL\_INTERFACE\_LAYER=ILP64  
set CCX\_PATH=C:\Users\housing  
cmd /k %CCX\_PATH%\ccx\_i8.exe MODELLO\_PRET\_CCX

---

<div class="post-metadata">

**Author:** ![Iacobellis88](https://avatars.discourse-cdn.com/v4/letter/i/9de0a6/32.png) [@Iacobellis88](https://calculix.discourse.group/u/Iacobellis88)\
**Post date:** [February 6, 2025, 4:45pm UTC](https://calculix.discourse.group/t/restart-does-not-write-resutls-with-ccx-i8/2572/2 "2025-02-06T16:45:11Z")

</div>

Anyone can help me,please?

---

<div class="post-metadata">

**Author:** ![yolk](https://avatars.discourse-cdn.com/v4/letter/y/d07c76/32.png) [@yolk](https://calculix.discourse.group/u/yolk)\
**Post date:** [February 6, 2025, 5:40pm UTC](https://calculix.discourse.group/t/restart-does-not-write-resutls-with-ccx-i8/2572/3 "2025-02-06T17:40:37Z")

</div>

Can you post your input file?

---

<div class="post-metadata">

**Author:** ![Iacobellis88](https://avatars.discourse-cdn.com/v4/letter/i/9de0a6/32.png) [@Iacobellis88](https://calculix.discourse.group/u/Iacobellis88)\
**Post date:** [February 7, 2025, 9:22am UTC](https://calculix.discourse.group/t/restart-does-not-write-resutls-with-ccx-i8/2572/4 "2025-02-07T09:22:52Z")

</div>

[https://calculix.discourse.group/t/restart-does-not-write-resutls-with-ccx-i8/2572/3?u=iacobellis88](https://calculix.discourse.group/t/restart-does-not-write-resutls-with-ccx-i8/2572/3)

I copied both files .Thank you

---

<div class="post-metadata">

**Author:** ![Iacobellis88](https://avatars.discourse-cdn.com/v4/letter/i/9de0a6/32.png) [@Iacobellis88](https://calculix.discourse.group/u/Iacobellis88)\
**Post date:** [February 9, 2025, 3:11pm UTC](https://calculix.discourse.group/t/restart-does-not-write-resutls-with-ccx-i8/2572/5 "2025-02-09T15:11:22Z")

</div>

did you check my inpu?

---

<div class="post-metadata">

**Author:** ![Durbul](https://avatars.discourse-cdn.com/v4/letter/d/8dc957/32.png) [@Durbul](https://calculix.discourse.group/u/Durbul)\
**Post date:** [February 9, 2025, 6:35pm UTC](https://calculix.discourse.group/t/restart-does-not-write-resutls-with-ccx-i8/2572/6 "2025-02-09T18:35:09Z")

</div>

Did you check if any of the restart test cases work for you?  
E.g. beamwrite / beamread?

---

<div class="post-metadata">

**Author:** ![yolk](https://avatars.discourse-cdn.com/v4/letter/y/d07c76/32.png) [@yolk](https://calculix.discourse.group/u/yolk)\
**Post date:** [February 10, 2025, 4:20am UTC](https://calculix.discourse.group/t/restart-does-not-write-resutls-with-ccx-i8/2572/7 "2025-02-10T04:20:06Z")

</div>

That link doesn’t seem to work for me unfortunately. I would also suggest trying the test cases Durbul mentioned.

---

<div class="post-metadata">

**Author:** ![Iacobellis88](https://avatars.discourse-cdn.com/v4/letter/i/9de0a6/32.png) [@Iacobellis88](https://calculix.discourse.group/u/Iacobellis88)\
**Post date:** [February 10, 2025, 11:19am UTC](https://calculix.discourse.group/t/restart-does-not-write-resutls-with-ccx-i8/2572/8 "2025-02-10T11:19:37Z")

</div>

As I told before, restart with dynamic.exe works perfectly. The problem is about i8.ccx. When I use it, everything works but at the end I dont get results from restart step. A file of 1kb is created. To run i8 analysis , I used the string above.

---

<div class="post-metadata">

**Author:** ![Iacobellis88](https://avatars.discourse-cdn.com/v4/letter/i/9de0a6/32.png) [@Iacobellis88](https://calculix.discourse.group/u/Iacobellis88)\
**Post date:** [February 10, 2025, 11:22am UTC](https://calculix.discourse.group/t/restart-does-not-write-resutls-with-ccx-i8/2572/10 "2025-02-10T11:22:11Z")

</div>

> **[MODELLO\_PRET\_CCX.inp](https://wetransfer.com/downloads/9d9898c83b3ac1bd946ff7ea9e9944a920250210112026/0e7344?t_exp=1739445626&t_lsid=647b485a-f649-45f3-9e6d-340b9cbc9ad7&t_network=link&t_rid=ZW1haWx8NjdhNWQwOTI2ZTQ3YzczOTVlMzgwMmVj&t_s=download_link&t_ts=1739186426)**
>
> 2 files sent via WeTransfer, the simplest way to send your files around the world

try now please.

---

<div class="post-metadata">

**Author:** ![fgr](https://avatars.discourse-cdn.com/v4/letter/f/f4b2a3/32.png) [@fgr](https://calculix.discourse.group/u/fgr)\
**Post date:** [February 10, 2025, 12:49pm UTC](https://calculix.discourse.group/t/restart-does-not-write-resutls-with-ccx-i8/2572/11 "2025-02-10T12:49:53Z")

</div>

@Iacobellis88  
I don’t know why you are using the extended version og ccx (ccx\_i8), I didn’t have problems with the standard version.  
I reduce the simulation time from 1 sec to 0.2 sec. but this was only because I’m not very patient.  
My approach was to run the job from a command shell. I can be windows, linux or mac-os, I don’t which one you are using.  
In the command shell you should as example execute the following commands:  
1:  
ccx\_2.22 -i MODELLO\_PRET\_CCX\_1  
2: windows  
copy MODELLO\_PRET\_CCX\_1.rout MODELLO\_PRET\_CCX.rin  
2: linux, mac-os  
cp MODELLO\_PRET\_CCX\_1.rout MODELLO\_PRET\_CCX.rin  
3:  
ccx\_2.22 -i MODELLO\_PRET\_CCX

this will give you 2 output files  
MODELLO\_PRET\_CCX\_1.frd  
MODELLO\_PRET\_CCX.frd

with app following contents and it seems you have some boundary errors in the restart

 ![MODELLO_PRET_CCX_1](https://global.discourse-cdn.com/free1/uploads/calculix/original/2X/e/eee7a9ae0667d25b544324376d42f9ef33e6ff4f.jpeg)  
 ![MODELLO_PRET_CCX](https://global.discourse-cdn.com/free1/uploads/calculix/original/2X/d/d1e27a776c3b735ffda7edc219c3f51dab66a057.jpeg)

I forget to append, that the offical ccx\_2.22 source isn’t prepared for running Pardiso with 64 bit integers.  
In order to do this one will need to implement following in the pardiso.c at the corrosponding lines

```auto
line 353
#ifdef INTSIZE64
  FORTRAN(pardiso_64,(pt,&maxfct,&mnum,&mtype,&phase,neq,aupardiso,
		   pointers,icolpardiso,perm,&nrhs,iparm,&msglvl,
                   b,x,&error));
#else
  FORTRAN(pardiso,(pt,&maxfct,&mnum,&mtype,&phase,neq,aupardiso,
		   pointers,icolpardiso,perm,&nrhs,iparm,&msglvl,
                   b,x,&error));
#endif

line 395
#ifdef INTSIZE64
  FORTRAN(pardiso_64,(pt,&maxfct,&mnum,&mtype,&phase,neq,aupardiso,
		   pointers,icolpardiso,perm,nrhs,iparm,&msglvl,
                   b,x,&error));
#else
  FORTRAN(pardiso,(pt,&maxfct,&mnum,&mtype,&phase,neq,aupardiso,
		   pointers,icolpardiso,perm,nrhs,iparm,&msglvl,
                   b,x,&error));
#endif

lline 420
#ifdef INTSIZE64
  FORTRAN(pardiso_64,(pt,&maxfct,&mnum,&mtype,&phase,neq,aupardiso,
		   pointers,icolpardiso,perm,&nrhs,iparm,&msglvl,
                   b,x,&error));
#else
  FORTRAN(pardiso,(pt,&maxfct,&mnum,&mtype,&phase,neq,aupardiso,
		   pointers,icolpardiso,perm,&nrhs,iparm,&msglvl,
                   b,x,&error));
#endif

```

---

<div class="post-metadata">

**Author:** ![Iacobellis88](https://avatars.discourse-cdn.com/v4/letter/i/9de0a6/32.png) [@Iacobellis88](https://calculix.discourse.group/u/Iacobellis88)\
**Post date:** [February 11, 2025, 8:08am UTC](https://calculix.discourse.group/t/restart-does-not-write-resutls-with-ccx-i8/2572/12 "2025-02-11T08:08:37Z")

</div>

I am using i8 because the model that I am running it is very big. 2.5 milion of nodes. This was just an example.

---

<div class="post-metadata">

**Author:** ![Iacobellis88](https://avatars.discourse-cdn.com/v4/letter/i/9de0a6/32.png) [@Iacobellis88](https://calculix.discourse.group/u/Iacobellis88)\
**Post date:** [February 11, 2025, 8:10am UTC](https://calculix.discourse.group/t/restart-does-not-write-resutls-with-ccx-i8/2572/13 "2025-02-11T08:10:34Z")

</div>

So if I wanna use i8, should I use the same procedure?

---

<div class="post-metadata">

**Author:** ![fgr](https://avatars.discourse-cdn.com/v4/letter/f/f4b2a3/32.png) [@fgr](https://calculix.discourse.group/u/fgr)\
**Post date:** [February 11, 2025, 8:49am UTC](https://calculix.discourse.group/t/restart-does-not-write-resutls-with-ccx-i8/2572/14 "2025-02-11T08:49:38Z")

</div>

@Iacobellis88 , if you want to use the Pardiso solver with 64 bit integers, then you will need to modify the source code in pardiso.c  
If you follow me suggest then you will have a general solution controlled by the option in the makefile.  
If you should be unfamiliarly with modifying source code you can get the file from the link below  
[pardiso.c - Google Drive](https://drive.google.com/file/d/1goHwRp3fg_kjkOx4aBKGGbyMMVvabzif/view?usp=sharing)  
Don’t be so suspicious, just try it. If it works, be happy, if it doesn’t you have other problems

---

<div class="post-metadata">

**Author:** ![Iacobellis88](https://avatars.discourse-cdn.com/v4/letter/i/9de0a6/32.png) [@Iacobellis88](https://calculix.discourse.group/u/Iacobellis88)\
**Post date:** [February 11, 2025, 12:52pm UTC](https://calculix.discourse.group/t/restart-does-not-write-resutls-with-ccx-i8/2572/15 "2025-02-11T12:52:11Z")

</div>

Sorry, Could you compile me it in order to provide me .exe, please? I am not expert to do this.

---

<div class="post-metadata">

**Author:** ![fgr](https://avatars.discourse-cdn.com/v4/letter/f/f4b2a3/32.png) [@fgr](https://calculix.discourse.group/u/fgr)\
**Post date:** [February 11, 2025, 3:29pm UTC](https://calculix.discourse.group/t/restart-does-not-write-resutls-with-ccx-i8/2572/16 "2025-02-11T15:29:30Z")

</div>

@Iacobellis88 , You can get my version here. You only need to extract the files  
[ccx\_2.22\_i8.zip](https://drive.google.com/file/d/1w-w4toMEGrElln2uG2oxMQ1c2mHEiOVs/view?usp=sharing)  
note – the pardiso solver isn’t static linked, so you should keep the dll file in the same folder as the ccx\_2.22\_i8.ece

---

<div class="post-metadata">

**Author:** ![Iacobellis88](https://avatars.discourse-cdn.com/v4/letter/i/9de0a6/32.png) [@Iacobellis88](https://calculix.discourse.group/u/Iacobellis88)\
**Post date:** [February 20, 2025, 10:02am UTC](https://calculix.discourse.group/t/restart-does-not-write-resutls-with-ccx-i8/2572/17 "2025-02-20T10:02:29Z")

</div>

Do you know how overcome a segmentation fault (core dumped) on linux? I think that is the same error in windows of ucalloc memory

---

<div class="post-metadata">

**Author:** ![fgr](https://avatars.discourse-cdn.com/v4/letter/f/f4b2a3/32.png) [@fgr](https://calculix.discourse.group/u/fgr)\
**Post date:** [February 20, 2025, 3:19pm UTC](https://calculix.discourse.group/t/restart-does-not-write-resutls-with-ccx-i8/2572/18 "2025-02-20T15:19:18Z")

</div>

@Iacobellis88 , the easy answer is no.  
A segmentation failure will always be wrong program code, so first you will need to identify the locating in the program code where the segmentation is initiated and afterward the reason.  
If you have compiled ccx with option O3, then try to omit this compiler option. Compiler optimization can randomly be a little unreliable special O3  
I don’t have it present, but maybe if you use the compiler option -g3 instead of, then you maybe could get little more info of the location. The -g3 option add maximum debug information into the program.  
I don’t either have present if the Spooles solver default can be compiled to 64 bit integer but in that case, you could try if the fault could rely on the specific solver.  
You will have my best wishes in seeking what initiate the segmentation fault

I just recognized you have nearly similary thread where you mention you use ccx-mt. I never use the -DUSE\_MT=1 option. Very weekly I remember randomly have had some problem by using that specify option, so try to omit that when you compile. You don’t need it if you are using the Pardiso solver
