Conversation
This commit adds an info log message in the `Experiment` class to indicate the number of repeats and parallels when running an experiment. Additionally, it updates the logging message in the `fire_spread` example to reflect when the experiment has finished, improving the clarity of the logging output during execution.
This commit updates the comments in the `absespy.yaml` file to clarify that the 'file' handler is not defined, as ABSESpy configures its own file logging through the `log.run.file` settings. This change enhances the understanding of the logging setup for users and developers.
📝 WalkthroughWalkthroughThe PR modifies logging configuration and instrumentation across the ABSESpy codebase. Changes include clarifying file handler documentation in the logging configuration file, adding informational logging to record batch run parameters, adjusting example log messages from experiment start to completion, and minor documentation formatting. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom Pre-merge checks in the settings. ✨ Finishing touches
📜 Recent review detailsConfiguration used: defaults Review profile: CHILL Plan: Pro 📒 Files selected for processing (4)
🧰 Additional context used🧬 Code graph analysis (2)abses/core/experiment.py (1)
examples/fire_spread/model.py (2)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (11)
🔇 Additional comments (4)
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. Comment |
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.