|August 17, 2004, 01:56||
User subroutines and STAR-HPC v3.2
I've got myself an apparently well-working newxyz.f file to handle the piston motion of my ICE simulation. That is, it works as long as I run sequential. When I run parallel, I get warning#113 upon execution of my cell layer deactivation events, stating that the cell side areas of the deactivated cells are non-zero. Plotting the resulting mesh in prostar shows that although the cell layers seemingly have been deactivated, the vertices of the layers have not been collapsed onto each other but continue to move as if there were no deactivation events. As a result, I get very distorted cells and bogus results.
Interestingly, I get warning #113 in sequential mode too but only when I run single precision and there are no evident problems, just the warning. Running sequential with double precision gives no no warnings either. Why then should this warning appear in parallel and double precision? And what are the vertex problems about?
An acquaintant of me mentioned that v3.2 is very picky about variable declarations hand he'd found that he couldn't make some subroutines work in parallel unless using implicit declarations of real and double precision variables. Could this be part of the answer. Has anybody got any experience to share with me on this issue?
Regs. Lars Ola
|Thread||Thread Starter||Forum||Replies||Last Post|
|user subroutines||vladimir||CD-adapco||7||October 12, 2004 13:59|
|User subroutines||Meiring||CD-adapco||5||January 17, 2003 01:14|
|User subroutines||Mir||CD-adapco||10||May 4, 2002 16:16|
|user subroutines in Star-CD||Zeng||CD-adapco||5||March 21, 2002 04:43|
|user subroutines in CFX||Zeng||CFX||3||March 19, 2002 20:35|