Skip to content

Conversation

@UZerbinati
Copy link
Contributor


name: "Bug fix or new feature"
description: ''
title: ''
labels: ''
assignees: ''


Description

Please include a summary of the changes introduced by this PR.
Additionally include any relevant motivation and context. List any
dependencies that are required for this change, other PRs upon
which this may depend, and associated issues.

Associated Pull Requests:

Fixes Issues:

If issues are fixed by this PR, prepend each of them with the word
"fixes", so they are automatically closed when this PR is merged. For
example "fixes #123, fixes #456".

Checklist for author:

  • I have linted the codebase (make lint in the firedrake source directory).
  • My changes generate no new warnings.
  • All of my functions and classes have appropriate docstrings.
  • I have commented my code where its purpose may be unclear.
  • I have included and updated any relevant documentation.
  • Documentation builds locally (make linkcheck; make html; make latexpdf in firedrake/docs directory)
  • I have added tests specific to the issues fixed in this PR.
  • I have added tests that exercise the new functionality I have introduced
  • Tests pass locally (pytest tests in the firedrake source directory) (useful, but not essential if you don't have suitable hardware).
  • I have performed a self-review of my own code using the below guidelines.

Checklist for reviewer:

  • Docstrings present
  • New tests present
  • Code correctly commented
  • No bad "code smells"
  • No issues in parallel
  • No CI issues (excessive parallelism/memory usage/time/warnings generated)
  • Upstream/dependent branches and PRs are ready

Feel free to add reviewers if you know there is someone who is already aware of this work.

Please open this PR initially as a draft and mark as ready for review once CI tests are passing.

Umberto Zerbinati added 2 commits October 16, 2023 23:03
Signed-off-by: Umberto Zerbinati <zerbinati@maths.ox.ac.uk>
Copy link
Contributor

@connorjward connorjward left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this the right way around? I wonder if ngsPETSc should internalise the import instead of us.

@UZerbinati
Copy link
Contributor Author

Is this the right way around? I wonder if ngsPETSc should internalise the import instead of us.

What do you mean internalise the import ?

@connorjward
Copy link
Contributor

Is this the right way around? I wonder if ngsPETSc should internalise the import instead of us.

What do you mean internalise the import ?

As in move the import firedrake statement in ngsPETSc inside a function to break the circular import. Instead of doing it in Firedrake.

I am not 100% sure on this so would be good to get opinions from others.

@dham dham merged commit ee41881 into master Oct 18, 2023
@dham dham deleted the uzerbinati/ngsHierarchy branch October 18, 2023 15:51
Ig-dolci pushed a commit that referenced this pull request Oct 20, 2023
Fixed circular import

Signed-off-by: Umberto Zerbinati <zerbinati@maths.ox.ac.uk>

---------

Signed-off-by: Umberto Zerbinati <zerbinati@maths.ox.ac.uk>
Co-authored-by: Umberto Zerbinati <zerbinati@maths.ox.ac.uk>
pbrubeck pushed a commit that referenced this pull request Oct 25, 2023
Fixed circular import

Signed-off-by: Umberto Zerbinati <zerbinati@maths.ox.ac.uk>

---------

Signed-off-by: Umberto Zerbinati <zerbinati@maths.ox.ac.uk>
Co-authored-by: Umberto Zerbinati <zerbinati@maths.ox.ac.uk>
pbrubeck pushed a commit that referenced this pull request Oct 25, 2023
Fixed circular import

Signed-off-by: Umberto Zerbinati <zerbinati@maths.ox.ac.uk>

---------

Signed-off-by: Umberto Zerbinati <zerbinati@maths.ox.ac.uk>
Co-authored-by: Umberto Zerbinati <zerbinati@maths.ox.ac.uk>
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

Successfully merging this pull request may close these issues.

Support for local_range

4 participants