| 01:33.26 | *** join/#brlcad LordOfBikes (~armin@ipservice-092-211-154-075.092.211.pools.vodafone-ip.de) |
| 03:23.16 | *** join/#brlcad Moult (~sevenstro@unaffiliated/moult) |
| 03:25.05 | Moult | brlcad: ping :) thought i'd catch you on irc |
| 07:21.50 | *** join/#brlcad TheJollyRoger (~Jolly_Rog@gateway/tor-sasl/thejollyroger) |
| 08:37.48 | brlcad | hello Moult, pong |
| 08:58.27 | teepee | hey brlcad :) |
| 08:59.22 | teepee | did you see the discussion on github? |
| 09:07.14 | Moult | brlcad teepee g'day :) just thought i'd ping about https://github.com/opencax/opencax.github.io/issues/2 |
| 09:27.08 | teepee | hi Moult |
| 09:27.16 | Moult | teepee: g'day :) |
| 09:28.13 | teepee | joining the fun at interesting times with the big changes in GSoC rules :) |
| 09:28.21 | Moult | teepee: what are the big changes? |
| 09:28.40 | Moult | teepee: i've never been involved in a past gsoc so i don't have a point of comparison :) |
| 09:32.14 | teepee | much short project time (pretty much half) and I guess it's a bit unclear what that will mean for |
| 09:32.25 | teepee | the whole thing |
| 09:32.36 | teepee | like if there will be more projects accepted and such |
| 09:33.17 | Moult | teepee:how long do the students have to do their work? |
| 09:33.26 | Moult | teepee: from memory it was 3 months? |
| 09:37.18 | teepee | yep |
| 09:37.39 | teepee | blog post... https://opensource.googleblog.com/2020/10/google-summer-of-code-2021-is-bringing.html |
| 09:39.56 | Moult | teepee: thanks for the link :) 10 weeks is indeed quite short |
| 09:42.26 | teepee | yeah, I'm still a bit unclear if it will make sense for us (OpenSCAD) it certainly means pretty much all of the existing project proposals dont work anymore |
| 09:44.29 | teepee | but as brlcad said in an earlier discussion it also has a couple of chances for interesting new ways how it could go |
| 09:45.28 | teepee | thing is that we are not a huge team, and I guess independent of the shorter project length, it's still requires the same amount of mentors |
| 09:58.40 | Moult | teepee: most foss cad seems to be small teams :( |
| 18:28.41 | brlcad | teepee: yes, I just responded -- it's been on my radar since it was posted, intending to reply but I was on vacation when it came in |
| 18:30.54 | brlcad | appreciate you, yorik, and others keeping the discussion going |
| 18:31.08 | teepee | oh my, I guess we should let you get back to Thanksgiving :) |
| 18:31.59 | brlcad | no worries, asynchronouse discussions ;) |
| 18:32.24 | TheJollyRoger | Hi guys! |
| 18:33.18 | teepee | hi! |
| 18:34.00 | TheJollyRoger | Hey! I'm a long time watcher, but haven't really taken part in discussions here much. I'm coming into this with no experience in MGED but a lot of experience at PTC Creo, Inventor and Siemens PLM NX. |
| 18:34.21 | brlcad | Moult: my biggest unspoken concern is ifcopenshell vs blenderbim vs openbim -- in terms of maturity, ifcopenshell is a no-brainer. if it weren't for opencascade, I'd have already pushed to integrate it into BRL-CAD, but having to manage handing geometry between multiple major geometry engines isn't something terribly appealing just yet :) |
| 18:34.22 | TheJollyRoger | Really eager to get started and try out BRL CAD sometime, been scouring the manuals for MGED and hoping I'll be able to wrap my head around this all. |
| 18:34.54 | brlcad | hello TheJollyRoger ! that's not surprising because we've not used IRC as our primary channel in years. |
| 18:35.52 | brlcad | I'm hoping to bridge everything back when we migrate from Zulip to Matrix (Gitter/Element), which bridges better with IRC than Zulip. |
| 18:36.14 | brlcad | TheJollyRoger: feel free to join us on https://brlcad.zulipchat.com too, that's where most of the guys are watching. |
| 18:37.21 | brlcad | teepee: I hope it makes sense for you guys! at least one slot... ;) |
| 18:37.24 | teepee | oh, matrix, yay! |
| 18:37.47 | TheJollyRoger | Ah, heh, I used to be big on Matrix, some time ago, but eventually migrated back to IRC. |
| 18:37.50 | teepee | yeah, at this point, I don't see 2 slots happening anyway |
| 18:38.19 | brlcad | I've been using Element since early summer now and have been liking it. |
| 18:38.39 | TheJollyRoger | Hey right on. I hope you'll keep IRC around, since I find that's probably the best for me. |
| 18:38.51 | TheJollyRoger | Strange as it's going to sound. |
| 18:38.55 | brlcad | Element purchased Gitter recently and said they're moving them to Matrix |
| 18:39.00 | TheJollyRoger | Hey right on. |
| 18:39.29 | brlcad | I love IRC, it's my preferred |
| 18:40.14 | TheJollyRoger | So do I! |
| 18:40.16 | yukonbob | hello #brlcad -- like a buzzing beehive in here ;) |
| 18:40.26 | TheJollyRoger | Yeah man! |
| 18:40.43 | brlcad | one of the things we learned from years of gci and gsoc, though, is that it is a big barrier for new contributors and harder to ensure project successes since it requires more synchronous attention |
| 18:40.52 | TheJollyRoger | When I read about BRL CAD I knew I just had to try it and possibly try compiling it on POWER9. |
| 18:40.54 | brlcad | howdy yukonbob .. yeah! |
| 18:41.10 | brlcad | TheJollyRoger: I compile it on power series regularly ;) |
| 18:41.14 | yukonbob | brlcad: o/ |
| 18:41.17 | TheJollyRoger | ...! |
| 18:41.18 | TheJollyRoger | AWESOME! |
| 18:41.31 | TheJollyRoger | Excellent aw man you are my hero! |
| 18:42.00 | yukonbob | technical q that's been on mind for a bit, and now that some nerds are here (haha) -- does BRLCAD have any notions of Wayland ? |
| 18:42.59 | TheJollyRoger | I currently am looking to make the jump from Siemens PLM NX and PTC Creo to BRL CAD, I'm kind of nervous about it and having to relearn everything from scratch, but that's part of the fun. |
| 18:43.15 | brlcad | yukonbob: in what sense? it does in the sense that it'll display on wayland because our windowing does, but nothing direct. if anything, our long-term direction is Qt so 'yes' from that indirect perspective. |
| 18:43.24 | TheJollyRoger | Wow. |
| 18:43.58 | yukonbob | brlcad: ah ok -- so the windowing does integrate w/ some wayland compositor -- that's all I wanted to know... |
| 18:45.04 | brlcad | TheJollyRoger: BRL-CAD is one of the oldest "portable" software systems predating things like TCP, ANSI C, and OpenGL ;) Our portability has degraded in recent years as we've embraced more and more modern libraries and standards, but I still have the perspective that it should compile and run if you can get the code on it. :) |
| 18:45.14 | yukonbob | currently working on Wayland/NetBSD, which is a WIP, but slowly heading in Wayland direction.... |
| 18:46.43 | yukonbob | re: QT -- does this speak to anything that's going on w/ Tcl in BRLCAD? |
| 18:47.06 | yukonbob | doesn't recall now if previous display was Tk or some other form of X11 on *nix.... |
| 18:47.08 | TheJollyRoger | brlcad: woohoo! |
| 18:47.31 | TheJollyRoger | I've got a lot of CPU cores and a lot of RAM, so I'd like to try sometime when I figure it out. |
| 18:47.53 | brlcad | yukonbob: I believe it'll happen via XWayland currently (for Xlib apps like our direct code). Tk I don't think has added Wayland as a backend yet. I believe Qt has direct support. |
| 18:48.38 | brlcad | yukonbob: current display tech is a mix of direct Xlib calls and Tk |
| 18:48.47 | yukonbob | ^- ah... perfect. |
| 18:48.49 | brlcad | opengl is optional |
| 18:49.39 | brlcad | TheJollyRoger: if you have a lot of cores, be sure to compile from source optimized (release mode), run the BRL-CAD Benchmark, and submit your performance results |
| 18:50.02 | TheJollyRoger | I will! I'll have to figure out what to do. I'm pretty new to this honestly. |
| 18:50.49 | yukonbob | brlcad: iirc Tk *does* have a pretty good path to Wayland, but I haven't pinned down details - I'm currently porting/stablizing Wayland to my NetBSD env, then working on some app integration... |
| 18:51.08 | yukonbob | Tk will one of the things I'll be looking at (surprise). |
| 18:56.21 | TheJollyRoger | brlcad, currently I've got a Talos, it's a pretty powerful machine with two CPUs and an AMD Vega Graphics card. I'm hoping that it might be a good match! |
| 18:57.04 | TheJollyRoger | Occasionally the amdgpu does misbehave so I have to fiddle with or change the kernel. |
| 18:58.07 | TheJollyRoger | *amdgpu driver |
| 19:53.00 | brlcad | TheJollyRoger: no worries, feel free to ask lots of questions. happy to answer and help you figure things out, find an exciting project |
| 19:53.08 | TheJollyRoger | Thanks! |
| 19:53.22 | TheJollyRoger | I might be a bit slow to get there, since I've been pretty swamped, but I'm really glad for this channel! |
| 21:44.54 | Moult | brlcad: g'day |
| 21:45.59 | Moult | brlcad: the ifcopenshell repo has contained code for blender since 2011, but the main dev didn't have time to maintain it, so i've been hacking on it since 2019 |
| 21:46.43 | Moult | brlcad: and since then it was rebranded by the users who called it "blenderbim". but the codebase is still part of ifcopenshell |
| 21:47.04 | Moult | brlcad: hope that clarifies it? |
| 21:48.03 | Moult | brlcad: also to clarify "OpenBIM" is not a project. it's all just really one project "IfcOpenShell". openbim is the umbrella of standards that ifcopenshell supports, and the blenderbim is the commonly used name for one of the components of ifcopenshell; |
| 21:49.53 | Moult | brlcad: in terms of mentors, aothms and I are the main devs. we have some other more casual contributors, but most likely it'll be aothms and I being the only mentors |