level 2 ocean salinity
Download
Skip this Video
Download Presentation
Level 2 Ocean Salinity

Loading in 2 Seconds...

play fullscreen
1 / 10

Level 2 Ocean Salinity - PowerPoint PPT Presentation


  • 72 Views
  • Uploaded on

Level 2 Ocean Salinity. 16-17 May 2013. v600 status v610 planning & schedule Slim-line UDP & improved DAP. v600 status. L2OS Post-FAT delivery 28 February 2013 L1OP FAT end April 2013 CCB v600 baseline May 2013: L1 & L2 product specifications will be updated Processing TDS

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Level 2 Ocean Salinity' - daphne-craig


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
level 2 ocean salinity

Level 2 Ocean Salinity

16-17 May 2013

v600 status

v610 planning & schedule

Slim-line UDP & improved DAP

slide2

v600 status

  • L2OS Post-FAT delivery 28 February 2013
  • L1OP FAT end April 2013
  • CCB v600 baseline May 2013: L1 & L2 product specifications will be updated
  • Processing TDS
  • G-POD L1OP processing started(?), includes JT’s OS set of S. Pacific orbits (?)
    • L1OP products expected in G-POD by end of May for analysis in June -> QWG 4/5 July
    • IDEAS to process 1 month (which?) L1c -> L2 SM & OS, to check AUX_DGGRFI post-processor
    • QWG to evaluate L1 v600, maybe approve hexagonal full cross-pol G-matrix for v610
  • DPGS installation TBD
slide3

v610 planning & schedule

  • Planned changes
    • Slim-line UDP, improved DAP – specification needed now
    • TEC from Stokes3 – approved at QWG#10, implemented, needs verification
    • OTT post-processor (OTTPP) – implementation on-going, will need verification
  • Proposed schedule
    • modify L2OS to generate AUX_DTBXY for OTTPP by mid-May 2013 (done)
    • implement OTTPP by mid-June 2013
    • QWG #11 approval of L2OS v610 baseline (need preliminary results by 4/5 July 2013)
    • process 1 month (same as DGGRFI test?) L1c (v504/v600?) for OTTPP/A3TEC verification
    • start June, finish end August -> ESL (use L1c May 2011)
    • pre-delivery for schema verification & orchestration tests early July 2013
    • ESL analysis (Argo/ISAS collocation) of 1 month of new UDP/DAP during September 2013
    • FAT end September 2013; L1OP v610 ???
    • QWG#12 October 2013?
    • v610 in DPGS late 2013, full reprocessing February 2014???
slide4

Slim-line UDP & improved DAP

  • Motivation
    • UDP includes too many flags & fields – confusing to users
    • UDP should be simplified so users are easily able to extract good quality data
    • DAP should be improved so it is easier to retrieve grid point data:
    • grid point records are variable length because they include measurement data ->
    • processing DAP takes a long time
  • Actions
    • Move flags/fields from UDP to DAP
    • which fields are useful for users?
    • which flags are essential for users?
    • Restructure DAP into block of all grid point data, followed by block of all measurement data
    • users/ESL can read just the grid point data (fixed size) & ignore measurements
    • all measurement data is still available if required
slide5

Improving the DAP

n x grid points:

ID

priors & posts

flags

fields

n x grid points:

ID

priors & posts

flags

fields

Fixed block size grid points

  • v600 DAP

Variable block size grid points

m x measurements:

flags

fields

deltaTB

TBgal

n x grid points:

ID

m x measurements:

flags

fields

deltaTB

TBgal

TBrough

...

Variable block size measurements

v610 DAP

slide6

Improving the UDP

n x grid points:

ID, lat, long, x_swath, time

science flags

Geophysical priors?

RFI probability

Tb 42.5? (nominal model retrieval)

  • Science flags
    • Land/sea/coast, ice?
    • Hi/lo SSS, SST, WS
  • Geophysical retrievals
    • M1: SSS, UN10, VN10, SST, TEC
    • M2 (?): SSS, SST, WS, TEC
    • M3: SSS, WS,TEC
    • M4: Acard, SST
    • Sigmas on retrieved parameters
    • Quality index per model
  • Geophysical priors (from ECMWF)?
    • SST, UN10, VN10, WS
  • RFI probability
  • TB 42.5?
  • xx/yy/hh/vv & sigmas

per model:

retrieved parameters & sigmas

retrieval quality index

retrieval quality flags

Quality flags

Fg_ctrl_good_quality

  • Fg_ctrl_poor_geophysical
  • Fg_ctrl_poor_retrieval
slide7

UDP v600 quality flags

  • Fg_ctrl_poor_retrieval
    • Fg_ctrl_range,
    • Fg_ctrl_sigma,
    • Fg_ctrl_chi2, Fg_ctrl_chi2_P,
    • Fg_ctrl_marq, Fg_ctrl_reach_maxiter, Fg_ctrl_retrieval_failed
  • Fg_ctrl_poor_geophysical
    • Fg_ctrl_many_outliers,
    • Fg_ctrl_sunglint, Fg_ctrl_moonglint,
    • Fg_ctrl_num_meas_low,
    • Fg_ctrl_sc_suspect_ice, Fg_ctrl_sc_rain
    • Recall that filters in AUX_CNFOSF define which flags are propagated into summary flags
    • (Fg_ctrl_poor_retrieval, Fg_ctrl_poor_geophysical)
slide8

Proposed UDP v610 quality flags

  • Fg_ctrl_poor_retrieval
    • Fg_ctrl_range, – what should the valid range be for SSS (20-40, 25-40?)
    • Fg_ctrl_sigma,
    • Fg_ctrl_chi2_P, (ignore Fg_ctrl_chi2)
    • Fg_ctrl_marq, Fg_ctrl_reach_maxiter (ignore Fg_ctrl_retrieval_failed: will set SSS = -999)

SSS ~20 psu

Amazon plume August 2013, BEC

slide9

Proposed UDP v610 quality flags

  • Fg_ctrl_poor_retrieval
    • Fg_ctrl_range,
    • Fg_ctrl_sigma, – ignore?
    • Fg_ctrl_chi2_P,
    • Fg_ctrl_marq, Fg_ctrl_reach_maxiter

Fg_ctrl_sigma, – set on only 2% of grid points (mainly Arctic) - BEC

slide10

Proposed UDP v610 quality flags

  • Fg_ctrl_poor_retrieval
    • Fg_ctrl_range, Fg_ctrl_sigma(?), Fg_ctrl_chi2_P,
    • Fg_ctrl_marq, Fg_ctrl_reach_maxiter
  • Fg_ctrl_poor_geophysical
    • Fg_ctrl_many_outliers, Fg_ctrl_sunglint, Fg_ctrl_moonglint, Fg_ctrl_num_meas_low
    • (ignore Fg_ctrl_sc_suspect_ice, Fg_ctrl_sc_rain – very low impact on retrievals) - agreed
  • Fg_ctrl_good_quality
    • Fg_ctrl_poor_retrieval = 0 and Fg_ctrl_poor_geophysical = 0 and x_swath < 360 km and Dg_af_fov >= 130 and Fg_ctrl_suspect_RFI = 0
    • (x_swath < 360 similar to Dg_af_fov >= 130) – but Dg_af_fov is just a counter of L1c AFFOV flag, so includes border/belt/braces measurements (border measurements not used)
ad