Timeline for Intersection of boundaries/surfaces of two cylinders
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| 21 hours ago | history | became hot network question | |||
| 22 hours ago | answer | added | azerbajdzan | timeline score: 3 | |
| yesterday | comment | added | A. Kato | @cvgmt I see, sometimes it works out well. And (+1) for your nice answer. | |
| yesterday | comment | added | cvgmt |
@A.Kato Only for the simple two dimension surfaces , the RegionIntersection work. Region[RegionIntersection[RegionBoundary@Ball[{0, 0, 0}, 1], RegionBoundary@Ball[{1, 0, 0}, 1]], PlotRange -> 1]
|
|
| yesterday | answer | added | lericr | timeline score: 3 | |
| 2 days ago | answer | added | cvgmt | timeline score: 5 | |
| 2 days ago | history | edited | azerbajdzan | CC BY-SA 4.0 |
edited title
|
| 2 days ago | comment | added | A. Kato |
I don't know why it just returns BooleanRegion. This is just my guess, but it seems like Region-related functions are primarily designed for "numerical" image processing. Maybe someone will come up with a nice solution (which I also want to get), but it might be quicker to "reinvent the wheel".
|
|
| 2 days ago | comment | added | azerbajdzan |
@A.Kato What is the point of Mathematica pretending "I can handle this"? So the output of RegionIntersection should be warning/error not BooleanRegion like everything is fine. Or is there any reasonable/practical usage of such output?
|
|
| 2 days ago | comment | added | A. Kato | Since the surfaces of cylinders are two-dimensional objects, their intersection is a one-dimensional curve. I don't think Mathematica can properly handle codimension two curves in a three-dimensional space as a "region." | |
| 2 days ago | history | edited | azerbajdzan | CC BY-SA 4.0 |
added 130 characters in body
|
| 2 days ago | history | asked | azerbajdzan | CC BY-SA 4.0 |