power_spectrum.xml 6.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204
  1. <?xml version="1.0" encoding="ISO-8859-1"?>
  2. <?xml-stylesheet type="text/xsl" href="odmlTerms.xsl" xmlns:odml="http://www.g-node.org/odml"?>
  3. <odML version="1">
  4. <repository>http://portal.g-node.org/odml/terminologies/v1.0/terminologies.xml</repository>
  5. <version>1.0</version>
  6. <date>2011-01-21</date>
  7. <!-- ********************************************************* -->
  8. <!-- Analysis section -->
  9. <!-- ********************************************************* -->
  10. <section>
  11. <type>analysis/power_spectrum</type>
  12. <name>Power spectrum</name>
  13. <definition>Properties of this section define the way a power spectrum was calculated.</definition>
  14. <property>
  15. <name>Author</name>
  16. <value>
  17. <type>person</type>
  18. </value>
  19. <definition>The name of the person who did the analysis, e.g. 'John Doe' or 'Doe, John'</definition>
  20. </property>
  21. <property>
  22. <name>Date</name>
  23. <value>
  24. <type>date</type>
  25. </value>
  26. <definition>The date of analysis.</definition>
  27. </property>
  28. <property>
  29. <name>Description</name>
  30. <value>
  31. <type>text</type>
  32. </value>
  33. <definition>A general description of the analysis.</definition>
  34. </property>
  35. <property>
  36. <name>SegmentLength</name>
  37. <value>
  38. <type>int</type>
  39. </value>
  40. <definition>The length of the analysed data stretches. Given in samples.</definition>
  41. </property>
  42. <property>
  43. <name>WindowFunction</name>
  44. <value>
  45. <type>string</type>
  46. </value>
  47. <definition>The type of window used. E.g. Hamming, Hanning, etc.</definition>
  48. </property>
  49. <property>
  50. <name>Overlap</name>
  51. <value>
  52. <unit>%</unit>
  53. <type>float</type>
  54. <definition>The overlap between consecutive data segments. Given in percent of the SegmentLength.</definition>
  55. </value>
  56. <value>
  57. <type>int</type>
  58. <definition>The overlap between consecutive data segments given in samples.</definition>
  59. </value>
  60. <definition>The overlap between consecutive data segments.</definition>
  61. </property>
  62. <property>
  63. <name>Method</name>
  64. <value>
  65. <type>string</type>
  66. </value>
  67. <definition>The name of a method used in this analysis. E.g. "power spectrum".</definition>
  68. </property>
  69. <property>
  70. <name>CommandlineCall</name>
  71. <value>
  72. <type>string</type>
  73. </value>
  74. <definition>The command used to execute the analysis including the command line parameter.</definition>
  75. </property>
  76. <property>
  77. <name>Comment</name>
  78. <value>
  79. <type>text</type>
  80. </value>
  81. <definition>Specific comments on this analysis.</definition>
  82. </property>
  83. <property>
  84. <name>Code</name>
  85. <value>
  86. <type>binary</type>
  87. <definition>The program code to analyse the data can be transferred using this property.
  88. Using it will blow up the the size of the metadatafile and we recommend to rather define the URL of underlying
  89. code file.
  90. </definition>
  91. </value>
  92. <value>
  93. <type>URL</type>
  94. <definition>The URL of the applied piece of program code to actually do the analysis.</definition>
  95. </value>
  96. <definition>The program code used to analyze the data.</definition>
  97. </property>
  98. <property>
  99. <name>CodeRevision</name>
  100. <value>
  101. <type>string</type>
  102. </value>
  103. <definition>If the analysis code is under version control the revision number can be specified using this
  104. property.
  105. </definition>
  106. </property>
  107. <property>
  108. <name>ConfigFile</name>
  109. <value>
  110. <type>URL</type>
  111. <definition>The URL of the used configuration file used to run the analysis.</definition>
  112. </value>
  113. <value>
  114. <type>binary</type>
  115. <definition>
  116. The configurations used to analyse the data can be transferred using this property.
  117. Using it will blow up the the size of the metadatafile and we recommend to rather define the URL of underlying
  118. configuration file.
  119. </definition>
  120. </value>
  121. <definition>The configurations used to analyse the data.</definition>
  122. </property>
  123. <property>
  124. <name>DatasetFile</name>
  125. <value>
  126. <type>binary</type>
  127. <definition>
  128. The data analysed ion the described way can be transferred using this property.
  129. Using it will blow up the the size of the metadatafile and we recommend to rather define the URL of underlying
  130. dataset file.
  131. </definition>
  132. </value>
  133. <value>
  134. <type>URL</type>
  135. <definition>The URL of a analysed datasetFile.</definition>
  136. </value>
  137. <definition>The analyzed dataset.</definition>
  138. </property>
  139. <property>
  140. <name>ResultFile</name>
  141. <value>
  142. <type>binary</type>
  143. <definition>
  144. The results of this analysis can be transferred using this property.
  145. Using it will blow up the the size of the metadatafile and we recommend to rather define the URL of the
  146. results file.
  147. </definition>
  148. </value>
  149. <value>
  150. <type>URL</type>
  151. <definition>The URL of a results file.</definition>
  152. </value>
  153. <definition>A file containing the results of this analysis.</definition>
  154. </property>
  155. <property>
  156. <name>ResultFigure</name>
  157. <value>
  158. <type>binary</type>
  159. <definition>
  160. This property is meant to store the real figure content. This will blow up the the size
  161. of the metadatafile and we recommend to rather define the URL of the figure.
  162. </definition>
  163. </value>
  164. <value>
  165. <type>URL</type>
  166. <definition>The url of the results figure.</definition>
  167. </value>
  168. <definition>A figure showing the results.</definition>
  169. </property>
  170. <property>
  171. <name>PaperDOI</name>
  172. <value>
  173. <type>text</type>
  174. </value>
  175. <definition>If the results of this analysis have been published one can store the doi of the paper.</definition>
  176. </property>
  177. <property>
  178. <name>PaperURL</name>
  179. <value>
  180. <type>URL</type>
  181. </value>
  182. <definition>If the results of this analysis have been published the URL of the document can be given here
  183. </definition>
  184. </property>
  185. </section>
  186. </odML>