Thomas Braun

On my vim the aligmaps `\tt` shortcut clashed with the vim-table-mode one. I've worked around the issue for me with defining: ```vim " Use AlignMaps \tt mapping, instead of vim-table-mode's...

The naming scheme is taken from boost, explained [1] as well. The toolset might not make sense vor VS 2015+, but for older versions it is important to have it...

Validation output: ``` $python -m pynwb.validate 001_140709EXP_A1_ndx_v3.nwb Traceback (most recent call last): File "/home/firma/.pyenv/versions/3.8.6/lib/python3.8/runpy.py", line 194, in _run_module_as_main return _run_code(code, main_globals, None, File "/home/firma/.pyenv/versions/3.8.6/lib/python3.8/runpy.py", line 87, in _run_code exec(code, run_globals)...

@oruebel This is just the file from the dandi link.

Why? There might be already files around with spaces in the name and so I would say this ship has sailed.

Does the file validate? The error message `"Could not construct DandiIcephysMetadata object due to: TypeMap.__get_cls_dict..__init__: missing argument 'help'"` suggests not.

We need to find a way to tell pynwb that certain datasets in HDF5 need to be written as chunked by default. Only then they are appendable. I don't know...

How about we use the standard abbreviations for the units? Like `s` / `V` in their official casing?

A list of SI units can be found [here](https://www.nist.gov/pml/nist-guide-si-chapter-4-two-classes-si-units-and-si-prefixes).

@bendichter I'm not sure I'll find time to write custom code for that. @oruebel This is not the usual nested spec problem. From the posted link above ```yaml stimset_referenced_folder =...