google-research / google-research/falken
Lifecycle diagram
- Dominant language
- Python
- Stars
- 275
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I'm noticing that the output from my game console log is different from the one of hello Falken demo. In particular I am missing the training frames when adding new chunks and I see only demo frames on my side. I am not even sure to understand the role of chunks in this context.
Questions are:
- is it possible to have a lifecycle diagram where I can understand step by step what I should expect from my console log and when stuff is created, called, deleted?
- if not, should I expect to have the exact same console log as the demo?
Thanks
Contributor guide
Research direction
Start by comparing the reporter's game console output with the hello Falken demo and documenting when chunks and training or demo frames are created, called, and deleted. Done means a lifecycle diagram explains the expected log differences and clarifies whether matching the demo output is required.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100