This code does what I expected: It displays the region of intersection between two disks:
Region[
RegionIntersection[
Disk[{0, 0}, 1],
Disk[{3/2, 1/4}, 3/4]
]
]
I expected this to do the same, but it does not:
R1 = Region[Disk[{0, 0}, 1]];
R2 = Region[Disk[{3/2, 1/4}, 3/4]];
Region[
RegionIntersection[R1, R2]
]
It runs for a long time, and I've not had the patience to see if it ever displays the lune intersection.
Can anyone explain the difference?
Update. @HenrikSchumacher's comments showed that the problem is that there
was a Region
bug in version 11.1.1, which I was using, a bug fixed by version 11.3.
Region
is meant to represent exact regions while the visual return of aRegion
is a coarse discritization solely meant for a quick preview. $\endgroup$MeshRegion
or aBoundaryMeshRegion
with customized resolution byDiscretizeRegion
andBoundaryDiscretizeRegion
. For example, the latter two have the optionMaxCellMeasure
that allows you to adjust how fine the discretization should be done. In total, allRegion
-related functionalities are rather new and a bit buggy; this is true in particular forBooleanRegion
which is used under the hood (as you can see by inspectingFullForm[RegionIntersection[R1, R2]]
). $\endgroup$