power_spectrum.xml 4.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136
  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <?xml-stylesheet type="text/xsl" href="odmlTerms.xsl" xmlns:odml="http://www.g-node.org/odml"?>
  3. <odML version="1.1">
  4. <repository>http://portal.g-node.org/odml/terminologies/v1.1/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. <type>person</type>
  17. <definition>The name of the person who did the analysis, e.g. 'John Doe' or 'Doe, John'</definition>
  18. </property>
  19. <property>
  20. <name>Date</name>
  21. <type>date</type>
  22. <definition>The date of analysis.</definition>
  23. </property>
  24. <property>
  25. <name>Description</name>
  26. <type>text</type>
  27. <definition>A general description of the analysis.</definition>
  28. </property>
  29. <property>
  30. <name>SegmentLength</name>
  31. <type>int</type>
  32. <definition>The length of the analysed data stretches. Given in samples.</definition>
  33. </property>
  34. <property>
  35. <name>WindowFunction</name>
  36. <type>string</type>
  37. <definition>The type of window used. E.g. Hamming, Hanning, etc.</definition>
  38. </property>
  39. <property>
  40. <name>Overlap</name>
  41. <unit>%</unit>
  42. <type>float</type>
  43. <definition>The overlap between consecutive data segments. Given in percent of the SegmentLength.</definition>
  44. </property>
  45. <property>
  46. <name>Method</name>
  47. <type>string</type>
  48. <definition>The name of a method used in this analysis. E.g. "power spectrum".</definition>
  49. </property>
  50. <property>
  51. <name>CommandlineCall</name>
  52. <type>string</type>
  53. <definition>The command used to execute the analysis including the command line parameter.</definition>
  54. </property>
  55. <property>
  56. <name>Comment</name>
  57. <type>text</type>
  58. <definition>Specific comments on this analysis.</definition>
  59. </property>
  60. <property>
  61. <name>Code</name>
  62. <type>binary</type>
  63. <definition>The program code to analyse the data can be transferred using this property.
  64. Using it will blow up the the size of the metadatafile and we recommend to rather define the URL of underlying
  65. code file.
  66. </definition>
  67. </property>
  68. <property>
  69. <name>CodeRevision</name>
  70. <type>string</type>
  71. <definition>If the analysis code is under version control the revision number can be specified using this
  72. property.
  73. </definition>
  74. </property>
  75. <property>
  76. <name>ConfigFile</name>
  77. <type>URL</type>
  78. <definition>The URL of the used configuration file used to run the analysis.</definition>
  79. </property>
  80. <property>
  81. <name>DatasetFile</name>
  82. <type>binary</type>
  83. <definition>
  84. The data analysed ion the described way can be transferred using this property.
  85. Using it will blow up the the size of the metadatafile and we recommend to rather define the URL of underlying
  86. dataset file.
  87. </definition>
  88. </property>
  89. <property>
  90. <name>ResultFile</name>
  91. <type>binary</type>
  92. <definition>
  93. A file containing the results of this analysis. The results of this analysis can be transferred using this
  94. property. Using it will blow up the the size of the metadatafile and we recommend to rather define the URL of
  95. the results file.
  96. </definition>
  97. </property>
  98. <property>
  99. <name>ResultFigure</name>
  100. <type>binary</type>
  101. <definition>
  102. This property is meant to store the real figure content. This will blow up the the size
  103. of the metadatafile and we recommend to rather define the URL of the figure.
  104. </definition>
  105. </property>
  106. <property>
  107. <name>PaperDOI</name>
  108. <type>text</type>
  109. <definition>If the results of this analysis have been published one can store the doi of the paper.</definition>
  110. </property>
  111. <property>
  112. <name>PaperURL</name>
  113. <type>URL</type>
  114. <definition>If the results of this analysis have been published the URL of the document can be given here
  115. </definition>
  116. </property>
  117. </section>
  118. </odML>