Kaggle / Kaggle/kaggle-environments
increase max_log_length from 1024 to 2048 or 4096?
- Dominant language
- JavaScript
- Stars
- 452
- Forks
- 190
- Avg merge
- 31m
- Merged PRs (30d)
- 2
Description
Could you increase the `max_log_length` per step in `core.py` and `agent.py`? 1024 is too small to log against the rich game state of Lux with hundreds of objects. 2048 or 4096 would be much better. With more than 12 months of Simulation experience you should be able to look at average log size and see that an increase will not be a burden.
Contributor guide
Research direction
Read core.py and agent.py to find the per-step max_log_length setting and check how the current 1024 limit is applied. Confirm whether 2048 or 4096 is appropriate from average log sizes, then verify that larger Lux game-state logs are accepted without imposing an undue burden.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100