[AlmostSurelyRob]

Dear Foamers,

I am having a problem compiling Openfoam 2.0 from git repository on OpenSUSE 11.4. I didn't try the RPM package yet and when I compile the application target fails.

Target 'application' not remade because of errors.

Please find attached the log from my compilation. There seem to be some undefined references there. I am really at my wits end here sine the amount of errors is simply staggering. What am I missing?

I would be really obliged for any comments.

[wyldckat]

Hi Robert,

OK, no OpenMPI nor scotch are available. There are two possible reasons for this to have happened:

1. You didn't follow to the letter the official instructions:

   Originally Posted by http://www.openfoam.com/download/git.php#x6-36000

   tar xzf ThirdParty-2.0.0.gtgz
   mv ThirdParty-2.0.0 ThirdParty-2.0.x

   If you have only now done the second line, then:
   • Start a new terminal window/tab.
   • Or run:

     wmSET

   And try again.
2. You got the git repo of ThirdParty as well. If so, check this bug report: http://www.openfoam.com/mantisbt/view.php?id=220
   Download the "get*_fixed" versions instead, when available. To make those scripts executable:
   

   chmod +x get*

Best regards,
Bruno

[alberto]

There seems to be a bug in the build script when trying to compile OF 2.0 with the ThirdParty MPI. I did not investigate too much, and used the version of MPI provided with openSUSE, following http://albertopassalacqua.com/?p=920

Best,

[AlmostSurelyRob]

Thanks for your replies. Unfortunately I cannot report any positive developments yet.

@alberto
Thanks for the comment and for your blog entries. I followed the Opensuse 11.4 and OpenFOAM 2.0. I downloaded the prefs.sh where I understand you change to openmpi from opensuse and to gcc45, but to no avail

@wylcat
ad 1. I changed it to 2.0.x but still the same error.
ad 2. I am currently trying this. I downloaded getOpenMPI_fixed and getGcc_fixed. The former one didn't produce any output the latter one downloaded...

(pause)

Whohoa! It worked. Thanks a lot! :-) And coming back to what you said at the beginning I don't seem to have any Scotch but now I feel like I'd like to have some.

But first I wish to test this film model. :-)

Many thanks for your advice!

[alberto]

Originally Posted by AlmostSurelyRob

Thanks for your replies. Unfortunately I cannot report any positive developments yet.

@alberto
Thanks for the comment and for your blog entries. I followed the Opensuse 11.4 and OpenFOAM 2.0. I downloaded the prefs.sh where I understand you change to openmpi from opensuse and to gcc45, but to no avail

This probably means you do not have a properly configured system openMPI. Most likely, you have to use mpi-selector to choose the default version.

Anyways, good you found an alternative solution! :-)

Best,

[AlmostSurelyRob]

Could I take the advantage here and ask one thing? Paraview doesn't seem to visualise my cases any more. I tried using it on film model tutorials and it produced the following errors.

ERROR: In /home/c111269/OpenFOAM/ThirdParty-2.0.x/ParaView-3.10.1/VTK/IO/vtkOpenFOAMReader.cxx, line 7374
 vtkOpenFOAMReaderPrivate (0x19b8de0): Error reading line 46 of /home/c111269/OpenFOAM/OpenFOAM-2.0.x/tutorials/lagrangian/reactingParcelFilmFoam/rivuletPanel/constant/polyMesh/boundary: Unsupported nonuniform list type ;
 
 
 ERROR: In /home/c111269/OpenFOAM/ThirdParty-2.0.x/ParaView-3.10.1/VTK/IO/vtkOpenFOAMReader.cxx, line 7374
 vtkOpenFOAMReaderPrivate (0x19b2450): Error reading line 52 of /home/c111269/OpenFOAM/OpenFOAM-2.0.x/tutorials/lagrangian/reactingParcelFilmFoam/rivuletPanel/constant/wallFilmRegion/polyMesh/boundary: Unsupported nonuniform list type ;
 
 
 ERROR: In /home/c111269/OpenFOAM/ThirdParty-2.0.x/ParaView-3.10.1/VTK/Filtering/vtkExecutive.cxx, line 756
 vtkPVCompositeDataPipeline (0x19e3190): Algorithm vtkPOpenFOAMReader(0x19e5700) returned failure for request: vtkInformation (0x19b8530)
   Debug: Off
   Modified Time: 72009
   Reference Count: 1
   Registered Events: (none)
   Request: REQUEST_INFORMATION
   ALGORITHM_AFTER_FORWARD: 1
   FORWARD_DIRECTION: 0

I compiled paraview from ThirdParty directory.

