[IPOL discuss] Software Guidelines, 3rd draft and path to adoption

[Nicolas Limare]

> > For the ASCII numeric text output mentioned by Mauricio, I propose to
> > add CSV as a possible format.
> 
> Is CSV commonly used for images?  I find matlab/octave's ascii matrix
> more natural, widely used for images, and trivial to write and read:
> simply write the numbers in ascii, separated by spaces, and the rows
> separated by newlines.

No, not used for images. I was not thinking about images for CSV, more
about various non-image numeric output a program can produce, and
trying to fill the gap between these guidelines and 2D graph question
(still open...). But finally, it is probably better not mix the
problems, and not mention the a text (csv or matrix) format for
images. No one asked for it and we don't really want to manage 45MB
files for 1000x1000 RGB images. The guidelines mention the input and
final output data, I don't consider this includes non-image output
such as CPU time, RMSE, etc..., which should naturally be produced in
simple ASCII text and don't need a "file format".

-- 
Nicolas LIMARE - CMLA - ENS Cachan    http://www.cmla.ens-cachan.fr/~limare/
IPOL - image processing on line                          http://www.ipol.im/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://tools.ipol.im/mailman/archive/discuss/attachments/20111128/dbd37179/attachment.pgp>