For some data types, I’m not really interested in what happen two months ago. It’s annoying having to specify the lag ranges every time I switch between a data type. The app should remember it per data type. E.g., caffeine intake matters a lot for today plus minus a day, but what happen two months ago is pointless.

This could alternatively be solved by adding order by lag too. Although, I would think of this as a more complimentary change.

Remembering the lag ranges per category might help improve performance, though. It would eliminate the need to calculate some unwanted correlations.