[GerhardHolzinger]

Hi all,

I wrote a little python script that allows me to probe a line.
Actually, I state the start and the end of the line as well as the number of points and my script generates a probesDict containing the defined points.

Have a look at it and if you find my nasty bit of code useful, feel free to use it, or even improve it.

The script assumes a file named "probeLineDict" to reside in the system directory. The script itself needs to be executed from the case directory. However, you can change the paths inside the script to get a different behaviour.

[kmooney]

I believe that the 'sample' utility can do this as well. Give a start point, and end point, fields to sample, and number of sample points, it will extract the data requested.

http://www.openfoam.org/docs/user/sample.php

[GerhardHolzinger]

Originally Posted by kmooney

I believe that the 'sample' utility can do this as well.

You are right. However, if I use the probe function to do the job, I get a good time resolution.

I use sample as well, but in some cases I fell the need for higher time resolution. And writing everything to disk at a short interval and running sample afterwards is simply a waste of space.

[laubeg]

Hi Gerhard,

I think in Line 25 it should be 'filename' instead of 'filenameW'.

And just to make things clear for future visitors of this thread: This file does not probe anything itselve, as one might expect from the title, but writes line coordinates to a probesDict, that is used by the 'native' OpenFOAM probeLocation application. As far as I know, you have to run this in advance of the processing itselve.

I never used the probe application, so Gerhard, maybe you could tell us a little more about the overall process: run Script -> run Solver -> find values in ./probes/-folder? Or is there anything else to consider? Do you have to modify the controlDict as well?

Thanks for the script! I hope that future generations of OpenFOAM will have a probe-application as good as the sample-app, but so far, this is a good workaround.

[GerhardHolzinger]

Originally Posted by laubeg

This file does not probe anything itselve, as one might expect from the title, but writes line coordinates to a probesDict, that is used by the 'native' OpenFOAM probeLocation application. As far as I know, you have to run this in advance of the processing itselve.

You are completely right. My first post was indeed short of the information of how to use the script.

The script reads probeLineDict and generates entries for the regular probe function object. However, defining (start, end, nPoints) is much easier than writing 50 points along a line manually into probesDict.

The script overwrites probesDict. However, you can change the name of the file into which the script writes. If you are already using probes, make sure they do not collide.

The variable filename is the name of the file which contains the definition of the line to be probed. The variable filenameW is the name of the file into which the generated dictionary for probes is written.

The definition of the probe function object in controlDict must make use of an external file for the definition of the probes, otherwise, the generated file would be useless. I let the script write a seperate file in order to prevent it from messing up the controlDict.

The usage follow this procedure.

Put the probeLineDict into the system directory.
Run probeLine.py from the case directory
Run the solver

The controlDict contains this code:

functions
{
    probes1
    {
        type probes;

        functionObjectLibs ("libsampling.so");

        dictionary probesDict;
    }
    
    probes2
    {
        type probes;

        functionObjectLibs ("libsampling.so");

        dictionary probesDict2;
    }
}

[laubeg]

Thanks for the explanation!

Originally Posted by GerhardHolzinger

The variable filename is the name of the file which contains the definition of the line to be probed. The variable filenameW is the name of the file into which the generated dictionary for probes is written.

From line 23 to 25 you define 'filename' and use 'filenameW' afterwards.

Copied from your zip-file, line 23 to 25:

filename = './system/' + probesDict
#filenameW = probesDict
mywfile = open(filenameW,'w')

As far as I know, '#' is interpreted as a comment. Anyway I get an error, running the script:

Traceback (most recent call last):
  File "Y:\Home\laubeg\SharedFolder\Fehlman1\Fehlman2D_4\probeLine.py", line 25, in <module>
    mywfile = open(filenameW,'w')
NameError: name 'filenameW' is not defined

[GerhardHolzinger]

Hi, sorry for posting a buggy script. Mea culpa.

The code

filename = './system/' + probesDict
#filenameW = probesDict

should read

filenameW = './system/' + probesDict
#filenameW = probesDict

I used the commented filename-statements to test the script without the need of having an system directory present. However, filename and filenameW are not very good variable names.

