1 / 27

Key points from ATW-2 for AST-8 Presented by B King

Key points from ATW-2 for AST-8 Presented by B King. Number one problem JULD_ASCENT_END must be filled in RT This is the number one priority for DACs to fix to enable progress on preparing a trajectory product. AST cochairs would like problem to be fixed by 2007 DMT.

pearl-jensen
Download Presentation

Key points from ATW-2 for AST-8 Presented by B King

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Key points from ATW-2 for AST-8Presented by B King

  2. Number one problem JULD_ASCENT_END must be filled in RT This is the number one priority for DACs to fix to enable progress on preparing a trajectory product. AST cochairs would like problem to be fixed by 2007 DMT. AST cochairs would like to see initial trajectory product that includes the majority of floats at AST in March 2007. DACs to report at next AST on steps they have taken to resolve problems.

  3. aomlapex Red circle is ascent_end Red plus is descent_start Solid blackis envelope

  4. bodcapex Red circle is ascent_end Red plus is descent_start Solid blackis envelope

  5. coriolis apex ascent_end should not equal earliest transmission Red circle is ascent_end Red plus is descent_start Solid blackis envelope

  6. aoml apex check start times Red circle is ascent_end Red plus is descent_start Solid blackis envelope

  7. jma apex problem at cyc 26 Red circle is ascent_end Red plus is descent_start Solid blackis envelope

  8. coriolis provor many missing data Red circle is ascent_end Red plus is descent_start Solid blackis envelope

  9. File consistency GDAC to introduce format checks on traj files (and enhanced checks on meta files) Run checks once per month; files to be flagged not rejected AIC monitor status & frequency of traj file problems DMT to define a mechanism for file inconsistencies to be logged and corrections monitored DMT to develop an action to identify and resolve improperly filled metafiles (examples: absent platform model, inconsistent drift pressures on ‘1 in 3’ park and profile)

  10. File consistency - continued APEX UP and DOWN parameters not defined in meta. DMT to resolve the problem , DACs to implement the solution. ATW-2 attendees to work with DACs to correct known problems. DACs to state if they anticipate difficulty (technical ? resource ?) in correcting problems as they are notified.

  11. Variable names /User Manual updates Variable name additions proposed to traj.nc to store results of trajectory calculations. DMT to discuss and approve/amend proposals. Updates and clarifications required to User Manual.

  12. Communication with ourselves and with users AIC to establish argo-dm-traj email list

  13. Progress since DMT-7 UK has a Masters student who will work on trajectories between 1 March and 30 September 2007 Tasks: Work with DACs to identify and correct problems Evaluate methods for surface extrapolation Generate a product: a set of improved traj.nc files

  14. Progress since DMT-7 Coriolis has a program in place to fill correct times for PROVOR floats Discussion with Coriolis on correct filling for APEXfloats CSIRO has addressed the problem; New files available;Not yet evaluated.

  15. csio apex Red circle is ascent_end Red plus is descent_start Solid blackis envelope

  16. jma apex Red circle is ascent_end Red plus is descent_start Solid blackis envelope

  17. Two points that didn’t get enough discussion on day 1 1) In meta: Fill APEX UP and DOWN in meta.nc When format working group agrees a way to code UP and DOWN into meta, DACs will be asked to rewrite meta.nc files In traj: please do not have missing cycle numbers(i) It is inconvenient if the set of CYCLE_NUMBERis incomplete, eg 0,0,0,1,1,1,1,4,4,4,4Insert dummy cycles to fill gap(ii) Every CYCLE_NUMBER should have a corresponding index in JULD_ASCENT_END etc More details in ATW2 report

  18. Proposed newRT filling oftraj.nc when thereare missing cycles New required entries in red

More Related