-
Bug
-
Resolution: Fixed
-
Minor
-
3.4
-
MOODLE_34_STABLE
-
MOODLE_34_STABLE
-
MDL-59638_master -
This has been discovered during MDL-57791 testing.
In students at risk of dropping out model we read logs from activities which due dates are part of the time range we want to predict dropouts for (e.g. half of the course). If activities do not have a due date and use topics format, we based that date the activity should be completed by in the section it belongs to.
MDL-57791 simple setup the testing instructions use 4 sections (1 for each quarter of the course) the problem is that we deduct 1 second from the end of each quarter (aka time range in time splitting methods entity) so 1 timestamp does not belong to 2 different time ranges, but instead of that what we should do is to increase the start of the next time range by 1 second otherwise activities' due dates are not part of that quarter of the course and predictions fail to match data from the finished course with data from the ongoing course.
- Discovered while testing
-
MDL-57791 Implement an analytics engine in Moodle
- Closed