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

variance across scope timing files (naive) #30

Merged
merged 1 commit into from
Sep 29, 2024
Merged

variance across scope timing files (naive) #30

merged 1 commit into from
Sep 29, 2024

Conversation

PhilipDeegan
Copy link
Owner

@PhilipDeegan PhilipDeegan commented Sep 28, 2024

Summary by CodeRabbit

  • New Features

    • Introduced functionality to analyze variance across multiple scope timer files, enhancing data processing capabilities.
    • Added new methods for writing and printing variance data, streamlining output to focus on variance calculations.
  • Version Updates

    • Updated project version from 0.0.26 to 0.0.27 across relevant files.

Copy link

coderabbitai bot commented Sep 28, 2024

Walkthrough

The changes introduce significant updates to the scope_timer.py file, replacing the write_root_as_csv and print_root_as_csv functions with new functions that handle multiple scope timer files using a glob pattern. The new functions calculate and print variance data, focusing on standard deviations of timing data. Additionally, the project version has been updated from "0.0.26" to "0.0.27" in both pyproject.toml and setup.py, reflecting the changes made.

Changes

Files Change Summary
phlop/timing/scope_timer.py Replaced write_root_as_csv with write_variance_across, and print_root_as_csv with print_variance_across. Updated method signatures to handle multiple files and calculate variance data.
pyproject.toml Updated project version from "0.0.26" to "0.0.27".
setup.py Updated package version from "0.0.26" to "0.0.27".

Poem

In the meadow where timers tick,
A rabbit hops, oh so quick!
Variance now dances in the air,
With glob patterns, we can share.
From "zero point oh" we take a leap,
To "zero point oh seven," our data we keep! 🐇✨


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: 2

🧹 Outside diff range and nitpick comments (3)
phlop/timing/scope_timer.py (3)

152-157: Improve variable names in the map_graph function

The variables n, k, and t in the map_graph function are not descriptive, which can make the code harder to understand. Consider using more meaningful variable names, such as node, index, and depth, to enhance readability.


159-163: Rename variable stf for clarity

The variable stf may not be immediately clear to readers. Consider renaming it to a more descriptive name like scope_timer_file or timer_file to improve code readability.


165-179: Clarify variable usage in numerics calculation

In lines 176-177, using _ and __ as variable names can be confusing. If these values are not needed, it's acceptable to use a single underscore _ for each unused variable. Alternatively, if they hold meaningful data, consider assigning descriptive names to enhance code clarity.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 868cca3 and a45955f.

📒 Files selected for processing (3)
  • phlop/timing/scope_timer.py (2 hunks)
  • pyproject.toml (1 hunks)
  • setup.py (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • pyproject.toml
  • setup.py
🧰 Additional context used
🪛 Ruff
phlop/timing/scope_timer.py

140-141: Use a single with statement with multiple contexts instead of nested with statements

Combine with statements

(SIM117)

🔇 Additional comments (1)
phlop/timing/scope_timer.py (1)

5-6: LGTM

The addition of the necessary imports numpy and Path is appropriate for the new functionality implemented in the code.

Comment on lines +146 to +148
scope_timer_files = [file_parser(f) for f in Path.cwd().glob(scope_timer_file_glob)]
if not scope_timer_files:
return
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Add error handling for file parsing failures

If any of the files matched by the glob pattern cannot be parsed correctly, the program may crash without a clear error message. Consider adding error handling to gracefully manage exceptions during file parsing and provide informative messages to the user.

Comment on lines +137 to +142
def write_variance_across(scope_timer_file_glob, outfile):
from contextlib import redirect_stdout

with open(outfile, "w") as f:
with redirect_stdout(f):
print_root_as_csv(scope_timer_file, headers, regex)
print_variance_across(scope_timer_file_glob)
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Simplify nested with statements

You can combine the nested with statements into a single with statement to make the code cleaner and more Pythonic.

Apply the following diff to combine the with statements:

 def write_variance_across(scope_timer_file_glob, outfile):
     from contextlib import redirect_stdout

-    with open(outfile, "w") as f:
-        with redirect_stdout(f):
+    with open(outfile, "w") as f, redirect_stdout(f):
         print_variance_across(scope_timer_file_glob)
📝 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
def write_variance_across(scope_timer_file_glob, outfile):
from contextlib import redirect_stdout
with open(outfile, "w") as f:
with redirect_stdout(f):
print_root_as_csv(scope_timer_file, headers, regex)
print_variance_across(scope_timer_file_glob)
def write_variance_across(scope_timer_file_glob, outfile):
from contextlib import redirect_stdout
with open(outfile, "w") as f, redirect_stdout(f):
print_variance_across(scope_timer_file_glob)
🧰 Tools
🪛 Ruff

140-141: Use a single with statement with multiple contexts instead of nested with statements

Combine with statements

(SIM117)

@PhilipDeegan PhilipDeegan merged commit f65198d into master Sep 29, 2024
2 checks passed
@PhilipDeegan PhilipDeegan deleted the next branch September 29, 2024 19:53
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.

1 participant