I am using a MOOSE app called DwarfElephant that allows the use of the
libMesh Reduced Basis functionality in MOOSE. The app can currently handle
reduced order modeling with material parameters. I am trying to extend the
app to include the EIM functionality of libMesh. I have implemented example
4 of libMesh reduced basis in DwarfElephant. I am facing some runtime
errors. When I run the code, it stops at with a failed assertion
'!this->is_initialized()'. The stack trace is below.

Starting InitializeRB::initialize()
Assertion `!this->is_initialized()' failed.

Detaching after fork from child process 17473.
Stack frames: 13
0: libMesh::print_trace(std::ostream&)
1: libMesh::MacroFunctions::report_error(char const*, int, char const*,
char const*)
2: libMesh::System::init()
3: libMesh::EquationSystems::init()
4: DwarfElephantInitializeRBSystemSteadyState::initialize()
5: FEProblemBase::computeUserObjects(MooseEnumItem const&, Moose::AuxGroup
const&)
6: FEProblemBase::initialSetup()
7: DwarfElephantRBExecutioner::init()
8: MooseApp::executeExecutioner()
9: MooseApp::run()
10:
/home/2014-0004_focal_therapy/PhDs/AdapTT/Nikhil/DwarfElephant/./DwarfElephant-dbg()
[0x40d0b5]
11: __libc_start_main
12:
/home/2014-0004_focal_therapy/PhDs/AdapTT/Nikhil/DwarfElephant/./DwarfElephant-dbg()
[0x40cf02]
[0] ../src/systems/system.C, line 240, compiled Jul  3 2018 at 15:01:06
application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0
[unset]: write_line error; fd=-1 buf=:cmd=abort exitcode=1
:
system msg for write_line failure : Bad file descriptor

In DwarfElephant, I am calling all the funtions called in the libMesh
example 4 as they are. What could be the problem?

Best regards,
Nikhil
------------------------------------------------------------------------------
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

Reply via email to