[jiujiumin]

Originally Posted by GerhardHolzinger

You are completely right. My first post was indeed short of the information of how to use the script.

The script reads probeLineDict and generates entries for the regular probe function object. However, defining (start, end, nPoints) is much easier than writing 50 points along a line manually into probesDict.

The script overwrites probesDict. However, you can change the name of the file into which the script writes. If you are already using probes, make sure they do not collide.

The variable filename is the name of the file which contains the definition of the line to be probed. The variable filenameW is the name of the file into which the generated dictionary for probes is written.

The definition of the probe function object in controlDict must make use of an external file for the definition of the probes, otherwise, the generated file would be useless. I let the script write a seperate file in order to prevent it from messing up the controlDict.

The usage follow this procedure.

Put the probeLineDict into the system directory.
Run probeLine.py from the case directory
Run the solver

The controlDict contains this code:

functions
{
    probes1
    {
        type probes;
 
        functionObjectLibs ("libsampling.so");
 
        dictionary probesDict;
    }
 
    probes2
    {
        type probes;
 
        functionObjectLibs ("libsampling.so");
 
        dictionary probesDict2;
    }
}

this ： Run probeLine.py from the case directory how to work?

[jiujiumin]

Originally Posted by GerhardHolzinger

Hi, sorry for posting a buggy script. Mea culpa.

The code

filename = './system/' + probesDict
#filenameW = probesDict

should read

filenameW = './system/' + probesDict
#filenameW = probesDict

I used the commented filename-statements to test the script without the need of having an system directory present. However, filename and filenameW are not very good variable names.

The probesDict file where can i find?????
The probesDict file where can i find?????
The probesDict file where can i find?????
The probesDict file where can i find?????

[laubeg]

Hi,

sorry for being rude, but did you even try to find a solution for one of your problems?

Here is one for running the python script: http://www.google.com

And one for the probesDict: Read the thread from the beginning or try the former solution!

This is a forum, not a google search. Regards!

[jiujiumin]

Originally Posted by laubeg

Hi,

sorry for being rude, but did you even try to find a solution for one of your problems?

Here is one for running the python script: http://www.google.com

And one for the probesDict: Read the thread from the beginning or try the former solution!

This is a forum, not a google search. Regards!

sorry never next and at the time i am very anxious.
At the same time
I have another question how do I set the probeLine.py file to probe many lines at the same time? such as two lines at a time. thanks

[ari003]

Originally Posted by GerhardHolzinger

Hi, sorry for posting a buggy script. Mea culpa.

The code

filename = './system/' + probesDict
#filenameW = probesDict

should read

filenameW = './system/' + probesDict
#filenameW = probesDict

I used the commented filename-statements to test the script without the need of having an system directory present. However, filename and filenameW are not very good variable names.

Sir I m trying the way which you just mentioned here but however I m confused whether to keep the python file and probeLineDict in the same system folder or not . Also do I have to include anything in controlDict folder?
I ll remain hopeful to get your reply.

[ari003]

Anyone from the forum can I get a response. I m in serious need. Please I ll remain hopeful.

[mcgoldba]

Originally Posted by ari003

Sir I m trying the way which you just mentioned here but however I m confused whether to keep the python file and probeLineDict in the same system folder or not . Also do I have to include anything in controlDict folder?
I ll remain hopeful to get your reply.

Hi Ari,

I have just started to look at using this script myself, and have not yet tested it. However, to answer your question, I believe the "probeLine.py" file should go into the main case directory, and the "probeLineDict" file should go into the "system/" sub-directory.

This is shown on line 17 of the python script:

filename = './system/' + probeLineDictName

Regards

[mcgoldba]

In regards to your question about the controlDict, this was answered earlier in Gerhard's post:

Originally Posted by GerhardHolzinger

The controlDict contains this code:

functions
{
    probes1
    {
        type probes;

        functionObjectLibs ("libsampling.so");

        dictionary probesDict;
    }
    
    probes2
    {
        type probes;

        functionObjectLibs ("libsampling.so");

        dictionary probesDict2;
    }
}