That sounds like fun!
Suaveant's suggestion of writing a filter (in perl, of
course) sounds like a good one.
I'd suggest you stay as close to perl as you can,
unless the syntax is just too wierd. Non-programmers
can handle some level of syntax... but then I'm assuming...
On the other hand, your proposed syntax looks fine.
Hey, have you thought of using an OO approach? Could
you define a perl object to contain your data + the
methods used to manipulate that data? For example,
would the chemists understand this kind of syntax?
loop $i (1 to 50)
new data;
data.read( datafile.$i );
data.shift( 0.05 );
data.normalize( constant=1.0 );
data.write( outfile.$i );
# note: could perl eval() the stuff in parentheses?
endloop
Anyhow, don't forget to post a reply to let us know
what you're deciding and how it's going.
-Rob
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|