[sega]

Hello again.

Can somebody tell me how I can manage to create points files and field files?
I looked through the sample tool, which can create foamFile outputs, but I haven't found the corresponding code.

What I want to do, is to

• read a field value at different specific location inside the domain,
• put the value inside a field file
• and its location in a points file

So, the first problem I'm searching a solution for is how to store the values obtained from this loop:

    surfaceScalarField ps = fvc::interpolate(p);

    for (label k=0; k<facesSet.size(); k++)
    {
        int faceNumber = faces[k];
        Info<< "Entry " << k << " equals "<< ps[faceNumber]<< endl;
    };

I want the different values of ps[faceNumber] to be stored and somehow transfered to the mentioned field file and its corresponding points file.

Does anybody know, how this can be done?

[henrik]

Sebastian,

I think you intended to do something like

for (label k=0; k<facesSet.size(); k++)
{
     label faceNumber = facesSet[k];
    // copy data
}

but a faceSet is a labelHash. Therefore, you better use iterators

forAllConstIter(faceSet, facesSet, f)
{
    label faceNumber = f.key();
    // copy data
}

OR ask for the table of content

const labelList faces = facesSet.toc();
for (label k=0; k<faces.size(); k++)
{
    label faceNumber = faces[k];
    // copy data
}

OR do something foamish like:

scalarField data(0);
vectorField pnts(0);
const labelList faces = facesSet.toc();
data.map(ps, faces);
pnts.map(mesh.Cf(), faces);

I haven't tested any of this and knowing myself none of this will work straightaway. But it should work along these principals.

Henrik

[sega]

Dear Henrik.

Maybe we are misunderstanding each other.
I already have a way of accessing the field data of interest.

My question is how I can manage to make my tool output these field data and its corresponding coordinates into a single points file and a single field value file.
Similar to the sample tools foamFile output.

Hope this makes my interest a little bit clearer.
S.

[henrik]

Dear Sebastian,

OFstream os ("points");
os << pnts;

Henrik

[sega]

Originally Posted by henrik

Dear Sebastian,

OFstream os ("points");
os << pnts;

Henrik

Hi Henrik.

I assume "points" is the name of the variable containing the coordinates, while

os << pnts;

outputs the file?

If this is correct it will lead to two further questions:

1) If I work through the above loop which contains some different face values how do I store them in an appropriate array before outputting them to a file?

I would do this in some kind of MATLAB style:

// creating an empty field
scalarField pf(0);

// accessing the new field with the loop index k
// and putting the previous read value into this new place
pf[k] = ps[faceNumber]

2) What is the code for the faceCenter coordinate?
I have tried

ps.Cf()[k]

but this doesn't seem to be right?

[henrik]

Dear Sebastian,

I assume "points" is the name of the variable containing the coordinates, while outputs the file?

C++ variable names are never enclosed in brackets!

"points" is the name of the file at the other end of that OFstream (os). pnts is the name of the variable to be output to this stream (or file).

@1) There is a DynamicList container in OF, but I suggest you allocate the memory and then fill the array because you know how long the Field will be.

vectorField pnts(facesSet.size());
scalarField data(facesSet.size());

The good thing about map in the third exaple is that it will do the resizing for you.

@2) Try mesh.Cf()()[k]

I already have a way of accessing the field data of interest.

Are you sure?

Henrik

[sega]

Originally Posted by henrik

Try mesh.Cf()()[k]

Info<< "Cf(): "<< mesh.Cf()()[k] << endl;

Leads to this message while compiling:

error: no match for call to ‘(const Foam::GeometricField<Foam::Vector<double>, Foam::fvsPatchField, Foam::surfaceMesh>) ()’

[sega]

Originally Posted by henrik

"points" is the name of the file at the other end of that OFstream (os). pnts is the name of the variable to be output to this stream (or file).

Looks like this is working, but

        OFstream os ("p");
        os << faceCenterPressure;

Just gives me a single file in the case directory, which is overwritten at each timestep.

How can I manage to put it inside of separate subdirectory, which contains also the time step name?!

Something like

     OFstream os("data/" + runTime.timeName() + "/p")

didn't work out which means there is no file written.
Maybe the runTime.timeName() has to be rewritten into a string?!

[henrik]

You are on the right track, but you need to create the directory structure.

$FOAM_SRC/postProcessing/forces/forces/forces.C

Henrik

[henrik]

And what was the error message for mesh.Cf()[k]?

[sega]

Originally Posted by henrik

And what was the error message for mesh.Cf()[k]?

There is none. Maybe there was something else wrong.

[sega]

Originally Posted by henrik

You are on the right track, but you need to create the directory structure.

$FOAM_SRC/postProcessing/forces/forces/forces.C

Henrik

Ok Henrik.
I had a look into the forces.C file, but in spite of thinking I got it, I didn't.

I'm not able to handle the expression for the directory structure.

fileName directoryP = "/data/"runTime.timeName()"/p";

is my best guess, which is not working

error: expected ‘,’ or ‘;’ before ‘runTime’

even with a comma before and/or after...

What may be wrong?

[henrik]

Sebastian,

the "/"-operators are overloaded for fileName. So

fileName directoryP = runTime.timeName()/p;

is NOT a division, but will - on a single processor run - yield something like

[case_dir]/[time]/p

which is close to what you are looking for.

Henrik

[sega]

Originally Posted by henrik

yield something like

[case_dir]/[time]/p

Unfortunately not. This exact statement outputs the attached message while compiling.

What if I want to add some directory before the time-step name?
Something like

[Case-Dir]/data/0.01/p

so the written file will not interfere with the actual timesteps...

[henrik]

Sebastian,

you had too many and I was missing some . Very foamish error message, thus . Let's settle for a compromise

fileName directoryP = runTime.path()/"data"/runTime.time()/"p";

Make sure to create the directory!

Henrik

[sega]

Originally Posted by henrik

fileName directoryP = runTime.path()/"data"/runTime.time()/"p";

Nope.

error: no match for ‘operator/’ in ‘Foam::operator/(const Foam::string&, const Foam::string&)(((const Foam::string&)(& Foam::string(((const char*)"data"))))) / runTime.Foam::Time::<anonymous>.Foam::objectRegistry::time()’

I think we should reconsider in the morning ...

[henrik]

Yes, indeed:

fileName directoryP = runTime.path()/"data"/runTime.timeName()/"p";

[sega]

Yes its working!
Great work!

Tell me, is this basic C++ or OpenFOAM related knowledge?

[sega]

If you don't mind I will draw you attention to my post about file headers, which is connected to the matters discussed here:
http://www.cfd-online.com/Forums/ope...tml#post223590

[henrik]

Sebastian,

first of all, I have the feeling, that the error messages make little sense to you. Maybe you could go back, break this code and analyse the error messages.

Have a look into forces.C again. In fact, this statement looks very similar to what you where looking for.

forcesDir = obr_.time().path()/name_/obr_.time().timeName();

Ask yourself, what went wrong when I modified it to

fileName directoryP = "/data/"runTime.timeName()"/p";

Where are the operators?

The next problem, and you are not alone, is how to find your way in the library. There are many options. For example Doxygen or you can try:

egrep \:\:timeName $FOAM_SRC/OpenFOAM/lnInclude/*

This outputs a little more than you need, but try and find the function's declaration and the associated code.

Henrik