CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > OpenFOAM Running, Solving & CFD

libsimpleFunctionObjects: functionObject name

Register Blogs Members List Search Today's Posts Mark Forums Read

Like Tree2Likes
  • 1 Post By gschaider
  • 1 Post By gschaider

Reply
 
LinkBack Thread Tools Display Modes
Old   June 26, 2013, 08:10
Question libsimpleFunctionObjects: functionObject name
  #1
pad
New Member
 
PA
Join Date: Mar 2009
Posts: 23
Rep Power: 8
pad is on a distinguished road
Hello,

I need to calculate massflow at certain patches for which I use libsimpleFunctionObjects.so.

However, when I specify the function object to be e.g.

_massflow
{
type patchMassFlow;
functionObjectLibs ("libsimpleFunctionObjects.so");
verbose true;
patches
(
inflow
ami_21_30
ami_40_31
outflow
ami_31_40
ami_30_21
);
factor 3600.0;
}

the data will be saved in a folder named patchMassFlows__massflow. Is there a way to specify that patchMassFlows_ should not be included in the name?

It might seem to be a small problem but my postprocessing script relies on every functionObject to be saved under _<NAME>.

Regards
Per
__________________
Regards,
Per
pad is offline   Reply With Quote

Old   June 26, 2013, 11:37
Default
  #2
Assistant Moderator
 
Bernhard Gschaider
Join Date: Mar 2009
Posts: 3,915
Rep Power: 40
gschaider will become famous soon enoughgschaider will become famous soon enough
Quote:
Originally Posted by pad View Post
Hello,

I need to calculate massflow at certain patches for which I use libsimpleFunctionObjects.so.

However, when I specify the function object to be e.g.

_massflow
{
type patchMassFlow;
functionObjectLibs ("libsimpleFunctionObjects.so");
verbose true;
patches
(
inflow
ami_21_30
ami_40_31
outflow
ami_31_40
ami_30_21
);
factor 3600.0;
}

the data will be saved in a folder named patchMassFlows__massflow. Is there a way to specify that patchMassFlows_ should not be included in the name?

It might seem to be a small problem but my postprocessing script relies on every functionObject to be saved under _<NAME>.

Regards
Per
Currently the hardcoded behaviour (to change it you'd have to go to the source) of the simpleFunctionObjects that write data is to compose the folder name from the type name and the FO-name. To make matters worse the latest release writes these folders to a sub-folder "postprocessing" (convention since OF 2.2)

Short answer: No
pad likes this.
__________________
Note: I don't use "Friend"-feature on this forum out of principle. Ah. And by the way: I'm not on Facebook either. So don't be offended if I don't accept your invitation/friend request
gschaider is online now   Reply With Quote

Old   June 27, 2013, 02:16
Default
  #3
pad
New Member
 
PA
Join Date: Mar 2009
Posts: 23
Rep Power: 8
pad is on a distinguished road
Hi Bernhard,

Thank you for your reply.

I don't like to modify the source code unless absolutely necessary so I guess for now I will modify my postprocessing scripts slightly.

Is there any particular reason for adding the typename in front of the FO name as this doesn't seem to be standard OF behaviour (at least in 2.1)? Or have I misunderstood something here?

Thanks again...
__________________
Regards,
Per
pad is offline   Reply With Quote

Old   June 27, 2013, 06:20
Default
  #4
Assistant Moderator
 
Bernhard Gschaider
Join Date: Mar 2009
Posts: 3,915
Rep Power: 40
gschaider will become famous soon enoughgschaider will become famous soon enough
Quote:
Originally Posted by pad View Post
Hi Bernhard,

Thank you for your reply.

I don't like to modify the source code unless absolutely necessary so I guess for now I will modify my postprocessing scripts slightly.

Is there any particular reason for adding the typename in front of the FO name as this doesn't seem to be standard OF behaviour (at least in 2.1)? Or have I misunderstood something here?

Thanks again...
Well. Reason. Similar to yours:
- Scripts. Mine say "Ah. 'patchMassFlow_*'. I know how to handle that"
- It is easier to remove files. "rm patch*" throws away all the patch-stuff. I don't have to look around "Err. 'fooFlow' is what? Ah. patchMassFlow. OK. Let it go"

So basically the types were added to the directory names because I think that redundant information makes life easier
pad likes this.
__________________
Note: I don't use "Friend"-feature on this forum out of principle. Ah. And by the way: I'm not on Facebook either. So don't be offended if I don't accept your invitation/friend request
gschaider is online now   Reply With Quote

Reply

Tags
functionobject, massflow

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Create registered object at runtime using a functionObject CedricVH OpenFOAM Programming & Development 21 November 28, 2012 06:04
runTime out of scope in functionObject Sune OpenFOAM Programming & Development 2 September 26, 2012 02:11
functionObject file format akidess OpenFOAM Post-Processing 7 February 24, 2012 09:51
Access particle data from functionObject CedricVH OpenFOAM 10 July 21, 2011 12:03
Process control functionObject Vetter OpenFOAM 4 January 14, 2011 11:38


All times are GMT -4. The time now is 09:08.