User Tools

Site Tools


devel:eubrewnetconfiguration

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
devel:eubrewnetconfiguration [2022/02/15 08:43]
jlsolano [Exclusion List]
devel:eubrewnetconfiguration [2023/09/20 14:07]
jlsolano [Temperature]
Line 1: Line 1:
 ====== Brewer Configuration constants ====== ====== Brewer Configuration constants ======
 ===== Configuration Upload ===== ===== Configuration Upload =====
-For a correct understanding of the Configuration Upload Interface, please take a look at the [[http://www.eubrewnet.org/​cost1207/​2015/​03/​04/​configuration-upload-intructions/​|Configuration Upload Instructions]] -- the behaviour of the form is described there.+For a correct understanding of the Configuration Upload Interface, please take a look at the [[http://​eubrewnet.aemet.es/​cost1207/​2015/​03/​04/​configuration-upload-intructions/​|Configuration Upload Instructions]] -- the behaviour of the form is described there.
  
 ===== Constants ===== ===== Constants =====
Line 421: Line 421:
 ==== UV response ==== ==== UV response ====
  
-table with one row for each wavelength (in Angströms) and its corresponding responsivity (in counts/​mW/​m<​sup>​2</​sup>/​nm). This information is provided by the ''​UVRJJJYY.BID''​ files.+The user has to provide a table with one row for each wavelength (in Angströms) and its corresponding responsivity (in counts/​mW/​m<​sup>​2</​sup>/​nm). ​
  
-This table is used to convert the raw counts measured by the Brewer to the irradiances (''​I'',​ in W/​m<​sup>​2</​sup>/​nm) ​shown in the level 1, 1.5, and 2 UV products+This information is included in the ''​UVRJJJYY.BID''​ files produced by the standard Brewer software. 
 + 
 +This table is used in the UV L1 product ​to convert the raw counts measured by the Brewer to irradiances (''​I'',​ in W/​m<​sup>​2</​sup>/​nm)
  
 ==== Temperature ==== ==== Temperature ====
  
-A field with a reference temperature (''​Tref'',​ in ºC), and table with one row for each wavelength (in Angströms) and the corresponding temperature dependence factor (''​Tdep'',​ in 1/​ºC). ​This information can be obtained by the experimental characterization described in [[https://​acp.copernicus.org/​articles/​8/​3369/​2008/​|Lakkala et al., Atmos. Chem. Phys., 8, 3369–3383,​ 2008]]+For the UV temperature correction, the user has to provide 
 + 
 +  * A field with a reference temperature (''​Tref'',​ in ºC), and 
 + 
 +  * A table with one row for each wavelength (in Angströms) and the corresponding temperature dependence factor (''​Tdep'',​ in 1/​ºC). ​ 
 + 
 +All this information can be obtained by the experimental characterization described in [[https://​acp.copernicus.org/​articles/​8/​3369/​2008/​|Lakkala et al., Atmos. Chem. Phys., 8, 3369–3383,​ 2008]]
  
 In the level 1.5 UV product, these data are used to calculate irradiances normalized to the reference temperature,​ ''​I(Tref) = I(T)/​[1+Tdep(T-Tref)]''​. In the level 1.5 UV product, these data are used to calculate irradiances normalized to the reference temperature,​ ''​I(Tref) = I(T)/​[1+Tdep(T-Tref)]''​.
  
 ==== Cosine Correction ==== ==== Cosine Correction ====
- 
-To calculate the cosine correction, we use a modified version of the [[https://​github.com/​pec0ra/​buvic|Brewer UV Irradiance Calculator (BUVIC)]] developed by Basile Maret and Julian Gröbner at the PMOD/WRC. BUVIC follows the method described in [[https://​acp.copernicus.org/​articles/​8/​3369/​2008/​|Lakkala et al., Atmos. Chem. Phys., 8, 3369–3383,​ 2008]] 
  
 In the configuration,​ the user can provide In the configuration,​ the user can provide
  
-* A table with five columns: angle (between 0 and 90 degrees), and angular responses in the N, S, W, and E directions (**as of February 2022, only the angular response in the N direction is used**) ​+  ​* A table with five columns: angle (between 0 and 90 degrees), and angular responses ​(measurements from the CR file normalized to the maximum value at 0 degrees) ​in the N, S, W, and E directions, see the next figure ​(**as of February 2022, only the angular response in the N direction is used**)
  
-* Fields with default values for the albedo, Angström'​s alpha and beta, and the cloud optical depth. These meteorological parameters will be used if no information for a specific day is provided in the following table.+{{ :​devel:​arf_measurement.png?​direct&​400 |}}
  
-A table with 5 columns: date (in YYYY-MM-DD format), ​albedo, Angström'​s alpha, Angström'​s ​beta, and cloud optical depth.+  ​Fields ​with default values for the albedo, Angström'​s alpha and beta, and the cloud cover. These meteorological parameters will be used if no information for a specific day is provided in the following table.
  
 +  * A table with 5 columns: date (in YYYY-MM-DD format), albedo, Angström'​s alpha, Angström'​s beta, and cloud cover. The cloud cover takes values from 0 to 1, and the cosine correction is only calculated for values lower than 0.9
  
 +These data are used to calculate the cosine correction in the level 2 UV product. For the calculation itself we use a modified version of the [[https://​github.com/​pec0ra/​buvic|Brewer UV Irradiance Calculator (BUVIC)]] developed by Basile Maret and Julian Gröbner at the [[https://​www.pmodwrc.ch/​en/​home/​|PMOD/​WRC]].
 ==== Exclusion List ==== ==== Exclusion List ====
  
-Finally, level 1.5 and 2.0 UV products ​can be filtered using a UV-specific [[http://rbcce.aemet.es/​dokuwiki/​doku.php?​id=devel:​eubrewnetconfiguration&#​exclusion_list1|Exclusion List]]+Finally, ​starting from the level 1.5 UV product, data can be filtered using a UV-specific [[http://eubrewnet.aemet.es/​dokuwiki/​doku.php?​id=devel:​eubrewnetconfiguration&#​exclusion_list1|Exclusion List]]
  
 ---- ----
Line 479: Line 487:
 As with any other parameter defined as a filter (see the documentation of the  [[codes:​ozoneproduct&#​level_15_realtime_observation|level 1.5 product]]), the effect of the Exclusion List can be checked using the process function with the &​rejected option, e.g: As with any other parameter defined as a filter (see the documentation of the  [[codes:​ozoneproduct&#​level_15_realtime_observation|level 1.5 product]]), the effect of the Exclusion List can be checked using the process function with the &​rejected option, e.g:
  
-http://rbcce.aemet.es/​eubrewnet/​data/​process/​O3L1_5?​brewerid=185&​date=2020-03-22&​enddate=2020-03-23&​rejected+http://eubrewnet.aemet.es/​eubrewnet/​data/​process/​O3L1_5?​brewerid=185&​date=2020-03-22&​enddate=2020-03-23&​rejected
  
 This will give a list of all the L1.5 individual measurements. If there are measurements affected by the Exclusion List, they will have a value greater or equal than 32 in the filter_flag field. This will give a list of all the L1.5 individual measurements. If there are measurements affected by the Exclusion List, they will have a value greater or equal than 32 in the filter_flag field.
  
-If the data has been completely processed, a call using the standard get function (e.g., http://rbcce.aemet.es/​eubrewnet/​data/​get.json/​O3L1_5?​brewerid=185&​date=2020-03-22&​enddate=2020-03-23) will omit all the measurements included in the Exclusion List.+If the data has been completely processed, a call using the standard get function (e.g., http://eubrewnet.aemet.es/​eubrewnet/​data/​get.json/​O3L1_5?​brewerid=185&​date=2020-03-22&​enddate=2020-03-23) will omit all the measurements included in the Exclusion List.
  
 ---- ----
Line 495: Line 503:
 **2)** If you just want to bypass some line of the exclusion list, you can pass the ''​allowtag=xxx''​ option, where ''​xxx''​ is (part) of a keyword in the comment of a exclusion range. **2)** If you just want to bypass some line of the exclusion list, you can pass the ''​allowtag=xxx''​ option, where ''​xxx''​ is (part) of a keyword in the comment of a exclusion range.
  
-For example, B#​185'​s data from the Arenosillo 2019 campaign has been added to the exclusion list using the following line:+For example, B#​185'​s data from the El Arenosillo 2019 campaign has been added to the exclusion list using the following line:
  
 <​code>​ <​code>​
Line 503: Line 511:
 So, if you try to open  So, if you try to open 
  
-http://rbcce.aemet.es/​eubrewnet/​data/​process/​O3L1_5?​brewerid=185&​date=2019-06-12&​enddate=2019-07-01&​format=text ​+http://eubrewnet.aemet.es/​eubrewnet/​data/​process/​O3L1_5?​brewerid=185&​date=2019-06-12&​enddate=2019-07-01&​format=text ​
  
 in your browser, you will not get any data. in your browser, you will not get any data.
Line 509: Line 517:
 However, if you add ''&​allowtag=campaign''​ to the URL, so that it looks like However, if you add ''&​allowtag=campaign''​ to the URL, so that it looks like
  
-http://rbcce.aemet.es/​eubrewnet/​data/​process/​O3L1_5?​brewerid=185&​date=2019-06-12&​enddate=2019-07-01&​format=text&​allowtag=campaign+http://eubrewnet.aemet.es/​eubrewnet/​data/​process/​O3L1_5?​brewerid=185&​date=2019-06-12&​enddate=2019-07-01&​format=text&​allowtag=campaign
  
 you will now get the campaign'​s data -- Eubrewnet has omitted the exclusion ranges which include the keyword ''​campaign''​ in the comment. you will now get the campaign'​s data -- Eubrewnet has omitted the exclusion ranges which include the keyword ''​campaign''​ in the comment.
  
 Note that, instead of ''​campaign'',​ you could have used ''​are2019''​ or ''​are''​ or ''​camp''​ -- Eubrewnet will check for incomplete keywords too. Note that, instead of ''​campaign'',​ you could have used ''​are2019''​ or ''​are''​ or ''​camp''​ -- Eubrewnet will check for incomplete keywords too.
 +
devel/eubrewnetconfiguration.txt · Last modified: 2024/03/25 16:00 by jlsolano