Include builds for accelerators in software overview page
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 12/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation
Research direction
The work is on the EESSI software overview page, where a table lists builds per CPU target marked with X; the payload names no file, test or entry point. The issue is an open design question with no decision in the thread, so the first step is to agree with maintainers on a layout (separate table, per-CPU tables, or tooltips). Done would mean accelerator builds are listed on the page in whichever layout was agreed.
Written by the indexing model from the issue text.
Description
We should also list the apps that are available for accelerators. I'm not sure what's the best way to do this, though.
I guess adding them to the existing table would make it way too big and unreadable, so maybe we can add them to a separate section/table. Maybe even a separate table for every CPU target, having the accelerator targets / compute capabilities as columns? All those tables would probably be very similar though...
Alternatively, it could perhaps be one table with tooltips or something showing the accelerator targets for a specific CPU target when you hover over / click on the X.
- Dominant language
- Python
- Stars
- 14
- Forks
- 54
- Avg merge
- 11h 2m
- Merged PRs (30d)
- 41
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 EESSI/docs
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
add "talks" sectionOpen
Difficulty 2/5 Half a day Newbie friendliness 62/100
Maintainers usually reply within 1 day
Similar issues
-
ChatBedrockConverse changes the keys of JSON tool results to camelCase (`order_id` becomes `orderId`)Possibly taken @geyazheng claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
langchain-ai/langchain-aws#1469 ·
Maintainers usually reply within 1 day
-
b4b usability
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
fix(schedule): align list_tasks since cursor filter boundary from strict > to >=Possibly taken @bfs2021 claimed this today. Openagent-ready bug p2 schedule
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
allenporter/supernote#540 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
frazane/scoringrules#164 ·
Maintainers usually reply within 1 day
-
The docs build fails: ecc's live inventory dropped the ecc.ecc names btclib's pinned ecc usesPossibly taken @fametrano claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
btclib-org/btclib#2968 ·
Maintainers usually reply within 1 day