docs/data_processing/introduction.rst

changeset 44
c37ebdf6d03f
parent 42
01cfcb387e7f
equal deleted inserted replaced
43:bda5e7160bf6 44:c37ebdf6d03f
39 measurement. The *channels* that are defined in the file should be the 39 measurement. The *channels* that are defined in the file should be the
40 ones defined in the selected system. The uploading of ancillary files or the 40 ones defined in the selected system. The uploading of ancillary files or the
41 selection of categories for the measurement are optional. 41 selection of categories for the measurement are optional.
42 42
43 When the file is uploaded, it is checked if it conforms to the needed 43 When the file is uploaded, it is checked if it conforms to the needed
44 netcdf format. The check guarantees that the mandatory variables are present 44 netCDF format. The check guarantees that the mandatory variables are present
45 in the file and that they have the correct format. Note that the check is not 45 in the file and that they have the correct format. Note that the check is not
46 exhaustive, in the sense it does not guarantee that the file is able to be 46 exhaustive, in the sense it does not guarantee that the file is able to be
47 correctly processed; the aim of this check is to detect as early as possible 47 correctly processed; the aim of this check is to detect as early as possible
48 common problems in the file. If some errors are found, the file will be 48 common problems in the file. If some errors are found, the file will be
49 deleted from the server. 49 deleted from the server.
57 #. **The ancillary file names should be defined in the submitted measurement 57 #. **The ancillary file names should be defined in the submitted measurement
58 file**. In contrast to the measurement files, the file name of the ancillary 58 file**. In contrast to the measurement files, the file name of the ancillary
59 files should follow a specified format, described in :ref:`netcdf_file`. In 59 files should follow a specified format, described in :ref:`netcdf_file`. In
60 brief, a sounding file should have a name rs_YYYYMMDDccNN.nc, a overlap file 60 brief, a sounding file should have a name rs_YYYYMMDDccNN.nc, a overlap file
61 a name ov_YYYYMMDDccNN.nc, and a lidar ratio file a name lr_YYYYMMDDccNN.nc, 61 a name ov_YYYYMMDDccNN.nc, and a lidar ratio file a name lr_YYYYMMDDccNN.nc,
62 where YYYY is a year, MM is the month, DD is the day, cc is the earlinet 62 where YYYY is a year, MM is the month, DD is the day, cc is the EARLINET
63 station call sign and NN is a number. 63 station call sign and NN is a number.
64 64
65 #. **The ancillary files should be uploaded on the server**. The uploading can be 65 #. **The ancillary files should be uploaded on the server**. The uploading can be
66 done in the same form as before, or independently in the "Upload ancillary" 66 done in the same form as before, or independently in the "Upload ancillary"
67 form. If an ancillary file required by a measurement is not present in the 67 form. If an ancillary file required by a measurement is not present in the

mercurial