optparse with numpy.array?
ekh.johan at gmail.com
Tue Jan 27 07:01:38 CET 2009
Thank you James,
but I just can't optparse to accept an array, only integers, floats ans
My code looks like this
from optparse import OptionParser
parser = OptionParser()
parser.add_option('-t', '--dt', action='store', type='float', dest='dt_i',
default=0.1, help='time increment where lsoda saves results')
parser.add_option('-T', '--tstop', action='store', type='float',
dest='tstop_i', default=1.0, help='duration of the solution')
parser.add_option('-m', '--mass_vector', action='store', type='float',
dest='m_i', default=[1.0, 1.0], help='vector with lumped masses')
op, args = parser.parse_args(sys.argv[1:])
I want this to work for m_i = array([1.0, 2.0, 3.0]) but the optparse
complains that m_i is not a float.
On Tue, Jan 27, 2009 at 6:53 AM, James Mills
<prologic at shortcircuit.net.au>wrote:
> On Tue, Jan 27, 2009 at 3:45 PM, Johan Ekh <ekh.johan at gmail.com> wrote:
> > Thank you Robert,
> > but what if I just want to create an array interactively, e.g. like m =
> > array([1.0, 2.0, 3.0]), and pass it
> > to my program? I tried extending optparse with a new type as explained in
> > the link you gave me
> > but I was not able to get it to work. Is it really neccessary follow that
> > route just to pass an array?
> > Lot's of people must have done this before!
> Normally command line applications accept
> a number of arguments which are available
> in sys.argv
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-list