... | ... | @@ -6,7 +6,9 @@ The basic data unit for our archive is an observation, within the database obser |
|
|
|
|
|
The properties shared by an observation are used to find the observations within the archive. This means that the definition of observations needs to be granular enough to ensure that only strongly related measurements are grouped within in one observation. On the other hand observation descriptions also need to be generic enough that a query is able yields a small enough amount of results to not overwhelm a potential user.
|
|
|
|
|
|
Files within one observation should share common properties, such as proximity in time or wavelength, while sufficient distance in such parameters warrants the definition of a new observation.
|
|
|
Files within one observation should share common properties, such as proximity in time or wavelength, while sufficient distance in such parameters warrants the definition of a new observation. See the exmple of a GRIS observation data set from 2019:
|
|
|
|
|
|
![observation](uploads/9cfc10712b83009f7b5c89c46eb97f2d/observation.png)
|
|
|
|
|
|
## Case Study for Observation Segmentation: BBI
|
|
|
The data aquisition framework of BBI does not explicitly mark files as belonging to certain observations. Nevertheless the concept of observations can be imposed on the data and reconstructed from the files. BBI observes a feature on the sun for a period of time specified by the user, cycling through four different wavelength filters every couple of seconds. When a new feature is focused with the telescope, there will be a brief period during which the instrument does not record images. These breaks can be used to separate observations, making a collection of images with consecutive timestamps and identical wavelengths the group of files used to build observations for bbi.
|
... | ... | |