Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

enhance(apps/analytics): add computation logic for activity progress #4392

Merged
merged 4 commits into from
Dec 6, 2024

Conversation

sjschlapbach
Copy link
Member

@sjschlapbach sjschlapbach commented Dec 6, 2024

Summary by CodeRabbit

Release Notes

  • New Features

    • Introduced new functions for tracking activity progress, including get_course_progress_activities, compute_progress_counts, save_practice_quiz_progress, and save_microlearning_progress.
    • Added a Jupyter notebook for computing and storing activity progress related to courses.
  • Improvements

    • Enhanced readability of import statements and function calls in the instance_activity_performance notebook.

These changes expand the analytics capabilities and improve code clarity for better maintainability.

Copy link

coderabbitai bot commented Dec 6, 2024

📝 Walkthrough

Walkthrough

This pull request introduces several changes across multiple files in the analytics module. Key modifications include the addition of new import statements in __init__.py files to enhance module functionality. New functions are defined in various files to compute and save activity progress related to courses, including methods for handling practice quizzes and microlearning activities. Additionally, a new Jupyter notebook is introduced for computing and storing activity progress, while another notebook has been updated for improved readability without altering its logic.

Changes

File Path Change Summary
apps/analytics/src/modules/__init__.py Added import: from .activity_progress import *
apps/analytics/src/modules/activity_progress/__init__.py Added imports: get_course_progress_activities, compute_progress_counts, save_practice_quiz_progress, save_microlearning_progress
apps/analytics/src/modules/activity_progress/compute_progress_counts.py Added function: compute_progress_counts(activity)
apps/analytics/src/modules/activity_progress/get_course_progress_activities.py Added function: get_course_progress_activities(db, course_id)
apps/analytics/src/modules/activity_progress/save_microlearning_progress.py Added function: save_microlearning_progress(db, course_participants, started_count, completed_count, course_id, ml_id)
apps/analytics/src/modules/activity_progress/save_practice_quiz_progress.py Added function: save_practice_quiz_progress(db, course_participants, started_count, completed_count, repeated_count, course_id, quiz_id)
apps/analytics/src/notebooks/activity_progress.ipynb Introduced new notebook for computing and storing activity progress
apps/analytics/src/notebooks/instance_activity_performance.ipynb Reformatted import statements and function calls for readability

Possibly related PRs

Suggested reviewers

  • rschlaefli

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 12

🧹 Outside diff range and nitpick comments (4)
apps/analytics/src/modules/activity_progress/get_course_progress_activities.py (1)

4-5: Consider optimizing the included relations.

The current implementation includes all stacks, elements, and responses which could impact performance for courses with large amounts of data. Consider:

  1. Limiting the number of responses or filtering by date
  2. Including only necessary fields

Also applies to: 10-11

apps/analytics/src/modules/activity_progress/compute_progress_counts.py (2)

11-13: Consider using list comprehension for element counting

The current implementation uses a loop to count elements, which could be simplified.

-        num_elements = 0
-        for stack in activity["stacks"]:
-            num_elements += len(stack["elements"])
+        num_elements = sum(len(stack["elements"]) for stack in activity["stacks"])

38-40: Enhance error logging

The current print statement for no responses could be more informative.

-        print("No responses found for activity", activity["id"])
+        logging.info(f"No responses found for activity {activity.get('id', 'unknown')}")

Consider adding logging import at the top of the file:

import logging
apps/analytics/src/modules/activity_progress/__init__.py (1)

1-4: Consider adding __all__ to explicitly define the public API.

To make the module's public interface more explicit and maintainable, consider adding an __all__ list.

+__all__ = [
+    'get_course_progress_activities',
+    'compute_progress_counts',
+    'save_practice_quiz_progress',
+    'save_microlearning_progress',
+]

from .get_course_progress_activities import get_course_progress_activities
from .compute_progress_counts import compute_progress_counts
from .save_practice_quiz_progress import save_practice_quiz_progress
from .save_microlearning_progress import save_microlearning_progress
🧰 Tools
🪛 Ruff (0.8.0)

1-1: .get_course_progress_activities.get_course_progress_activities imported but unused; consider removing, adding to __all__, or using a redundant alias

