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

not closing files prevents re-opening them #901

Merged
merged 1 commit into from
Oct 11, 2024

Conversation

nicolasaunai
Copy link
Member

@nicolasaunai nicolasaunai commented Oct 11, 2024

Summary by CodeRabbit

  • New Features

    • Introduced a new method to retrieve time arrays for specific quantities.
    • Enhanced the processing of time data from HDF5 files.
  • Bug Fixes

    • Corrected the loop indentation in the time processing method for proper execution.

@nicolasaunai nicolasaunai added the bug 🔥 Something isn't working label Oct 11, 2024
Copy link

coderabbitai bot commented Oct 11, 2024

📝 Walkthrough

Walkthrough

The changes involve modifications to the Run class within the pyphare/pyphare/pharesee/run/run.py file. The all_times method has been updated to include a new loop that processes time keys from HDF5 files and stores them in a dictionary. Additionally, the indentation of the loop has been corrected. A new method, times, has been added to retrieve the time array for a specified quantity by utilizing the all_times method.

Changes

File Path Change Summary
pyphare/pyphare/pharesee/run/run.py - Added method times(self, qty) to retrieve time array for a specified quantity.
- Updated method all_times(self) with a new loop for processing time keys and corrected indentation.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Run

    User->>Run: call times(qty)
    Run->>Run: call all_times()
    Run->>HDF5: process time keys
    HDF5-->>Run: return time data
    Run->>Run: store time data in dictionary
    Run-->>User: return time array for qty
Loading

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.

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

🧹 Outside diff range and nitpick comments (2)
pyphare/pyphare/pharesee/run/run.py (2)

Line range hint 268-287: Improvements in resource management and code structure.

The changes in the all_times method are beneficial:

  1. The loop indentation has been corrected, ensuring all files are processed.
  2. The HDF5 file is now properly closed after processing, preventing resource leaks.

These improvements enhance the method's reliability and resource management.

However, consider the following suggestions for further improvement:

  1. Add error handling for file operations and key lookups to make the code more robust.
  2. Consider moving the quantities_per_file dictionary to a class attribute for better encapsulation.

Example of error handling and using a class attribute:

class Run:
    quantities_per_file = {
        "EM_B": "B",
        "EM_E": "E",
        "ions_bulkVelocity": "Vi",
        "ions_density": "Ni",
        "particle_count": "nppc",
    }

    def all_times(self):
        from glob import glob
        import os
        import h5py

        files = self.available_diags
        ts = {}
        for file in files:
            basename = os.path.basename(file).split(".")[0]
            try:
                with h5py.File(file, 'r') as ff:
                    time_keys = ff["t"].keys()
                    time = np.zeros(len(time_keys))
                    for it, t in enumerate(time_keys):
                        time[it] = float(t)
                    ts[self.quantities_per_file[basename]] = time
            except (IOError, KeyError) as e:
                logger.error(f"Error processing file {file}: {str(e)}")
        return ts

289-290: New method for accessing quantity-specific time data.

The addition of the times method is a good improvement, providing a convenient way to access time data for a specific quantity.

To enhance its robustness and usability, consider the following suggestions:

  1. Add error handling to gracefully manage cases where the specified quantity doesn't exist.
  2. Include a docstring to explain the method's purpose, parameters, and return value.

Here's an example of how you might implement these suggestions:

def times(self, qty):
    """
    Retrieve the time array for a specified quantity.

    Args:
        qty (str): The quantity for which to retrieve the time array.

    Returns:
        numpy.ndarray: The time array for the specified quantity.

    Raises:
        KeyError: If the specified quantity is not found in the available data.
    """
    all_times_data = self.all_times()
    if qty not in all_times_data:
        raise KeyError(f"Quantity '{qty}' not found in available data.")
    return all_times_data[qty]
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 8d15f77 and 6c6bca5.

📒 Files selected for processing (1)
  • pyphare/pyphare/pharesee/run/run.py (1 hunks)
🧰 Additional context used

@nicolasaunai nicolasaunai merged commit 356720a into PHAREHUB:master Oct 11, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🔥 Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants