On Fri, May 12, 2017 at 1:17 PM, Salazar De Troya, Miguel <
[email protected]> wrote:
> Hi
>
> I want to visualize the boundary id’s on paraview to make sure I am
> marking them correctly. I want to see the face of a certain element with a
> color that corresponds to its boundary id. Is there
In ParaView there is currently no way to color the side of an element. Only
point/nodal data or cell/element data can be plotted. The normal way to get
around this is to do something like the ExodusII file format does which has
separate "cells" for boundaries (e.g. 2D boundary cells for 3D domains)
Maybe you could just project a DG function with a certain value on the
corresponding boundary and then write the result with your preferred
IO?
On Fri, May 12, 2017 at 11:18 PM, Shayan Hoshyari wrote:
> Hi,
>
> I have this incomplete piece of code. It is definitely an overkill, but I
> thought it
Hi,
I have this incomplete piece of code. It is definitely an overkill, but I
thought it might help.
*
struct Face
{
uint bdry_id;
libMesh::ElemType type;
std::vector nodes;
Face(const uint _id, const libMesh::ElemType type
On Oct 30, 2012, at 12:34 PM, David Knezevic wrote:
> OK, so for now should I go ahead and check in my patch from yesterday?
>
I'm OK with it.
--
Everyone hates slow websites. So do we.
Make your web apps faster with
OK, so for now should I go ahead and check in my patch from yesterday?
> On Tue, Oct 30, 2012 at 10:07 AM, Roy Stogner wrote:
>
>> Interesting; I hadn't noticed that method when it went in. Looks like
>> you're out of luck if a single EquationSystems has more than one
>> System with the same var
On Tue, Oct 30, 2012 at 10:07 AM, Roy Stogner wrote:
> Interesting; I hadn't noticed that method when it went in. Looks like
> you're out of luck if a single EquationSystems has more than one
> System with the same variable name, but then I suspect pretty much all
> our I/O other than xda/xdr fai
On Tue, 30 Oct 2012, Derek Gaston wrote:
It should be noted that you can already restrict what variables come
out into an Exodus file. On your ExodusII_IO object just use
set_output_variables()
Interesting; I hadn't noticed that method when it went in. Looks like
you're out of luck if a sin
On Mon, Oct 29, 2012 at 9:09 PM, Roy Stogner wrote:
> Looks good. While we're at it should we just go whole hog and
> figure out how to supply a list of sysname/varname pairs if desired
> too? That FEType parameter is kind of a poor hack.
>
It should be noted that you can already restrict what
On 10/29/2012 11:13 PM, Paul T. Bauman wrote:
> On Mon, Oct 29, 2012 at 10:09 PM, Roy Stogner
> mailto:[email protected]>> wrote:
>
> While we're at it should we just go whole hog and
> figure out how to supply a list of sysname/varname pairs if desired
> too? That FEType para
On Mon, Oct 29, 2012 at 10:09 PM, Roy Stogner wrote:
> While we're at it should we just go whole hog and
> figure out how to supply a list of sysname/varname pairs if desired
> too? That FEType parameter is kind of a poor hack.
That'll be a bit more work, I think, because Exodus output, for exa
On Mon, 29 Oct 2012, David Knezevic wrote:
> The attached patch does the job for me. Let me know if there are any
> suggestions, otherwise I'll go ahead and check it in.
Looks good. While we're at it should we just go whole hog and
figure out how to supply a list of sysname/varname pairs if de
The attached patch does the job for me. Let me know if there are any
suggestions, otherwise I'll go ahead and check it in.
David
On 10/29/2012 07:18 PM, Kirk, Benjamin (JSC-EG311) wrote:
That would be a very, very welcome patch.
-Ben
On Oct 29, 2012, at 4:30 PM, "David Knezevic"
wrote
That would be a very, very welcome patch.
-Ben
On Oct 29, 2012, at 4:30 PM, "David Knezevic"
wrote:
> I'd like to be able to plot data from a subset of the Systems in an
> EquationSystems object. I generally use write_equation_systems, which
> writes out data from all the systems. I didn'
Thanks, I didn't know that, that's helpful.
But my main motivation was to reduce data by only writing out the
surface, so I'll go with BoundaryInfo::sync.
David
On 08/04/2012 01:14 PM, Derek Gaston wrote:
> If you have a side set on the side you are interested in then in
> Paraview you can sh
If you have a side set on the side you are interested in then in
Paraview you can show only that side and plot the solution on it.
When you open the result just deselect all "blocks" and the select the
side set corresponding to the boundary you want to view and then hit
Apply. You can then color
> On Sat, 4 Aug 2012, David Knezevic wrote:
>
>> I was wondering if anyone can suggest a good way to plot the solution on
>> the boundary of a mesh only? I guess I could use BoundaryInfo::sync to
>> make the boundary mesh, then use a MeshFunction to project the boundary
>> solution, and then plot.
On Sat, 4 Aug 2012, David Knezevic wrote:
> I was wondering if anyone can suggest a good way to plot the solution on
> the boundary of a mesh only? I guess I could use BoundaryInfo::sync to
> make the boundary mesh, then use a MeshFunction to project the boundary
> solution, and then plot. But I
That's pretty much what I do, except sometimes add additional variables to a
boundary system for post processing. This is nice because you can extract just
a subset corresponding to specified bcs.
That's the most flexible approach. For special classes of properties sometimes
you can exploit fe
On Wed, 10 Dec 2008, Derek Gaston wrote:
> This works for me. Maybe it's because I start with an Exodus file in the
> beginning that has sidesets declared on it. But if I go through the
> following with meshtool... everything works fine:
>
> meshtool -d 3 -i input.e -o out.xda
> meshtool -d 3 -
Roy,
This works for me. Maybe it's because I start with an Exodus file in the
beginning that has sidesets declared on it. But if I go through the
following with meshtool... everything works fine:
meshtool -d 3 -i input.e -o out.xda
meshtool -d 3 -i out.xda -o out.e
After all of this out.e is es
Weird we have many people using this stuff all day long. I'll take a
look at meshtool this afternoon.
Derek
Sent from my iPhone
On Dec 8, 2008, at 11:04 AM, Roy Stogner <[EMAIL PROTECTED]>
wrote:
>
> On Mon, 8 Dec 2008, Derek Gaston wrote:
>
>> You could also use Exodus... I modified the E
On Mon, 8 Dec 2008, Derek Gaston wrote:
> You could also use Exodus... I modified the Exodus writer to correctly write
> out the boundary ids
For some definition of "correctly", anyway. ;-) With the SVN head,
my attempt to run "meshtool -d 2 -i one_tri.xda -o one_tri.exd" dies
in ExodusII_IO_
> You could also use Exodus... I modified the Exodus writer to correctly
> write out the boundary ids which you should then be able to see in
> Paraview (I can definitely see them with Ensight...).
>
>> I've written a little tool to twiddle boundary_info ids based on point
>> location and face norm
You could also use Exodus... I modified the Exodus writer to correctly
write out the boundary ids which you should then be able to see in
Paraview (I can definitely see them with Ensight...).
Derek
On Dec 2, 2008, at 2:23 PM, Roy Stogner wrote:
>
> I've written a little tool to twiddle bound
>> Fine with me as long as mesh.partition(n) still does what it always has.
>
> Two changes for simplicity's sake on the ParallelMesh behavior:
>
> ParMETIS instead of METIS is now the default even when the
> ParallelMesh is still serialized.
>
> The ParmetisPartitioner object doesn't get destro
On Tue, 2 Dec 2008, John Peterson wrote:
> Fine with me as long as mesh.partition(n) still does what it always has.
Two changes for simplicity's sake on the ParallelMesh behavior:
ParMETIS instead of METIS is now the default even when the
ParallelMesh is still serialized.
The ParmetisPartition
On Tue, Dec 2, 2008 at 5:44 PM, Roy Stogner <[EMAIL PROTECTED]> wrote:
> On Tue, 2 Dec 2008, Roy Stogner wrote:
>
>> On Tue, 2 Dec 2008, John Peterson wrote:
>>
>>> Use the BoundaryInfo object to Sync with a boundary mesh and write to
>>> GMV. Set each element's processor_id to its boundary ID to
On Tue, 2 Dec 2008, Roy Stogner wrote:
> Or better yet - instead of creating a Parmetis or Metis partitioner
> deep in mesh_base.C, let's leave it up to the Mesh constructor to
> create a partitioner, then give the user the ability to destruct the
> default and replace it with their own (including
On Tue, 2 Dec 2008, Roy Stogner wrote:
> On Tue, 2 Dec 2008, John Peterson wrote:
>
>> Use the BoundaryInfo object to Sync with a boundary mesh and write to
>> GMV. Set each element's processor_id to its boundary ID to color them
>> independently.
>
> Nice idea! Thanks!
>
> It looks like meshtoo
On Tue, Dec 2, 2008 at 3:47 PM, Roy Stogner <[EMAIL PROTECTED]> wrote:
> On Tue, 2 Dec 2008, John Peterson wrote:
>
>> On Tue, Dec 2, 2008 at 3:23 PM, Roy Stogner <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> I've written a little tool to twiddle boundary_info ids based on point
>>> location and face norma
On Tue, 2 Dec 2008, John Peterson wrote:
> On Tue, Dec 2, 2008 at 3:23 PM, Roy Stogner <[EMAIL PROTECTED]> wrote:
>>
>> I've written a little tool to twiddle boundary_info ids based on point
>> location and face normal direction, but I'm using it on a fine mesh
>> where I'd like to visualize the r
On Tue, Dec 2, 2008 at 3:23 PM, Roy Stogner <[EMAIL PROTECTED]> wrote:
>
> I've written a little tool to twiddle boundary_info ids based on point
> location and face normal direction, but I'm using it on a fine mesh
> where I'd like to visualize the results to verify them. Do we output
> boundary
thank you very much Roy,
df
On Wed, 17 Sep 2008, Roy Stogner wrote:
>
> On Wed, 17 Sep 2008, David Fuentes wrote:
>
>> Thanks Roy. It seems as though the solution vector
>> is managed by libmesh. How can I access the solution vector?
>
> It's managed by the library, but you've still got fu
On Wed, 17 Sep 2008, David Fuentes wrote:
> Thanks Roy. It seems as though the solution vector
> is managed by libmesh. How can I access the solution vector?
It's managed by the library, but you've still got full read-write
access through the System::solution auto pointer. Just don't
repartitio
Thanks Roy. It seems as though the solution vector
is managed by libmesh. How can I access the solution vector?
df
On Wed, 17 Sep 2008, Roy Stogner wrote:
>
> On Wed, 17 Sep 2008, David Fuentes wrote:
>
>> when using
>>
>> ExodusII_IO(mesh).write_equation_systems()
>>
>> Is it possible
Thank you Derek!
David
On Wed, 17 Sep 2008, Derek Gaston wrote:
> The easy way to do this is to add an ExplicitSystem with a variable in it to
> hold your exact solution values to your EquationSystem and then attach an
> initial condition function that evaluates your exact solution and ret
On Wed, 17 Sep 2008, David Fuentes wrote:
> when using
>
> ExodusII_IO(mesh).write_equation_systems()
>
> Is it possible to plot variable *other* than the
> solution for the system?
> I want to plot the function that I am using
> for the ExactSolution class.
I'm not sure if there's an official
The easy way to do this is to add an ExplicitSystem with a variable in
it to hold your exact solution values to your EquationSystem and then
attach an initial condition function that evaluates your exact
solution and returns the value. Then when you write out your equation
system that vari
39 matches
Mail list logo
