This should in theory make it possible for people to write their own
DiffPhysics subclasses and attach them to a DiffSystem rather than
writing DiffSystem subclasses.
For now I'd just like to be sure we don't break any existing
DiffSystem and/or FEMSystem users. Give the following patch a try?
All -
I'm refactoring the SystemIO code to help address the RB IO bottleneck. As of
r6316, serialized vectors are written as
for node…
for var…
for comp…
instead of the previous implementation
for var…
for node…
for comp…
This allows the parallel communication to occur NVAR tim
On 11/06/2012 05:24 PM, Kirk, Benjamin (JSC-EG311) wrote:
> All -
>
> I'm refactoring the SystemIO code to help address the RB IO bottleneck. As
> of r6316, serialized vectors are written as
>
> for node…
>for var…
> for comp…
>
>
> instead of the previous implementation
>
> for var…
>
On Tue, 6 Nov 2012, Kirk, Benjamin (JSC-EG311) wrote:
> I tested this on all my stuff and am pretty confident with it, but
> let me know if anything breaks!
We should probably coordinate commits of "stuff that works great on
all our tests but fundamentally changes core library functionality"
bet
It wont compile for me:
In file included from src/physics/fem_physics.C:25:0:
/home/vikram/libmesh/include/libmesh/fem_system.h:58:1: error: expected
class-name before ‘{’ token
src/physics/fem_physics.C: In member function ‘void
libMesh::FEMSystem::mesh_position_set()’:
src/physics/fem_physics.C:
On Tue, 6 Nov 2012, Vikram Garg wrote:
It wont compile for me:
In file included from src/physics/fem_physics.C:25:0:
/home/vikram/libmesh/include/libmesh/fem_system.h:58:1: error: expected
class-name before ‘{’ token
src/physics/fem_physics.C: In member function ‘void
libMesh::FEMSystem::mes
