Very nice!
Regards,
Martin
Very nice!
Regards, Martin |
Amazing what can happen during
Amazing what can happen during one nighthttp://www.cfd-online.com/OpenFOAM_D...part/happy.gif
Looks good. - Niels |
Great Work Alberto :-)
I ha
Great Work Alberto :-)
I have some very basic documentation in the pipeline. will send you the pdf's in two weeks for review. The aim is to avoid the same basic questions on the forum. Lets see if it works ... Best Regards Jaswi |
Hi Jaswi
Please distribute
Hi Jaswi
Please distribute it, as it would be beneficial to all to have such a document. - Niels |
Hi Jaswi!
Wouldn't http://o
Hi Jaswi!
Wouldn't http://openfoamwiki.net/index.php/Main_FAQ be an appropriate place for that kind of stuff? I know that not much has been added there in the last time, but you could change that ... Bernhard |
Dear Bernhard and Niels
The
Dear Bernhard and Niels
The purpose of making such documentation is distribution only but it needs some peer review as it is very basic and mostly consolidates the information taken from the forum. I just need some time (after 16th July + 1 week) to refine it. With Best Regards Jaswi |
Thanks Jaswi. I'll be happy to
Thanks Jaswi. I'll be happy to read it :-)
Regards, A. |
Hi Jaswi
What is not very c
Hi Jaswi
What is not very clear from my post is that I would like to read the document and give feed-back. Best regards, Niels |
Hi Niels
That would be grea
Hi Niels
That would be great. Will send it over to you once I have the initial draft ready. Best Regards Jaswi |
Hi everyone:
I tried the ea
Hi everyone:
I tried the easy way of compiling OF-1.4.1-dev, but run into problems when compiling src, the errors are something like: /******************************************** . . . lex.yy.cc:6502: error: 'yy_buffer_stack_max' was not declared in this scope lex.yy.cc:6503: error: 'yy_buffer_stack_top' was not declared in this scope lex.yy.cc:6507: error: 'yy_buffer_stack_top' was not declared in this scope lex.yy.cc:6507: error: 'yy_buffer_stack_max' was not declared in this scope lex.yy.cc:6513: error: 'yy_buffer_stack' was not declared in this scope lex.yy.cc:6516: warning: use of old-style cast lex.yy.cc: In member function 'void yyFlexLexer::yy_push_state(int)': lex.yy.cc:6534: warning: use of old-style cast lex.yy.cc:6537: warning: use of old-style cast lex.yy.cc:6537: warning: use of old-style cast . . . /****************************** /****************************** . . . /usr/bin/ld: cannot find -lfiniteVolume collect2: ld returned 1 exit status . . . . /***************************** /**************************** . . . Xstream/Xstream.C:155: error: 'ButtonPressMask' was not declared in this scope Xstream/Xstream.C:155: error: 'KeyPressMask' was not declared in this scope Xstream/Xstream.C:155: error: 'ExposureMask' was not declared in this scope Xstream/Xstream.C:155: error: 'StructureNotifyMask' was not declared in this scope . . . /************************************ I read some threads related to my problem, but haven't got a solution how to solve it, Could anyone give me some ideas? (BTW: OS: ubuntu 7.10; gcc:4.2.1; flex: 2.5.33 Kind regards feng |
Hi feng,
the procedure work
Hi feng,
the procedure worked on openSUSE 11.0 (gcc 4.2.1 packaged by OpenCFD, flex 2.5.35). Regards, A. |
Hi Alberto & anyone,
Thanks
Hi Alberto & anyone,
Thanks for reply. I think I've made a progress in solving the problem related to zlib, but I am now still struggling with flex, Here is what I have in OpenFOAM-1.4.1-dev/wmake/rules/General/flex++ .SUFFIXES: .L #Ltoo = foamFlex++ -f $$SOURCE ; mv lex.yy.cc $*.C ; $(CC) $(c++FLAGS) -c $*.C -o $@ Ltoo = flex++ -f $$SOURCE ; mv lex.yy.cc $*.C ; $(CC) $(c++FLAGS) -c $*.C -o $@ .L.dep: $(MAKE_DEP) Could anyone give me some help? Kind regards feng |
Hi Feng !
I'm on ubuntu 8.0
Hi Feng !
I'm on ubuntu 8.04 and I use Flex 2.5.4 (old flex in the synaptic package manager) and the compilation is ok. Mathieu |
Hi Mathieu !
Thanks for you
Hi Mathieu !
Thanks for your help! I tried your method, but it doesn't work, but I find way around it and make it work. I noticed in my error list that there is something like "c++ linkage" and I get some idea from this post: http://www.cfd-online.com/OpenFOAM_D...es/1/7503.html so I replace: "int yywrap()" with "extern "C" int yywrap()" which is located at $WM_PROJECT_DIR/src/triSurface/triSurface/interfaces/STL/readSTLASCII.L then most of the libraries in the "src" is compiled, except some libraries related to combustion and something else. as my project is about f-s, I tried icoFsiFoam and the stress solvers, they are all compiled correctly, anyway, OF-1.4.1-dev is working for me. I think the uncompiled libraries can also be solved with the same method as the compiler also complains about flex-related issues. kind regards feng |
Hi All
I have just download
Hi All
I have just downloaded 1.4.1-dev tonight, and the finiteArea module is missing. Does anyone know if it has been redrawn or anything? If not, when will it become available again. Thanks, Niels |
Hi
I am terrible sorry for
Hi
I am terrible sorry for having posted this ... turns out that I had stepped into the wrong directory and compiled the 'not-dev' version. Time for bed. Thanks, Niels |
I had my fluctuation with inst
I had my fluctuation with installation. I spent almost a whole week from 8:00am to 10:00pm and finally I got it right.
Now I have to deal with the solvers. As a beginner I need to search the internet for days for answers. SOmetimes I get it and sometimes I do not. The tutorial document is very brief and spends a large portion to introduce the grid generation. It does not cover how to code a program. It lacks the material to introduce the overall structure of this big code. For long time users, it may be easier. I have my own in-house code. I know where to change and how to change it. But for my students it takes two years to understand the code. Lots of users are students and they work on a project for a short time of period. The code will continue to grow, and someday, it will become so hard for a beginner to grasp and add new components (that is the purpose of a research code). They may just switch to Fluent (with a few thousand for 10 licenses, fluent is not that expensive) I contacted the supporting group. I concern about the total number of hours (50 hours). Well, if I want to implement a new solver, I really do not know how many hours will they spend. I agree they should get paid for their work. There could be a better way to do that. Peter |
All times are GMT -4. The time now is 17:58. |