Version 21.1 by marissadiazpier on 2022/01/04 17:40

Hide last authors
marissadiazpier 5.1 1 (% class="row" %)
marissadiazpier 1.1 2 (((
marissadiazpier 5.1 3 (% class="col-xs-12 col-sm-8" %)
marissadiazpier 1.1 4 (((
marissadiazpier 18.2 5 = [[image:banner.png||alt="EBRAINS at the service of the scientific research community."]] =
6
marissadiazpier 18.3 7 = EBRAINS SLU at the service of the scientific research community. =
marissadiazpier 1.1 8
marissadiazpier 19.1 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.
marissadiazpier 6.2 10
marissadiazpier 5.1 11 = What can I find here? =
12
13 * (((
marissadiazpier 12.1 14 SLU description.
marissadiazpier 1.1 15 )))
marissadiazpier 5.1 16 * (((
marissadiazpier 19.1 17 SLU objectives, goals, and activities.
marissadiazpier 5.1 18 )))
marissadiazpier 12.1 19 * Tools for the identification of the community’s needs.
20 * Tools and contacts for Expanding the EBRAINS Community.
marissadiazpier 19.1 21 * Technical coordination across SCs.
marissadiazpier 1.1 22
marissadiazpier 19.1 23 == Description ==
marissadiazpier 1.1 24
marissadiazpier 19.1 25 SLU Combines understanding of both the scientific nature and the technical capabilities of the EBRAINS infrastructure.
26
marissadiazpier 20.2 27 Due to the complexity of EBRAINS infrastructure we synthesize and summarize EBRAINS services to provide a guide to scientist in using or adapting their research into it.
marissadiazpier 19.1 28
marissadiazpier 20.2 29 (% style="color:#1a202c; font-family:inherit; font-size:23px" %)As described on SG3 Agreement
marissadiazpier 19.1 30
31 (% style="text-align: justify;" %)
32 The SLU will act at the interfaces between different WPs’ 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.
33
34 The selected projects will prioritize, in the early stages of SGA3, 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 the Flagship.
35
36
37 (% style="text-align:center" %)
38 [[image:1637146332681-540.png]]
39
40
41 == SLU objectives, goals, and activities. ==
42
marissadiazpier 20.2 43 === Objectives ===
marissadiazpier 19.1 44
marissadiazpier 20.1 45 * Transform scientific description in technical requirement analysis.
marissadiazpier 19.1 46 * Supporting the development of workflows.
47 * Span the breadth of neural data, models, and functions.
marissadiazpier 20.1 48 * Facilitates the identification of requirements and scientific needs.
marissadiazpier 19.1 49
marissadiazpier 20.2 50 === Goals ===
marissadiazpier 19.1 51
52 * Empower the scientific community to take ownership of the services offered, fulfilling EBRAINS’ ambition of digitising neuroscience.
marissadiazpier 5.1 53 * Help EBRAINS development teams into transforming scientific needs into technical requirements.
marissadiazpier 20.1 54 * Structure and trigger self contained projects resulting in integrated and composable workflows and services.
marissadiazpier 1.1 55
marissadiazpier 20.2 56 === Activity ===
marissadiazpier 6.2 57
marissadiazpier 12.1 58 (% style="text-align:center" %)
59 [[image:1637146688078-285.png]]
60
marissadiazpier 18.3 61
marissadiazpier 6.2 62 * The SLU act at the interfaces between different WPs’ work plans, and those between Science and Infrastructure activities.
marissadiazpier 12.2 63 * (((
64 Find the best way Helping showcases with process definitions and diagramatic tools.
65 )))
66 * (((
67 Making possible the interaction between technical teams and scientific teams.
68 )))
69 * (((
70 Profiling needs and guidance for integrated workflows
71 )))
72 * (((
73 Using knowhow and past experience of user cases to improve service integration.
74 )))
marissadiazpier 6.2 75 * 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.
76 * Asist selected projects to prioritize functional connections of key services.
77 * Support the development of workflows spanning the breadth of neural data, models, and functions, highlighting the holistic perspective.
78
marissadiazpier 1.1 79 = Who has access? =
80
marissadiazpier 5.1 81 * EBRAINS members: everyone  WP1 - WP9
82 * non-EBRAINS members: everyone interested in using an specific EBRAINS service.
83 * (((
84 All HBP affiliates during SGA3 (Viewers)
marissadiazpier 1.1 85 )))
marissadiazpier 5.1 86 )))
marissadiazpier 1.1 87
88
89 (% class="col-xs-12 col-sm-4" %)
90 (((
91 {{box title="**Contents**"}}
92 {{toc/}}
93 {{/box}}
94
marissadiazpier 18.2 95 [[image:EBRAINS logos_yellow_green.png]]
marissadiazpier 1.1 96 )))
97 )))