-
Notifications
You must be signed in to change notification settings - Fork 3
Implement matching algorithm #29
Comments
Link to MUNComputerScienceSociety#29. Match view now shows all the counterparts (the opposite user types) found. The `AbaLookup\Match` class will need to sort the array of counterparts first.
cc @MitMaro
|
I think this should be in its own module (in the same project, but its own module in the project). That way it'd be a bit more reusable. We could have it so, given the user's schedule, it returns the list of matches. We could even have it so we pass in flags for the sort order. Thoughts? |
I agree on it's own module. We need a get together to discuss the algorithm. We will have a face-to-face meeting soon. |
Score = SUM(Sn), where Sn = {0, t < a; t2, a ≤ t ≤ b, a > b; b2 + (t - b), t > b} Where Sn is the score for partition n, t is the number of time slots in Sn, a is the desired minimum duration, b is the desired maximum duration. |
How are we planning on representing the scores? Integers vs. floats? |
Integers. There are no floats in the score. |
As of writing, the users can login/register, and enter their schedules.
The matching algorithm needs to be implemented - this will be easier once #12 is completed.
The text was updated successfully, but these errors were encountered: