<ohsix>
i tried to do this to put a cap on a motor mount thing, but i ended up just changing the radius of part of it so it wouldn't break, what's the proper way to get around this and have the faces be coincident
<ohsix>
haha the draw image stuff rules. i haven't had to model anything like that yet but it is excellent
d42 has quit [Excess Flood]
d42 has joined #solvespace
vegii has quit [Read error: Connection reset by peer]
<whitequark>
ohsix: either change the radius or force to mesh
Guest67561 has quit [Ping timeout: 240 seconds]
lineprinter has joined #solvespace
lineprinter is now known as Guest60736
sankey has joined #solvespace
<sankey>
with solvespace is it possible to programatically set constraints from, e.g., a CSV file?
<sankey>
in FreeCAD, i create a spreadsheet and use a python script to populate the spreadsheet, then all the constraints reference the spreadsheet cells
<sankey>
I'm only using CAD as an intermediate step in my automation workflow to solve constraints and produce reference values for consumption by the next step, so i'd need it to be completely hands-off
<whitequark>
sankey: not at the moment with the solvespace GUI
<whitequark>
however!
<whitequark>
solvespace has an associated library, libslvs
<whitequark>
it provides a subset of solvespace's functionality, e.g. you cannot generate solids with it
<whitequark>
bu if you only need to solve constraints, libslvs sounds like a perfect fit for you
<whitequark>
someone wrote python bindings for libslvs, too
<sankey>
whitequark: thanks for the quick response! i'll take a look
<sankey>
does libslvs have functions to read .slvs files created from the GUI?
<whitequark>
sankey: no
<whitequark>
libslvs does not implement the full solvespace geometric core
<whitequark>
it corresponds to a single group in the UI
<ohsix>
whitequark: that's what i've done, is that not a bad thing to do? noted
<ohsix>
what makes the coincident faces break?
<whitequark>
ohsix: I don't know
<whitequark>
it's something in the NURBS code
<ohsix>
sankey: that workflow might work with something like openscad
<ohsix>
whitequark: so it's not some math thing that i should know? :p
<whitequark>
ohsix: maybe it is
<whitequark>
I don't have nearly enough insight into the NURBS code to know *what* it is
<ohsix>
ic
<whitequark>
I just know that it fails
<ohsix>
i didn't suspect it was the underlying thing, it makes sense now, i don't think nurbs can deal with that kind of discontinuity
<ohsix>
at least i can follow up, it's been a while since i've read about them
<whitequark>
sure, go ahead, all help in that regard is welcome
<whitequark>
the problem is not nurbs itself but boolean operations on trimmed nurbs surfaces
<ohsix>
i love the random stuff i find googling that kind of stuff, http://mfem.org/examples/ hadn't heard of this before
<whitequark>
huh
<ohsix>
it's weird how google doesn't find stuff now, when i'm looking for meshing libraries and stuff, i find a lot; but not that one, for example
<ohsix>
but when i'm looking for singularity/stitching/edge handling + nurbs, stuff like that pops up
<whitequark>
well, do you understand why the boolean op fails?
<ohsix>
sort of, i plan on finding out
<ohsix>
there's two edges meeting and that's no bueno
<ohsix>
i have a copy of foley & van damm, and that would be about as much as i've read about it, i remember using 3ds4 a million years ago, all the stuff you had to do to use nurbs surfaces