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

multipatch boundary id magic number #416

Open
j042 opened this issue Apr 17, 2024 · 2 comments
Open

multipatch boundary id magic number #416

j042 opened this issue Apr 17, 2024 · 2 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@j042
Copy link
Member

j042 commented Apr 17, 2024

BID=1 doesn't seem to have any effect, when you try to call
mp.boundary_multipatch(1). is it because of default value -1?

@jzwar
Copy link
Collaborator

jzwar commented Apr 17, 2024

Yes. BID starts at 1. Hence, 1 is default. Should you have more than one boundary, it should only return the first one, though.

@j042
Copy link
Member Author

j042 commented Apr 17, 2024

Ok, I guess it is helpful. Maybe we should add a note. I tried to set a certain boundary to BID=1, and I kept getting all the the boundaries. I will add this to upcoming clean up

@j042 j042 self-assigned this Apr 17, 2024
@j042 j042 added the documentation Improvements or additions to documentation label Jun 26, 2024
@j042 j042 unassigned jzwar Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants