How to give enough info to get help
This is a repost of another post hoping that it can be made sticky.
An example on how to get proper help following the guideline shown.
I will try to give an example taken purely from my own imagination that show the kind of info I would like in order to help people.
=== 0 ===
Prepare for getting help. cfd-online does not provide large filesize uploads so registering a dropbox/box account and use a public link to the picture/file makes it a lot easier to share files/pics or the full case.
=== 1 ===
First give it a relevant name in the title of the thread
simpleFoam pipe case diverges
What this little information tells us is that the solver is simpleFoam, the geometry is a pipe and we know that the problem is that it diverges.
=== 2 ===
Second give a sketch of the geometry, a screendump of the mesh and maybe even a cut through the mesh. Paraview and the Clip filter works good here.
This helps immensely when trying to visualise the case in others brains.
The "a picture says more than a thousand words" quote springs to mind here
Below is an example of a picture inserted using a public link from dropbox.
Also the first info you need to give is the output from checkMesh put into a log file
Ok now people know that you have a pipe with two bends and that the mesh is fully structured (paraview shows some as tets, but that is a render issue). The dimensions of the pipe is also known now. Also from the header files people know that you are using OpenFOAM version 2.1.x, this is relevant since there can be some bugs in the version used.
=== 3 ===
Ok now we are ready to start identifying the problem.
You know that you have divergence problems and if you have opened just one book about CFD, you know that stability is related to a number of things.
This will allow people to see if you have the correct setup for the type of case/mesh you have.
=== 4 ===
Also some good information to give is the output from the terminal, but please don't post 10+ iterations. Post only the relevant bits, for example the 2-3 iterations where the solver start to diverge. Another options would be to give the log file as a upload/link. The output can be put into a file using.
=== 5 ===
This might seem like a lot of work, but if you want people to invest time on you, you must invest at least as much time in asking the right question and give sufficient input to allow people to help you.
I'm sure that if you follow this simple guide you will get the help you need.
I made this thread sticky.
And some other points.
Don't hijack other threads and don't post the same question multiple times.
I see that some people post new questions in active threads cause they think this will attract more readers. Do not do this, since it makes it really hard to search the forum.
And heads up. If you post a question in this thread I will just remove it. So don't do that either.
Linnemann's sample post and some more tips can be found on the wiki as well: http://openfoamwiki.net/index.php/Ho..._Message_Board
It's a good job that people doing in other forums always.
Summarizing all different thread about one subject.
It will be more perfect with attached simple cases for download for new users.
And finally some threds like it could became a pdf file for users.
Relevant: doi:10.1371/journal.pcbi.1002202 (http://www.ploscompbiol.org/article/...l.pcbi.1002202)
Section "3.3.3 Solver output" at openfoamwiki.net already explains the following, but feel free to point people to this post for instructions on how to post code in the forum.
Take for example this piece of code:
nSend = 0;
label procI = complexData[i].first();
sendMap[procI][nSend[procI]++] = i;
So, to avoid messy looking posts with ugly code in the middle of a post, use the "[CODE]" tag. There are two ways to do this:
Two more things of a more technical nature (that are bothering me sometimes):
Maybe these points can be added if the original article is updated/extended (along with other valuable remarks in this thread like on citing code etc)
|All times are GMT -4. The time now is 01:00.|