Hi,
No, said line shouldn't be the cause of anything... :( And fdf inputs
shouldn't generate a seg-fault.
Another try for debugging would be to add full traceback calls:
Intel:
FFLAGS = -O0 -g -check bounds -traceback
Which should be more informative.
Also, Intel is notorious for using the
Deleting the TBTGF files did not solve the problem. So, my two guesses now
are that there is an issue with the compilation of TBTrans (but it's
compiled with stock Intel compiler, so I imagine someone else would have
run into this) or there is an error in the input code. Would an error in
the
Could you please delete all TBTGF* files, and rerun the calculation?
Alternatively, see if increasing the eta value helps.
Den fre. 8. mar. 2019 kl. 22.02 skrev Day, Zacharie :
> Hello,
>
> A user on my cluster is trying to process something with Siesta 4.0.2
> TBTrans_rep. The process works up
Hello,
A user on my cluster is trying to process something with Siesta 4.0.2
TBTrans_rep. The process works up until this output:
==
Projection Region: atoms : [ 183; 244]
Projection Region: states: [ 1639; 2172] Tot: 534
Reading
