codes:eubrewnet_report
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
codes:eubrewnet_report [2018/03/23 15:35] ilias |
codes:eubrewnet_report [2018/03/23 15:45] ilias [4.4. Configuration versioning] |
||
|---|---|---|---|
| Line 50: | Line 50: | ||
| ===== 2. General description ===== | ===== 2. General description ===== | ||
| - | In Figure 1 there is a simplified diagram of the Eubrewnet system. The system works using Hypertext Transfer Protocol (HTTP)([[https://www.google.com/url?q=https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol&sa=D&ust=1521821549665000&usg=AFQjCNHYmkYGoGrsH4S14LfX_7ZDGpCMaA|https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol]]), the outer layer of which is a HTTP proxy. This proxy attends external requests and redirects them to the appropriate subsystem which can be: | + | In **Figure 1** there is a simplified diagram of the Eubrewnet system. The system works using Hypertext Transfer Protocol (HTTP)([[https://www.google.com/url?q=https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol&sa=D&ust=1521821549665000&usg=AFQjCNHYmkYGoGrsH4S14LfX_7ZDGpCMaA|https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol]]), the outer layer of which is a HTTP proxy. This proxy attends external requests and redirects them to the appropriate subsystem which can be: |
| * The website of Eubrewnet: Attends the user requests and shows visual information. It also provide links to access the information in the database and performs product generation tasks on demand. | * The website of Eubrewnet: Attends the user requests and shows visual information. It also provide links to access the information in the database and performs product generation tasks on demand. | ||
| Line 70: | Line 70: | ||
| ==== Import module ==== | ==== Import module ==== | ||
| - | This module is the basis of the entire project. It is responsible for verifying the validity of each file obtained in the acquisition module and then store the desired information in the database. This module consists by four sub-modules described above. A schematic diagram of this process is shown in Figure 2. | + | This module is the basis of the entire project. It is responsible for verifying the validity of each file obtained in the acquisition module and then store the desired information in the database. This module consists by four sub-modules described above. A schematic diagram of this process is shown in **Figure 2**. |
| {{ :codes:image2.png |}}**Figure 2:** Schematic diagram of the import Module | {{ :codes:image2.png |}}**Figure 2:** Schematic diagram of the import Module | ||
| Line 97: | Line 97: | ||
| ===== 3. Interface ===== | ===== 3. Interface ===== | ||
| - | The interface of the Eubrewnet webpage is presented in the following figures. An interactive map shows the stations which provide data by one or more Brewers. The user can choose a station either from the map (Figure 3) or from a list (Figure 4). As already explained, registered users have more options. | + | The interface of the Eubrewnet webpage is presented in the following figures. An interactive map shows the stations which provide data by one or more Brewers. The user can choose a station either from the map (**Figure 3**) or from a list (**Figure 4**). As already explained, registered users have more options. |
| + | |||
| + | | {{ :codes:image5.png |}} || {{:codes:image8.png}} | | ||
| + | **Figure 3:** The interactive map of the Eubrewnet webpage for (a) non-registered and (b) registered users. | ||
| - | | {{ :codes:image5.png |}} || {{:codes:image8.png}} |**Figure 3:** The interactive map of the Eubrewnet webpage for (a) non-registered and (b) registered users. | ||
| {{:codes:image3.png}}**Figure 4:** The list of Brewers. | {{:codes:image3.png}}**Figure 4:** The list of Brewers. | ||
| - | When a station has been selected, then additional options and information appear for the particular station and instruments (Figure 5). | + | When a station has been selected, then additional options and information appear for the particular station and instruments (**Figure 5**). |
| {{:codes:image6.png}}**Figure 5:** Information for the Brewer operating at Thessaloniki. | {{:codes:image6.png}}**Figure 5:** Information for the Brewer operating at Thessaloniki. | ||
| Line 110: | Line 112: | ||
| - | ===== 4. Products ===== | + | ===== 4. Products ===== |
| As already discussed, three products are available: TOC, UV and AOD. The generation of the TOC product is already operative while the generation of the UV and AOD products is still under development. There are three different levels of the products (1.0, 1.5 and 2.0). Levels 1.5 and 2.0 are available to the public, while level 1.0 is available only to the registered users. Raw data (which could be described as Level 0) are stored in the database, though graphical information is not available through the web page. Though, registered users can download raw data using proper functions (see Section 5.5). In general, a higher product level means a more reliable product. | As already discussed, three products are available: TOC, UV and AOD. The generation of the TOC product is already operative while the generation of the UV and AOD products is still under development. There are three different levels of the products (1.0, 1.5 and 2.0). Levels 1.5 and 2.0 are available to the public, while level 1.0 is available only to the registered users. Raw data (which could be described as Level 0) are stored in the database, though graphical information is not available through the web page. Though, registered users can download raw data using proper functions (see Section 5.5). In general, a higher product level means a more reliable product. | ||
| Line 160: | Line 162: | ||
| [[https://www.google.com/url?q=http://rbcce.aemet.es/dokuwiki/doku.php?id%3Ddevel:eubrewnetconfiguration%23brewer_configuration_constants&sa=D&ust=1521821549678000&usg=AFQjCNHmymYyBfT1KVobElXc3sFglIRJkw|http://rbcce.aemet.es/dokuwiki/doku.php?id=devel:eubrewnetconfiguration#brewer_configuration_constants]] | [[https://www.google.com/url?q=http://rbcce.aemet.es/dokuwiki/doku.php?id%3Ddevel:eubrewnetconfiguration%23brewer_configuration_constants&sa=D&ust=1521821549678000&usg=AFQjCNHmymYyBfT1KVobElXc3sFglIRJkw|http://rbcce.aemet.es/dokuwiki/doku.php?id=devel:eubrewnetconfiguration#brewer_configuration_constants]] | ||
| - | The TOC configuration constants have to be updated after a new calibration of the instrument (usually every ~2 years) or after important changes in its operational characteristics. Occasionally, update of the station configuration constants may be also necessary. Proper tools have been developed and are available to the users so that they can update the configuration constants in an easy way ([[https://www.google.com/url?q=http://www.eubrewnet.org/cost1207/2015/03/04/configuration-upload-intructions/&sa=D&ust=1521821549679000&usg=AFQjCNFwHvVISTkrx1wv97UvCKoAaMBtNw|http://www.eubrewnet.org/cost1207/2015/03/04/configuration-upload-intructions/]]). A flowchart of the TOC configuration change procedure is shown in Figure 6, while in Figure 7 the interface through which the operator can update the TOC configuration constants is presented. | + | The TOC configuration constants have to be updated after a new calibration of the instrument (usually every ~2 years) or after important changes in its operational characteristics. Occasionally, update of the station configuration constants may be also necessary. Proper tools have been developed and are available to the users so that they can update the configuration constants in an easy way ([[https://www.google.com/url?q=http://www.eubrewnet.org/cost1207/2015/03/04/configuration-upload-intructions/&sa=D&ust=1521821549679000&usg=AFQjCNFwHvVISTkrx1wv97UvCKoAaMBtNw|http://www.eubrewnet.org/cost1207/2015/03/04/configuration-upload-intructions/]]). A flowchart of the TOC configuration change procedure is shown in **Figure 6**, while in **Figure 7** the interface through which the operator can update the TOC configuration constants is presented. |
| - | {{:codes:image2.png}}Figure 6: Generalized flowchart of the TOC configuration change procedure | + | {{:codes:image2.png}}**Figure 6:** Generalized flowchart of the TOC configuration change procedure |
| - | {{:codes:image1.png}}Figure 7: Interface of the TOC configuration tool | + | {{:codes:image1.png}}**Figure 7:** Interface of the TOC configuration tool |
| Different sets of configuration constants correspond to different periods (Figure 7). When a user is logged in, he/she should select whether he/she wants to modify an existing set of configuration constants or to add a new one (for a new period). Then the user can either upload a file with all the needed information or change the information he/she wants by hand. The corresponding tools and procedures for UV and AOD will be more complicated since a larger amount of information has to be provided by the user. More information regarding the configuration versioning can be found in: | Different sets of configuration constants correspond to different periods (Figure 7). When a user is logged in, he/she should select whether he/she wants to modify an existing set of configuration constants or to add a new one (for a new period). Then the user can either upload a file with all the needed information or change the information he/she wants by hand. The corresponding tools and procedures for UV and AOD will be more complicated since a larger amount of information has to be provided by the user. More information regarding the configuration versioning can be found in: | ||
codes/eubrewnet_report.txt · Last modified: 2022/10/20 07:57 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 3.0 Unported
