is there a better way to name the results rds file
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 184
- Forks
- 53
- Avg merge
- 7d 2h
- Merged PRs (30d)
- 1
Description
currently, in the results folder of the experiment registry, the results are named after i.rds where i is n integer. Suppose of the current scenario: the user needs to change some algorithms but still want to run them and put them in the same job id, in this case, will the results rds file be overwritten? If so, is it better to store using the job hash id of the algorithm and problem and maybe git sha key?
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
Start by reviewing how the experiment registry names and writes result files in its results folder, especially the current i.rds convention. Determine whether changing algorithms within the same job ID can overwrite results, and evaluate the proposed algorithm/problem job hash and git SHA naming. Done should include an agreed naming scheme that avoids unintended overwrites.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- hpc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100