-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathproject_goals.html
197 lines (169 loc) · 9.07 KB
/
project_goals.html
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
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="generator" content="Docutils 0.19: https://docutils.sourceforge.io/" />
<title>Project goals — NeXDaTaS 1.0.0 documentation</title>
<link rel="stylesheet" type="text/css" href="_static/pygments.css" />
<link rel="stylesheet" type="text/css" href="_static/bootstrap-sphinx.css" />
<script data-url_root="./" id="documentation_options" src="_static/documentation_options.js"></script>
<script src="_static/jquery.js"></script>
<script src="_static/underscore.js"></script>
<script src="_static/_sphinx_javascript_frameworks_compat.js"></script>
<script src="_static/doctools.js"></script>
<script src="_static/sphinx_highlight.js"></script>
<link rel="index" title="Index" href="genindex.html" />
<link rel="search" title="Search" href="search.html" />
<link rel="next" title="NXDL extensions for data sources" href="design.html" />
<link rel="prev" title="Welcome to NeXDaTaS’s documentation!" href="index.html" />
<meta charset='utf-8'>
<meta http-equiv='X-UA-Compatible' content='IE=edge,chrome=1'>
<meta name='viewport' content='width=device-width, initial-scale=1.0, maximum-scale=1'>
<meta name="apple-mobile-web-app-capable" content="yes">
<script type="text/javascript" src="_static/js/jquery-1.12.4.min.js"></script>
<script type="text/javascript" src="_static/js/jquery-fix.js"></script>
<script type="text/javascript" src="_static/bootstrap-3.4.1/js/bootstrap.min.js"></script>
<script type="text/javascript" src="_static/bootstrap-sphinx.js"></script>
</head><body>
<div id="navbar" class="navbar navbar-default navbar-fixed-top">
<div class="container">
<div class="navbar-header">
<!-- .btn-navbar is used as the toggle for collapsed navbar content -->
<button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".nav-collapse">
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand" href="index.html">
NeXDaTaS</a>
<span class="navbar-text navbar-version pull-left"><b>1.0</b></span>
</div>
<div class="collapse navbar-collapse nav-collapse">
<ul class="nav navbar-nav">
<li class="dropdown globaltoc-container">
<a role="button"
id="dLabelGlobalToc"
data-toggle="dropdown"
data-target="#"
href="index.html">Site <b class="caret"></b></a>
<ul class="dropdown-menu globaltoc"
role="menu"
aria-labelledby="dLabelGlobalToc"><ul class="current">
<li class="toctree-l1 current"><a class="current reference internal" href="#">Project goals</a></li>
<li class="toctree-l1"><a class="reference internal" href="#the-importance-of-the-client">The importance of the client</a></li>
<li class="toctree-l1"><a class="reference internal" href="design.html">NXDL extensions for data sources</a><ul>
<li class="toctree-l2"><a class="reference internal" href="design.html#the-strategy-tag">The <code class="docutils literal notranslate"><span class="pre"><strategy></span></code> tag</a></li>
<li class="toctree-l2"><a class="reference internal" href="design.html#the-datasource-tag">The <code class="docutils literal notranslate"><span class="pre"><datasource></span></code> tag</a></li>
<li class="toctree-l2"><a class="reference internal" href="design.html#client-datasource"><em>CLIENT</em> datasource</a></li>
<li class="toctree-l2"><a class="reference internal" href="design.html#tango-datasource"><em>TANGO</em> datasource</a></li>
<li class="toctree-l2"><a class="reference internal" href="design.html#db-datasource"><em>DB</em> datasource</a></li>
<li class="toctree-l2"><a class="reference internal" href="design.html#pyeval-datasource"><em>PYEVAL</em> datasource</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="design.html#sequence-diagrams">Sequence diagrams</a></li>
</ul>
</ul>
</li>
<li class="dropdown">
<a role="button"
id="dLabelLocalToc"
data-toggle="dropdown"
data-target="#"
href="#">Page <b class="caret"></b></a>
<ul class="dropdown-menu localtoc"
role="menu"
aria-labelledby="dLabelLocalToc"><ul>
<li><a class="reference internal" href="#">Project goals</a></li>
<li><a class="reference internal" href="#the-importance-of-the-client">The importance of the client</a></li>
</ul>
</ul>
</li>
<li>
<a href="index.html" title="Previous Chapter: Welcome to NeXDaTaS’s documentation!"><span class="glyphicon glyphicon-chevron-left visible-sm"></span><span class="hidden-sm hidden-tablet">« Welcome to Ne...</span>
</a>
</li>
<li>
<a href="design.html" title="Next Chapter: NXDL extensions for data sources"><span class="glyphicon glyphicon-chevron-right visible-sm"></span><span class="hidden-sm hidden-tablet">NXDL extensio... »</span>
</a>
</li>
</ul>
<form class="navbar-form navbar-right" action="search.html" method="get">
<div class="form-group">
<input type="text" name="q" class="form-control" placeholder="Search" />
</div>
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
</div>
</div>
</div>
<div class="container">
<div class="row">
<div class="body col-md-12 content" role="main">
<section id="project-goals">
<h1>Project goals<a class="headerlink" href="#project-goals" title="Permalink to this heading">¶</a></h1>
<p>The aim of this project is to implement a Tango server that manages data
IO for synchrotron (and maybe neutron) beamlines. The server should
satisfy the following requirements</p>
<ul class="simple">
<li><p>remove responsibility for data IO
from the beamline control client</p></li>
<li><p>provide a simple configuration mechanism via NXDL</p></li>
<li><p>read data from the following sources without client interaction</p></li>
<li><p>SQL databases (MySQL, Postgres, Oracle, DB2, …)</p></li>
<li><p>other TANGO servers</p></li>
<li><p>JSON records (important for the interaction
with the client and SARDANA)</p></li>
<li><p>the first implementation of the server will be written in Python</p></li>
<li><p>the communication model of the first implementation will be strictly synchronous
(future version most probably will support other communication models too)</p></li>
<li><p>the control client software has full control over the behavior of the server via
TANGO commands</p></li>
<li><p>only low data-rate sources will be handled directly by the server.
High data-rate sources will write their data independently
and additional software will add this data to the Nexus file produced by
the server once the experiment is finished.</p></li>
</ul>
<p>The server should make it easy to implement control clients which write
Nexus files as the entire Nexus logic is kept in the server. Clients
only produce NXDL configurations or use third party tools for this job.
The first Python implementation of this server will serve as a proof of
concept.</p>
</section>
<section id="the-importance-of-the-client">
<h1>The importance of the client<a class="headerlink" href="#the-importance-of-the-client" title="Permalink to this heading">¶</a></h1>
<img alt="_images/system_layout.png" src="_images/system_layout.png" />
<p>All operations carried out on a beamline are orchestrated by the control
client (CC), a software operated by the beamline-scientist and/or a
user. Although the term client suggests that it is only a minor
component aside from all the hardware control servers, databases, and
whatever software is running on a beamline it is responsible for all the
other components and tells them what to do at which point in time. In
terms of an orchestra the CC is the director which tells each group of
instruments or individual artist what to do at a certain point in time.</p>
<p>It is important to understand the role of the CC in the entire software
system on a beamline as it determines who is responsible for certain
operations. The CC might be a simple single script running on the
control PC which can is configured by the user before start or it might
be a whole application of its own like SPEC or ONLINE. Historically it
is the job of the CC to write the data recorded during the experiment
(this is true at least for low rate data-sources). However, with the
appearance of complex data formats like Nexus the IO code becomes more
complex.</p>
</section>
</div>
</div>
</div>
<footer class="footer">
<div class="container">
<p class="pull-right">
<a href="#">Back to top</a>
</p>
<p>
© Copyright 2016, DESY, Jan Kotanski, Eugen Wintersberger, Halil Pasic, Maria-Teresa Núñez-Pardo-de-Vera.<br/>
Created using <a href="http://sphinx-doc.org/">Sphinx</a> 5.3.0.<br/>
</p>
</div>
</footer>
</body>
</html>