-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathglossary.tex
107 lines (86 loc) · 6.87 KB
/
glossary.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
107
\makeglossaries
\newglossaryentry{LOFAR}
{
name=LOFAR,
description={The LOw Frequency ARray: A large, low-frequency aperture synthesis radio telescope}
}
\newglossaryentry{HBA}
{
name=HBA,
description={The High Band Array is an array of LOFAR antennas sensitive to 110-240MHz. Each lofar station in the Netherlands has 48 HBA elements, with core stations having two separate sub-arrays of 24; while international stations have 96 HBA elements. The naming schele of these antenasis as such: LLNNNHBAS, where LL is the location (CS for core stations, RS for remote stations, and the ISO 3166-1 2-letter country code for the international stations); NNN is the station number, starting at 000, HBA/LBA denotes whether it's a HBA or LBA antenna and S refers to the core station sub-array}
}
\newglossaryentry{HTC}
{
name=HTC,
description={High Throughput Computing, as opposed to High Performance Computing (\Gls{HPC}), focuses on minimizing the time taken processing large amounts of data by using techniques in streaming, parallelizing and distributing many small jobs on a cluster }
}
\newglossaryentry{LoTSS}
{
name=LoTSS,
description={The LOFAR Two-Meter Sky Survey is a whole-sky study of the low-frequency radio sky at 120-168MHz. LoTSS is composed of a broad, Tier 1, survey of the entire sky, as well as deeper tiers targeted at specific fields of interest }
}
\newglossaryentry{Subband}
{
name=Subband,
description={Broadband LOFAR observations are stored in separate 'Subbands', splitting the frequency range into several individual files, before storing at the Long Term Archive. Depending on the observation mode, one observation can have 230-480 Subbands. This splitting makes it easier for users to request, download and process a fraction of observation's entire bandwidth}
}
\newglossaryentry{HPC}
{
name=HPC,
description={High Performance Computing, as opposed to High Throughput Computing (\Gls{HTC}), refers to computation on one or multiple machines with many, fast CPUS; large quantities of RAM and fast disks. Often HPC jobs are done on clusters where multiple of these machines are connected with a fast network used to pass messages and to synchronize workloads
}}
\newglossaryentry{visibilities}
{
name={visibilities},
description={Radio Astronomers use the term `UV plane' or `visibilities' interchangably to refer to the Fourier Transform of the final image. Each baseline of an aperture synthesis telescope corresponds to one measurement in this space. The letters U and V refer to the two orthogonal components of a baseline with respect to an observation's phase center. The $u$ and $v$ vectors are defined in a plane orthogonal to the direction towards the phase center, and are typically in units of wavelength. To obtain an image, the UV data needs to be `cleaned' by iteratively removing the point spread function of the telescope}
}
\newglossaryentry{Grid}
{
name={Grid},
description={Grid computing refers to massively parallel distributed computing introduced in the '90s to tackle the processing challenges processing data from the Large Hadron Collider. A computational grid is a set of compute nodes connected with a high throughput connection, common job scheduler and shared, distributed storage. The computational and storage resources in a Grid are federated, and users are provided a share of those resources by a managing authority }
}
\newglossaryentry{GridLRT}
{
name={GRID\_LRT},
text={GRID\_LRT},
description={GRID\_LRT is the GRID LOFAR Reduction Tools package. This software consists of a set of tools to easily create and launch processing jobs on a distributed infrastructure. It includes tools to manage LOFAR data stored on the grid filesystem. These tools make it possible to quickly integrate processing scripts with a high throughput environment, accelerating bottleneck steps in LOFAR processing }
}
\newglossaryentry{AGLOW}
{
name={AGLOW},
description={AGLOW is a combination of Apache Airflow with GRID\_LRT. This integration allows LOFAR users to build and launch massively parallel workflows
}}
\newglossaryentry{dCache}{
name={dCache},
description={dCache is a system for storing and retrieving large amounts of data, distributed across heterogenous servers. dCache provides a common virtual filesystem, while also allows data to be located on varied storage devices including SSDs, spinning disks and magnetic tape }
}
\newglossaryentry{VOMS}
{
name=VOMS,
description={The Virtual Organization Membership Service is a service that manages the access to data and computational resources provided to each Grid user. It handles authentication and authorisation of job launching and access to data on the grid filesystem. More information can be found at \url{https://italiangrid.github.io/voms/} }
}
\newglossaryentry{CouchDB}
{
name=CouchDB,
description={CouchDB is a document-based eventually consistent database, that we use to store processing information for distributed jobs. Each CouchDB document corresponds to a single distributed job, and contains a full description of the job required to run on a worker node. As jobs run, they update their status in the CouchDB document, which can be accessed by users through their browsers or a Python client}
}
\newglossaryentry{CVMFS}
{
name=CVMFS,
description={The CERN VM Filesystem is a virtually mounted filesystem that is used to distribute software on multiple clusters, cluster nodes and individual machines. CVMFS allows an institute to host a portable installation of their software, which is distributed and cached by other CVMFS clients. The software is cached locally on the worker nodes as a FileSystem in Userspace (FUSE) module }
}
\newglossaryentry{demix}
{
name=demix,
description={Demixing data is a processing step which removes the effects of bright off-axis sources. Because the LOFAR telescope is sensitive to sources away from its phase center, when a bright radio source is close to the observation, it contributes to the data and needs to be removed. Typically the brightest radio sources removed are called the A-team sources, and their contribution is removed using a well-known model of the source and the distance between the source and the observation's phase center
}}
\newglossaryentry{PiCaS}
{
name=PiCaS,
description={A framework to manage the status and metadata of distributed jobs on a central \Gls{CouchDB} server. This server is accessed through HTTP by processing jobs, to update their progress, or download metadata. Additionally, users can access it through their browser or python client to create, launch or reset processing jobs }
}
\newglossaryentry{srm}
{
name=srm,
description={Storage Resource Manager, a system to co-ordinate data storage. This system defines the protocols for referencing data on a distributed system, accessing metadata and changing data locality (e.g., moving from tape to disk). }
}