comparison: docs/data_processing/uploading_ancillary.rst
docs/data_processing/uploading_ancillary.rst
- changeset 47
- ea696c3c4cb8
- parent 37
- 4e3f530ac84e
- child 48
- 958ab1f5bd41
equal
deleted
inserted
replaced
| 46:5cb4da4bed26 | 47:ea696c3c4cb8 |
|---|---|
| 1 .. _uploading_ancillary: | 1 .. _uploading_ancillary: |
| 2 | 2 |
| 3 Uploading ancillary files | 3 Ancillary files |
| 4 ========================= | 4 =============== |
| 5 123 | 5 |
| 6 Together with your measurement data, you can submit ancillary files that will | |
| 7 be used in the processing procedure. The files that are currently supported | |
| 8 are **sounding files**, **overlap files**, and **lidar ratio files**. | |
| 9 | |
| 10 These files can be submitted either together with a measurement, using the | |
| 11 "Quick upload" form, or on their own, using the "Upload ancillary" form. Both | |
| 12 methods are equivalent and will not affect which files is used for processing | |
| 13 your measurements. The file that will be used are defined in the *measurement | |
| 14 file* using the appropriate attributes as described in the :ref:`netcdf_file` | |
| 15 section. | |
| 16 | |
| 17 If one of your measurements requires ancillary files for its processing, the | |
| 18 actual processing of the data will start only after all the required files | |
| 19 have been uploaded. The files that are missing will appear in the ancillary file | |
| 20 list with "Missing" status. When all these files have been uploaded the | |
| 21 processing of the measurement will start automatically. | |
| 22 | |
| 23 | |
| 24 Upload ancillary | |
| 25 ---------------- | |
| 26 In the "Upload ancillary" form you need to specify to submit at least one | |
| 27 ancillary file. | |
| 28 | |
| 29 Form fields | |
| 30 ~~~~~~~~~~~ | |
| 31 | |
| 32 Station (Required) | |
| 33 You need to specify the EARLINET station that is related to this file. In | |
| 34 most cases you will just have to select your station. | |
| 35 | |
| 36 Sounding file (Optional) | |
| 37 In this optional field you can submit a sounding file that will be used | |
| 38 by your measurements in the processing. The file needs to follow the netCDF | |
| 39 file format specified in the pdf file found in the :ref:`netcdf_file` section. | |
| 40 The file you submit will not be necessarily connected with the | |
| 41 submitted measurement; which sounding file will be used in the processing of | |
| 42 each measurement is specified in the measurement's file. The file you upload | |
| 43 will, nevertheless, remain on the SCC and will be used whenever needed. | |
| 44 | |
| 45 Overlap file (Optional) | |
| 46 In this optional field you can submit a overlap file that will be used | |
| 47 by your measurements in the processing. The file needs to follow the netCDF | |
| 48 file format specified in the pdf file found in the :ref:`netcdf_file` section. | |
| 49 The file you submit will not be necessarily connected with the | |
| 50 submitted measurement; which overlap file will be used in the processing of | |
| 51 each measurement is specified in the measurement's file. The file you upload | |
| 52 will, nevertheless, remain on the SCC and will be used whenever needed. | |
| 53 | |
| 54 Lidar ratio file (Optional) | |
| 55 In this optional field you can submit a lidar ratio file that will be used | |
| 56 by your measurements in the processing. The file needs to follow the netCDF | |
| 57 file format specified in the pdf file found in the :ref:`netcdf_file` section. | |
| 58 The file you submit will not be necessarily connected with the | |
| 59 submitted measurement; which lidar ratio file will be used in the processing | |
| 60 of each measurement is specified in the measurement's file. The file you | |
| 61 upload will, nevertheless, remain on the SCC and will be used whenever needed. | |
| 62 | |
| 63 Form Validation | |
| 64 ~~~~~~~~~~~~~~~ | |
| 65 | |
| 66 The aim of form validation is to detect errors in your submitted data as early | |
| 67 as possible. In this way you can save time by correcting errors before the | |
| 68 processing of your data fails. | |
| 69 | |
| 70 When the files are submitted the following checks are performed: | |
| 71 | |
| 72 * At least one file needs to be submitted. | |
| 73 | |
| 74 * The submitted measurement file should have the correct netCDF format. All | |
| 75 mandatory variables and attributes should be present in the file. All | |
| 76 variables and attributes should have the correct type (float, integer, etc). | |
| 77 | |
| 78 * A file with the same filename should not exist in the SCC or, if it exists, | |
| 79 it should have status "Missing" or "Error". If a file with the same filename | |
| 80 exists, and its status is "OK" the submitted file is rejected. | |
| 81 | |
| 82 | |
| 83 Browse ancillary files | |
| 84 ---------------------- | |
| 85 | |
| 86 You can browse existing and missing ancillary files in the "Ancillary files" | |
| 87 page of the Data processing sub menu. | |
| 88 | |
| 89 You can filter the results of the list using the **Filter** box above the form. | |
| 90 The filter searches for matches in all columns of the table, i.e you can use it | |
| 91 to filter the results by filename, stations, data, and status. | |
| 92 | |
| 93 You can view more information about the ancillary file following the link on the | |
| 94 name of the file. | |
| 95 | |
| 96 | |
| 97 View ancillary file page | |
| 98 ------------------------ | |
| 99 | |
| 100 In the ancillary file status page you can view more detailed information about | |
| 101 the selected file. The following info are provided. | |
| 102 | |
| 103 Status | |
| 104 The status of the file can have three values. **Ok** means that the file | |
| 105 has been uploaded successfully and is ready to be used in the processing. | |
| 106 **Missing** status means that one or more of the submitted measurements | |
| 107 have requested this file, but the file has not been submitted yet. An | |
| 108 **Error** file indicates that the file has been submitted but there was | |
| 109 an error while reading its content; you will need to correct its content | |
| 110 and resubmit the file. | |
| 111 | |
| 112 Interpolation | |
| 113 This indicates the interpolation type that will be used on the content of | |
| 114 the ancillary file. You can change the interpolation type in the admin | |
| 115 section following the "Edit in admin" link in the File actions sub menu. | |
| 116 | |
| 117 Station | |
| 118 The EARLINET station that is the related to this ancillary file | |
| 119 | |
| 120 Submitted on | |
| 121 The date and time that the file was submitted. If the file is missing, but is | |
| 122 required by an uploaded measurement, this date indicated the date and time | |
| 123 of the measurement upload. | |
| 124 | |
| 125 At the bottom part of the page you can see a list of **Related measurements**. | |
| 126 These are measurements that use the specific ancillary file for their | |
| 127 processing. | |
| 128 |
