changeset
Typos correction
Thu, 21 Oct 2021 12:37:45 +0200
- author
- Giuseppe D'Amico <giuseppe.damico@imaa.cnr.it>
- date
- Thu, 21 Oct 2021 12:37:45 +0200
- changeset 133
- 3a3dd5f91db4
- parent 132
- d20e02efcd2c
- child 134
- e50ad6a54b7b
Typos correction
| docs/administration/product_channel_connections.rst | file | annotate | diff | comparison | revisions |
--- a/docs/administration/product_channel_connections.rst Thu Oct 21 12:19:16 2021 +0200 +++ b/docs/administration/product_channel_connections.rst Thu Oct 21 12:37:45 2021 +0200 @@ -12,20 +12,22 @@ For example, from the schema defining the usecase 5 of Raman backscatter product we find that 4 channels need to be linked: -- 2 elastic channels (one for near range and another for the far range - elTnr and elTfr) -- 2 Raman channels (again one for near range and one for the far range vrRN2nr of vrRN2fr). +- 2 elastic channels (one for near range and another for the far range - *elTnr* and *elTfr*) +- 2 Raman channels (again one for near range and one for the far range *vrRN2nr* of *vrRN2fr*). -Lidar channels are linked to a particular product by using the tab 'Product/channel connections' available in each product settings page (from admin section). To enstablish the link two channel characteristic should be provided: +Lidar channels are linked to a particular product by using the tab 'Product/channel connections' available in each product settings page (from admin section). To make the link two channel characteristics should be provided: - channel ID - Signal Type -The channel ID is automatically provided when you select on the small maggnifying glass available on the right of channel ID field (tab Product/channel connections) and select the channel you want to use in the pop up list (if the channel ID to be included is already known it is possible to provide it there directly). +The channel ID is automatically provided when you click on the small magnifying glass available on the right of channel ID field (tab Product/channel connections) and select the channel you want to use in the pop up list (if the channel ID to be included is already known it is possible to type it directly). -The signal type should be selected among the available options according to the role of the specific channel in the product calculation. To facilitate the consistency between the definition of signal type and what is required by the selected product usecase, the input channels reported in each usecase schema are named as the available signal types. Coming back to the example of the usecase 5 of Raman backscatter, for the near range and far range elastic channels the signal type "elTnr" and "elTfr" should be used respectively. In the same way for the near range and far range Raman channel the signal type "vrRN2nr" and "vrRN2fr" should be used. +The signal type should be selected among the available options according to the role of the specific channel in the product calculation. To facilitate the consistency between the definition of signal type and what is required by the selected product usecase, the input channels reported in each usecase schema are named according to the available signal types. + +Coming back to the example of the usecase 5 of Raman backscatter, for the near range and far range elastic channels the signal types *elTnr* and *elTfr* should be used. In the same way for the near range and far range Raman channels the signal types *vrRN2nr* and *vrRN2fr* should be selected. .. warning:: - If the definition of the channels in "Product/channel connections" is not consistent with what expected according to the selected product usecase, an error reporting inconsistent product adefinition is reported by ELPP module. + If the definition of the channels in "Product/channel connections" is not consistent with what expected from the specified product usecase, an error reporting inconsistent product definition is reported by ELPP module. Sygnal types are defined as it follows:
