Author |
Message |
Mongi Mansouri (mongim_pde)
Member Username: mongim_pde
Post Number: 39 Registered: 11-2003
| Posted on Sunday, August 07, 2005 - 11:01 am: | |
Dear Robert, Thanks for your answer. I think that this suggestion might work better. But I have one related question: In elevation plot, there a modifier to specify the number of points to write "points=number". See eg the sample PLOTTEST.PDE. I tried this with export to file but it keeps writing a different number of points no matter what number i specify. I need to specify this number to make it easier for me to read and modify the file by a different program and read it back into Flexpde. The code line i used is: elevation(u) on "boundaryname" points=n export file="filename.dat" where n is a number of data points i want saved and "boundaryname" is defined using feature tool, and u is a solution. I used the elevationgrid=n in the select section but this did not change the outcome. What am i doing wrong? Can we control the number of points written to file in elevation plot to be a number we specify? Thank you for your help. /Mongi M.
|
Robert G. Nelson (rgnelson)
Moderator Username: rgnelson
Post Number: 424 Registered: 06-2003
| Posted on Tuesday, August 09, 2005 - 03:25 pm: | |
The number of points specified for an elevation plot is taken as a minimum resolution. The actual points in the plot are taken from the intersections of the plot line with the mesh cells, in order to preserve the resolution of the computed data. If the intersections are spaced farther than the point specification implies, then additional values are interpolated inside the mesh cells. There is at present no way to enforce a precise number of plot points. You'll have to do an external interpolation in the exported data to regularize the spacing.
|
|