SEGV on Deception for ExaGO+IPOPT+ma57

[ovasios]

Issue type

• New feature
• Bug
• Discussion
• Other

Relates to

• OPFLOW
• SOPFLOW
• SCOPFLOW
• TCOPFLOW
• CMake build system
• Spack configuration
• Manual
• Web docs
• Other

Summary

Running OPFLOW using ma57 rather than ma27 on Deception results in SEGV. May be similar to #152.

Branch: develop
Machine: deception
Optimizer: IPOPT
System models: case_ACTIVSg25k.m, tgo30K_JUN_13_2018.m

Command:
./opflow -netfile case_ACTIVSg25k.m

Result:

[ExaGO] Creating OPFlow


******************************************************************************
This program contains Ipopt, a library for large-scale nonlinear optimization.
 Ipopt is released as open source code under the Eclipse Public License (EPL).
         For more information visit http://projects.coin-or.org/Ipopt
******************************************************************************

This is Ipopt version 3.12.10, running with linear solver ma57.

Number of nonzeros in equality constraint Jacobian...:   348438
Number of nonzeros in inequality constraint Jacobian.:   186640
Number of nonzeros in Lagrangian Hessian.............:   250917

Total number of variables............................:    57558
                     variables with only lower bounds:        0
                variables with lower and upper bounds:    32559
                     variables with only upper bounds:        0
Total number of equality constraints.................:    50000
Total number of inequality constraints...............:    46660
        inequality constraints with only lower bounds:        0
   inequality constraints with lower and upper bounds:    46660
        inequality constraints with only upper bounds:        0

iter    objective    inf_pr   inf_du lg(mu)  ||d||  lg(rg) alpha_du alpha_pr  ls
   0  5.0088244e+06 2.23e+04 3.61e+03  -1.0 0.00e+00    -  0.00e+00 0.00e+00   0
Input Error: Incorrect objective type.
Input Error: Incorrect objective type.
[0]PETSC ERROR: ------------------------------------------------------------------------
[0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range
[0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
[0]PETSC ERROR: or see https://petsc.org/release/faq/#valgrind and https://petsc.org/release/faq/
[0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run
[0]PETSC ERROR: to get more information on the crash.
[0]PETSC ERROR: Run with -malloc_debug to check if memory corruption is causing the crash.
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
with errorcode 59.

NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.

[cameronrutherford]

I think this is completely distinct from #152. These are separate platforms and different runs.

cc @nychiang @pelesh @cnpetra as we have discussed offline

cc @abhyshr

[pelesh]

I came across similar issue. It seems as if ExaGO does not allocate sufficient space for large problems.

@ovasios, if you substitute 25k system with 10k one in the input, does your simulation run correctly?

[pelesh]

Also, what I noticed -- why is Ipopt reporting Input Error: Incorrect objective type.?

[pelesh]

I think this is completely distinct from #152. These are separate platforms and different runs.

I also think this is a different issue. @ovasios, can you backtrace the segfault?