MICRESS Forum

Hi,
i just use 1000*1000*1 domain to simulate a grain growth of around grain surrounded by a rectangular grain. But during the running, the following comes into screen. and simulation failed. Do you know why? Thank you.
# Beginning of initialisation
# ===========================
# Routine init calls routine initDateien
# Routine init calls routine initRand
Segmentation fault

Dear zhubq,

This error definitively should not occur! I have never seen itbefore, but, if it is reproducable, it seems to be connected to the initialisation of the boundary conditions in the subroutine initRand. Do you use strange boundary conditions or do something wrong in the input which is not properly handled in the code?

To trace down the problem, we need the driving file which gives the error and the version of MICRESS which you are using (printed at the top of the .log file). You can paste the driving file in this thread if you wish, or send it to the MICRESS support (support@micress.de) or to me via PM.

Bernd

Hi, Bernd.
I found the problem. I made a mistake in the driving file. I set Z=1 for 2D where it should be Y=1. Thank you for your answer.

Dear zhubq,

Nevertheless, MICRESS should not behave like that! I am still interested in seeing the driving file in order to know exactly how it fails!

Thanks!
Bernd

Hello

I am having problem with this bug


# Data for phase 1:
# -----------------
# Simulation of recrystallisation in phase 1?
# Options: recrystall no_recrystall

no_recrystall


Input error in routine leseEingabe
Input: no_recrystall

Best Regards
Raghav

Dear Raghav,

this is definitively an error which is due to a wrong input file! The screen output you sent us seems to be screwed up just before it stops - I would guess that the error occurs in the time input data: probably there is a wrong character in one of the lines, which is interpreted wrongly, but the complaint comes later when recrystallisation is asked!

I cannot tell you for sure what is happening without seeing the original input file...

Wish you a happy new year!

Bernd

@ Bernd

I had just hand typed and the problem was solved.

Thanks
Raghav