Closed matthew-blackman closed 1 year ago
From co-review with @matthew-blackman:
scoreTrajectory( position, trajectory )
. Not sure we need the trajectory instance, but just a thought!null
(not landed yet) or 0-3. Then it can be up to the wrapper to put that into the Boolean that CODAP wants.It doesn't matter to me how (or when) the marker for whether the trajectory has hit the target is passed into CODAP, just whether the projectile has hit it, even when the target has moved. A bonus would be to track how close the trajectory got to the target (the 0-3 rating), and it sounds like this is easier, so great! It's ok if the rest (e.g., boolean) is done in the CODAP table by the user, although having both the boolean and the 0-3 rating would be extra bonus :) The categorical data would be useful for lessons where the learning goal was to differentiate between categorical vs quantitative data, as well as estimating probabilities from the proportion of successes. But the method of getting that data should definitely go the route of whatever is best for the now and future code.
Are we okay to close this issue?
Who are you asking? Please assign if looking for comment from me.
The boolean data for whether the projectile has hit the target is now being sent into the CODAP wrapper.
@catherinecarter asked for boolean data in the CODAP wrapper for whether or not the projectile hit the target. This will allow for plotting binomial distributions / categorical data / law of large numbers.
Future discussion: Would it be useful to have data as the 'number of stars' (0, 1, 2, 3)? This could be processed within CODAP to a boolean, but would require an additional step.