Himanshu (Jan 29 2023 at 14:44): Himanshu (Jan 29 2023 at 14:44):Are we participating this year too? All seems busy here?
Himanshu (Jan 29 2023 at 14:44):(deleted)
Himanshu (Jan 29 2023 at 14:44):(deleted)
Himanshu (Jan 29 2023 at 14:44):(deleted)
Sean (Feb 07 2023 at 20:09):I’ve been crazy busy since the new year for me which is why I’ve been away of late but finally getting caught up.
Sean (Feb 07 2023 at 20:10):I did apply for BRL-CAD in anticipation. We need unto update our project ideas list, check on mentor interests, and touch base with the other orgs to see whom all is participating.
Himanshu (Feb 23 2023 at 04:54):@Sean Just updated the year in the issues list. https://github.com/opencax/opencax.github.io/pull/5
Sean (Feb 23 2023 at 06:33):That's great, thank you @Himanshu Sekhar Nayak ! There's a bit more work to do as FreeCAD is not participating under our umbrella this year, so some updates will need to be made to pull a couple of their org sponsorships.
Sean (Feb 23 2023 at 06:36):We also need to update our ideas list, identify interested mentors, close out the completed project ideas, and consolidate on new/continuation priority projects. Love to see more progress on the GUI/API, physically-based rendering, robust export, and performance.
Himanshu (Feb 23 2023 at 16:26):I would love to develop again on GUI and try to add or fix feature. But love to see if any other will continue this project this year.
Daniel Rossberg (Feb 23 2023 at 16:48):@Himanshu Sekhar Nayak, I could imagine you being a mentor this year.
Himanshu (Feb 23 2023 at 17:15):Currently I am learning ray tracing and implemented it too. Ray traced a Cornell box and wow :ok: my interest grows more towards game graphics and how the game developers able to implement that. Today, I rendered a sphere using ray marching through the help of SDF and it looks cool. The more I getting to know these, the more it looks interesting.
Himanshu (Feb 23 2023 at 17:17):Saw 2 projects regarding these. I hope I can contribute these too in future.
Himanshu (Feb 23 2023 at 17:19):Daniel Rossberg said:
Himanshu Sekhar Nayak, I could imagine you being a mentor this year.
Mentor :sweat_smile:. I am no good enough I think. But whatever I learned from this organization, yes I can help someone to start only.
Sean (Feb 23 2023 at 20:03):@Himanshu Sekhar Nayak you’ve participated twice now yes? If so then you’d definitely make a great mentor..
Sean (Feb 23 2023 at 20:03):You could also do great things on a graphics project, especially if you’re getting into ray tracing
Himanshu (Feb 24 2023 at 01:57):Sean said:
Himanshu Sekhar Nayak you’ve participated twice now yes? If so then you’d definitely make a great mentor..
Twice yes, one gci and second one gsoc.
Daniel Rossberg (Feb 24 2023 at 08:38):Himanshu Sekhar Nayak said:
Daniel Rossberg said:
Himanshu Sekhar Nayak, I could imagine you being a mentor this year.
Mentor :sweat_smile:. I am no good enough I think. But whatever I learned from this organization, yes I can help someone to start only.
You are member of our community since many years and have seen many parts of the BRL-CAD suite during this time. Not only that you can guide newbies during their first steps, you followed the developer discussions too and got an idea in which directions the development shall go.
In addition, you will obtain new skills when mentoring. This is not a one-way street. Looking at and understanding other peoples patches will broaden your horizon as well.
And last but not least: You won't mentor alone but together with an experienced developer. We aim for two mentors per project in general.
Himanshu (Feb 24 2023 at 10:40):Okay, I am in. :sunglasses:
GregoryLi (Mar 08 2023 at 07:39):Hi, I noticed we have NURBS editing topic this year, I'm interested in it! I've been working on splines for a few months now, including NURBS intersection, Spline knot subdivision and insert, bounding box, symbolic computation & numerical computation. My doctoral topics in the next few years will also be related research directions. I'm using SISL NURBS lib. I have a lot of experience with NURBS algorithm implementation, but I'm not so familar with GUI development which is also important. Is it possible to join twice? I would love to attend with or without GSOC :grinning: because I'm interested in concrete industrial implementations of NURBS. I would like to know about and implement newer algorithms in industry softwares.
starseeker (Mar 08 2023 at 18:28):@GregoryLi Unfortunately, SISL NURBS isn't license compatible with BRL-CAD :-( My suggestion, if you feel comfortable working with it, would be to keep digging into our boolean evaluation logic for NURBS. That capability, if we can make it production ready, is a potential game changer for our export capabilities and a number of other very interesting features.
Another effort in a similar vein is continuing to improve our polygonalization codes for NURBS - we use a variation on the poly2tri code in combination with a variety of custom logic, but our watertight meshing capabilities need work both for speed and robustness (See https://apps.dtic.mil/sti/pdfs/AD1094344.pdf)
You'd have to talk to one of the others about what's allowed/not allowed for GSOC - I'm not acting as a mentor this go-around...
Daniel Rossberg (Mar 08 2023 at 18:40):This years GSoC rules allow to join twice.
To understand, what the "NURBS Editing Support in BRL-CAD" project idea means, you should go through the mged tutorial. Then, the task would be to create and modify NURBS objects the same way :wink:
Daniel Rossberg (Mar 08 2023 at 18:44):BRL-CAD uses the openNURBS library.
GregoryLi (Mar 09 2023 at 01:17):starseeker @Daniel Rossberg
Thanks! I will use openNURBS within BRL-CAD. I will check what has ben implemented in BRL-CAD & openNURBS and what is needed for NURBS.
I think the "NURBS Editing Support in BRL-CAD" project needs mged development much more than NURBS algorithm implement(because openNURBS has done this). Am I right?
Daniel Rossberg (Mar 09 2023 at 18:05):The right answer is probably yes, even if you don't have to touch the mged code yet. This is because it is only one of many programs build on top of the core libraries. These are the ones you have to work extend. Maybe libbrep and libged? Ideally, you don't have to change the openNURBS library.
The first step would be to get access to the data structures. The openNURBS library has probably an API for this, but it isn't used on the BRL-CAD side yet. Then, a kind of ASCII serialization would be nice. Having this, you could implement a function in libged, which creates a NURBS from such a string. And so on...
Sean (Mar 10 2023 at 20:41):Agreed, you definitely will have to use openNURBS and would likely end up adding command-line editing capabilities in libged and/or librt first, then if there's time you'd be figuring out how to expose editing through a GUI. Solid polygonal export of NURBS is definitely also needed. There is/was code that supposedly guarantees they're solid, but it's not been tested, is slower, and I believe is presently #ifdef'd out so it's not even compiled.
GregoryLi (Mar 14 2023 at 07:57):I checked NURBS Editing Support and NURBS curve editing operations in openNURBS and bound NURBS curve operations and openNURBS functions. I found some operations needs to be implemented in BRL-CAD, too.
image.png
I don't fully understand the specific meaning of some operations so I marked "?", we can discuss these specific issues after discussing the whole process :)
GregoryLi (Mar 14 2023 at 08:02):Here is a brief work sequence for NURBS editing project. Is my understanding of this project too broad, too narrow or biased?
GregoryLi (Mar 14 2023 at 08:07):I see there are a lot of interesting work to do in BRL-CAD, which is familiar and interesting to me...
Daniel Rossberg (Mar 14 2023 at 12:02):Number 4. could be a problem, because openNURBS is another project, and maintaining a fork is challenging. Hopefully, it isn't necessary.
Daniel Rossberg (Mar 14 2023 at 14:38):Hi @Mohamed Adel, Welcome to our community. To start, you may look at
GregoryLi (Mar 15 2023 at 01:57):Daniel Rossberg said:
Number 4. could be a problem, because openNURBS is another project, and maintaining a fork is challenging. Hopefully, it isn't necessary.
Yeah, maybe we can implement those functions in libbrep/libged?
For example, NURBS curve Attach operation doesn't exists in openNURBS, we can implement it in libged based on openNURBS.
GregoryLi (Mar 15 2023 at 01:58):Just as " or identifying that the equivalent routine doesn't exist in openNURBS and will need to be implemented" here NURBS Editing Support
Sean (Mar 15 2023 at 06:54):@GregoryLi functions that opennurbs has in headers but doesn't have the implementation for are typically implemented in libbrep. Note that those are typically functions that are harder to implement too. The opennurbs folks remove the hard bits that don't have anything to do with the 3dm file format in order to encourage people to buy their rhinosdk licensing which costs, is not open source.
There's actually a project starseeker started some 10+ years ago to address that very issue that is worth studying (called libnurbs). Looks like someone pulled it over to github: https://github.com/yiskang/libnurbs
Other references worth checking out: https://www.google.com/search?q=nurbs+editing+site%3Agithub.com&ie=UTF-8&oe=UTF-8#ip=1
Neeraj Sharma (Mar 15 2023 at 08:49):Hii , myself Neeraj Sharma I build the BRLCAD. now I want to go further .
Himanshu (Mar 15 2023 at 10:02):Follow rest? #Google Summer of Code > general @Neeraj Sharma
starseeker (Mar 15 2023 at 15:42):@GregoryLi the libnurbs "project" never came to anything much, mostly due to lack of time... when it comes to the notion of "forking" openNURBS, I agree in principle that it's usually undesirable to do that due to the amount of work involved. We've not been compelled to thus far. That said, my sense is that the core parts of openNURBS we need for what we're focused on (opennurbs_brep.h and its friends) haven't changed enormously over the decades.
starseeker (Mar 15 2023 at 15:47):If we were to think about a "libnurbs" style project, I'd probably look at identifying a "minimal functional core" of openNURBS needed for BRep NURBS solids and related data types. My hunch is that the core code there hasn't undergone extensive modification for a long time, and even if it would be challenging to try to keep up with the changes for ALL of openNURBS it might be much more practical to identify the changes for that core. If for a "libnurbs" we stripped out subdivision, I/O, layers, visualization, mesh, etc. and narrowed it just to the ON_Brep related parts, and then checked to see how stable that code has been in the upstream repository, it would give us some idea of how hard that might be.
starseeker (Mar 15 2023 at 15:52):We would still use openNURBS proper for 3dm import and export (which after all is what it's intended for) and build more advanced NURBS BRep capabilities on top of the smaller "libnurbs" core, making minimal modifications to the "original" openNURBS files (for example, replacing stubs with real implementations) and defining all-new functionality (for example, a proper ASCII serialization of the ON_Brep containers to replace our current b64 hack used by asc2g) in our own files. Then with any luck we could merge upstream changes to just the files in question fairly easily, without having to worry about new code they introduce.
starseeker (Mar 15 2023 at 15:54):Although that articulates the idea behind libnurbs, I should point out I'm not actually advocating for that approach - it still has some potentially significant upfront costs even if the stability of the relevant portions of the openNURBS code holds, and it should be possible to do most of the substantive work we need in libbrep.
GregoryLi (Mar 16 2023 at 03:16):Sean said:
GregoryLi functions that opennurbs has in headers but doesn't have the implementation for are typically implemented in libbrep. Note that those are typically functions that are harder to implement too. The opennurbs folks remove the hard bits that don't have anything to do with the 3dm file format in order to encourage people to buy their rhinosdk licensing which costs, is not open source.
There's actually a project starseeker started some 10+ years ago to address that very issue that is worth studying (called libnurbs). Looks like someone pulled it over to github: https://github.com/yiskang/libnurbs
Other references worth checking out: https://www.google.com/search?q=nurbs+editing+site%3Agithub.com&ie=UTF-8&oe=UTF-8#ip=1
@starseeker libnurbs is really great work! starseeker pointed out a feasible method to build a "libnurbs" like project. But as you said, it time consuming with little payoff. So I think focus on NURBS editing support for BRL-CAD is OK. So Achieving other NURBS operations is the icing on the cake...
I will see how to call NURBS editing operation though cmd. This is something I'm not familiar with. :smile:
Sean (Mar 16 2023 at 04:32):@GregoryLi a potential starting point that might help would be to look at the opennurbs examples in src/proc-db which are in C++ and construct basic shapes manually like a cube. imagine having a CLI in mged where you could create the twisted cube example, or take an existing twisted cube and move an existing control point, or adjust a knot, or move an edge , or move a surface, or clamp all the control points precisely to their parametric domain counterparts, etc
Himanshu (May 05 2023 at 15:00):Congratulations @GregoryLi, @Caio José Dos Santos Brito and @Abhiram. We are as excited as you. I as member of BRL-CAD community, welcomes you all and can't wait to start working on projects.
Himanshu (May 05 2023 at 15:06):It is sad that this year, we didn't get more slots than previous year but not to worry @Nishanth, you can still contribute, learn and can gain experience here. I know how it feels to not get pass through even if we are dedicating for something. I hope you will stay and contribute. This will broaden your horizon as well.
Caio José Dos Santos Brito (May 05 2023 at 17:54):Thank you for the opportunity!!! I am very excited and it will be fun for sure! =)
Sean (May 05 2023 at 19:30):Congratulations and thank you to all that applied. Alas, we won't get to all the applicants we wanted to work with, but encourage all to get involved and apply again next year (especially if this was your first time applying). Open source thrives on communication, so being active and involved is one of the best ways to learn, get noticed, and get selected.
Sean (May 05 2023 at 19:31):That said, for @GregoryLi @Caio José Dos Santos Brito and @Abhiram please do check up the checklist for what steps are next: https://opencax.github.io/gsoc_checklist.html
Himanshu (May 07 2023 at 20:37):GSoC 2023 page site is now created and now you will able to maintain your project related information here https://brlcad.org/wiki/Google_Summer_of_Code/2023. You can look into other project info which are selected previously https://brlcad.org/wiki/Google_Summer_of_Code/2022 otherwise there is a template added to 2023 page. Whatever you like pick it.
Abhiram (May 08 2023 at 14:50):Himanshu Sekhar Nayak said:
GSoC 2023 page site is now created and now you will able to maintain your project related information here https://brlcad.org/wiki/Google_Summer_of_Code/2023. You can look into other project info which are selected previously https://brlcad.org/wiki/Google_Summer_of_Code/2022 otherwise there is a template added to 2023 page. Whatever you like pick it.
Okay will do!
Abhiram (May 11 2023 at 17:13):Hi @Sean , can we have a meeting over the weekend or whenever you are free in the coming days so that we can both plan and discuss the updated deliverables (changes to boost etc, which I haven't really emphasized on in the proposal) and any other things you'd like me to do?
Last updated: Nov 15 2024 at 00:49 UTC