From 4a44c272e11c32aaf3e28c4f4815023a76003f42 Mon Sep 17 00:00:00 2001 From: Alessandra Trapani <55453048+alessandratrapani@users.noreply.github.com> Date: Tue, 26 Sep 2023 19:51:40 +0200 Subject: [PATCH] Update docs/best_practices/ecephys.rst Co-authored-by: Ben Dichter --- docs/best_practices/ecephys.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/best_practices/ecephys.rst b/docs/best_practices/ecephys.rst index 25a7615a7..8dfbb5ad8 100644 --- a/docs/best_practices/ecephys.rst +++ b/docs/best_practices/ecephys.rst @@ -91,6 +91,6 @@ Check function: :py:meth:`~nwbinspector.checks.ecephys.check_spike_times_not_in_ Ascending Spike Times ~~~~~~~~~~~~~~~~~~~~~ -All spike times should be sorted in ascending order. Spike times may reset to zero about halfway through. This can happen if the spikes are not properly aligned with the ``timestamps_reference_time`` of the :ref:`nwb-schema:sec-NWBFile`. +All spike times should be sorted in ascending order. If they reset to zero, this can be a sign that spikes are not properly aligned with the ``timestamps_reference_time`` of the :ref:`nwb-schema:sec-NWBFile`. Check function: :py:meth:`~nwbinspector.checks.ecephys.check_ascending_spike_times`