[Go-essp-tech] qc-data-level2 output and qc-tool
Martina Stockhause
martina.stockhause at zmaw.de
Mon Sep 27 00:08:40 MDT 2010
Hi Bryan,
my state of what should be sent to the metadata repository is a quality
document. I kept track with the changes in the schema and sent my
examples to the metafor list and to you. I did a few changes so that the
example passes the CIM validator without errors. I attach it again.
Since I have received neither reaction for nor objection against these
examples (first sent out end of June) so far, I have started to
implement that.
The DQ_DomainConstistency document is new to me. And unfortunately I
have not the time right now to figure out how to map my qc information
to that new schema on my own. I would need a concrete example from
metafor for that.
I have to concentrate on finishing the qc checks:
- derive a set of rules for the assignment of qc level 2 if the tool
detects warnings
- adapt our qc level 3 workflow to CMIP5 requirements.
- adapt/check qc workflow and tools for changed DRS
Best wishes,
Martina
On 09/23/2010 12:52 PM, Bryan Lawrence wrote:
> The diagram wasn't attached, but you can see it at
> http://metafortrac.badc.rl.ac.uk/trac/browser/QualityControlTool/trunk/qcproj/Quality-
> Brief.png
>
> Cheers
> Bryan
>
>> Hi Frank& Martina
>>
>> Michael tells me you will be trying to build something to produce
>> CIM- XML for the output of qc-data-level2 ... prefereably something
>> that the software itself will generate.
>>
>> Ideally that would be a DQ_DomainConstistency document, which we
>> would upload via our qc-tool to attach to a CIM_Quality document -
>> is that what you think is happening?
>>
>> (We currently don't have an upload piece in the tool - which you can
>> see coming along at
>> http://proj.badc.rl.ac.uk/svn/metafor/QualityControlTool/
>> but it would be easy to add such a facility, and we'll have done that
>> by tomorrow).
>>
>> (NB: see attached diagram which summarises most of what we are
>> working to for the CIM qc).
>>
>> We are buliding the tool so we can run an instance at each of our
>> data centres (and elsewhere), and the gateway can poll the feed to
>> upload the information (Maurizio is working on that piece for the
>> gateway team). (An eventual extension will be to allow the qc-tools
>> to peer with each other, but that's not a priority in the next two
>> weeks).
>>
>> It occurs to me that ideally the qc-level-2 tool is producing some
>> plots as well, so we could (and probalby should) modify the UML so
>>
>> 1) we have have a specialistaion of DQ_Element that allows result to
>> have three DQ_Result attributes and we
>>
>> 2) introduce a new specialisation of DQ_Result which is essentially a
>> plot/image result which could be uploaded and stored ....
>>
>> (We should do this anyway, since I can see a lot of other uses for
>> it, not just CMIP5 qc-level-2 - we have a real EO application for it
>> right now ...)
>>
>> Is the qc-tool producing plots, and should we have this facility as a
>> priority?
>>
>> thanks
>> Bryan
>>
>>
>> Bryan Lawrence
>> Director of Environmental Archival and Associated Research
>> (NCAS/British Atmospheric Data Centre and NCEO/NERC NEODC)
>> STFC, Rutherford Appleton Laboratory
>> Phone +44 1235 445012; Fax ... 5848;
>> Web: home.badc.rl.ac.uk/lawrence
> Bryan Lawrence
> Director of Environmental Archival and Associated Research
> (NCAS/British Atmospheric Data Centre and NCEO/NERC NEODC)
> STFC, Rutherford Appleton Laboratory
> Phone +44 1235 445012; Fax ... 5848;
> Web: home.badc.rl.ac.uk/lawrence
--
----------- DKRZ / Data Management -----------
Martina Stockhause
Deutsches Klimarechenzentrum
Bundesstr. 45a
D-20146 Hamburg
Germany
phone: +49-40-460094-122
FAX: +49-40-460094-106
e-mail: martina.stockhause at zmaw.de
----------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CIM_Quality_QCL2.xml
Type: text/xml
Size: 4738 bytes
Desc: not available
Url : http://mailman.ucar.edu/pipermail/go-essp-tech/attachments/20100927/fefd544e/attachment.xml
More information about the GO-ESSP-TECH
mailing list