-
-
Notifications
You must be signed in to change notification settings - Fork 376
GSoC 2025 King Ordering Algorithm and Minimum Degree Ordering Algorithm
- Proposal
- Participants
-
Timeline
-
Community Bonding Period
- [Week -1 & Week 0](#Week -1 & Week 0)
- First Coding Period
- Second Coding Period
- Third Coding Period
-
Community Bonding Period
- Log of Pull Requests
- Slides
- Final Report
-
Weekly Reports
- Third Evaluation Period
- Second Evaluation Period
- First Evaluation Period
-
Community Bonding Period
- [Week -1 & Week 0](#Week -1 & Week 0)
- Meeting Discussions
- Tasks
- Pre-Bonding Period
- References
This project aims to implement the King Ordering Algorithm and Minimum Degree Ordering Algorithm from the Boost Graph Library into pgRouting, expanding its graph reordering capabilities beyond the existing Cuthill-McKee ordering. These algorithms optimize graph structures for improved numerical solver performance in scientific computing and network analysis. The King Ordering Algorithm minimizes graph bandwidth by reordering vertex indices based on pseudo-degree, reducing adjacency gaps and enhancing sparse matrix computations. The Minimum Degree Ordering Algorithm reduces fill-in during Cholesky factorization by reordering matrix rows to minimize nonzero elements introduced during Gaussian elimination. By integrating these algorithms, pgRouting will offer more efficient preprocessing options, benefiting large-scale network analysis and pathfinding tasks. Deliverables include the implementation of pgr_kingOrdering() and pgr_minimumDegreeOrdering(), comprehensive documentation, test cases ensuring correctness, and regular progress updates.
Before this project, pgRouting did not support the King Ordering or Minimum Degree Ordering algorithms. The only implemented graph reordering algorithm available was the Cuthill-McKee ordering. Adding these new algorithms will expand pgRouting's capabilities for graph preprocessing and optimization.
- Implementation of pgr_kingOrdering() and pgr_minimumDegreeOrdering() functions.
- Code with detailed and essential comments following the style guide and best practices.
- User documentation for both functions.
- Basic pgTap test cases to ensure correctness and stability.
- A wiki page detailing weekly progress.
- Detailed reports for the first and final evaluations.
Detailed Proposal Link (Google Doc)
Title | GitHub Handle | Name |
---|---|---|
1st Mentor | @cvvergara | Vicky Vergara |
2nd Mentor | @robe2 | Regina Obe |
3rd Mentor | @iosefa | Iosefa Percival |
4th Mentor | @sanak | Ko Nagase |
Student Developer | @wifi | Fan Wu |
- Introduce myself to the pgRouting mentors and the broader community to begin building connections.
- Set up and configure the development environment required for contributing to pgRouting.
- Explore and understand the pgRouting codebase, development workflow, and best practices.
- Study pgTap and the Boost Graph Library to prepare for effective development and testing.
- Create and regularly update a personal wiki page to document weekly project progress.
- Actively participate in community meetings, discussions, and forums to stay engaged and informed.
- Deepen my understanding of PostgreSQL and PostGIS to support development and integration tasks.
- Reach out to pgRouting mentors and community members to introduce myself and begin building rapport.
- Install and configure all necessary tools to establish a functional development environment for pgRouting.
- Create a wiki page to document and track the weekly progress of my project.
TBD
TBD
TBD
TBD
TBD
TBD
TBD
TBD
TBD
TBD
TBD
TBD
Link to all the Pull Requests made in GSoC-pgRouting repository
Pull Request | Description | Date | Status |
---|---|---|---|
# 1604 | TBD | TBD | TBD |
TBD
TBD
- Links:
(i) Code Documentation:
TBD
(ii) Tags:
TBD
(iii) Pull Requests:
TBD
(iv) Wiki Pages:
TBD
- Images:
TBD
- Media:
TBD
-
Report Mail - TBD
-
What did I get done this week?
TBD
- What do I plan on doing next week? TBD
TBD
-
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.
-
What I Plan on doing next week?
- 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 (from develop/upstream)
- Plan out how to structure my weeks and daily routine to meet the Mid-Term Evaluation deliverables
-
Am I Blocked on anything?
No