Re: Advanced Capstone 1.3 clarification

[Laura]

You are correct that in the real world in practice date or session could be considered – it depends what the end goal is.

Taking date for example you could either:

• join on time (no date included)
  • gives an average value over a certain window across multiple days
  • this tells the user that after say 3 days of practice sessions on average the sensor value is X in the morning or afternoon
  • for example this might indicate if temperature tyres are colder in the morning and hotter in the afternoon meaning we might want to adjust the car setup in the later sessions
  • in this scenario we don’t care about date – rather just the time of day it happened
• join on date and time
  • gives an average value over a certain window on a specific day
  • the dataset would be much larger (triple the size if 3 days)
  • this would be useful if I wanted to have the breakdown of averages per window per day

The same is true for session – we don’t actually care what session it is – we just want averages per time of day.

Hope this makes sense!