Maybe instead of this you could just use the meas date from the first file if that's well-defined?

Yeah, I wasn't sure if a strict check to require all .ncs meas_dates to be exactly the same is needed. For example, I see that a real dataset with cca 80 chans happens to have a meas date for one channel off by a second (see snippet below); so it invalidates the strict check.

Not sure if this can happen with acquisition systems and datetime objects (like a numeric precision thing when writing to disk) and it's not an issue or is it unusual? (don't know myself much hands-on about Neuralynx acq systems)

meas_dates # shape = (n_channels,)
array([datetime.datetime(2022, 4, 2, 11, 42, 12),
       datetime.datetime(2022, 4, 2, 11, 42, 12),
       datetime.datetime(2022, 4, 2, 11, 42, 12),
       ...,
       datetime.datetime(2022, 4, 2, 11, 42, 12),
       datetime.datetime(2022, 4, 2, 11, 42, 13),  # <--- a different value, off by a sec
       datetime.datetime(2022, 4, 2, 11, 42, 12),
       ...,
       datetime.datetime(2022, 4, 2, 11, 42, 12)]

I suppose it could be a bit off (?). One option would be use the median time of all files, and warn if that's off by more than say a couple of seconds. Or just always use the first one. Or something else. I think as long as we pick something reasonable and document what it is in the read_raw_neuralynx docstring it's okay

and something about the meas_date?

@larsoner mind having a look at this docstring in read_raw_neuralynx()? I'm formatting something wrong, but can't figure out what. Ruff doesn't detect anything locally.

With this commit, it's failing like so:

FAILED mne/tests/test_docstring_parameters.py::test_docstring_parameters - AssertionError: 2 errors found:
mne.io : mne.io.neuralynx.neuralynx.read_raw_neuralynx : GL02 : Closing quotes should be placed in the line after the last text in the docstring (do not close the quotes in the same line as the text, or leave a blank line between the last text and the quotes)
mne.io : mne.io.neuralynx.neuralynx.read_raw_neuralynx : GL03 : Double line break found; please use only one blank line to separate sections or paragraphs, and do not leave blank lines at the end of docstrings

But if I delete the blank line (l. 68), then I think sphinx will break when building docs and I see this log (full CircleCI link):

/home/circleci/project/mne/io/neuralynx/neuralynx.py:docstring of mne.io.neuralynx.neuralynx.read_raw_neuralynx:64: WARNING: Explicit markup ends without a blank line; unexpected unindent.

Ah, wait, I think I see it. I guess I need to indent the code chunk after .. code-block:: python