v3150A on Red Hat Enterp.WS3
 

Hi anyone, I have just received a new computer and have installed: Linux 2.4.21-27.0.2.ELsmp (Red Hat Enterprise WS 3) - all standard setup and have installed the latest v3.150A.044 and it simply does not work. v3.24 works fine, but I have a lot of old models which I do not want to transfer (=a lot of work)...

My problem is that I can't write any geom file without warnings and I can't run the case.

For example: I make a very small test case (3x3x3 cells with inlet and outlet) When running "geom" I get the warnings:

BEGINNING CONNECTIVITY SEARCH

162 CELL FACES TO PROCESS

**WARNING - BAFFLE CELL 1 IS NOT ATTACHED TO ANY FLUID OR SOLID CELLS. BAFFLE IGNORED.

**WARNING - BAFFLE CELL 2 IS NOT ATTACHED TO ANY FLUID OR SOLID CELLS. BAFFLE IGNORED.

**WARNING - BAFFLE CELL 5 IS NOT ATTACHED TO ANY FLUID OR SOLID CELLS. BAFFLE IGNORED.

... for all cells

Then I get a second warning:

**WARNING - CELL 1 HAS PHYSICAL BOUNDARIES ON ALL SIDES

**WARNING - CELL 2 HAS PHYSICAL BOUNDARIES ON ALL SIDES

... again for all cells

I can make a starlink on the case but it really does not make any sense because the model says that there is boundaries on all cell sides = 162. And the output is nonsense...

Have anybody seen this before and have a solution for it??? I can't be the only one running v3150A on RHEL 3.0?

Hoping for response. dams

Re: v3150A on Red Hat Enterp.WS3
 

I have seen this warning and it might help to delete the param.prp file and let prostar create a new one.

Another option is to install Suse 8.2 which works with all 32bit version of star.

Re: v3150A on Red Hat Enterp.WS3
 

Thanks for your response...

I tried deleting param.prp, but the problem still exist.

I can not really change os system - it is out of my hands to decide...

Re: v3150A on Red Hat Enterp.WS3
 

I was told there was a memory conflict with the compiler used for prostar 3.150a and the glibc in your version of RH. It got sorted out in 3.2 but I don't think there is any way around it in 3.15 other than to switch to Suse as William said.

Re: v3150A on Red Hat Enterp.WS3
 

What about rereleasing 3.15 for new versions of Linux? I would be very happy about this too.

Re: v3150A on Red Hat Enterp.WS3
 

I have had the error with the baffle and I believe, in my case, that it was because the baffle was placed between fluid cells with different surface areas. Maybe check on that. Hope that helps.

Re: v3150A on Red Hat Enterp.WS3
 

No, this is an old error which occured in models without any baffles at all. Usually it happend when maxsc2 was set to a very large number during some operations in proam meshing. So deleting the param.prp was a workaround. This means that there is some problem with memory allocation. It might be the same reason why it does not run under new versions of linux.

Re: v3150A on Red Hat Enterp.WS3
 

Thanks for all the responses. Unfortunately this has nothing to do with baffles - there is none in the very simple model. It seems to be related to this distinct version of redhat with kernel: Linux 2.4.21-27.0.2.ELsmp (Red Hat Enterprise WS 3). Am I the only one using this one in the whole world together with prostar 3.150A???

dams

Re: v3150A on Red Hat Enterp.WS3
 

Since it is not supported - probably so.

Re: v3150A on Red Hat Enterp.WS3
 

Where can you see which kernels are supported for this version of prostar (V3150A.044)???

Re: v3150A on Red Hat Enterp.WS3
 

It is outlined in The Installation and Systems Guide - an Acrobat "pdf" file on the installation disks.

Re: v3150A on Red Hat Enterp.WS3
 

I'm using RH 3 on a 32-bit machine and I have no problems with pro-STAR 519-523. To make sure there are no problems with the model, you should try tutorial 1. In order to run the STAR executable you need to enter "setenv LD_ASSUME_KERNEL 2.4.10" (csh) or "export LD_ASSUME_KERNEL=2.4.10" (bash), but this has nothing to do with pro-STAR.

Re: v3150A on Red Hat Enterp.WS3
 

perhaps you can continue doing it in v3.24.Just maintain the .mdl file and delete those .geom,.prob and parm.inc file.Do not use the older one because the structures had all changed.Start with a fresh one.