(F401)


2-2: .compute_progress_counts.compute_progress_counts imported but unused; consider removing, adding to __all__, or using a redundant alias

(F401)


3-3: .save_practice_quiz_progress.save_practice_quiz_progress imported but unused; consider removing, adding to __all__, or using a redundant alias

(F401)


4-4: .save_microlearning_progress.save_microlearning_progress imported but unused; consider removing, adding to __all__, or using a redundant alias

(F401)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between a04be0a and 40e3864.

📒 Files selected for processing (8)
  • apps/analytics/src/modules/__init__.py (1 hunks)
  • apps/analytics/src/modules/activity_progress/__init__.py (1 hunks)
  • apps/analytics/src/modules/activity_progress/compute_progress_counts.py (1 hunks)
  • apps/analytics/src/modules/activity_progress/get_course_progress_activities.py (1 hunks)
  • apps/analytics/src/modules/activity_progress/save_microlearning_progress.py (1 hunks)
  • apps/analytics/src/modules/activity_progress/save_practice_quiz_progress.py (1 hunks)
  • apps/analytics/src/notebooks/activity_progress.ipynb (1 hunks)
  • apps/analytics/src/notebooks/instance_activity_performance.ipynb (3 hunks)
✅ Files skipped from review due to trivial changes (1)
  • apps/analytics/src/notebooks/instance_activity_performance.ipynb
🧰 Additional context used
🪛 Ruff (0.8.0)
apps/analytics/src/modules/__init__.py

7-7: from .activity_progress import * used; unable to detect undefined names

(F403)

apps/analytics/src/modules/activity_progress/__init__.py

1-1: .get_course_progress_activities.get_course_progress_activities imported but unused; consider removing, adding to __all__, or using a redundant alias

(F401)


2-2: .compute_progress_counts.compute_progress_counts imported but unused; consider removing, adding to __all__, or using a redundant alias

(F401)


3-3: .save_practice_quiz_progress.save_practice_quiz_progress imported but unused; consider removing, adding to __all__, or using a redundant alias

(F401)


4-4: .save_microlearning_progress.save_microlearning_progress imported but unused; consider removing, adding to __all__, or using a redundant alias

(F401)

🔇 Additional comments (1)
apps/analytics/src/modules/activity_progress/__init__.py (1)

1-4: LGTM! The imports are correctly structured for module re-exports.

These imports make the activity progress computation functions available at the package level, which aligns with their usage in the Jupyter notebooks.

🧰 Tools
🪛 Ruff (0.8.0)

1-1: .get_course_progress_activities.get_course_progress_activities imported but unused; consider removing, adding to __all__, or using a redundant alias

(F401)


2-2: .compute_progress_counts.compute_progress_counts imported but unused; consider removing, adding to __all__, or using a redundant alias

(F401)


3-3: .save_practice_quiz_progress.save_practice_quiz_progress imported but unused; consider removing, adding to __all__, or using a redundant alias

(F401)


4-4: .save_microlearning_progress.save_microlearning_progress imported but unused; consider removing, adding to __all__, or using a redundant alias

(F401)

Copy link

sonarqubecloud bot commented Dec 6, 2024

@sjschlapbach sjschlapbach merged commit 28d64f6 into v3-analytics Dec 6, 2024
13 of 14 checks passed
@sjschlapbach sjschlapbach deleted the activity-progress branch December 6, 2024 10:23
Copy link

cypress bot commented Dec 6, 2024

klicker-uzh    Run #3786

Run Properties:  status check passed Passed #3786  •  git commit 60b3a2c02b ℹ️: Merge 40e38640e6bc2fc9bd985162778caea032ad3432 into a04be0a2adcc8e9b800987963e89...
Project klicker-uzh
Branch Review activity-progress
Run status status check passed Passed #3786
Run duration 12m 13s
Commit git commit 60b3a2c02b ℹ️: Merge 40e38640e6bc2fc9bd985162778caea032ad3432 into a04be0a2adcc8e9b800987963e89...
Committer Julius Schlapbach
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 0
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 148
View all changes introduced in this branch ↗︎

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant