-
-
Notifications
You must be signed in to change notification settings - Fork 367
Gsoc 2013 Mukul Priya
cvvergara edited this page Mar 17, 2017
·
27 revisions
- Report 14
- Report 13
- Report 12
- Report 11
- Report 10
- Report 9
- Report 8
- Report 7
- Report 6
- Report 5
- Report 4
- Report 3
- Report 2
- Report 1
- Name: Mukul Priya
- Country: India
- School and degree: International Institute Of Information Technology- Hyderabad, B.Tech(Hons) + Masters
- Email : mukul2047@gmail.com , mukul.priya@students.iiit.ac.in ,mukul.priya@research.iiit.ac.in
OSGeo Wiki notes: http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2013_Ideas#What_to_expect_during_the_summer
- Report 1, 21-06-2013
- Report 2, 28-06-2013
- Report 3, 05-07-2013
- Report 4, 12-07-2013
- Report 5, 19-07-2013
- Report 6, 26-07-2013
- Report 7, 02-08-2013
- Report 8, 09-08-2013
- Report 9, 16-08-2013
- Report 10,23-08-2013
- Report 11,30-08-2013
- Report 12,06-09-2013
- Report 13,13-09-2013
- Report 14,20-09-2013
- Completed integration with pgrouting.The algorithm however will need some more testing before it is available with the pgrouting package. The proposed goals have been met for now but i will always be available in future for its further testing , modification or bug fixing.The codes are available on the git repository I would like to thank my mentors Steve and Daniel for their support and guidance.
- upload code samples on melange.
- Have the documentation ready.
- Started integrating it with pgrouting and tested the code on a bigger scale.
- Will focus on integration and documentation.I will have discussions with my mentors regarding the same.In between further improve the code if required.
- Not much .
- Fixed some more errors in the code. Set up the whole testing environment .
- Testing and integration with pgrouting. A little bit of documentation if possible.
- Got stuck with two or three segmentation faults ,that consumed time.
- This week i fixed a lot of compile errors as i was trying to test my code.I generated my own test data.Overall the whole week was devoted to debugging.
- Fix all the compile errors , have my test cases formulated in the input file.Get the read me file ready so that the community can have it tested as well .
- The debugging took some time , i hope i can finish the integration in time before the deadline .
- Completed the solver class , will focus now on improving it a bit in some areas.
*start testing it using input from files and make appropriate changes as required . update the c functions appropriately .Discuss with my mentor about any change if required .
- i was having a health issue that elongated a bit and that derailed a lot of my plans.
- The solver class is almost complete.There are still a few things that need to be fixed.
- Complete the solver class and start testing it.
- The ethernet card of my laptop malfunctioned due to which i was not able to even connect to internet or update my code repository. Initially i thought it was some proxy issue . I have called the customer care people and they will change either the card or the motherboard by Monday or tuesday. I will be able to update the repository by then only.
- Added some more lines of code to the solver class. It is yet not complete but i will try hard to complete it this week .
- Achieve the above objective .
- I wasn't able to work much this week due to a health issue . I am still recovering from it and i will compensate the working hours that i lost in coming weeks. I deeply regret for the time that i lost due to my health issue this week .
- Made significant progress towards a working solver class. Hopefully it will be ready by this week according to my original schedule.After that some testing process will be initiated.
- Achieve the above objective .
- Nothing very significant. Steve did point out some mistakes in c++ code.
- Reimplemented the partition retrieval mechanism so that regularly the partition can be fetched whenever demand arises and we don't have to make ant recursive SPI_calls ( inbuilt function which talks to database). Made few changes to the solver class which constructs the graph and computes the path. still in the process of making those changes .
- Try and complete implementing the solver class.
- Basic implementation issue that was solved through discussion with Steve.
- No i don't think any change is required . I devoted week 5-8 for solver class implementation. I will have my solver class completed by then.
- started Implementing the main routing algorithm ( astar) , was finally able to implement partition retrieval mechanism using partition id. I hope that i will be able to complete a functional astar algorithm by next week , atleast a basic one that manually takes some input ( from file ).
- will try to complete the above mentioned task.
- some c++ issues which i googled successfully.
- Tried coding the partition retrieval and graph increment mechanism, the work is still in progress.I am having some difficulty but i hope i can do it this weekend and commit it by sunday.
- Complete the above mentioned work and try to start implementing astar.
- Basically coding issues but learned a lot while tackling them.
- Implemented the basic partitioning stuff with help from Steve's code on a sample self generated data set.
- Tried to implement the same on an OSM data set .
- Currently working on mechanism for retrieval of partitions so that the graph can be incremented.
- Basically get point 3 of the above done i.e code the partition retrieval and graph increment mechanism.
- had some basic doubts that were solved through discussions.
- Tried understanding the internal aspects of pgrouting i.e studied about the basic data flow using bd_astar source code .
- Tested some basic pl/pgsql codes.
- Read and deployed the basic partitioning code that Steve provided.Have made some changes to it, will try testing it this weekend.
- For the next two weeks the major focus will be to implement the partitioning stuff using quad tree approach as discussed with Steve and Daniel . Will have to discuss and tackle new issues that may pop up during this period.
- It took a while for me to understand the basic data flow.
- I am new to procedural languages but it wasn't so tricky to understand.
- Installed postgresql , postgis and pgrouting successfully on a virtual machine that was set up using vagrant.
- Built and tested pgrouting with some querries.
- Got familiar with git, i was already provided with gsoc-partition branch by my mentors,so didn't have to do much regarding this.
- Try to understand the internal aspects of pgrouting.
- Get more familiar with PL/pgSQL Procedural Language.
- Try and modify the code of partitioning that Steve provided.
- Had to face a few problems because of proxy issue while i was trying to set up the development environment.Thanks to Steve and Daniel for the quick responses regarding the same.