Scheduled service maintenance on November 22


On Friday, November 22, 2024, between 06:00 CET and 18:00 CET, GIN services will undergo planned maintenance. Extended service interruptions should be expected. We will try to keep downtimes to a minimum, but recommend that users avoid critical tasks, large data uploads, or DOI requests during this time.

We apologize for any inconvenience.

psth.xml 6.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210
  1. <?xml version="1.0" encoding="ISO-8859-1"?>
  2. <?xml-stylesheet type="text/xsl" href="odmlTerms.xsl"?>
  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. <!-- PSTH section -->
  9. <!-- ********************************************************* -->
  10. <section>
  11. <type>analysis/psth</type>
  12. <name>PSTH</name>
  13. <definition>An Analysis-type section to describe an PSTH.</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>Method</name>
  37. <value>
  38. instantaneous spike rate
  39. <type>string</type>
  40. <definition>Estimation of the firing rate by using the inverse of the interspike interval.</definition>
  41. </value>
  42. <value>
  43. sliding window
  44. <type>string</type>
  45. <definition>The window function was slid over the data at recording resolution.</definition>
  46. </value>
  47. <value>
  48. discrete window
  49. <type>string</type>
  50. <definition>Spikes were averaged within the window, window discretely displaced by the window width.
  51. </definition>
  52. </value>
  53. <definition>The method used for creating the PSTH.</definition>
  54. </property>
  55. <property>
  56. <name>WindowType</name>
  57. <value>
  58. rectangular
  59. <type>string</type>
  60. <definition>A recangular kernel was used.</definition>
  61. </value>
  62. <value>
  63. gaussian
  64. <type>string</type>
  65. <definition>A gaussian kernel was used.</definition>
  66. </value>
  67. <value>
  68. alpha
  69. <type>string</type>
  70. <definition>A alpha function was used as window function.</definition>
  71. </value>
  72. <definition>The kind of windowing function used to cerate the PSTH.</definition>
  73. </property>
  74. <property>
  75. <name>CommandlineCall</name>
  76. <value>
  77. <type>string</type>
  78. </value>
  79. <definition>The command used to execute the analysis including the command line parameter.</definition>
  80. </property>
  81. <property>
  82. <name>Comment</name>
  83. <value>
  84. <type>text</type>
  85. </value>
  86. <definition>Specific comments on this analysis.</definition>
  87. </property>
  88. <property>
  89. <name>CodeFile</name>
  90. <value>
  91. <type>binary</type>
  92. </value>
  93. <definition>The program code to analyse the data can be transferred using this property.
  94. Using it will blow up the the size of the metadatafile and we recommend to rather define the URL of underlying
  95. code file.
  96. </definition>
  97. </property>
  98. <property>
  99. <name>CodeFileURL</name>
  100. <value>
  101. <type>URL</type>
  102. </value>
  103. <definition>The URL of the applied piece of program code to actually do the analysis.</definition>
  104. </property>
  105. <property>
  106. <name>CodeRevision</name>
  107. <value>
  108. <type>string</type>
  109. </value>
  110. <definition>If the analysis code is under version control the revision number can be specified using this
  111. property.
  112. </definition>
  113. </property>
  114. <property>
  115. <name>ConfigFile</name>
  116. <value>
  117. <type>binary</type>
  118. </value>
  119. <definition>The configurations used to analyse the data can be transferred using this property.
  120. Using it will blow up the the size of the metadatafile and we recommend to rather define the URL of underlying
  121. configuration file.
  122. </definition>
  123. </property>
  124. <property>
  125. <name>ConfigFileURL</name>
  126. <value>
  127. <type>URL</type>
  128. </value>
  129. <definition>The URL of the used configuration file used to run the analysis.</definition>
  130. </property>
  131. <property>
  132. <name>DatasetFile</name>
  133. <value>
  134. <type>binary</type>
  135. </value>
  136. <definition>The data analysed ion the described way can be transferred using this property.
  137. Using it will blow up the the size of the metadatafile and we recommend to rather define the URL of underlying
  138. dataset file.
  139. </definition>
  140. </property>
  141. <property>
  142. <name>DatasetFileURL</name>
  143. <value>
  144. <type>URL</type>
  145. </value>
  146. <definition>The URL of a analysed datasetFile.</definition>
  147. </property>
  148. <property>
  149. <name>ResultFile</name>
  150. <value>
  151. <type>binary</type>
  152. </value>
  153. <definition>The results of this analysis can be transferred using this property.
  154. Using it willblow up the the size of the metadatafile and we recommend to rather define the URL of the results
  155. file.
  156. </definition>
  157. </property>
  158. <property>
  159. <name>ResultFileURL</name>
  160. <value>
  161. <type>URL</type>
  162. </value>
  163. <definition>The URL of a results file.</definition>
  164. </property>
  165. <property>
  166. <name>ResultFigure</name>
  167. <value>
  168. <type>binary</type>
  169. </value>
  170. <definition>A figure showing the results. This property is meant to store the real figure content.
  171. This will blow up the the size of the metadatafile and we recommend to rather define the URL of the figure.
  172. </definition>
  173. </property>
  174. <property>
  175. <name>PaperDOI</name>
  176. <value>
  177. <type>text</type>
  178. </value>
  179. <definition>If the results of this analysis have been published one can store the doi of the paper.</definition>
  180. </property>
  181. <property>
  182. <name>PaperURL</name>
  183. <value>
  184. <type>URL</type>
  185. </value>
  186. <definition>If the results of this analysis have been published the URL of the document can be given here
  187. </definition>
  188. </property>
  189. </section>
  190. </odML>