Fix/fix calculate power law r2

[ChenZiHong-Gavin]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @ChenZiHong-Gavin, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a critical bug in the power law R-squared calculation within the graph evaluation module, ensuring accurate statistical analysis. It also refactors environment variable loading for better application structure and enhances the WebUI's configuration with default backend settings and output saving for the generation process. These changes collectively improve the robustness, maintainability, and functionality of the system.

Highlights

• Corrected Power Law R2 Calculation: Fixed an issue in structure_evaluator.py where the R-squared value for power law distribution fitting was incorrectly calculated. The change ensures that the rvalue attribute is properly accessed from the scipy.stats.linregress result object.
• Refactored Environment Variable Loading: The load_dotenv() call was moved from graphgen/engine.py to graphgen/run.py, centralizing the loading of environment variables to the application's main entry point.
• Enhanced WebUI Configuration: The WebUI's run_graphgen function now includes "save_output": True for the generate operator and sets default graph_backend to "kuzu" and kv_backend to "rocksdb" within the global parameters.
• Streamlined Ray Initialization: Removed a redundant explicit ray.init() check in webui/app.py, indicating that Ray initialization is now handled implicitly or at a higher level.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request addresses a critical bug in the power-law R² calculation by correctly using the rvalue from scipy.stats.linregress instead of the slope. It also includes several related fixes and improvements, such as moving the load_dotenv call to a more appropriate entry point, and updating the web UI configuration to ensure correct pipeline execution and output handling. My review includes one suggestion to improve the flexibility of the web UI by avoiding hardcoded storage backend configurations.

[gemini-code-assist]

The graph_backend and kv_backend are hardcoded in the configuration. This reduces the flexibility of the web application, as users cannot easily switch to other supported backends (e.g., networkx for graphs, json_kv for key-value stores) without modifying the source code. It would be better to expose these as configurable options in the UI, perhaps by adding them to the WebuiParams dataclass.