-
Notifications
You must be signed in to change notification settings - Fork 16
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
Direct Solver: Multilevel Proxy-based Solver #174
Open
alexfikl
wants to merge
4
commits into
inducer:main
Choose a base branch
from
alexfikl:direct-solver-solve
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This also contains #164 at the moment and is still quite WIP. For one, only implemented a forward matvec, not the actual solver 😢 |
alexfikl
force-pushed
the
direct-solver-solve
branch
from
August 4, 2022 18:23
5e7f654
to
3164799
Compare
alexfikl
force-pushed
the
direct-solver-solve
branch
9 times, most recently
from
August 19, 2022 07:52
a00d5a0
to
6efa838
Compare
alexfikl
force-pushed
the
direct-solver-solve
branch
4 times, most recently
from
August 25, 2022 16:43
ae83dd5
to
0105f84
Compare
alexfikl
force-pushed
the
direct-solver-solve
branch
from
September 3, 2022 12:38
0105f84
to
9ed57c2
Compare
alexfikl
force-pushed
the
direct-solver-solve
branch
6 times, most recently
from
September 14, 2022 11:19
871c491
to
c742491
Compare
This now implements both a matvec and a direct solver with recursive skeletonization. Both seem to work pretty close to design parameters. Still need to stress test it more though! |
alexfikl
force-pushed
the
direct-solver-solve
branch
5 times, most recently
from
September 22, 2022 16:37
7d5bb22
to
ddc4a8b
Compare
alexfikl
force-pushed
the
direct-solver-solve
branch
from
September 23, 2022 13:29
ddc4a8b
to
d3f168c
Compare
alexfikl
force-pushed
the
direct-solver-solve
branch
from
April 26, 2023 07:43
7cfa997
to
e7371f9
Compare
alexfikl
force-pushed
the
direct-solver-solve
branch
from
May 3, 2023 11:04
e7371f9
to
f5ab988
Compare
alexfikl
force-pushed
the
direct-solver-solve
branch
from
May 18, 2023 13:20
ff9ee43
to
41326fa
Compare
alexfikl
force-pushed
the
direct-solver-solve
branch
2 times, most recently
from
June 20, 2023 06:42
09d715b
to
f5e02b6
Compare
alexfikl
force-pushed
the
direct-solver-solve
branch
from
June 27, 2023 06:14
f5e02b6
to
c0e261e
Compare
alexfikl
force-pushed
the
direct-solver-solve
branch
3 times, most recently
from
August 4, 2023 06:55
f8bf7c0
to
f680a72
Compare
alexfikl
force-pushed
the
direct-solver-solve
branch
2 times, most recently
from
September 8, 2023 07:20
5062dd1
to
1524bc9
Compare
alexfikl
force-pushed
the
direct-solver-solve
branch
from
October 17, 2023 06:44
1524bc9
to
af9c2d0
Compare
alexfikl
force-pushed
the
direct-solver-solve
branch
from
November 1, 2023 15:52
af9c2d0
to
28c1c92
Compare
alexfikl
force-pushed
the
direct-solver-solve
branch
from
May 29, 2024 07:02
28c1c92
to
8813bce
Compare
alexfikl
force-pushed
the
direct-solver-solve
branch
from
July 6, 2024 06:33
8813bce
to
be87bed
Compare
alexfikl
force-pushed
the
direct-solver-solve
branch
3 times, most recently
from
August 2, 2024 11:53
64a779a
to
158afc9
Compare
alexfikl
force-pushed
the
direct-solver-solve
branch
2 times, most recently
from
September 1, 2024 08:41
d6fc4ac
to
ee7fb16
Compare
alexfikl
force-pushed
the
direct-solver-solve
branch
2 times, most recently
from
November 16, 2024 09:02
47c06b1
to
83658ca
Compare
alexfikl
force-pushed
the
direct-solver-solve
branch
from
December 17, 2024 08:16
83658ca
to
0e74b01
Compare
alexfikl
force-pushed
the
direct-solver-solve
branch
from
January 8, 2025 09:11
0e74b01
to
7211102
Compare
alexfikl
force-pushed
the
direct-solver-solve
branch
from
January 8, 2025 09:26
7211102
to
bf42a83
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Attempting to break up the direct solver MR into smaller, more reviewable pieces. As a rundown
linalg.proxy
).The code for this is mostly in the deprecated https://gitlab.tiker.net/inducer/pytential/-/merge_requests/137.