Provide neurodesk convenience command
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
Start by reading transparent-singularity/run_transparent_singularity.sh and ts_binaryFinder.sh, along with the neurocontainers afni/build.sh entry-point generation. Then review how lmod-loaded environments and the proposed datalad neurodesk-run TOOL command could be represented. Done would require a defined lookup across the loaded stack and a commit message identifying the used container.
Written by the indexing model from the issue text.
Description
- neurodesk uses lmod to provide entry points (tools) for each container
- currently there is no centralized/recorded manifest. container has BIN path pointed to https://github.com/NeuroDesk/neurocontainers/blob/master/recipes/afni/build.sh#L34C4-L34C41 and upon build script generates all lmod entry points.
- considering adopting singularity-hpc (shpc, https://singularity-hpc.readthedocs.io/)
- NB: somewhat relates to the effort @yarikoptic tried to do somewhere to create index of all files per each container
- lmod could load multiple container "environments" (with version) so that later loaded container entry points take precedence over earlier
- what if we could do smth like
datalad neurodesk-run TOOLwhich would then "lookup" within currently loaded "stack" of environment which actual container and which tool gets invoked and then the datalad would have a commit message pointing to that particular used container (within repronim/containers collection)
attn @stebo85
- Dominant language
- Python
- Stars
- 32
- Forks
- 17
- Avg merge
- 12h 2m
- Merged PRs (30d)
- 3
Contributor guide
No contributing guide indexed for this repository
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 ReproNim/containers
-
ReproNim/containers#171 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
ReproNim/containers#169 ·
-
ReproNim/containers#160 · 1 reaction · 2 assignees ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
ReproNim/containers#155 ·
-
Add AIND containers Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
ReproNim/containers#144 · 1 comment ·
All issues in ReproNim/containers
Similar issues
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100