After being confused by headerdoc use of the word
“kilobyte”, I did a bit of an audit:

- changed many comments to use kibibyte and also
added the number 1024
- noted that one function returns bytes, unlike many
other functions with same name that return kibibytes
- changed some default value initializations
that were a mix of power 2 and power 10 ex:
vtkPImageWriter called “1 gigabyte” = 1000000 kibibytes,
changed to power 2 since that’s prevailing in VTK

Although many don’t like the binary prefixes,
they have the advantage of being unambiguous.