Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29270 Discussions

"problem after compile code as parallel "

hamid_mosaddeghi
Beginner
682 Views
Hi Dear

I change module of code and insert some command but after compile this code work seq well but after compile parallel , don't work. and I get error.

in hint of some module "parallel replicated data version : block data" exist , what 's the meaning it?

for exmaple afetr run with 8 node ,I get error for 7 node :

---------------------------------------------------------------------------------------

cool region: -9.537 -7.803

hot region: 7.803 9.537

inital atoms: 24 28 6596

error! the atoms number in cool and hot region are incorrect 24 28

cool region: -9.537 -7.803

hot region: 7.803 9.537

inital atoms: 0 0 6648

error! the atoms number in cool and hot region are incorrect 0 0

cool region: -9.537 -7.803

hot region: 7.803 9.537

inital atoms: 0 0 6648

error! the atoms number in cool and hot region are incorrect 0 0

cool region: -9.537 -7.803

hot region: 7.803 9.537

inital atoms: 34 16 6598

error! the atoms number in cool and hot region are incorrect 34 16

cool region: -9.537 -7.803

hot region: 7.803 9.537

inital atoms: 0 0 6648

error! the atoms number in cool and hot region are incorrect 0 0

cool region: -9.537 -7.803

hot region: 7.803 9.537

inital atoms: 0 0 6648

error! the atoms number in cool and hot region are incorrect 0 0

cool region: -9.537 -7.803

hot region: 7.803 9.537

inital atoms: 31 22 6595

error! the atoms number in cool and hot region are incorrect 31 22

rank 6 in job 116 node12.phychem.iut_55559 caused collective abort of all ranks

exit status of rank 6: return code 0

rank 4 in job 116 node12.phychem.iut_55559 caused collective abort of all ranks

exit status of rank 4: killed by signal 9

rank 3 in job 116 node12.phychem.iut_55559 caused collective abort of all ranks

exit status of rank 3: killed by signal 9

rank 2 in job 116 node12.phychem.iut_55559 caused collective abort of all ranks

exit status of rank 2: killed by signal 9

--------------------------------------------------------------------------------------------

what's your idea?

0 Kudos
1 Reply
TimP
Honored Contributor III
682 Views
If your source code has more than one BLOCK DATA, or multiple references to the same variable or array in BLOCK DATA, that would explain the message. Some legacy applications depend on compilers which permitted such violations of standards, not always with predictable results (does the first or the last instance rule; will a second BLOCK DATA have any effect?).
If you added a data initialization on a variable or array which was already present in BLOCK DATA, that also would trigger such a complaint.
0 Kudos
Reply