samples_token
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 390
- Forks
- 99
- PR merge metrics
- No merged PRs in 30d
Description
I would include all sample tokens for each scene as a list.
It would be better then cycling over next_sample_token = my_scene.get("sample", my_sample_token)["next"] for 126 times to get all sample tokens.
Also, I am not sure where the naming convention is coming from, but if I had a choice I would name all samples as scene_token_000 scene_token_001 ... scene_token_125, so that scene token is a part of the sample token name, which belongs to that run
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name a file, test, or entry point. Start by locating the scene/sample-token API and compare the current repeated `next_sample_token` traversal with the requested list-based access. Done means the sample tokens can be obtained as a complete list, with the naming convention clarified or updated if that remains in scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100