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

Extraneous write to LU_ERR with ULMAT HYPRE #14346

Open
rmcdermo opened this issue Mar 7, 2025 · 2 comments
Open

Extraneous write to LU_ERR with ULMAT HYPRE #14346

rmcdermo opened this issue Mar 7, 2025 · 2 comments
Assignees

Comments

@rmcdermo
Copy link
Contributor

rmcdermo commented Mar 7, 2025

Decided to test a slightly different case as I was testing the bundle and found this:

 Fire Dynamics Simulator

 Current Date     : March  7, 2025  09:53:55
 Revision         : FDS-6.10.0-0-gdd3edb3-release
 Revision Date    : Wed Mar 5 16:10:42 2025 -0500
 Compiler         : Intel(R) Fortran Intel(R) 64 Compiler Classic for applications running on Intel(R) 64, Version 2021.7.1 Build 20221019_000000
 Compilation Date : Mar 06, 2025  20:17:39

 Number of MPI Processes:  8

 MPI version: 3.1
 MPI library version: Open MPI v4.1.5, package: Open MPI mnv@excess.campus.nist.gov Distribution, ident: 4.1.5, repo rev: v4.1.5, Feb 23, 2023
 Hypre library version: v2.32.0
 Sundials library version: v6.7.0

 Job TITLE        : Flow through a duct, test of ULMAT with HYPRE
 Job ID string    : duct_flow_ulmat_hypre

 HYPRE : Matrix and Solver setup for MESH,ZONE=           1           0        4071
 Time Step:       1, Simulation Time:   0.12623 s
 Time Step:       2, Simulation Time:   0.25245 s
 Time Step:       3, Simulation Time:   0.37868 s

Need to remove this comment.

@rmcdermo rmcdermo self-assigned this Mar 7, 2025
@marcosvanella
Copy link
Contributor

Looks like you have CHECK_POISSON set to true?

@rmcdermo
Copy link
Contributor Author

rmcdermo commented Mar 7, 2025

Yes. I think CHECK_POISSON and something like PRESSURE_SOLVER_VERBOSE should be independent. But too late for this release. Whatever we do needs to be documented. Let's leave this open and I'll address it later.

@gforney we do not need to hold up release over this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants