-
Notifications
You must be signed in to change notification settings - Fork 229
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
dsl: Move SubDimension thickness evaluation to the thicknesses themselves #2470
Merged
Merged
Changes from all commits
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
90cd794
dsl: Adjust how SubDimensions are created
EdCaunt 6469359
dsl: Tweaks to subdimensions
EdCaunt 549af29
misc: Further investigations
EdCaunt e83e671
misc: Reworking SubDomainThickness
EdCaunt 59136ca
misc: Further SubDomain fiddling
EdCaunt 1cf8116
compiler: Started moving SubDimension arg vals to SubDimensionThickness
EdCaunt f45ee73
compiler: Moved compiler gubbins from SubDimension to SubDimensionThi…
EdCaunt d5b16c2
tests; Fix up tests and update concretisation functionality
EdCaunt e2eed6a
tests: Fix up symbolics tests
EdCaunt f11d50d
dsl: Continue refactoring SubDimensions
EdCaunt 5c5ee9d
compiler: Moved thickness arg vals in operator
EdCaunt 2e02924
compiler: Remove leftovers from operator
EdCaunt 62cd507
dsl: Rework SubDimension types for better inheritance
EdCaunt 3805333
misc: Fix up class names
EdCaunt a5e42a9
misc: Adjust tests and tidy variable names for clarity
EdCaunt 26edbc6
tests: Tweak caching tests to reflect lazy touch of Dimension bounds
EdCaunt 3939b06
misc: Tidy up
EdCaunt a6dd6b0
examples: Update printed code in examples to reflect SymPy ordering
EdCaunt abf00f8
tests: Update caching test and fix minor decomposition bug
EdCaunt 6e7c017
misc: Tidy up
EdCaunt File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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 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 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 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
Oops, something went wrong.
Oops, something went wrong.
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.
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 think this should be triggered from within
SubDimension._arg_values
itselfThere 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.
No, the issue is that the
SubDimension
isn't necessarily available to the operator. You can craft legalOperator
s which only contain the thickness, not the parent subdimension, hence the reworking in this PRThere 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.
Why isn't it caught by
self.input
's default line 487There 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.
Assuming "it" means the subdomain, you can craft a legal operator as in the MFE at the top of this PR where the Operator never sees the SubDimension, only its thickness symbols
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 don't mean the subdomain no, I mean the thickness, you're saying you can create an operator where the Thickness (p here) is in op.parameters but is not in op.inputs?
If it's the case, i.e if it is not in inputs, then it should not need to be in args since it's not an input.
If it's not the case, the line 487 processes all inputs and should cover that case already
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 tried it, and this is not the case
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.
How is that possible? It's clearly in parameters since you added this so if you add is_Input and it doesn't catch it then something is broken
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.
There's no grid in the kwargs at the point where
_arg_values
is called on the inputs, which makes it no-op. It also needs to be done before objects get_arg_values
called on them iirc, hence the current position of this loop.You could reorder
_prepare_arguments
to process the grid earlier, but my functions-on-subdomains branch has a bunch of reworking here and fixing the merge conflicts will be a pain, so best to stick a pin in it and fix down the line imo.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 you open an issue about it then
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 also don't understand this thing honestly. We need an issue and ideally a comment on top of this loop explaining what's going on and what should actually happen instead. You can do it in another branch as it's a minor thing