Version 2 (modified by djlea, 9 years ago) (diff)

Last edited Timestamp?

Author : Daniel Lea

ticket : #869

Branch : dev_2802_OBStools


This change is to add some OBS tools for working with the observation operator input and output:

One example is fbcomb which rebuilds feedback files produced in multiprocessor runs. Other tools are those to convert files from enact, coriolis, bufr or SLA to standard feedback format.

The other part of the work would be to update the documentation to describe these tools.

There is a possibility that some work may result from the NEMO-Assim meeting which will take place by visioconference on Thursday 13 October, from 14:00 to 17:00 with the following participants:

Eric Blayo, Claire Lévy; Gurvan Madec; Christian Ethe; Pierre-Antoine Bouttier; franck vigilant; Arthur Vidard; Benedicte Lemieux; Claire Chauvin; Jean-Michel Brankart; Pierre Brasseur; Jacques Verron; Elisabeth Remy; Eric Dombrowsky; Charles-Emmanuel Testut; Anthony Weaver; Olivier Titaud; Isabelle Mirouze; keith haines; Kristian Mogensen; Bell, Mike; Lea, Daniel; Hao Zuo; Simona Masina; Srdjan Dobricic; Andrea Storto Martin, Matthew; Benshila Benshila; Eric Blayo


Note many of these tests are not applicable since there are no changes to the NEMO code. The changes are simply to add some useful OBS tools and to update the documentation.

Testing could consider (where appropriate) other configurations in addition to NVTK].

NVTK Tested N/A
Other model configurations N/A
Processor configurations tested N/A
If adding new functionality please confirm that the
New code doesn't change results when it is switched off
and ''works'' when switched on

(Answering UNSURE is likely to generate further questions from reviewers.)

'Please add further summary details here'

  • Processor configurations tested
  • etc——

Bit Comparability

Does this change preserve answers in your tested standard configurations (to the last bit) ? N/A
Does this change bit compare across various processor configurations. (1xM, Nx1 and MxN are recommended) N/A
Is this change expected to preserve answers in all possible model configurations? N/A
Is this change expected to preserve all diagnostics?
,,''Preserving answers in model runs does not necessarily imply preserved diagnostics. ''

If you answered '''NO''' to any of the above, please provide further details:

  • Which routine(s) are causing the difference?
  • Why the changes are not protected by a logical switch or new section-version
  • What is needed to achieve regression with the previous model release (e.g. a regression branch, hand-edits etc). If this is not possible, explain why not.
  • What do you expect to see occur in the test harness jobs?
  • Which diagnostics have you altered and why have they changed?Please add details here……..

System Changes

Does your change alter namelists? No
Does your change require a change in compiler options? No

If any of these apply, please document the changes required here…….


''Please ''summarize'' any changes in runtime or memory use caused by this change……''


IPR issues

Has the code been wholly (100%) produced by NEMO developers staff working exclusively on NEMO? Yes

If No:

  • Identify the collaboration agreement details
  • Ensure the code routine header is in accordance with the agreement, (Copyright/Redistribution? etc).Add further details here if required……….