in reply to Re^2: A generic biomedical data processing library
in thread A generic biomedical data processing library

I am leaning towards YAML for this.

Just a general note.  During my last job (in a lab mostly frequented by psychologists, linguists, etc.) I wrote a suite of modules for EEG/ERP analysis, and my general conclusion was that if you make the user interface too complex (as is unfortunately sometimes required for generic solutions), people simply aren't going to use the tool — in particular, if the entry threshold is high, and it doesn't come with lots of ready to use cut-n-paste examples.

In other words, using YAML would be fine if they know it already, but otherwise they might not be willing to learn it  (which could mean - at least if you work in the same lab - you'll always be the one eventually writing the code for them :)

  • Comment on Re^3: A generic biomedical data processing library

Replies are listed 'Best First'.
Re^4: A generic biomedical data processing library
by spiros (Beadle) on Mar 23, 2010 at 08:54 UTC
    I agree with your points and at the same time I am being realistic. I dont expect anybody from my work here to use this module - they all use statistical packages. I would expect the average Perl user though to be able to use it easily. My plan, is/was to have a separate tool and have something like "Cut and paste the column names in this space" and the markup would be generated automagically.
Re^4: A generic biomedical data processing library
by spiros (Beadle) on Mar 22, 2010 at 18:07 UTC
    Thank you all for your useful comments. Spiros