On Thu, 25 Jan 2018, Michael Povolotskyi wrote:
Can I add just a plain System to the EquationSystem?
That's actually a good question, and if you'd try it and report back
I'd appreciate it.
The answer used to be "no", which is why everybody habitually
recommends adding ExplicitSystem for storing auxilliary data.
But at some point a few years back IIRC I added the ability for us to
instantiate a bare System. I've only used that in various
postprocessing tools, though. It should be the "proper" way to create
an auxilliary data system now, but I don't know if anybody's ever
tried it!
So: give it a shot? Then if it works let us know, and if it doesn't
then file a ticket and use ExplicitSystem instead?
Thanks,
---
Roy
On 01/25/2018 12:17 PM, Roy Stogner wrote:
On Thu, 25 Jan 2018, Michael Povolotskyi wrote:
I will add another system and will not solve it.
Make sure it's ExplicitSystem (no, wait, maybe just plain System?
ExplicitSystem does still allocate an rhs, not just a solution).
ImplicitSystem will try to allocate a Jacobian for you whether you
plan to eventually assemble and solve with it or not, and that can get
expensive.
---
Roy
On 01/25/2018 08:25 AM, Roy Stogner wrote:
On Wed, 24 Jan 2018, Paul T. Bauman wrote:
Sorry for slow response. I have nothing better to offer other than 3
vectors, but maybe others will.
You can add another ExplicitSystem to the mesh, giving it a
vector-valued variable corresponding to your solution system's
scalar-valued variable.
This is more flexible (if you have multiple variables in your solution
system but only want to add a vector-valued postprocessed field for
one of them, for instance) but probably a bit harder to work with.
---
Roy
On Mon, Jan 22, 2018 at 12:40 PM, Michael Povolotskyi
<[email protected]>
wrote:
Dear Libmesh developers and users,
I need to compute a field on mesh based on a solution.
To do so I usually add a vector to a system and fill it with data.
This works perfectly for a scalar field.
What would you recommend to do for a vector field.
Of course, I can add 3 vectors, one for each component of the field.
Is
there a better way?
Thank you,
Michael.
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users
