Conversation
|
TODO: Update BehavioralEpochs docstring |
Clarified documentation for timestamps in seconds.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Replace the deprecation of TimeSeries/data.continuity="instantaneous" with a doc-level recommendation to use an EventsTable. The best-practice check will live in nwbinspector instead. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…resolution doc Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
If I recall correctly, at our team discussion, we decided not to deprecate setting |
Describe resolution as the sampling period (clock period) of the source data acquisition system rather than the smallest possible difference between values. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
oruebel
left a comment
There was a problem hiding this comment.
Looks good to me. I added minor suggestion to clarify the docs. Feel free to accept/reject that suggestion as you deem appropriate.
Co-authored-by: Oliver Ruebel <oruebel@users.noreply.github.com>
Summary of changes
Checklist
For all schema changes:
docs/format/source/format_release_notes.rst.hdmf-common-schemapoints to the latest release and not the latest commit on themainbranch.If this is the first schema change after a schema release (i.e., the version string in
core/nwb.namespace.yamldoes notend in "-alpha"), then:
core/nwb.namespace.yamlandcore/nwb.file.yamlto the next major/minor/patchversion with the suffix "-alpha". For example, if the current version is 2.4.0 and this is a minor change, then the
new version string should be "2.5.0-alpha".
versionvariable indocs/format/source/conf.pyto the next version without thesuffix "-alpha", e.g., "2.5.0".
releasevariable indocs/format/source/conf.pyto the next version with the suffix"-alpha", e.g., "2.5.0-alpha".
docs/format/source/format_release_notes.rstfor the new versionwith the date "Upcoming" in parentheses.