-
Notifications
You must be signed in to change notification settings - Fork 23
Production #551
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
Draft
MTCam
wants to merge
2,104
commits into
build-production
Choose a base branch
from
production
base: build-production
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.
Draft
Production #551
Conversation
This file contains hidden or 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
73e8347
to
92bb2c0
Compare
MTCam
commented
Apr 2, 2023
PrescribedFluidBoundary.__init__( | ||
self, | ||
boundary_state_func=self.get_external_state, | ||
boundary_grad_av_func=self.get_external_grad_av, |
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.
MTCam
commented
Apr 10, 2023
no longer done automatically in grudge when passing discr_tag_to_group_factory
…' into production-pilot
need to fix loop fusion to distinguish base DOF axis from quad DOF axis for this case to work reliably
* install pocl 6 by default but warn about potential performance degradation issue * fix pydocstyle * make check more specific * fix mypy * make check less specific * nudge pyro eos test tolerance * temporarily xfail the failing overintegration test need to fix loop fusion to distinguish base DOF axis from quad DOF axis for this case to work reliably * make doublemach and doublemach_physical_av generate the same mesh * add issue link to xfail * use non-deprecated argument in generate_gmsh * disable SVM on pocl6 where possible, otherwise warn
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.
This is all mirgecom development supporting the current CEESD prediction. It is not intended to be merged to main.
To see all the branches that are "feeding production", use the "Production Feeder" PR tag:
https://github.com/illinois-ceesd/mirgecom/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc+label%3A%22Production+Feeder%22
Rebuilding the
production
branch is required any time any of the feeder branches (includingmain
) changes.The procedure for building the
production
branch is as follows:All feeder branches are kept up-to-date with
main
Create the
build-production
branch by merging together these branches in this order:Merge
build-production
intoproduction