project status: year 1. milestones and deliverables year 1 contained: 25 milestones (from 78) 9...
Post on 02-Jan-2016
222 Views
Preview:
TRANSCRIPT
Milestones and Deliverables
Year 1 contained:
• 25 milestones (from 78)
• 9 deliverables (from 38)
Of these:
• 22 milestones and 7 deliverables completed successfully (3 tasks pending)
• Installation of new database hardware; transfer of UV database
• Web-page interface to the database
Main results
Main results
• Installation of new database hardware; transfer of UV database
• Web-page interface to the database• BASINT
Main results
• Installation of new database hardware; transfer of UV database
• Web-page interface to the database• New structures for auxiliary data
New symbols for data description line of multiple line data: ozone_column ( O3COL ; Dobson Units ; float ; )Column label for the ozone column in Dobson units snow_cover ( SNOWCVR ; ; int ; )Column label for snow cover flag (1: snow cover; 0: no snow cover; -1: don’tknow) cloud_amount ( CLD8 ; ; int ; )Column label for cloud amount in oktas (0: clear sky; 1: one okta or less ofcloud cover; … ; 8: complete overcast; 9: no data due to fog or snow flurry) sunshine_duration ( SUNT ; hours ; float ; )Column label for sunshine duration in decimal hours year_UTC ( UYEAR ; ; int ; [1900:2100] )
Column label for the year in Coordinated Universal Time month_UTC ( UMONTH ; ; int ; [1:12] )
Column label for the month in Coordinated Universal Time day_UTC ( UDAY ; ; int; [1:31] )
Column label for the day of the month in Coordinated Universal Time
SQL> desc ozone_info Name Null? Type ----------------------------------------- -------- ------------------ SUBMIT_ID NOT NULL NUMBER(8) REGISTERATION_ID NOT NULL NUMBER(5) OZONE_INFO_ID NOT NULL CHAR(14) INSTRUMENT_IDENTIFIER CHAR(20) ALTITUDE NOT NULL NUMBER(6,2) LATITUDE NOT NULL NUMBER(6,4) LONGITUDE NOT NULL NUMBER(7,4) ZONE_STD NUMBER(5,3) UNCERTAINTY_TIME VARCHAR2(100) UNCERTAINTY_TIME_SEC NUMBER(32) CALIBRATION_DATE DATE MODEL_IDENTIFIER CHAR(20) CALIBRATION_PROCEDURE_FILE VARCHAR2(20)
SQL> desc ozone_day Name Null? Type ----------------------------------------- -------- ------------------ OZONE_INFO_ID NOT NULL CHAR(14) DATE_UTC NOT NULL DATE OZONE_DAY_ID NOT NULL CHAR(14) OZONE_DAILY NUMBER(5,2)
SQL> desc ozone Name Null? Type ----------------------------------------- -------- ------------------ OZONE_DAY_ID NOT NULL CHAR(14) TIME_UTC NOT NULL NUMBER(7,5) SOLAR_ZENITH_ANGLE NUMBER(6,3) OZONE NOT NULL NUMBER(5,2)
Data types considered:
1. Ozone column (daily representative values and diurnal variation)2. Information on snow cover3. Cloud amount4. Sunshine duration
(Oracle structures and Flexstor formats for integrated irradiance already exist.)
Main results
• Installation of new database hardware; transfer of UV database
• Web-page interface to the database• New structures for auxiliary data• Statement of user requirements
Main results
• Installation of new database hardware; transfer of UV database
• Web-page interface to the database• New structures for auxiliary data• Statement of user requirements• Inventory of QC procedures
Main results
• Installation of new database hardware; transfer of UV database
• Web-page interface to the database• New structures for auxiliary data• Statement of user requirements• Inventory of QC procedures• Topography and surface inhomogeneties
Main results
• Installation of new database hardware; transfer of UV database
• Web-page interface to the database• New structures for auxiliary data• Statement of user requirements• Inventory of QC procedures• Topography and surface inhomogeneties• Reports on 3D modelling and flagging
WG1: Data analysis
• Progress in description of UV climatology [LAP, RIVM]
• Aerosol climatology for UV modelling [UG]
• Evaluation of the impact of atmospheric variability on long-term changes in UVR [FMI]
• Definition of optimal wavelength band and location for investigation of long-term changes in UVR [UH]
WG2: Database management
• Submission of approx. 15,000 days of UV data [BOKU et al.]
• Database reports [UG]
• Addition of structures for auxiliary data [FMI]
• Updated and validated metadata pages [UMIST]
WG2: Database management (continued)
• Installation of web-page interface for BASINT tools [BAS]
• Flagging of spectral irradiance for wavelength shifts and spectral anomalies [RIVM]
Month
1212
1515
1818
2121
2424
2727
3030
WG3: Data Flagging
5e. Outline of method for cloud-flagging algorithm [NPI]
6b. Description of method for the flaggingof atmospheric anomalies [NPI]
6a. Development & testing of methodsto identify erroneous values of spectral
UV irradiance [RIVM]
6d. Report on the method used in thedetection of natural spectral distortion [LAP]
6e. Report on analysis of wavelength-shift & spectral anomalies for subsets of
data in database[RIVM]
6g. Flagging of all valid spectra indatabase completed [RIVM]
6i. Report on methods for detectionof natural factors influencing spectral
measurements [LAP]
6j. Flagging of atmospheric anomaliesapplied to data with suitable ancillary
information [NPI]
6.2 Flagging of atmospheric anomalies[NPI]
6.1 Flagging spectral irradiance forwavelength shifts & spectral anomalies [RIVM]
6.4 Report on status and meaning ofall database flagging [LAP]
6h. flagging algorithmfor atmospheric anomalies made available
at the database [NPI]
5h. Beta version of cloud-flagging algorithm available for testing [NPI]
WG3: QA/QC
• Report on status & relevance of flagging within database [LAP]
• Recommendation on QA at sites [BAS]
• Quality audit of measuring sites [UG]
• Evaluation and distribution of QC tools [RIVM, UI]
• Development & application of cloud flagging algorithm [NPI]
WG4: Modelling
• Development, evaluation and installation of fast RT model [NPI]
• Algorithm for reconstruction of spectra from filter radiometers [UJF]
• Cast study on influence of topography and inhomogeneous surfaces [NILU]
top related