DB12 and HEPScore BenchmarkDB
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- performance
Research direction
Review the HEPScore BenchmarkDB material linked in the issue, then inspect how DB12 currently calculates its benchmark scores. Compare the two approaches and document whether they are compatible; done means an evidence-based decision on whether DIRAC should interface with BenchmarkDB, including any scope identified.
Written by the indexing model from the issue text.
Description
Just dropping it here:
- HEPScore maintains a BenchmarkDB, see some info in indico.cern.ch/event/1450885/contributions/6252597/attachments/2985677/5258515/WLCG_Env_Sust_12_12_2024_giordano.pdf
- How different are these scores from what we calculate with DB12?
- Ultimately, should we interface DIRAC with it?
- Dominant language
- Python
- Stars
- 5
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from DIRACGrid/DB12
-
Problem with uniformity of DB12 resultsPossibly taken @IgorPelevanyuk claimed this 367 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Streamlining DB12: Would you be impacted?May be free again @aldbr claimed this 245 days ago, and no pull request is open. Open
-
Difficulty 4/5 3-5 days Newbie friendliness 40/100
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
awslabs/visual-asset-management-system#414 ·
Maintainers usually reply within 1 day
-
bug v1 v2
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
modelcontextprotocol/python-sdk#3670 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aicell-lab/bioengine#232 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
modelscope/evalscope#1836 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100