GSoC 2025 Bonding period Week -1 Report: King Ordering Algorithm and Minimum Degree Ordering Algorithm

Initiatives Google Summer of Code
1

Week -1 Report (May 19 – May 25)

Reporting Week: May 19 – May 25
Status: :white_check_mark: On track

:white_check_mark: What I got done this week:

  • Finished up cleaning up the Wiki template and started filling in the relevant fields.
  • Finished filling up the OSGeos wiki for OSGeo-GSoC 2025.
  • Attended introductory meeting on May 19
  • Set up local dev environment

:date: Plan for Week 0 (May 26 – June 1):

  • Finish up and streamline the wiki and weekly reports.
  • Go through and study BGL documentation for king ordering algorithm and minimum degree ordering algorithm.
  • Go through pgRouting docs.
  • Start planning how to implement pgr_kingOrdering() & pgr_minimumDegreeOrdering and the work for the coding period starting from next week.
  • Create my own branch
  • Plan out how to structure my weeks and daily routine to meet the Mid-Term Evaluation deliverables`

:construction: Am I blocked on anything?

No

Thank you!

2

Hi @wifi
Thanks for the report.
It is nice you start to get to the habit of the weekly report.
Took the liberty of adding “Bonding period” on the title so it doesn’t confuse other participants.
In another separate matter, You are registered with 2 accounts.
@wifi and @wifi, will merge your accounts during our weekly meeting
Regards

3

Hi @wifi
Was reviewing in detail your report.

For the coding reports please don’t forget to add the link to the wiki page’s appropriate sections.

Original plan: link to wiki that contains the plan you had on your proposal
Revised plan: link to the plan that came to be because of real advance and edit it after our weekly meeting
Work done: link to the expanded work done
Plan for next week: link to what you think you will be doing during next week

notes:

  • The plan for next week will become the Revised plan on the next report.

Kinda those boxes that you have here also have them in the wiki.

Liked your weekly report style. :slight_smile:

Regards

4

Hi Vicky,

Thanks for the heads-up, and no worries about the title — adding “Bonding period” makes total sense! :blush:

Glad to be getting into the habit of writing weekly reports.

Also noted on the duplicate accounts — happy to get that sorted during the weekly meeting.

Cheers,

Wifi

5

Hi @cvvergara ,

Thanks a lot for the detailed feedback! That makes things much clearer.

I’ll make sure to add the proper wiki links for each section in future reports, and keep the wiki updated alongside the report — boxes and all :blush:

Really appreciate the kind words about the report style. I’m still figuring things out, so your guidance helps a lot!

Cheers,

Wifi

6

Hi @cvvergara, would it be better to post your diagram in a new topic for Bipasha and Saloni?

7

Hi @wifi

Dont ask for opinions just act on your best judgment, then we can “evaluate” that judgment.

And for your future judgments:
In this category the rest of the GSoC students/mentors don’t care about the pgRouting code structure.
On pgRouting-dev there are people interested on the code structure because they are interested on contributing or building or packaging pgRouting.
On pgRouting-user the users don’t care about how the code is organized, but they care on how to use it.

Think on:
Is it a continuation of a topic?
Should a new topic be open?
where?

Regards.

8

Hi @cvvergara ,

Thanks for the clarification.

I’ll open a new topic under pgRouting-dev for this.

Best regards