search

oulan / oppia

Automatically exported from code.google.com/p/oppia
Apache License 2.0
0 stars 0 forks source link

World Map distance metric is not intuitive #487

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Create a new exploration, and make the first state have a World Map 
interaction.
2. Create a new rule, along the lines of "Answer is within ... of ... degrees 
N, ... degrees E".

What is the expected output? What do you see instead?

The rule is not intuitive. It does not specify the unit of measurement. It may 
also be unclear that entering negative numbers to specify southerly latitudes 
or westerly longitudes is an option.

The rule is currently implemented using Euclidean distance on the degree 
coordinates(!), but it should really be implemented based on a spherical metric 
instead.

Original issue reported on code.google.com by s...@seanlip.org on 1 Dec 2014 at 2:58

GoogleCodeExporter commented 9 years ago 
We're now proposing to do this in three stages:
1. Change the "Euclidean distance on co-ordinates" to a distance in km, that 
the backend rules compute correctly on a sphere.
2. Replace the (latitude, longitude) argument with a map on which the user can 
click to specify the location which the student needs to get close to.
3. Once it becomes possible to make rule editors depend on interaction 
customisations, make the map from point 2 begin in the view specified by the 
customisations.

Original comment by jacobdav...@gmail.com on 23 Jan 2015 at 8:50

GoogleCodeExporter commented 9 years ago

Original comment by s...@google.com on 30 Jan 2015 at 2:53

GoogleCodeExporter commented 9 years ago 
Stage 1 of this is complete.

Estelle, would you like to move on to stage 2?

Original comment by s...@seanlip.org on 9 Feb 2015 at 4:49

GoogleCodeExporter commented 9 years ago 
Oh, and also -- congratulations on your first commit to Oppia! :-)

Original comment by s...@google.com on 9 Feb 2015 at 8:55

GoogleCodeExporter commented 9 years ago 
Hi Estelle, one further thought: you might like to delete the issue-487 branch 
following the instructions at the bottom of this page:

    https://code.google.com/p/oppia/wiki/DevelopmentWorkflow

Then, when you're ready for stage 2, you can start a brand-new branch from the 
latest version of develop. I think this is preferable to merging develop into 
your branch because it would make the commit history less muddy.

Thanks!

Original comment by s...@seanlip.org on 10 Feb 2015 at 3:06

GoogleCodeExporter commented 9 years ago 
Thanks :) I'm ready for stage 2 now, so should I delete the old branch and 
create a new one?

Original comment by estelle0...@gmail.com on 11 Feb 2015 at 4:38

GoogleCodeExporter commented 9 years ago 
Sounds good! I would suggest calling the new branch something like
"map-widget-improvements" so that people don't have to remember the issue
number when looking it up.

Original comment by jacobdav...@gmail.com on 11 Feb 2015 at 4:58

GoogleCodeExporter commented 9 years ago 
Sounds good! Yep, please feel free to do so. Make sure you sync to the latest 
version of develop:

    git checkout develop
    git pull origin develop

before creating a new branch off of it.

Original comment by s...@seanlip.org on 11 Feb 2015 at 4:58

GoogleCodeExporter commented 9 years ago 
Alright - I've just created a new branch that's synced to the latest version of 
develop.

Original comment by estelle0...@gmail.com on 15 Feb 2015 at 4:00