OpenFOAM-1.6-ext_nextRelease
Hi everyone,
i wonder if one (or two :) ) of the Extend project guys could give me a hand with an installation problem i am having! I am trying to install the nextRelease branch of OF-1.6-ext, and the install is hanging when it tries to download the RPM packages for: Code:
Package name : ParMGridGen-1.0 Code:
Package name : ParMGridGen-1.0 Does anyone know where i can make the change to point to the working repo? As far as i can see from the package name, the package is identical, so changing it should not be a problem. Many thanks and best regards Jonathan |
solved (i think)
Hi,
ok, so if anyone else is wondering - i think i have solved this - you can change the repository address in: AllMake.stage3 Code:
# ParMGridGen i am yet to test the install to see that everything works, but it appears it will. cheers jonathan |
Interesting: it seems that some mirrors are available in some parts of the world and others are not.
I have tried: wget ftp://ftp.proxad.net/.mirrors1/ftp.f...Gen-1.0.tar.gz wget http://www.mgnet.org/mgnet/Codes/par...Gen-1.0.tar.gz and both work for me. Can you please check them by hand and let me know, Hrv |
repo's tested
Hi Hrv,
thanks for your reply. I tested by hand and: Code:
jonathan@01:/media/data/temp1-meshing/ICEM/mesh_4/openFoam/tmp$ wget http://www.mgnet.org/mgnet/Codes/parmgridgen/ParMGridGen-1.0.tar.gz Code:
jonathan@01:/media/data/temp1-meshing/ICEM/mesh_4/openFoam/tmp$ wget ftp://ftp.proxad.net/.mirrors1/ftp.freebsd.org/ports/distfiles/ParMGridGen-1.0.tar.gz PS I am trying to compile and install the entire nextRelease branch of the Extend project (because i would like to do some turbomachinery calculations), and I have come across a couple things i needed to do to get it to install correctly (actually, i am still working on it, 80% -> finished), so perhaps i could report some of them here (if they actually turn out to be real issues). many thanks and best regards jonathan |
Hi guys,
I am also having some trouble getting swak4foam (AllMake.stage5) to compile on my machine. I have tried this by running ./AllMake.stage5 from the ThirdParty directory, but also directly by running ./Allwmake and wmake libso in /ThirdParty/rpmBuild/BUILD/swak4Foam-0.2.4/ and /ThirdParty/rpmBuild/BUILD/swak4Foam-0.2.4/Libraries/groovyBC/ respectively, and i am getting the following! Code:
groovyBCJumpFvPatchFields.C:49:5: error: specializing member ‘Foam::groovyBCJumpFvPatchField<double>::typeName’ requires ‘template<>’ syntax Code:
/usr/bin/ld: cannot find -lgroovyBC I was just wondering if this version of swak had been tested with the nextRelease branch, and whether there was anything i could do to fix it. again, many thanks and best regards Jonathan PS i dont know if i am using the correct forum for these discussions - i didnt know whether there was a particular mailing list where you are supposed to report / discuss this stuff, as up to now i have only been using the releases from OpenCFD. Please correct me if i need to redirect this stuff :) System details: Code:
No 'swakConfiguration'. Python etc won't work |
> PS i dont know if i am using the correct forum for these discussions - i didnt know whether there was a particular mailing list where you are supposed to report / discuss this stuff, as up to now i have only been using the releases from OpenCFD. Please correct me if i need to redirect this stuff
The proper place to report these kind of errors for OpenFOAM-1.6-ext is here: http://sourceforge.net/apps/mantisbt..._view_page.php Martin |
Quote:
|
thanks
thanks Martin,
best regards jonathan Quote:
|
Dear Bernhard
thanks for your reply - any ideas how I can fix it? I think my setup is fairly benign: Code:
i.e. I am at the moment trying to move everything i am doing onto OF-1.6-ext so I can run some tests with the mixing plane interface. sincerely and best regards jonathan PS I am not saying it is in fact a bona fide bug - i may just have done something incorrectly, but i can't see what! :) Quote:
|
fix?
Hi Bernhard,
I think I found a solution. In groovyBCJumpFvPatchFields.C, if i change: Code:
namespace Foam Code:
namespace Foam |
Quote:
My problem with that fix is that is breaks compilation on old 1.6-ext versions (so I'll have to find a way to differentiate between them) |
Hi Bernhard,
Thanks for the reply ... swak is so good for foam that i can't live without a working install of it! thanks again for contributing it :) I just wanted to ask whether there was any particular previous version which was known to definitely work with 1.6-ext? I have moved my simulations from 2.1.1 / swak for 2.1.1 onto 1.6-ext / swak that comes with the nextRelease branch (0.2.4), and i am struggling (even having gotten it to compile as per above), to get my simulations to run. :( Code:
Time = 1 apologies for the long, somewhat garbled message! :) its been a long day! best regards and many thanks Jonathan |
Quote:
Quote:
Last release of swak compiled with last release of 1.6-ext. That is all I can say. Next release of swak will compile with whatever is released at that time. So in general I'd say "Only use released versions" with the addition "unless ou know how to fix and report problems" (it seems that you fall under that clause) Quote:
If you pull a new OF-version and recompile it ALWAYS recompile 3rd-party software that depends on OF Quote:
|
Thanks very much Bernhard,
its much appreciated. best regards jonathan Quote:
|
I am also trying to compile nextRelease branch of OpenFOAM-1.6, but I have a problem with compiling, I get the following error:
Code:
make: Nothing to be done for `all'. |
I have fixed the above problem by increasing the -ftemplate-depth from 40 to 80 in the c++ file in the following directory:
/opt/OpenFOAM/OpenFOAM-1.6-nextRelease/wmake/rules/linux64Gcc44 does it have any side effects? I did not have the same problem when I was compiling OpenFOAM-1.6ext. |
Quote:
Seriously: No. The only reason this is set to a low value is because usually code doesn't need it and it potentially uses more memory DURING COMPILATION Quote:
|
Hi Daniel,
I needed to make this change as well in order to get my source to compile. I just wonder whether you would mind letting me know whether you managed to get everything running well once you got it compiled? I had issues running in parallel with swak4Foam (groovyBC), but couldnt figure out whether the problem was with my install or the source which is still developing. many thanks and best regards Jonathan Quote:
|
Quote:
I have still some problems with swak4Foam compilation. I have fixed the problem you have mentioned but there is another problem that I have not fixed it yet. It complains about a 4th order symmetry tensor(pointpatch....) So I can not tell if groovyBC is working fine in parallel or not. Although I have tested one of solidMechanics solvers in parallel without any problems. I will try to fix that error and test a parallel case with groovyBC and let you know. Regards |
OK, I have fixed that problem to make swak4Foam compatible with nextRelease_philipc branch of OpenFOAM-1.6ext.
I have to add the following lines to groovyBCPointPatchFields.H: Code:
typedef groovyBCPointPatchField<symmTensor4thOrder> groovyBCPointPatchSymmTensor4thOrderField; tell me if you have any special cases in mind. ---------------- I have tested one of swak4Foam examples and I can confirm that the problem is there: Code:
Selecting incompressible transport model Newtonian |
Quote:
Do the following (in that order): - pull OF-sources - recompile OF - recompile swak - retry your case Check after every step that the FULL compilation went alright (for instance finiteVolume may have alright and not produced a new library. But all subsequent stages happily use the old library) If the error stays and you're convinced that swak is the problem open a bug report on the openfoam-extend-Mantis and I'll have a look (please provide an example-case) |
All times are GMT -4. The time now is 06:49. |