[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Managing measurement metadata
From: |
Lukas Reichlin |
Subject: |
Re: Managing measurement metadata |
Date: |
Sat, 11 Jan 2014 17:39:09 +0100 |
On 11.01.2014, at 17:24, CdeMills <address@hidden> wrote:
> Hello,
>
> I do a lot of data acquistions followed by post-processing in Octave. In
> order to ease data management, I would like to share experience about best
> practices for helping finding the link between data and real world
> parameter.
>
> To give a short example: I have 8 sensors (thermocouples), then some device
> transforming the thermocouple voltage into a temperature. Each reading may
> thus be characterised by
> - the sensor
> - the converter
> - its timestamp
> - a short description of where the sensor is, to which device it is
> attached, the purpose of the experiment, and so on.
>
> Are there good practices to store and retrieve those metadata in Octave ?
> How to link efficiently (i.e. with a minimum redundancy) specific reading to
> its full context ?
>
> Regards
>
> Pascal
Hi Pascal,
You may want to have a look at the iddata class of the control package:
http://octave.sourceforge.net/control/function/iddata.html
The class is intended to store measurements and metadata for system
identification.
Hope this helps,
Lukas