-
Notifications
You must be signed in to change notification settings - Fork 89
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
feat: hypre improvements #3339
base: develop
Are you sure you want to change the base?
feat: hypre improvements #3339
Conversation
Here is a quick test I ran on a version of SPE10 with burdens, compositional poromechanics, though with homogeneous properties, (so its just a high perm slab between two low perm boxes). Should be about 40 million DoF, and I ran on Dane. Here were the results with develop a few weeks ago
Here are the results with the new Hypre
Note that this does not double the number of nodes for each test, I will do that now |
Old results for heterogeneous SPE10 compositional poromechanics on CPU (dane)
New results for heterogeneous SPE10 compositional poromechanics on CPU (dane)
|
…/GEOS into feature/paludettomag1/hypre-sdc
…er in several functions
…/GEOS into feature/paludettomag1/hypre-sdc
HYPRE_SetUmpirePinnedPoolName( "HYPRE_PINNED" ); | ||
#endif | ||
|
||
HYPRE_SetLogLevel( getenv( "HYPRE_LOG_LEVEL" ) ? atoi( getenv( "HYPRE_LOG_LEVEL" ) ) : 0 ); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can it be set by linear solver log level?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but I did this way because the information provided here is mainly for developers. Other libraries such as umpire and rocsparse work this way as well (using env variable). I am open to change the strategy here if needeed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sounds reasonable, thanks, no need to change
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's not use environment variables please.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can remove this. What is the issue with env vars again?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I personally don't like them. It's hard to keep track of who sets them. Also we don't really do it for anything else in GEOS.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here's a place where it's being used:
int columns = getenv( "COLUMNS" ) ? atoi( getenv( "COLUMNS" )) : 120; |
HYPRE_LOG_LEVEL
is an option supposed to be used by developers only. It's very convenient to turn it on/off if it's a env var wrt a XML input. I don't see any harm with using env var specifically, but I'm happy to remove it if that's the best solution
@paveltomin this should work for SEQ runs now |
[like] Thomadakis, Michael reacted to your message:
…________________________________
From: Victor A. P. Magri ***@***.***>
Sent: Thursday, October 10, 2024 9:29:13 PM
To: GEOS-DEV/GEOS ***@***.***>
Cc: Thomadakis, Michael ***@***.***>; Mention ***@***.***>
Subject: [**EXTERNAL**] Re: [GEOS-DEV/GEOS] feat: hypre improvements (PR #3339)
Be aware this external email contains an attachment and/or link.
Ensure the email and contents are expected. If there are concerns, please submit suspicious messages to the Cyber Intelligence Center using the Report Phishing button.
We are investigating a few convergence issues with Poromechanics runs using this branch. @drmichaeltcvx<https://github.com/drmichaeltcvx>, please you can put your tests on hold until the issue is sorted out
—
Reply to this email directly, view it on GitHub<#3339 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AS6ZG2RPWTBYKN45GHRDVELZ23WSTAVCNFSM6AAAAABN4TL2HKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBWGA3DSOJWHA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
[like] Thomadakis, Michael reacted to your message:
…________________________________
From: Victor A. P. Magri ***@***.***>
Sent: Tuesday, October 22, 2024 5:23:58 PM
To: GEOS-DEV/GEOS ***@***.***>
Cc: Thomadakis, Michael ***@***.***>; Mention ***@***.***>
Subject: [**EXTERNAL**] Re: [GEOS-DEV/GEOS] feat: hypre improvements (PR #3339)
Be aware this external email contains an attachment and/or link.
Ensure the email and contents are expected. If there are concerns, please submit suspicious messages to the Cyber Intelligence Center using the Report Phishing button.
@paveltomin<https://github.com/paveltomin> this should work for SEQ runs now
—
Reply to this email directly, view it on GitHub<#3339 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AS6ZG2S5RJU3QN4QOIMEZB3Z42C25AVCNFSM6AAAAABN4TL2HKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRZHA2DQMBVHE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will approve it but please add an xml option for the linear solver log level instead of using that env variable.
…/GEOS into feature/paludettomag1/hypre-sdc
@CusiniM @rrsettgast Could you do a new LC build and create the LvArray PR? Can we put this on the merge queue? Thanks! |
@castelletto1 @CusiniM @rrsettgast Can you guys take it from here? It seems there's nothing else I can do. Thanks! |
is this basically ready? I mean it clearly needs an LvArray PR and a rebaseline but is it ready otherwise? |
Right, it's ready. Needs a LvArray PR and LC build, which I can't do. Rebaseline is due to field value change ( |
separateComponents
option to mechanics solver setup in MGRaddCommaSeparators
to StringUtilitiesRequires GEOS-DEV/thirdPartyLibs#286