paraview is hashed (/home/c111269/OpenFOAM/ThirdParty-2.0.x/platforms/linux64Gcc/paraview-3.10.1/bin/paraview)

I know that the specification of boundaries in OF 2.0 changed. How does it affect paraview and visualisation? I know it's a bit off topic but could you perhaps advise something here?

[wyldckat]

Hi Robert,

Which reader are you using to open the case? Is it the internal reader or the official one on OpenFOAM? In other words, what's the file extension:

• .OpenFOAM - the official reader.
• .foam - the internal reader.

Which brings me to the next question: if you are using the official reader, did you (re-)build it?

Best regards,
Bruno

[7islands]

Hi Robert,
The error most surely is coming from an internal reader problem. I'll take a look into that early next week.

Thanks for bringing that to my attention (I am the main developer of the internal reader).

Takuya

[AlmostSurelyRob]

Thank you for your replies.

@wyldcat
I am using the internal reader. I usually create a *.foam file within a working directory and then open it with paraview. When I create *.OpenFOAM file paraview doesn't even see it. On the other hand, running paraFoam creates an casename.OpenFOAM file. Unfortunately it results with the same error.

Originally Posted by wyldcat

Which brings me to the next question: if you are using the official reader, did you (re-)build it?

I believe I did rebuild some readers. I executed the following instructions (taken from Alberto blog-entry) ?

cd $FOAM_UTILITIES/postProcessing/graphics/PV3Readers/
./Allwclean
./Allwmake

@7islands
Thanks for that. I am looking forward to hear from you.

[wyldckat]

Greetings to all!

@Robert:

Originally Posted by AlmostSurelyRob

I believe I did rebuild some readers. I executed the following instructions (taken from Alberto blog-entry) ?

cd $FOAM_UTILITIES/postProcessing/graphics/PV3Readers/
./Allwclean
./Allwmake

Try again with these commands:

Originally Posted by http://www.openfoam.com/download/source.php#x5-28000

cd $FOAM_UTILITIES/postProcessing/graphics/PV3Readers 
wmSET
./Allwclean
./Allwmake

The main difference is wmSET. Right now it shouldn't make any difference to use it or not, but this command makes sure that your build of ParaView is visible to the All* scripts. Either way, run them again, just to be sure.

By the way, your OpenSuSE was installed in English or in another language?


@Takuya: I wanted to be certain of this before reporting it as a bug But yes, it is the internal reader that isn't ready for the new stuff
You are going to have your hands full with the new stuff in OpenFOAM 2.0, including the new super binary meshes: http://www.openfoam.com/version2.0.0....php#x11-36000


Best regards,
Bruno

[AlmostSurelyRob]

Dear Bruno,

yes! :-)

The wmSET command did make a difference. Now Paraview opens case.OpenFOAM files and I can visualise film cases. Many, many, thanks for that. I also tried opening a case.foam file but the same error occurs.

My system has language set to English UK but keyboard is set to Polish. Is that important?

Kind Regards,
Robert

[wyldckat]

Hi Robert,

Originally Posted by AlmostSurelyRob

The wmSET command did make a difference. Now Paraview opens case.OpenFOAM files and I can visualise film cases. Many, many, thanks for that.

You're welcome

Originally Posted by AlmostSurelyRob

I also tried opening a case.foam file but the same error occurs.

OK, then it's 100% confirmed that the internal reader can't read some of the changes made in OpenFOAM 2.0

Originally Posted by AlmostSurelyRob

My system has language set to English UK but keyboard is set to Polish. Is that important?

OK, if it's just the keyboard then there is no problem!
If the language was set to Polish as well, then that could have had some influence.

Best regards,
Bruno

[7islands]

Hi Bruno,

Originally Posted by wyldckat

You are going to have your hands full with the new stuff in OpenFOAM 2.0, including the new super binary meshes: http://www.openfoam.com/version2.0.0....php#x11-36000

The PV 3.10.1 internal reader should already have support for the new binary file format (thanks to help from Mark Olesen). However I say should because it has not been tested thoroughly so bug report is welcomed.

Takuya

[ming]

Dear all,

I tested reactingParcelFilmFoam of openfoam 2.0 on several tutorial cases.
But I can't watch the film flow under paraFoam, while the file deltaf exists under directories wallFilmRegion and the calculate seems ok.
What's wrong with it?

Best Regards,
Ming

[alberto]

Originally Posted by ming

Dear all,

I tested reactingParcelFilmFoam of openfoam 2.0 on several tutorial cases.
But I can't watch the film flow under paraFoam, while the file deltaf exists under directories wallFilmRegion and the calculate seems ok.
What's wrong with it?

Best Regards,
Ming

Please open another thread to ask this question, since it is not related to the topic of the existing thread.

Best,