Code suitability for Leonardo
Yes. The PyTorch/MONAI/CUDA stack is fully compatible with the A100 GPUs of the BOOSTER partition.
Technical evaluation
1 saved evaluation · Revision 71c0f5e8fee9
Direct answers from the automatic evaluation
Yes. The PyTorch/MONAI/CUDA stack is fully compatible with the A100 GPUs of the BOOSTER partition.
Partially. Base libraries are available; framework has been previously tested and verified by the applicant on the system.
Yes. Requested node hours (4,500) are within the cap and the 12-month duration is sufficient for the proposed optimization tasks.
High quality. The proposal identifies specific HPC bottlenecks and provides a clear, technically sound plan for optimization and scaling.
The project meets all technical and resource constraints of the Development call, with a sound technical plan and verified implementation readiness.
The complete saved technical evaluation
Final Decision: ACCEPTED
1. Are the codes to be used suitable for Leonardo's architecture? Yes. The project utilizes a standard deep learning stack (PyTorch, MONAI, NumPy, CUDA) that is fully compatible with the NVIDIA A100 GPUs on the Leonardo BOOSTER partition. The use of SIREN and Persistent Homology libraries is also compatible with the system's GPU and CPU architecture.
2. Is the code installed on Leonardo?
Partially.
While the specific research code (CARAVEL) is not a pre-installed system module, the applicant has explicitly verified that a functional PyTorch DDP implementation of the framework has already been tested and executed on Leonardo. The underlying libraries (PyTorch, CUDA) are available via the cineca-ai module.
3. Are the proposed targets feasible within the allocation time? Yes. The requested 4,500 node hours are within the fixed cap for Development calls. The project's objectives—optimizing MoE routing, implementing topology-aware supervision, and benchmarking scaling efficiency—are realistic for the 12-month duration and the requested resources.
4. Technical data quality and conclusions The technical data provided is of high quality. The applicant demonstrates a deep understanding of both the scientific challenges (vascular topology) and the HPC bottlenecks (MoE routing overhead, DDP synchronization, and GPU memory). The workplan is clear, and the performance targets (e.g., $\ge 60\%$ strong-scaling efficiency) are measurable and realistic.
5. Reasons for final classification The application is ACCEPTED because it meets all technical requirements of the Development call. The resource request is exactly at the cap (4,500 node hours) and does not exceed it. The software stack is fully compatible, the technical approach is sound, and the project is already in a functional state on the target hardware.
| Questions | Direct answer | Evidence/comment |
|---|---|---|
| Are the codes suitable for Leonardo's architecture? | Yes | PyTorch/MONAI/CUDA compatible with A100 GPUs. |
| Is the code installed on Leonardo? | Partially | Framework tested on Leonardo; base libraries available via cineca-ai. |
| Are the proposed targets feasible within the allocation time? | Yes | 4,500 node hours $\le$ cap; 12-month duration is adequate. |
| What are the technical-data quality conclusions? | High Quality | Clear objectives, identified bottlenecks, and realistic KPIs. |
| What are the reasons for final classification? | ACCEPTED | All technical and resource constraints met; high implementation readiness. |
The project aims to develop and optimize a computational framework for learning population-level cerebrovascular atlases from 3D Magnetic Resonance Angiography (MRA). It builds upon the VITAL framework, utilizing continuous neural implicit representations (SIREN) and a Mixture-of-Experts (MoE) architecture. The primary technical goals are to incorporate topology-aware supervision via persistent homology to ensure vascular connectivity and to optimize the distributed training workflow on HPC systems.
The workplan is technically sound, focusing on resolving specific bottlenecks such as MoE routing overhead and GPU memory consumption. The project is highly feasible, as the team has already established a functional multi-node pipeline on Leonardo. All resource requests are within the limits of the Development call, and the software stack is fully compatible with the BOOSTER partition.
Verdict: ACCEPTED Summary: The software stack is standard and fully compatible with the A100 architecture. Evidence: PyTorch, MONAI, and CUDA are natively supported on Leonardo BOOSTER.
| Component | Applicant version or assumption | Partition | Result | Key condition | Source URL |
|---|---|---|---|---|---|
| PyTorch | Latest/Stable | BOOSTER | COMPATIBLE | Standard | https://pytorch.org/ |
| MONAI | Latest/Stable | BOOSTER | COMPATIBLE | PyTorch-based | https://monai.io/ |
| CUDA | 11.x / 12.x | BOOSTER | COMPATIBLE | Ampere Arch | https://developer.nvidia.com/ |
| SIREN | PyTorch-based | BOOSTER | COMPATIBLE | Standard | N/A |
| TDA/Gudhi | CPU-based | BOOSTER | COMPATIBLE | Standard | https://gudhi.inria.fr/ |
Verdict: ACCEPTED Summary: Resource requests are within all call-specific caps. Evidence: - Node hours: 4,500 / 4,500 (100% of cap) - Storage: 5 TB / 10 TB (50% of cap) - Data Transfer: 2 TB (within daily reference) - Memory: 256 GB total usage is well within the 512 GiB per node limit.
Verdict: ACCEPTED Summary: High-quality technical proposal with a clear optimization path. Evidence: The project identifies specific HPC bottlenecks (MoE routing, DDP synchronization) and proposes concrete solutions (batched execution, precomputation).
The evaluation across all three technical dimensions (Code Compatibility, Feasibility, and Technical Details) resulted in an ACCEPTED status.
Following the fail-safe logic: All sub-agents returned ACCEPTED $\rightarrow$ Final Decision: ACCEPTED.
torch.cuda.amp to maximize the efficiency of A100 Tensor Cores.High. All technical requirements are met, and the applicant has already demonstrated functional code on the target system.