Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Saving outputs when running sopflow with HiOp PriDec #160

Open
2 of 13 tasks
nkoukpaizan opened this issue Dec 13, 2024 · 4 comments
Open
2 of 13 tasks

Saving outputs when running sopflow with HiOp PriDec #160

nkoukpaizan opened this issue Dec 13, 2024 · 4 comments
Labels
bug Something isn't working sopflow Concerning the SOPFLOW application

Comments

@nkoukpaizan
Copy link
Collaborator

Issue type

  • New feature
  • Bug
  • Discussion
  • Other

Relates to

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

Summary
When running sopflow at scale on Summit with HiOp PriDec on GPUs, the code would crash when attempting to write the output files for each contingency (when this was requested). It looked to me like ExaGo was trying to run multiple instances of opflow again to convert to PS format, and it was running out of GPU memory. Note that HiOp PriDec had already converged when this happened. In the end, I turned off the final output generation to collect the scaling data.

@abhyshr, would you mind elaborating on how the outputs are generated? Is there a way to get the converged solution directly?

cc @pelesh @maksud

@pelesh
Copy link
Collaborator

pelesh commented Dec 13, 2024

CC @nychiang @cnpetra

@pelesh pelesh added bug Something isn't working sopflow Concerning the SOPFLOW application labels Dec 13, 2024
@cnpetra
Copy link

cnpetra commented Jan 6, 2025

By "output" you mean the standard convergence history of the solvers or some other output like files?

@nkoukpaizan
Copy link
Collaborator Author

By "output" you mean the standard convergence history of the solvers or some other output like files?

The latter. I'm referring to the solution output file. This defines what that is for opflow. For sopflow, a file gets written per recourse problem.

Somehow, we need to get the solution vector and convert it to whatever format is requested, and I don't fully understand what ExaGO is doing there.

@nkoukpaizan
Copy link
Collaborator Author

To be more specific, I tracked the failure to:

ierr = OPFLOWSolve(opflow);
. There is a OPFLOWSolve(opflow) within SOPFLOWSolverGetSolution_HIOP. I would expect the solution to be readily available at this stage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working sopflow Concerning the SOPFLOW application
Projects
None yet
Development

No branches or pull requests

3 participants