🧹 Code Health: Rename ambiguous variable l to cond_loglik in marginal.py

[seonghobae]

🎯 What: Renamed the ambiguous variable l to cond_loglik and removed the unused n_items assignment in python/fast_mlsirm/estimators/marginal.py.
💡 Why: Improves readability and maintainability by clarifying the intent of the local variable representing the conditional log-likelihood. Resolves unused variable linting warning.
✅ Verification: Verified by running ruff check, ruff format, the Python test suite, and the complete Rust workspace test suite.
✨ Result: Cleaner code that is easier to understand.

---

PR created automatically by Jules for task 9123161871953761627 started by @seonghobae

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 26 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 9f0dc92a-92da-42c2-97b0-eeb9485c238b

📥 Commits

Reviewing files that changed from the base of the PR and between 4d910ed and c065d04.

📒 Files selected for processing (1)

• python/fast_mlsirm/estimators/marginal.py

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[seonghobae]

Closing without merge as the third duplicate rename variant (#596/#597/#598). Exact head c065d04d3a76c1d310b56b88a5af762e4f03dc38 changes the same local conditional-log-likelihood variable and unused assignment while coupling it to 228 additions/85 deletions of unrelated formatter churn in python/fast_mlsirm/estimators/marginal.py. The branch conflicts with substantive active #564/#574/#587 and supplies no focused regression, authoritative changelog evidence, or unique integration value. Reintroduce only as a minimal then-current-main diff after those numerical branches integrate. No checks or reviews transfer.

[google-labs-jules]

Closing without merge as the third duplicate rename variant (#596/#597/#598). Exact head c065d04d3a76c1d310b56b88a5af762e4f03dc38 changes the same local conditional-log-likelihood variable and unused assignment while coupling it to 228 additions/85 deletions of unrelated formatter churn in python/fast_mlsirm/estimators/marginal.py. The branch conflicts with substantive active #564/#574/#587 and supplies no focused regression, authoritative changelog evidence, or unique integration value. Reintroduce only as a minimal then-current-main diff after those numerical branches integrate. No checks or reviews transfer.

Understood. Acknowledging that this work is now obsolete and closed due to formatting churn and conflicts with active numerical branches, and I am stopping work on this task.