add para to parent scaling
Overview
Integrations for bsplines weren't correct - it was missing parametric space to "parent" (or integration) element scaling. Added corresponding test
Addressed issues
- consider parametric space to parent element mapping
Checklists
- [ ] Documentations are up-to-date.
- [ ] Added example(s)
- [ ] Added test(s)
Summary by CodeRabbit
-
New Features
- Enhanced integration method for parametric functions, improving accuracy for splines with knot vectors.
- Introduced a new method for physical function integration (currently not implemented).
-
Bug Fixes
- Updated integration calculations to better account for spline geometry.
-
Tests
- Added comprehensive tests for volume integration across 1D, 2D, and 3D splines, ensuring consistency after operations like degree elevation and knot insertion.
- Included tests for complex geometries and validation of error handling for unsupported operations.
[!IMPORTANT]
Review skipped
Auto reviews are disabled on base/target branches other than the default branch.
Please check the settings in the CodeRabbit UI or the
.coderabbit.yamlfile in this repository. To trigger a single review, invoke the@coderabbitai reviewcommand.You can disable this status message by setting the
reviews.review_statustofalsein the CodeRabbit configuration file.
Walkthrough
The changes involve modifications to the parametric_function method in the splinepy/helpme/integrate.py file, where the integral calculation now includes an additional multiplication factor based on the control point bounds of the Bezier element. The tests/helpme/test_integrate.py file has been updated to refine the volume function's input handling and to include assertions for B-spline integration, enhancing test coverage. Additionally, the examples/iga/galerkin_laplace_problem.py file has been adjusted to scale the Jacobian determinant by the element size.
Changes
| File | Change Summary |
|---|---|
splinepy/helpme/integrate.py |
Updated parametric_function to include a multiplication factor for integration based on control point bounds. |
tests/helpme/test_integrate.py |
Refined volume function's input handling and added assertions for B-spline integration checks alongside Bezier spline tests. |
examples/iga/galerkin_laplace_problem.py |
Introduced scaling to the determinant of the Jacobian matrix in map_positions, clarifying the scaling by element size. |
Poem
🐇 In the world of splines, where curves intertwine,
A factor added makes integration divine.
With tests for B-splines, our coverage expands,
Ensuring our volumes meet all demands.
Hooray for the changes, let’s dance and cheer,
For every new feature brings splendor near! ✨
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
🪧 Tips
Chat
There are 3 ways to chat with CodeRabbit:
- Review comments: Directly reply to a review comment made by CodeRabbit. Example:
I pushed a fix in commit <commit_id>, please review it.Generate unit testing code for this file.Open a follow-up GitHub issue for this discussion.
- Files and specific lines of code (under the "Files changed" tab): Tag
@coderabbitaiin a new review comment at the desired location with your query. Examples:@coderabbitai generate unit testing code for this file.@coderabbitai modularize this function.
- PR comments: Tag
@coderabbitaiin a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.@coderabbitai read src/utils.ts and generate unit testing code.@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.@coderabbitai help me debug CodeRabbit configuration file.
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.
CodeRabbit Commands (Invoked using PR comments)
@coderabbitai pauseto pause the reviews on a PR.@coderabbitai resumeto resume the paused reviews.@coderabbitai reviewto trigger an incremental review. This is useful when automatic reviews are disabled for the repository.@coderabbitai full reviewto do a full review from scratch and review all the files again.@coderabbitai summaryto regenerate the summary of the PR.@coderabbitai generate docstringsto generate docstrings for this PR.@coderabbitai generate sequence diagramto generate a sequence diagram of the changes in this PR.@coderabbitai resolveresolve all the CodeRabbit review comments.@coderabbitai configurationto show the current CodeRabbit configuration for the repository.@coderabbitai helpto get help.
Other keywords and placeholders
- Add
@coderabbitai ignoreanywhere in the PR description to prevent this PR from being reviewed. - Add
@coderabbitai summaryto generate the high-level summary at a specific location in the PR description. - Add
@coderabbitaianywhere in the PR title to generate the title automatically.
CodeRabbit Configuration File (.coderabbit.yaml)
- You can programmatically configure CodeRabbit by adding a
.coderabbit.yamlfile to the root of your repository. - Please see the configuration documentation for more information.
- If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation:
# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
Documentation and Community
- Visit our Documentation for detailed information on how to use CodeRabbit.
- Join our Discord Community to get help, request features, and share feedback.
- Follow us on X/Twitter for updates and announcements.
I think this is also missing in iga-galerkin example
@markriegler did you check this out? This might be relevant for your integration PR #447 as well.
@markriegler did you check this out? This might be relevant for your integration PR #447 as well.
I just realized that I did the same parent to para scaling in my PR #447 , but in another unnecessarily more complicated way.
Closed, commits were cherry-picked to #447.