comparison: docs/data_processing/uploading_measurements.rst
docs/data_processing/uploading_measurements.rst
- changeset 44
- c37ebdf6d03f
- parent 43
- bda5e7160bf6
- child 45
- 156eaee2f510
equal
deleted
inserted
replaced
| 43:bda5e7160bf6 | 44:c37ebdf6d03f |
|---|---|
| 20 In this field you have to select the measurement file that will be processed. | 20 In this field you have to select the measurement file that will be processed. |
| 21 The file has to be in the specific format described in :ref:`netcdf_file`. | 21 The file has to be in the specific format described in :ref:`netcdf_file`. |
| 22 | 22 |
| 23 Sounding file (Optional) | 23 Sounding file (Optional) |
| 24 In this optional field you can submit a sounding file that will be used | 24 In this optional field you can submit a sounding file that will be used |
| 25 by your measurements in the processing. The file needs to follow the netcdf | 25 by your measurements in the processing. The file needs to follow the netCDF |
| 26 file format specified in the pdf file found in the :ref:`netcdf_file` section. | 26 file format specified in the pdf file found in the :ref:`netcdf_file` section. |
| 27 The file you submit will not be necessarily connected with the | 27 The file you submit will not be necessarily connected with the |
| 28 submitted measurement; which sounding file will be used in the processing of | 28 submitted measurement; which sounding file will be used in the processing of |
| 29 each measurement is specified in the measurement's file. The file you upload | 29 each measurement is specified in the measurement's file. The file you upload |
| 30 will, nevertheless, remain on the SCC and will be used whenever needed. | 30 will, nevertheless, remain on the SCC and will be used whenever needed. |
| 31 | 31 |
| 32 Overlap file (Optional) | 32 Overlap file (Optional) |
| 33 In this optional field you can submit a overlap file that will be used | 33 In this optional field you can submit a overlap file that will be used |
| 34 by your measurements in the processing. The file needs to follow the netcdf | 34 by your measurements in the processing. The file needs to follow the netCDF |
| 35 file format specified in the pdf file found in the :ref:`netcdf_file` section. | 35 file format specified in the pdf file found in the :ref:`netcdf_file` section. |
| 36 The file you submit will not be necessarily connected with the | 36 The file you submit will not be necessarily connected with the |
| 37 submitted measurement; which overlap file will be used in the processing of | 37 submitted measurement; which overlap file will be used in the processing of |
| 38 each measurement is specified in the measurement's file. The file you upload | 38 each measurement is specified in the measurement's file. The file you upload |
| 39 will, nevertheless, remain on the SCC and will be used whenever needed. | 39 will, nevertheless, remain on the SCC and will be used whenever needed. |
| 40 | 40 |
| 41 Lidar ratio file (Optional) | 41 Lidar ratio file (Optional) |
| 42 In this optional field you can submit a lidar ratio file that will be used | 42 In this optional field you can submit a lidar ratio file that will be used |
| 43 by your measurements in the processing. The file needs to follow the netcdf | 43 by your measurements in the processing. The file needs to follow the netCDF |
| 44 file format specified in the pdf file found in the :ref:`netcdf_file` section. | 44 file format specified in the pdf file found in the :ref:`netcdf_file` section. |
| 45 The file you submit will not be necessarily connected with the | 45 The file you submit will not be necessarily connected with the |
| 46 submitted measurement; which lidar ratio file will be used in the processing | 46 submitted measurement; which lidar ratio file will be used in the processing |
| 47 of each measurement is specified in the measurement's file. The file you | 47 of each measurement is specified in the measurement's file. The file you |
| 48 upload will, nevertheless, remain on the SCC and will be used whenever needed. | 48 upload will, nevertheless, remain on the SCC and will be used whenever needed. |
| 50 Categories (Optional) | 50 Categories (Optional) |
| 51 You can assign a number of categories to the uploaded measurement. The | 51 You can assign a number of categories to the uploaded measurement. The |
| 52 categories you assign can be lated changed in the in the "Station Admin" | 52 categories you assign can be lated changed in the in the "Station Admin" |
| 53 section of the site. You can select multiple categories by holding down the | 53 section of the site. You can select multiple categories by holding down the |
| 54 "Control" key (PC) or "Command" key (MAC) while selecting. | 54 "Control" key (PC) or "Command" key (MAC) while selecting. |
| 55 | |
| 56 | |
| 57 Form Validation | |
| 58 --------------- | |
| 59 | |
| 60 | 55 |
| 61 .. note:: | 56 .. note:: |
| 62 | 57 |
| 63 Uploading the measurement file can take considerable time, depending on | 58 Uploading the measurement file can take considerable time, depending on |
| 64 the size of the file and the speed of your Internet connection. In the | 59 the size of the file and the speed of your Internet connection. In the |
| 72 A progress indicator is built it. | 67 A progress indicator is built it. |
| 73 | 68 |
| 74 IE 9- | 69 IE 9- |
| 75 No progress bar is available (as far as we know). | 70 No progress bar is available (as far as we know). |
| 76 | 71 |
| 72 | |
| 73 Form Validation | |
| 74 --------------- | |
| 75 | |
| 76 The data you submit in the form are check in two stages. | |
| 77 | |
| 78 Before you submit the form | |
| 79 ~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
| 80 | |
| 81 Before you submit the form the following checks are performed: | |
| 82 | |
| 83 * All the necessary fields (i.e. "system" and "data file") need to be submitted. | |
| 84 | |
| 85 * The ancillary file names have to be in the appropriate format described | |
| 86 in :ref:`netcdf_file`. In brief, a sounding file should have a name | |
| 87 rs_YYYYMMDDccNN.nc, a overlap file a name ov_YYYYMMDDccNN.nc, and a lidar ratio | |
| 88 file a name lr_YYYYMMDDccNN.nc, where YYYY is a year, MM is the month, DD is | |
| 89 the day, cc is the EARLINET station call sign and NN is a number. | |
| 90 | |
| 91 | |
| 92 After you submit the form | |
| 93 ~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
| 94 | |
| 95 After you submit the form: | |
| 96 | |
| 97 * The uploaded **data file** needs to have a unique name. | |
| 98 | |
| 99 * The **measurement id** defined in the file should *not* exist in the SCC. | |
| 100 | |
| 101 * All channels declared in the measurement file should correspond to declared | |
| 102 channels in the SCC. | |
| 103 | |
| 104 * The submitted measurement file should have the correct netCDF format. All | |
| 105 mandatory variables and attributes should be present in the file. All | |
| 106 variables and attributes should have the correct type (float, integer, etc). | |
| 107 This check is not exhaustive, and it is possible that some errors are **not** | |
| 108 detected. For example "conditionally" mandatory variables are not checked | |
| 109 (as, for example "LR_Input", that is mandatory if elastic backscatter retrievals | |
| 110 have to be done). | |
| 111 | |
| 112 If ancillary files are submitted | |
| 113 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
| 114 | |
| 115 Additionally, if ancillary files are also uploaded, the following checks are | |
| 116 performed: | |
| 117 | |
| 118 * The submitted measurement file should have the correct netCDF format. All | |
| 119 mandatory variables and attributes should be present in the file. All | |
| 120 variables and attributes should have the correct type (float, integer, etc). | |
| 121 | |
| 122 * A file with the same filename should not exist in the SCC or, if it exists, | |
| 123 it should have status "Missing" or "Error". If a file with the same filename | |
| 124 exists, and its status is "OK" the submitted file is regected. |
