google-deepmind / google-deepmind/reverb
How to change Table max_time_sampled param when reloading ?
- Dominant language
- C++
- Stars
- 793
- Forks
- 113
- PR merge metrics
- No merged PRs in 30d
Description
Hi, everyone, sorry if this is not the appropriate place for questions but I can't find any doc related to this.
There is a way to change the max_time_sampled parameter when a reverb table is restored?
Let's say I've collected some trajectories. to run some tests I've created some copies of the saved tables.
I would like to test my training pipeline using different max_time_sampled but seems that every time I reload the tables
the parameter max_time_sampled is the same as when I created the first instance of the server.
Any help or link to documentation is truly appreciated.
Contributor guide
Research direction
Start by reviewing the documentation and implementation related to max_time_sampled, restored tables, and Reverb server initialization. Determine whether the parameter can be changed after reloading saved tables; done means documenting the supported behavior and the steps, if any, for testing different values.
Written by the indexing model from the issue text.
Assessment
- Domain
- data, machine-learning
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100