Version 27.1 by marissadiazpier on 2022/05/13 13:59
Show last authors
1 (% class="row" %)
2 (((
3 (% class="col-xs-12 col-sm-8" %)
4 (((
5 = [[image:banner.png||alt="EBRAINS at the service of the scientific research community."]] =
6
7 = EBRAINS SLU at the service of the scientific research community. =
8
9 SLU was created to anchor technical developments within the EBRAINS Community’s needs, through the combined understanding of both the scientific nature of the problems to be addressed and the technical capacities or constraints (to overcome) of the Infrastructure.
10
11 = What can I find here? =
12
13 (((
14 * SLU description.
15 * SLU objectives, goals, and activities.Tools for the identification of the community’s needs.
16 * Tools and contacts for Expanding the EBRAINS Community.
17 * Technical coordination across SCs.
18 )))
19
20 == Description ==
21
22 SLU Combines an understanding of both the scientific nature and the technical capabilities of the EBRAINS infrastructure.
23
24 Due to the complexity of EBRAINS infrastructure, we synthesize and summarize EBRAINS services to provide a guide for the scientist in using or adapting their research to it.
25
26
27 As described for EBRAINS
28
29 The SLU will act at the interfaces between work plans, and those between Science and Infrastructure activities. It will structure and trigger cross-Service Category (SC) developments foreseen around self-contained projects, to enforce comprehensive solutions that respect the principle of service composability, i.e., to systematically bring the EBRAINS services together in a range of typical and specific contexts.
30
31 The selected projects will prioritize, functional connections of key services with the aim of supporting the development of workflows spanning the breadth of neural data, models, and functions, highlighting the holistic perspective promoted by Flagship.
32
33 == SLU objectives, goals, and activities. ==
34
35 === Objectives ===
36
37 * Transform scientific description into technical requirement analysis.
38 * Support the development of workflows.
39 * Span the breadth of neural data, models, and functions.
40 * Facilitate the identification of requirements and scientific needs.
41
42 === Goals ===
43
44 * Empower the scientific community to take ownership of the services offered, fulfilling EBRAINS’ ambition of digitizing neuroscience.
45 * Help EBRAINS development teams in transforming scientific needs into technical requirements.
46 * Structure and trigger self-contained projects resulting in integrated and composable workflows and services.
47
48 === Activity ===
49
50 (% style="text-align:center" %)
51 [[image:1637146688078-285.png]]
52
53
54 * The SLU acts at the interfaces between different WPs’ work plans, and those between Science and Infrastructure activities.
55 * Find the best way helping showcases with process definitions and diagramatic tools.
56 * SLU makes possible interaction between technical and scientific teams.
57 * Profiling needs and guidance for integrated workflows
58 * Uses the knowhow and past experience of user cases to improve service integration.
59 * Structure and trigger cross-Service Category (SC) developments foreseen around self-contained projects to enforce comprehensive solutions that respect the principle of service composability, i.e., to systematically bring the EBRAINS services together in a range of typical and specific contexts.
60 * Asist selected projects to prioritize functional connections of key services.
61 * Support the development of workflows spanning the breadth of neural data, models, and functions, highlighting the holistic perspective.
62 * (((
63 = Who has access? =
64 )))
65 * EBRAINS members.
66 * Non-EBRAINS members: everyone interested in using an specific EBRAINS service.
67 * All HBP affiliates.
68 * (((
69
70 )))
71 )))
72
73
74 (% class="col-xs-12 col-sm-4" %)
75 (((
76 {{box title="**Contents**"}}
77 {{toc/}}
78 {{/box}}
79
80 [[image:EBRAINS logos_yellow_green.png]]
81 )))
82 )))