search

ifed3 / PBR

Personalized Bike Routing
11 stars 2 forks source link

Work Flow (Force) #4

Open jaellis opened 9 years ago

jaellis commented 9 years ago

Hi All, it was great to meet everyone and hear your ideas last night.

There was mention early of work flow, and I was wondering if we should start dividing tasks. Thoughts?

thcrock commented 9 years ago

So we came up with a couple of starting tasks:

2

5

Currently I'm probably the only one who has server access to do the first one; the web app is probably going to be a big focus for the rest of the team this first week or two.

thcrock commented 9 years ago

Since you've created this, we've gotten some more issues created. What is your background, and what type of work are you looking to do?

jaellis commented 9 years ago

Hey, sorry for the delay.

I work as a data analyst doing SQL queries and lots of descriptive statistics. My background is in Neuroscience (MSc), and I would like to work on the routing algorithm, mostly.

-J

On Fri, Jul 31, 2015 at 8:33 PM, Tristan Crockett notifications@github.com wrote:

Since you've created this, we've gotten some more issues created. What is your background, and what type of work are you looking to do?

— Reply to this email directly or view it on GitHub https://github.com/ifed3/PBR/issues/4#issuecomment-126848017.

thcrock commented 9 years ago

Cool! As far as the algorithm goes, I think we'll have two ways of interacting with it:

  1. Modifying the profile. The routing algorithm is heavily tunable based on the .lua profile we pass in; any arbitrary weights so I think most (if not all) work will go through this.
  2. Modifying the algorithm itself; the routing algorithms are implemented in C++, and we may in the future have features that we can only implement by forking https://github.com/Project-OSRM/osrm-backend and making the changes ourselves. So you may be interested in checking out that repo and seeing how the algorithm and profile interact; I can't be much more help than that at this point.

I'm tagging our OSRM routing task issues with 'OSRM', so you'll probably want to keep an eye on those.

jaellis commented 9 years ago

Sweet! Thanks for the info. I haven't coded in C++ before so it will take me some time to get up to par. I'm also happy to contribute to our front-end design, I've got some experience with JS and HTML/CSS.

On Sun, Aug 2, 2015 at 3:07 PM, Tristan Crockett notifications@github.com wrote:

Cool! As far as the algorithm goes, I think we'll have two ways of interacting with it:

1.

Modifying the profile. The routing algorithm is heavily tunable based on the .lua profile we pass in; any arbitrary weights so I think most (if not all) work will go through this. 2.

Modifying the algorithm itself; the routing algorithms are implemented in C++, and we may in the future have features that we can only implement by forking https://github.com/Project-OSRM/osrm-backend and making the changes ourselves. So you may be interested in checking out that repo and seeing how the algorithm and profile interact; I can't be much more help than that at this point.

I'm tagging our OSRM routing task issues with 'OSRM', so you'll probably want to keep an eye on those.

— Reply to this email directly or view it on GitHub https://github.com/ifed3/PBR/issues/4#issuecomment-127065769.