ROM SAF PTM18 IEEC, Barcelona

Slides:



Advertisements
Similar presentations
Design Validation CSCI 5801: Software Engineering.
Advertisements

Lectures on File Management
McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 20 Systems Operations and Support.
MP IP Strategy public Stateye Training (Getting Started) Please enable author’s notes for a textual description of the slides. A audio file.
Using Programmer-Written Compiler Extensions to Catch Security Holes Authors: Ken Ashcraft and Dawson Engler Presented by : Hong Chen CS590F 2/7/2007.
Database Design Concepts Info 1408 Lecture 2 An Introduction to Data Storage.
Chapter 1 Program Design
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
Regression testing Tor Stållhane. What is regression testing – 1 Regression testing is testing done to check that a system update does not re- introduce.
SEG Software Maintenance1 Software Maintenance “The modification of a software product after delivery to correct faults, to improve performance or.
Fruitful functions. Return values The built-in functions we have used, such as abs, pow, int, max, and range, have produced results. Calling each of these.
What is Sure BDCs? BDC stands for Batch Data Communication and is also known as Batch Input. It is a technique for mass input of data into SAP by simulating.
7 th TTG meeting – Trieste – 3-4 March, 2015 SeaDataNet tools, new developments IFREMER : M. Fichaut, A. Briand, M. Larour, T. Loubrieu, V. Tosello ALTRAN.
TOPIC R Software Maintenance, Evolution, Program Comprehension, and Reverse Engineering SEG4110 Advanced Software Design and Reengineering.
Software Metrics - Data Collection What is good data? Are they correct? Are they accurate? Are they appropriately precise? Are they consist? Are they associated.
Different options for the assimilation of GPS Radio Occultation data within GSI Lidia Cucurull NOAA/NWS/NCEP/EMC GSI workshop, Boulder CO, 28 June 2011.
Designing classes How to write classes in a way that they are easily understandable, maintainable and reusable 3.0.
System Development Life Cycle. The Cycle When creating software, hardware, or any kind of product you will go through several stages, we define these.
Software Development Software Testing. Testing Definitions There are many tests going under various names. The following is a general list to get a feel.
Module 2.4 Computer management 1. Contents Initial maintenance Setting up accounts Configuring the desktop Security settings Ongoing maintenance Adding.
Progress with migration to SVN Part3: How to work with g4svn and geant4tags tools. Geant4.
SE: CHAPTER 7 Writing The Program
Oracle Data Integrator Procedures, Advanced Workflows.
Problem Statement: Users can get too busy at work or at home to check the current weather condition for sever weather. Many of the free weather software.
The european ITM Task Force data structure F. Imbeaux.
Improving the Mars Thermal 1D Model E. Millour, A Colaitis, F. Forget EXM-AMSA PM6, 7th July 2011.
Partners’ Webinar 01/31/2013 Karol Jarkovsky Solution Architect Upgrading Kentico.
QA and Testing. QA Activity Processes monitoring Standards compliance monitoring Software testing Infrastructure testing Documentation testing Usability.
GRAS SAF AND RADIO OCCULTATION DATA K. B. Lauritsen 1, H. Gleisner 1, M. E. Gorbunov 2, F. Rubek 1, S. Syndergaard 1, H. Wilhelmsen 1 (1) Danish Meteorological.
11 GRAS SAF Status & Next Steps Kent B. Lauritsen Danish Meteorological Institute Copenhagen, Denmark Contents - Short introduction to the GRAS SAF.
The Software Development Process
I Power Higher Computing Software Development High Level Language Constructs.
02 August OraMonPlans 08/ August Topics Enhancements –OraMon DB redundancy layer –Compare and fix OraMon configurations –Expiry of historical.
Feb. 8, 2008 UHCO Graduate Course in MATLAB Core Programming Module Best Practices Core Grant Programming Module Best Practices (Coding Conventions) General.
20-1 Systems support is the on-going technical support for users, as well as the maintenance required to fix any errors, omissions, or new requirements.
SEG 4110 – Advanced Software Design and Reengineering Topic T Introduction to Refactoring.
Beginning Fortran Introduction 13 October 2009 *Black text on white background provided for easy printing.
10 th Argo data management 2009 Toulouse What is new at GDACs ?
Geant4 release 5.1 summary Gabriele Cosmo EP/SFT.
1 09/2003 Processing Library Update CF Checker – Script made available as a web based form on the BADC site -
Sequential Processing to Update a File Please use speaker notes for additional information!
Defensive Programming. Good programming practices that protect you from your own programming mistakes, as well as those of others – Assertions – Parameter.
Progression in KS3/4 Algorithms MONDAY 30 TH NOVEMBER SUE SENTANCE.
The information systems lifecycle Far more boring than you ever dreamed possible!
Maria Alandes Pradillo, CERN Training on GLUE 2 information validation EGI Technical Forum September 2013.
L1Calo Databases ● Overview ● Trigger Configuration DB ● L1Calo OKS Database ● L1Calo COOL Database ● ACE Murrough Landon 16 June 2008.
Measurement Model Refactoring
User-Written Functions
s2dverification Update meeting – 21/09/2015 Sprint review
Oracle Subledger Accounting
Eclipse Navigation & Usage.
Towards connecting geospatial information and statistical standards in statistical production: two cases from Statistics Finland Workshop on Integrating.
Outline RTQC goals to achieve Description of current proposal Tests
CVS revisions UML diagram
Agenda Control Flow Statements Purpose test statement
Ruth Anderson UW CSE 160 Winter 2017
Some Basics for Problem Analysis and Solutions
12 Product Configurator
Design and Programming
5 Tips for Upgrading Reports to v 6.3
Programming Logic and Design Fourth Edition, Comprehensive
Computer-System Architecture
Coding Concepts (Basics)
Software Design Lecture : 9.
Embedded System Development Lecture 13 4/11/2007
Regression testing Tor Stållhane.
Systems Operations and Support
COMP755 Advanced Operating Systems
Defensive Programming
End of day Calculator and special order parts tracking
Presentation transcript:

