Radial and orbital excitations of static-light mesons

We present results for the spectrum of static-light mesons from Nf=2 lattice QCD. These results were obtained using all-to-all light quark propagators on an anisotropic lattice, yielding an improved signal resolution when compared to more conventional lattice techniques. With a light quark mass close to the strange quark, we have measured the splittings between the ground-state S-wave static-light meson and higher excitations. We attempt to identify the quantum numbers of the excited states in the context of the reduced spatial symmetries of the lattice.Comment: 14 pages, 10 figure

D5.5: ESDW guidelines and programme V

This deliverables outlines E-CAM&rsquo;s Extended Software DevelopmentWorkshop (ESDW) programme for 2020/2021. In&nbsp;addition, it provides the most recent guidelines for the organisation of these events, including: the scope of training at ESDW events the structure of ESDWs; the timeline for the organization of an ESDW; the capture of lectures at ESDWs; the role of the E-CAM online training infrastructure; the role of E-CAM programmers at ESDW events; the concept of a module in E-CAM and its acceptance criteria. The present document is an updated version of deliverable D5.4 [https://doi.org/10.5281/zenodo.2586966] submitted in March 2019, on the guidelines for&nbsp;content, structure and output for our ESDWs. These guidelines are intended to be a living document which evolves to&nbsp;reflect experience gained in running the ESDWs and thus they are subject to further revision based on the outcomes&nbsp;of each year&rsquo;s activities, with the present document being the fifth, and last iteration. This updated version of the&nbsp;guidelines, valid from April 2020 to March 2021, will help to ensure that the workshops run consistently across the&nbsp;scientific Work Packages (WPs) and meet the quality standards for E-CAM software.&nbsp; In addition to refining the guidelines for our ESDWs, this deliverable also analyses the profile of the participants to&nbsp;our ESDWs and the results of our satisfaction surveys. Specifically, we will report on the analysis of&nbsp; the participants profile (country of origin, gender, qualification) the satisfaction surveys training needs highlighted by the participants of our ESDWs. When appropriate, output from these surveys has been used to refine the reported guidelines.</p

E-CAM Software Platform II

<p>Update on E-CAM software tools and platforms which includes:<br> - the E-CAM library of software modules and interfaces;<br> - end users portal (to access E-CAM’s resources, make requests for software developments, register for events);<br> - web infrastructure for teaching tools.</p

Scientific Software Management in Real Life: Deployment of EasyBuild on a Large Scale System

Managing scientific software stacks has traditionally been a manual task that required a sizeable team with knowledge about the specifics of building each application. Keeping the software stack up to date also caused a significant overhead for system administrators as well as support teams. Furthermore, a flat module view and the manual creation of modules by different members of the teams can end up providing a confusing view of the installed software to end users. In addition, on many HPC clusters the OS images have to include auxiliary packages to support components of the scientific software stack, potentially bloating the images of the cluster nodes and restricting the installation of new software to a designated maintenance window.To alleviate this situation, tools like EasyBuild help to manage a large number of scientific software packages in a structured way, decoupling the scientific stack from the OS-provided software and lowering the overall overhead of managing a complex HPC software infrastructure. However, the relative novelty of these tools and the variety of requirements from both users and HPC sites means that such frameworks still have to evolve and adapt to different environments. In this paper, we report on how we deployed EasyBuild in a cluster with 45K+ cores (JURECA). In particular, we discuss which features were missing in order to meet our requirements, how we implemented them, how the installation, upgrade, and retirement of software is managed, and how this approach is reused for other internal systems. Finally, we outline some enhancements we would like to see implemented in our setup and in EasyBuild in the future