Calculation summary: the job's allocation and how much of it is left (projinfo / Slurm)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c, linux
- Domain
- backend, desktop, distributed-systems
Research direction
Start by reading the calculation summary's Launcher block and the shared SSH connection work referenced in #487 and #599; then review #541 for how accounts are stored per allocation. Identify the machine registration path for the allocation command and how remote commands are cached. Done means the summary can show the allocation, remaining core-hours, and read time, while missing or failed commands display nothing; the issue calls for design review of the remote-shell behavior.
Written by the indexing model from the issue text.
Description
Andy 2026-10-27: on a cluster with a limited allocation, the calculation summary's Launcher block (Machine, Processors, Start Date, Comp. Date) should show the allocation the job runs under and how much of it is left.
- Allocation: the account/project the job was submitted with (the Slurm
--account, as stored at launch). - Left: core-hours used / allocated, from the site's own tool where there is one (HPC2N/NAISS:
projinfo), else Slurm (sshare -A <account>/sreport), set per machine in Register Machines ("Allocation command", empty = not shown). - Read over the machine's shared ssh connection (#487/#599), no new login; at most every 15 min per machine and account, cached; shown with when it was read ("checked 10:20"). A failed or missing command shows nothing rather than an error.
- Goes with #541 (several allocations on one compute machine), which stores the account per allocation.
Remote-shell code: design review before the change (no extra prompts, nothing run on a machine that has no allocation command).
- Dominant language
- C
- Stars
- 10
- Forks
- 8
- Avg merge
- 1h 45m
- Merged PRs (30d)
- 5
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 FriendsofECCE/ECCE
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FriendsofECCE/ECCE#529 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
FriendsofECCE/ECCE#519 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FriendsofECCE/ECCE#336 · 1 comment ·
-
Compare Energies: sums of calculations, E/E+ZPE/H/G, solvation energyPossibly taken @ohlincha claimed this today. Open
FriendsofECCE/ECCE#612 · 1 comment · 1 assignee ·
-
9.4.1 hand-check findings: selection boxes, spin density tables, MO composition box, Compare Energies order, XC in summary, frequency progressPossibly taken @ohlincha claimed this today. Open
FriendsofECCE/ECCE#611 · 2 comments · 1 assignee ·
All issues in FriendsofECCE/ECCE
Similar issues
-
bug intrinsic medium priority rt_lib
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
[CLI] Clarify distinction between 'capture camera' and 'capture screen' in help text and outputOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
espressif/esp-vision#18 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
sumatrapdfreader/sumatrapdf#6417 · 3 comments ·
-
[BUG] Cython cache evicts most recent instead of oldest entry on cleanupPossibly taken @scoder claimed this today. OpenBuild System defect
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
HexaCluster/credcheck#94 ·