forked from bossee-project/proposal
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathobjectives.tex
106 lines (83 loc) · 4.67 KB
/
objectives.tex
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
\eucommentary{1-2 pages}
\eucommentary{\emph{Describe the specific objectives for the project,
which should be clear, measurable, realistic and achievable within the
duration of the project. Objectives should be consistent with the expected
exploitation and impact of the project (see section 2).}}
\TODO{Desirable keywords: sustainability, impact, reproducibility,
interoperability, ...}
\noindent The aims and objectives of \TheProject are:
\begin{compactenum}[\textbf{Objective} 1:]
\item \label{aim:eosc}%
Develop an infrastructure for the EOSC-hub and the wider open
science community, that can be tailored and used to provide a
multitude of specific services on the EOSC to support open science
in a wide range of scientific domains and projects. This infrastructure
builds on the Jupyter project and ecosystem.
\item \label{aim:jupyter}%
Support and steer the Jupyter ecosystem, as a general purpose
toolbox for better science through interactive computing and
visualisation that supports the entire life-cycle of open science:
from initial exploration to publication, research and development in
industry, teaching, and outreach. In particular shape and develop
the Jupyter ecosystem of tools further so that they can become key
technology for the EOSC-hub.
\item \label{aim:jupyter-reusability}%
Extend the Jupyter project's capabilities to better support FAIR
data requirements. In particular, the archival of execution
environments to support re-usability of notebooks in the future
needs attention. Such notebooks may be published together with
publication manuscripts to detail the computation of published data
and figures, to address the Re-usable requirement of FAIR data.
\item \label{aim:jupyter-collaboration}%
Extend the Jupyter project's capabilities to better support
collaborative work, in particular enabling concurrent editing of a
document.
\item \label{aim:jupyter-widgets}%
Improve on the core Jupyter Widget libraries to better support advanced
use cases such as the case of large widgets state saved in the notebook, or
the use of Jupyter Interactive Widgets outside of Jupyter. This also includes
improvements to the tooling built around interactive widgets such as the
testing of widget packages.
\item \label{aim:demonstrators}%
Demonstrate and evaluate the value and versatility of the design and
the services building on it through applications to a number of
domains in academic research, research infrastructures, SMEs and for
the public sector, driven through our project partners. In
particular, demonstrators for research infrastructure facilities and
Photon Science (EuXFEL), SMEs (QuantStack, WildTreeTech), public
sector (Paul), academic research (UPSud), \ldots.
\TODO{Hans: Paul and all, please add your own domain above}
\item \label{aim:binderservice}%
Design and provide a pilot MyBinder service on EOSC-Hub as a service
that can be used immediately for EOSC-hub users from any domain to
support their reproducible open science and assess the importance of
this service for the future.
\item \label{aim:outreach-and-engagement}%
Reach out to researchers outside this project to encourage engagement
and exploitation of the EOSC-Hub and the Jupyter-based Open Science
Services for their research domains.
%Engaging a larger community will also make the
%future maintenance and development of the infrastructure more sustainable.
\end{compactenum}
\subsection*{Detailed Descriptions of Objectives}
\TODO{HF: I think the detailed description that follows below should
go into the work package description.}
\paragraph{Objective~\ref{aim:jupyter-widgets}: Jupyter Interactive Widgets}\
More than a collection of controls, Jupyter Interactive Widgets are a
framework, and a specified communication protocol to build upon.
Popular visualization libraries such as \emph{bqplot}, \emph{ipyvolume}, and
\emph{ipyleaflet} for 2-D, 3-D, and maps visualization are based upon Jupyter
Interactive Widgets.
We propose a number of improvements to the core Jupyter Widgets package.
\begin{itemize}
\item Improvement of the tooling for the testing of Jupyter Widget libraries.
\item Modernization of the core JavaScript package codebase.
\item Development of new controls to the core package.
\item Support for predefined rich widget layouts for simplified authoring of rich GUIs in Jupyter.
\item Better handling of large notebook state by allowing widgets to refer to external data sources.
\end{itemize}
\paragraph{Objective~\ref{aim:demonstrators}: Demonstrators}\
Objectives and impact will be measured using Key Performance
Indicators (KPI).
\TODO{Hans: Can we say something about sustainability? See commented
source in last item.}