Mercurial > hg > ltpda
comparison m-toolbox/html_help/help/ug/ao_intro_content.html @ 0:f0afece42f48
Import.
author | Daniele Nicolodi <nicolodi@science.unitn.it> |
---|---|
date | Wed, 23 Nov 2011 19:22:13 +0100 |
parents | |
children |
comparison
equal
deleted
inserted
replaced
-1:000000000000 | 0:f0afece42f48 |
---|---|
1 | |
2 <p>Based on the requirement that all results produced by the LTP Data Analysis software must be | |
3 easily reproducible as well as fully traceable, the idea of implementing analysis objects (AO) as | |
4 they are described in S2-AEI-TN-3037 arose.</p> | |
5 | |
6 <p>An analysis object contains all information necessary to be able to reproduce a given result. For | |
7 example | |
8 <ul> | |
9 <li>which raw data was involved (date, channel, time segment, time of retrieval if data can be | |
10 changed later by new downlinks)</li> | |
11 <li>all operations performed on the data</li> | |
12 <li>the above for all channels of a multi-channel plot</li> | |
13 </ul> | |
14 </p> | |
15 <p>The AO will therefore hold | |
16 <ul> | |
17 <li>the numerical data belonging to the result</li> | |
18 <li>the full processing history needed to reproduce the numerical result</li> | |
19 </ul> | |
20 </p> | |
21 | |
22 <p>The majority of algorithms in the LTPDA Toolbox will operate on AOs only (these are always methods | |
23 of the AO class) but there are also utility functions which do not take AOs as inputs, as well as methods | |
24 of other classes. Functions in the toolbox are designed to be as simple and elementary as | |
25 possible. </p> | |
26 | |
27 |