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

Update/calculate hourly airqualitydata using bigqdata #4351

Conversation

NicholasTurner23
Copy link
Contributor

@NicholasTurner23 NicholasTurner23 commented Feb 4, 2025

Description

Create default calibrated fields for non airqo device measurements.

Summary by CodeRabbit

  • New Features

    • Enhanced sensor calibration now includes two additional measurement fields for particulate matter, providing improved tracking of refined air quality readings.
  • Refactor

    • Streamlined the calibration process to ensure updated predicted values are accurately assigned.

Copy link
Contributor

coderabbitai bot commented Feb 4, 2025

📝 Walkthrough

Walkthrough

This pull request updates the data calibration process in the AirQoDataUtils class. Two new columns, pm2_5_calibrated_value and pm10_calibrated_value, are introduced in the calibrate_data method, initialized with np.nan. The method now includes these columns in its input variables and assigns predictions from random forest and lasso models to them based on city groupings. Additionally, a redundant comment has been removed to improve the clarity of the calibration logic.

Changes

File(s) Change Summary
src/.../airqo_utils.py Added new columns (pm2_5_calibrated_value, pm10_calibrated_value) initialized to np.nan; updated calibration logic to assign predictions from random forest and lasso models; removed a redundant comment.

Sequence Diagram(s)

sequenceDiagram
    participant Client as Client
    participant Utils as AirQoDataUtils
    participant Data as DataFrame
    participant RFModel as RandomForestModel
    participant LassoModel as LassoModel

    Client->>Utils: Call calibrate_data(data)
    Utils->>Data: Initialize pm2_5_calibrated_value & pm10_calibrated_value (np.nan)
    Utils->>Data: Group data by city
    Utils->>RFModel: Predict PM2.5 values for group
    Utils->>LassoModel: Predict PM10 values for group
    RFModel-->>Utils: Return PM2.5 predictions
    LassoModel-->>Utils: Return PM10 predictions
    Utils->>Data: Update DataFrame with calibrated values
    Utils->>Client: Return calibrated DataFrame
Loading

Suggested reviewers

  • Baalmart
  • BenjaminSsempala

Poem

In lines of code, new fields arise,
PM2.5 and PM10, under digital skies,
Predictions flow where logic complies,
A fusion of models in a data ballet,
With clarity restored in each display,
Cheers to the code that lights our way! 🌟

Tip

🌐 Web search-backed reviews and chat
  • We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
  • You can disable this feature by setting web_search: false in the knowledge_base settings.
  • Please share any feedback in the Discord discussion.
✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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
Contributor

@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: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6f0282b and 388a57b.

📒 Files selected for processing (1)
  • src/workflows/airqo_etl_utils/airqo_utils.py (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Analyze (python)
  • GitHub Check: Analyze (javascript)
🔇 Additional comments (1)
src/workflows/airqo_etl_utils/airqo_utils.py (1)

621-622: LGTM! Good initialization of calibrated value columns.

Using np.nan for initializing the calibrated value columns is a good practice as it properly represents missing values in pandas DataFrames.

Comment on lines +633 to +634
"pm2_5_calibrated_value",
"pm10_calibrated_value",
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Remove calibrated value columns from input variables.

Including pm2_5_calibrated_value and pm10_calibrated_value in the input variables list could cause issues:

  1. These columns are initialized with np.nan, and line 641 drops rows with missing values in input variables.
  2. These are target variables that we're trying to predict, not input features.

Apply this diff to fix the issue:

            "error_pm10",
            "pm2_5_pm10",
            "pm2_5_pm10_mod",
-            "pm2_5_calibrated_value",
-            "pm10_calibrated_value",
        ]
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"pm2_5_calibrated_value",
"pm10_calibrated_value",
"error_pm10",
"pm2_5_pm10",
"pm2_5_pm10_mod",
]

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

Successfully merging this pull request may close these issues.

2 participants