Stream: Google Summer of Code

Topic: Geometry Verification and Validation GUI in Qt

Divyanshu Garg (May 01 2026 at 08:20):

Hey @Kanchan Borole This is the channel we will use to track your GSoC progress and discussions

Divyanshu Garg (May 01 2026 at 08:20):

On that note, Welcome to the chat!

Kanchan Borole (May 01 2026 at 08:42):

Thank you @Divyanshu Garg. Looking forward to getting started!

Divyanshu Garg (May 01 2026 at 09:17):

Awesome, since we are in the community bonding period, we can take it as an opportunity to get more familiar with what we are working with.
Here are our goals for the next 20 days:-

1. Project setup (Dev environment).
2. Going through the repository, documentation, and other resources.
3. Scope building - This is as important as writing down the actual code; remember, managing the project plays a huge role in the project's success and completion.

• What we need is a well-defined and organized board that lists out the tasks/features we are going to be working on. This will let us know that we are on track. You can use GitHub issues/projects for that (In case you want to use any other tool, feel free to do that)
• Every task and feature will consist of a description/explanation of what exactly it covers.
• You send PRs out based on those issues and tasks.
• This clears out the expectations and keeps clarity on what exactly we are working on and what's done.
• The point is, good documentation is really important, so we have to maintain it that way.

Once this is all done, we will potentially be ready for the coding period.

Divyanshu Garg (May 01 2026 at 09:33):

Another important aspect of contribution would be communication,

• Be clear about the availability; it doesn't have to be like a 24/7 task, but as a simple example, if you are gonna be away for a day, week, or any period of time due to exams, travel, or any other potential reason, inform them beforehand.
• This creates a sense of clarity and trust, since in opposite scenarios, it creates problems for the ORG to calculate the progress and continuation of the project. Example - Disappearing for 15 days without notice might give mentors the impression that the contributor abandoned the GSoC program mid-way. It might sound absurd, but trust me, we have seen this happening a lot in recent years. (In terms of recent generation its called ghosting)
• Never hesitate to ask questions, remember GSoC efforts are focused on a few agendas, one being to help new contributors learn.
• Sharing Updates - can play a very good role in keeping the conversation active and letting the ORG and mentors know what's happening around the project.
• You can choose to put casual updates regularly or choose an SOD or EOD plan to give yourself daily goals and see if you were able to achieve those goals.

Divyanshu Garg (May 01 2026 at 09:37):

With that, I am Divyanshu, and we will be working together for the next few months to deal with the problem statements proposed. Excited about the good things we are gonna be achieving by the end of it.

Kanchan Borole (May 01 2026 at 10:16):

Thank you for the detailed overview! I will keep all of this in mind. I will start with setting up the development environment and going through the repository and documentation over the next few days. I will keep you updated on my progress regularly.

Kanchan Borole (May 02 2026 at 05:17):

Hi @Divyanshu Garg , I wanted to clarify my understanding before I proceed further.
My goal is to take the V&V features from the old isaacy13/arbalest fork (https://github.com/isaacy13/arbalest) and bring them into the latest official BRL-CAD/arbalest codebase. The old fork has the V&V functionality but uses Qt5. The latest arbalest uses Qt6 so my plan is to work on the latest BRL-CAD/arbalest and port the V&V features there using Qt6.
To set this up I need help with two things:

1. Should I install Qt6? If yes which version exactly?
2. How do I set up BRLCAD_MOOSE correctly on Windows?

Divyanshu Garg (May 02 2026 at 07:25):

Hey @Kanchan Borole

1. [removed by author]

Divyanshu Garg (May 02 2026 at 07:31):

Wait a second, my bad, i misread it, If the latest is in QT6 ofcourse we do that one, Based on the last update i see it mentions Qt6.4.2

Divyanshu Garg (May 02 2026 at 07:32):

https://github.com/BRL-CAD/arbalest/blob/main/README.md
This file mentions that

Divyanshu Garg (May 02 2026 at 07:36):

Have you already setup BRL-CAD core on your system?

Kanchan Borole (May 02 2026 at 07:39):

I have Installed BRL-CAD(7.32.2) not build it from source.

Divyanshu Garg (May 02 2026 at 07:51):

Setting up BRLCAD MOOSE shouldn't be different since it follows standard/similar procedures we have in textbook C++ projects. One of the easiest ways to do that is to search and learn how we usually run similar apps on windows and it should be following the same procedure.

But, also noticed that you mentioned BRLCAD_MOOSE not BRLCAD/MOOSE a variable which is mentioned in the arbalest repository cmakelist. In that particular query
it should work with something like this cmake .. -DBRLCAD_MOOSE_DIR=C:\moose-install, basically resolving the directory as required.

Last updated: May 03 2026 at 01:53 UTC