Helper functions for gismo export

[markriegler]

Overview

I found the current implementation of exporting gismo-compatible xml-files regarding boundary conditions, custom functions and the assembly options too cumbersome and hard to read with all the nested curly brackets. Therefore, I added three new helper functions to gismo export: one for boundary conditions, one for a function block and one for the assembly options block. This should lead to clearer code.

New features

All related to gismo export.

• Create boundary conditions block
• Create function block
• Create assembly options block
• Add comment above one of these blocks

Showcase

New example examples/export_gismo.py recreates the xml-file for gismo's Poisson example.

Checklists

• [ ] Documentations are up-to-date.
• [x] Added example(s)
• [x] Added test(s)

Summary by CodeRabbit

• New Features

  • Introduced the ability to create and export multipatch geometry to a gismo-compatible XML file.
  • Added functionality to define boundary conditions, right-hand side functions, and manufactured solutions for geometry export.
  • New XML structure for multi-patch geometry, enhancing simulation capabilities.

• Enhancements

  • Updated the gismo export module to include a new class for managing boundary conditions and assembly options.
  • Improved clarity of exported XML data with additional documentation parameters.
  • Enhanced usability with structured data blocks for easier representation of simulation parameters.

• Testing

  • Added new test functions to validate the export of additional blocks and ensure comprehensive coverage of gismo export features.

[j042]

Are those all new features or can this replace any of the existing section?

[markriegler]

These are all new features.

[coderabbitai[bot]]

[!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.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The updates enhance the capability to create and export multipatch geometries in a gismo-compatible format, introducing a class for structured data management. Users can now easily define NURBS curves, set boundary conditions, and specify function blocks, streamlining the export process. The new features are thoroughly tested to ensure reliability, making the splinepy library more robust for computational simulations.

Changes

File	Change Summary
examples/export_gismo.py	Enhanced with functions to create multipatch geometries, define boundary conditions, and export XML for gismo compatibility.
splinepy/io/gismo.py	Introduced the AdditionalBlocks class for managing structured data blocks, including methods for boundary conditions, function blocks, and assembly options, improving usability.
tests/io/test_gismo.py	Added tests to validate the export of function blocks and additional XML blocks, ensuring data integrity and adherence to the defined XML structure.
tests/data/gismo_additional_blocks.xml	New XML file defining a multi-patch geometry structure for simulations, including patches, boundaries, functions, and configuration options, ensuring detailed specification.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant export_gismo.py
    participant gismo
    participant gismo_io
    
    User->>export_gismo.py: Trigger export
    export_gismo.py->>gismo_io: Prepare geometries and boundaries
    gismo_io->>export_gismo.py: Return structured data
    export_gismo.py->>gismo: Call export with data
    gismo->>User: Exported XML File

Poem

In patches, our geometry thrives,
NURBS and boundaries come alive.
Functions bound, solutions clear,
Export to gismo, no fear.
With structured flow in files so neat,
Our code's journey is complete. 🎉

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in 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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file 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.

[j042]

Thanks for the update! Can you please go through the comments from the bot and mark them resolved afterwards? Feel free to leave a small comment if needed

[markriegler]

Can i merge this PR or do you do it?

[j042]

I will

[j042]

@markriegler can you comment on @s-tillmann's commits?

[markriegler]

As part of the boundary conditions in g+smo it is possible to prescribe a value at a certain corner (e.g. prescribing zero pressure at a specific corner for the lid driven cavity). @s-tillmann implemented this option for the export.