|
[Sponsors] |
Wierd...POSDAT boundary problem...please help |
![]() |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
![]() |
![]() |
#1 |
Guest
Posts: n/a
|
Hi,
I am trying to find the onset of separation along a wall in posdat.f and feed this data back to some other subroutines. My program seems to give me Segmentatin fault AFTER A FEW ITERATIONS if I use 'write(*,*) IB,IREG' but works allright if I use 'write(*,*) IB,IRN(IB)'... I have checked to see if anuy of the IRN(IB) are -ve (just in case) but none are... I have no idea why it should do so only due to a diferent write command??? Anyone has any idea? Please help... I am getting paranoid that STAR-CD has its own mind and its not on my side... StarCD |
|
![]() |
![]() |
![]() |
#2 |
Guest
Posts: n/a
|
I don't think IREG is defined in POSDAT: have a look in nom.inc. As far as I know, IREG is only defined for subroutines which are called per boundary, so it tells you which region the boundary belongs to. POSDAT is called for the whole domain so there isn't a unique value which could be given to IREG.
It is correct to use IRN in POSDAT, but make sure you only address it with IB between 1 and NWLMX, otherwise you'll get a segmentation fault. |
|
![]() |
![]() |
![]() |
#3 |
Guest
Posts: n/a
|
Thanks Richard. May be it is the NWLMX... I was using NBP23...
Will check it out soon ![]() |
|
![]() |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
POSDAT boundary problem | Duarte Albuquerque | Siemens | 6 | October 1, 2008 10:41 |
Boundary cell looping in posdat.f [v4.06] | hirokata | Siemens | 6 | September 22, 2008 14:34 |
CFL in posdat | hamodi | Siemens | 2 | August 6, 2007 02:27 |
How can I know a cell is boundary in the posdat.f | wy | Siemens | 1 | August 9, 2002 02:53 |
posdat in HPC | Won-Geun Lee | Siemens | 0 | May 23, 2001 20:03 |