ROM SAF PTM18 IEEC, Barcelona 31-05-2016 DMI ROPP developments: Recent and coming updates to dmi_trunk Stig Syndergaard

Purpose of the dmi_trunk A well-maintained branch of ROPP Used at DMI as our main ROPP development branch (thus, it is our ‘trunk’) Usually the latest ROPP release + development made at DMI dmi_trunk is upgraded whenever a new ROPP is released: merge of new ROPP and current dmi_trunk dmi_trunk is the ROPP software that we use in operations (when we make a GPAC upgrade) Development work at DMI always take the starting point in dmi_trunk (typically making a branch from dmi_trunk and merge back when done) Currently at dmi_trunk_8.1 (ROPP 8.1 + DMI developments) Over time, we strive to keep dmi_trunk ≅ ROPP (facilitating next merges of ROPP and dmi_trunk) Developments in dmi_trunk should become part of a next ROPP release (possibly internal release; upon agreement with Met Office) Philosophy: if it is needed for us, then it is also useful for others Where things can be done in different ways, we always adhere to the way things are done in ROPP (to facilitate future merges) We regularly forward our changes to Met Office in advance of a ROPP GG meeting or new ROPP release

Recent updates to dmi_trunk Final adjustments for including ropp_pp_invert_tool.f90 into ropp_pp_occ_tool.f90 ropp_pp_invert_tool is now obsolete; ropp_pp_occ_tool processes from lev1b with -inv option Changes to ropp_pp_occ_tool.f90 and related subroutines Optionally calculate tangent points (lat_tp, lon_tp) to account for bending (thanks to Chris Burrows) Changes to occ_point.f90 and tangent_point.f90 Fixed problem with occultation point determination on an ellipsoid – error for north-south going GNSS-LEO lines was of the size of the difference between geographic and geocentric latitude (Simon later found a more mathematically correct solution, but it is not yet implemented) Minor change to ropp_pp_preprocess_cosmic.f90 Now returning fatal error (instead of just info) when navigation bit file is not found Change to ropp_fm_abel.f90 Now returns bending angles on all observational heights, also above the state vector top Change to ropp_pp_ionospheric_correction.f90 Now always using w_smooth as in ‘implementation from OCC’ (fixing smoothing bug #2) Minor changes to README.ropp, build_ropp, roppauto, roppconfig Included ropp_apps in installation scripts

Recent updates to dmi_trunk (cont.) Change to ropp_pp_types.f90 Longer strings for mfile, bfile, navfile (to be consistent with previous change in ropp_pp tools) Changes to ropp_io_read_ncdf_get.f90 Determine open loop bit based on ol_data_used flag, not on ol_data_available/rs_data_available Settings of PCD bits in ropp_io_read_ucardata_atmPhs and ropp_io_read_ucardata_atmPrf routines Change to ropp_io_assign.f90 Copying the %bg substructure of Roprof Changes to ropp_fm_bg2ro_1d.f90 Implemented forward-modeling to dry_temp. This required adding two new routines in ropp_fm/refrac_1d, changing the interfaces in ropp_fm.f90, and minor changes to two Makefile.am files. Now copying only height variables when initializing with the -l option, not the whole lev1b and lev2a structures New routines to initialize the Obs1dRefrac and Obs1dBangle structures when called with the -l option Minor changes to grib2bgrasc.f90 Now setting PCD bit 15 (background data) Now using fcperiod (lead time) from grib1 when interpolating in time (still debating on that one)

Recent updates to dmi_trunk (cont.) Change to ropp_apps_tph_tool.f90 Avoiding extra variables stored in Vlist to be lost Minor change to ropp_io_types.f90 Changed Level 2b shum valid range from 5 g/kg to 50 g/kg (still debating on that one, see #437) Minor changes to eum2ropp, ucar2ropp, ropp2ropp, and ropp_fm_bg2ro_1d No warnings (exit code 1) when using --no-ranchk or --no-zapem options

Coming updates to dmi_trunk Fixes to ropp_pp_occ_tool (problems originally detected with ropp_pp_invert_tool) Related to poor input data – the code needs to be able to handle them better (must not hang or give segmentation faults) (tickets #319, #332, #358, #374, #442) Possibly more fixes after looking into odd case from JGR paper by Wang et al. (ticket #344) More global attributes (harmonizing with our level 3 products) Introducing description, product_id, product_name, product_acronym, product_version, etc. (ticket #342) Possibly more changes to eum2ropp Level 1a parts in connection with our reprocessing (ticket #370) Possibly changes to ropp_fm_bg2ro Problems with using the -l option (output on observation levels) when input level 1b levels are severely out of order (ticket #334) Changes to ropp_pp_occ_tool To make sure that profiles now failing to process because of e.g., stat.opt. problems are still processed, but with relevant QC parameters written to the NetCDF output file (tickets #317, #441) Possibly more changes to ropp_pp_occ_tool subroutines Subroutines related to the wave optics part to deal with kink at 25 km (no ticket yet)