Skip to content
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

Error instead of warning for zero-dim boundaries not periodic or Bloch #1221

Merged
merged 1 commit into from
Oct 30, 2023

Conversation

shashwat-sh
Copy link
Contributor

No description provided.

@shashwat-sh shashwat-sh self-assigned this Oct 30, 2023
@shashwat-sh shashwat-sh force-pushed the shash/zero_dim_pml_error branch 2 times, most recently from e4f9518 to 5be7616 Compare October 30, 2023 16:52
@momchil-flex momchil-flex added the rc3 3rd pre-release label Oct 30, 2023
Copy link
Collaborator

@momchil-flex momchil-flex left a comment

Choose a reason for hiding this comment

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

Looks good, just a typo in the changelog. You can merge after fixing.

CHANGELOG.md Outdated
@@ -18,6 +18,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- Update versions of `boto3`, `requests`, and `click`.
- python 3.7 no longer tested nor supported.
- Remove warning that monitors now have `colocate=True` by default.
- If `PML` or any absorbing boundary condition is used along a direction where the `Simulation` size is zero, and error will be raised, rather than just a warning.
Copy link
Collaborator

Choose a reason for hiding this comment

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

"an error"

@momchil-flex momchil-flex merged commit 1e5d85e into pre/2.5 Oct 30, 2023
0 of 12 checks passed
@momchil-flex momchil-flex deleted the shash/zero_dim_pml_error branch October 30, 2023 18:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
rc3 3rd pre-release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants