From pearu at cens.ioc.ee  Tue Dec  4 09:16:10 2001
From: pearu at cens.ioc.ee (Pearu Peterson)
Date: Tue, 4 Dec 2001 16:16:10 +0200 (EET)
Subject: [SciPy-dev] ANN: F2PY - Fortran to Python Interface Generator
Message-ID: <Pine.LNX.4.21.0112041610320.11555-100000@kev.ioc.ee>

F2PY - Fortran to Python Interface Generator

I am pleased to announce the third public release of f2py (2nd Edition)
(version 2.3.328):

     http://cens.ioc.ee/projects/f2py2e/

f2py is a command line tool for binding Python and Fortran codes.  It
scans Fortran 77/90/95 codes and generates a Python C/API module that
makes it possible to call Fortran subroutines from Python.  No Fortran or
C expertise is required for using this tool.

Features include:

   *** All basic Fortran types are supported:
         integer[ | *1 | *2 | *4 | *8 ], logical[ | *1 | *2 | *4 | *8 ], 
         character[ | *(*) | *1 | *2 | *3 | ... ]
         real[ | *4 | *8 | *16 ], double precision,
         complex[ | *8 | *16 | *32 ]

   *** Multi-dimensional arrays of (almost) all basic types.
       Dimension specifications: 
		 <dim> | <start>:<end> | * | :

   *** Supported attributes and statements:
         intent([ in | inout | out | hide | in,out | inout,out ])
	 dimension(<dimspec>)
	 depend([<names>])
	 check([<C-booleanexpr>])
	 note(<LaTeX text>)
	 optional, required, external
NEW:     intent(c), threadsafe, fortranname

   *** Calling Fortran 77/90/95 subroutines and functions.  Also
       Fortran 90/95 module subroutines are supported.  Internal 
       initialization of optional arguments.

   *** Accessing COMMON blocks from Python.
NEW:   Accessing Fortran 90/95 module data.

   *** Call-back functions: calling Python functions from Fortran with
       very flexible hooks.

   *** In Python, arguments of the interfaced functions may be of
       different type - necessary type conversations are done
       internally in C level.

   *** Automatically generates documentation (__doc__,LaTeX) for
       interfaced functions.

   *** Automatically generates signature files --- user has full
       control over the interface constructions.  Automatically
       detects the signatures of call-back functions, solves argument
       dependencies, etc.

NEW: * Automatically generates setup_<modulename>.py for building
       extension modules using tools from distutils and 
       fortran_support module (from SciPy).

   *** Automatically generates Makefile for compiling Fortran and C
       codes and linking them to a shared module. Many compilers are
       supported: gcc, Compaq Fortran, VAST/f90 Fortran, Absoft
       F77/F90, MIPSpro 7 Compilers, etc.  Platforms: Intel/Alpha
       Linux, HP-UX, IRIX64.

   *** Complete User's Guide in various formats (html,ps,pdf,dvi).

   *** f2py users list is available for support, feedback, etc.

NEW: * Installation with distutils.

   *** And finally, many bugs were fixed.

More information about f2py, see 

     http://cens.ioc.ee/projects/f2py2e/

LICENSE:
	f2py is released under the LGPL.

Sincerely,
     Pearu Peterson <pearu at cens.ioc.ee>
     December 4, 2001

<P><A HREF="http://cens.ioc.ee/projects/f2py2e/">f2py 2.3.328</A> - The
Fortran to Python Interface Generator (04-Dec-01)



From adam.brett at mail.internetseer.com  Wed Dec 12 11:07:29 2001
From: adam.brett at mail.internetseer.com (adam.brett at mail.internetseer.com)
Date: Wed, 12 Dec 2001 11:07:29 -0500 (EST)
Subject: [SciPy-dev] Broken link on your website
Message-ID: <4950943.1008173249262.JavaMail.promon@pm68>

I noticed that your page: http://www.scipy.org/site_content/FAQ/document_view 
contains a link to: http://www.scipy.org/site_content/FAQ/tutorials\testing_guidelines.

The page at http://www.scipy.org/site_content/FAQ/tutorials\testing_guidelines cannot currently be accessed because of the following 
error: 404 File not found.?

No one likes broken links on their website so we thought you?d like to be the 
first to know.

WHO ARE WE?
We?re Internetseer.com, the worlds largest FREE website monitoring service. 
One recent subscriber wrote the following; ?You did an awesome job 
identifying to me that our site went down and tracking it until it came back 
up again?.

HOW CAN OUR SERVICE BE FREE?
Our service is supported by advertisers and subscribers who purchase 
additional services, but our basic service is FREE.

WHAT DO YOU GET FOR FREE?
We?ll monitor your site once every hour, 24 hours a day, seven days a week for 
free. You can even have multiple people notified when we detect an error. In 
addition, you?ll receive a website performance report every week showing 
uptime percentages, average connect times, helpful links to others sites and 
of course promotions from our advertisers. You can cancel your free 
subscription at any time.

This message is not spam because we are not trying to sell you a service. We 
are simply advising you that a link on your website is currently broken due to 
the error listed above.

If you would like to subscribe to our free website monitoring service, please 
click on the following link:
http://scclick.internetseer.com/sitecheck/clickthrough.jsp?I5s57l5f5h5h5g5o52R5sz_SWkecK5c_RJ5sxRXyA5aNPD53U5pXTxy5p5b5cKTU5dz_SNK5dIzL5bxSxR6u6vNyxRyx5c655t6e5e_NRPHMHP6uWLMT53T5p5e=e3

If you do not wish to receive any further email messages from us, please 
respond to this message with the word ?cancel? in the subject line. You must 
leave the entire body of this message in your reply so we can accurately 
determine whom we originally notified about the broken link. 

We sincerely hope that you?ll become one of InternetSeer's 850,000
satisfied subscribers.

Adam Brett?
Web Site Analyst
cs-adam.brett at mail.internetseer.com
InternetSeer.com "Free Website Monitoring"
http://www.internetseer.com

##scipy-dev at scipy.org##
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20011212/21c0ad3e/attachment.html>

From jmr at engineering.uiowa.edu  Tue Dec 18 20:14:40 2001
From: jmr at engineering.uiowa.edu (Joe Reinhardt)
Date: Tue, 18 Dec 2001 19:14:40 -0600
Subject: [SciPy-dev] Debian package for SciPy
In-Reply-To: <87u1z1j90m.fsf@phantom.ecn.uiowa.edu>
 (jmr@engineering.uiowa.edu's message of "Tue, 21 Aug 2001 18:19:53 -0500")
References: <Pine.LNX.4.33.0107231957590.15960-100000@oliphant.ee.byu.edu>
	<87snfmn8o1.fsf@jeeves.blindglobe.net>
	<87u1z1j90m.fsf@phantom.ecn.uiowa.edu>
Message-ID: <87itb4huyn.fsf_-_@phantom.ecn.uiowa.edu>

Hi - I haven't heard much from this list recently.  Hope things are
still progressing.

I packaged the latest SciPy for debian.  You can get it from
people.debian.org/~jmr.     Hopefully, it will make it into the
distribution soon.

I found a small error in quadrature.py, line 351:

    if scipy.isinf(a) or scipy.isinf(b):
        raise ValueError: "Romberg integration only available for finite limits."

The colon should be comma.


I really like the plot tool - I now use it all the time for my image
processing work.  One thing that would be very useful for me is to see
what the pixel value is below the cursor -- any plans to add that?

Thanks.



-- 
Joseph M. Reinhardt, Ph.D.   Department of Biomedical Engineering
joe-reinhardt at uiowa.edu      University of Iowa, Iowa City, IA  52242
Telephone: 319-335-5634      FAX:       319-335-5631


From rossini at blindglobe.net  Wed Dec 19 00:36:01 2001
From: rossini at blindglobe.net (A.J. Rossini)
Date: 18 Dec 2001 21:36:01 -0800
Subject: [SciPy-dev] Debian package for SciPy
In-Reply-To: <87itb4huyn.fsf_-_@phantom.ecn.uiowa.edu>
References: <Pine.LNX.4.33.0107231957590.15960-100000@oliphant.ee.byu.edu>
	<87snfmn8o1.fsf@jeeves.blindglobe.net>
	<87u1z1j90m.fsf@phantom.ecn.uiowa.edu>
	<87itb4huyn.fsf_-_@phantom.ecn.uiowa.edu>
Message-ID: <87itb3bwla.fsf@jeeves.blindglobe.net>

Thanks, cool!  I've been much but much too occupied, but should be
checking it out soon.

best,
-tony

-- 
A.J. Rossini				Rsrch. Asst. Prof. of Biostatistics
U. of Washington Biostatistics		rossini at u.washington.edu	
FHCRC/SCHARP/HIV Vaccine Trials Net	rossini at scharp.org
-------------- http://software.biostat.washington.edu/ --------------
FHCRC: M-W: 206-667-7025 (fax=4812)|Voicemail is pretty sketchy/use Email
UW:   T-Th: 206-543-1044 (fax=3286)|Change last 4 digits of phone to FAX
Rosen: (Mullins' Lab) Fridays, and I'm unreachable except by email.


From eric at scipy.org  Thu Dec 20 09:55:41 2001
From: eric at scipy.org (eric)
Date: Thu, 20 Dec 2001 09:55:41 -0500
Subject: [SciPy-dev] Debian package for SciPy
References: <Pine.LNX.4.33.0107231957590.15960-100000@oliphant.ee.byu.edu><87snfmn8o1.fsf@jeeves.blindglobe.net><87u1z1j90m.fsf@phantom.ecn.uiowa.edu> <87itb4huyn.fsf_-_@phantom.ecn.uiowa.edu>
Message-ID: <038901c18966$64e567f0$777ba8c0@ericlaptop>

Hi Joseph,

> Hi - I haven't heard much from this list recently.  Hope things are
> still progressing.

It has been sorta slow.  Development should accelerate mid-January when
several other things here are out of the way.

>
> I packaged the latest SciPy for debian.  You can get it from
> people.debian.org/~jmr.     Hopefully, it will make it into the
> distribution soon.

Thanks.  I've added the link to the SciPy website and posted a news item
about it.  Did you build these from the latest CVS or are they from the same
source base as 0.1?  I noticed the packages had a 0.2.0 name on them.

>
> I found a small error in quadrature.py, line 351:
>
>     if scipy.isinf(a) or scipy.isinf(b):
>         raise ValueError: "Romberg integration only available for finite
limits."
>
> The colon should be comma.

I'll check this.

>
>
> I really like the plot tool - I now use it all the time for my image
> processing work.  One thing that would be very useful for me is to see
> what the pixel value is below the cursor -- any plans to add that?

That would be nice.  I'll put it on the list.

eric




From eric at scipy.org  Thu Dec 20 10:17:57 2001
From: eric at scipy.org (eric)
Date: Thu, 20 Dec 2001 10:17:57 -0500
Subject: [SciPy-dev] Re: [Numpy-discussion] converting IDL to python
References: <876672h6n7.fsf@phantom.ecn.uiowa.edu>
Message-ID: <03ad01c18969$8130e080$777ba8c0@ericlaptop>

Rick and Joe,

I'm not familiar with these erosion and dialation functions.  Are they
something that should be in SciPy?  We could start an "idl" package that
houses functions familiar to this community.  Or maybe they should live in
another place like "signal" or maybe an image processing package.  Thoughts?

I've crossed posted this to the scipy-dev at scipy.org list as this is probably
the best place to continue such a discussion.

eric


----- Original Message -----
From: "Joe Reinhardt" <jmr at engineering.uiowa.edu>
To: <numpy-discussion at lists.sourceforge.net>
Sent: Wednesday, December 19, 2001 11:12 PM
Subject: [Numpy-discussion] converting IDL to python


>
> Rick White writes:
> > The hardest part (as you mention) is that IDL has a really large
> > collection of built-in functions which probably will not be readily
> > available in Python.  Until someone writes things like the morphological
> > dilation and erosion operations, it won't be possible to translate IDL
> > programs that use them.
>
> By the way, I do have binary erosion and dilation, along with
> connected components analysis, flood fill region grow, and several
> other common 2D/3D image processing functions working in NumPy.
>
> I would be glad to share them.    I don't know how similar the
> interface is to IDL, since I have never used IDL.
>
> - Joe Reinhardt
>
>
>
> --
> Joseph M. Reinhardt, Ph.D.   Department of Biomedical Engineering
> joe-reinhardt at uiowa.edu      University of Iowa, Iowa City, IA  52242
> Telephone: 319-335-5634      FAX:       319-335-5631
>
> _______________________________________________
> Numpy-discussion mailing list
> Numpy-discussion at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/numpy-discussion
>




From jmr at engineering.uiowa.edu  Thu Dec 20 11:27:30 2001
From: jmr at engineering.uiowa.edu (Joe Reinhardt)
Date: Thu, 20 Dec 2001 10:27:30 -0600
Subject: [SciPy-dev] Re: [Numpy-discussion] converting IDL to python
In-Reply-To: <03ad01c18969$8130e080$777ba8c0@ericlaptop> ("eric"'s message
 of "Thu, 20 Dec 2001 10:17:57 -0500")
References: <876672h6n7.fsf@phantom.ecn.uiowa.edu>
	<03ad01c18969$8130e080$777ba8c0@ericlaptop>
Message-ID: <lg1adwdc0wd.fsf@pet.ecn.uiowa.edu>

"eric" <eric at enthought.com> writes:

> I'm not familiar with these erosion and dialation functions.  Are they
> something that should be in SciPy?  We could start an "idl" package that
> houses functions familiar to this community.  Or maybe they should live in
> another place like "signal" or maybe an image processing package.
> Thoughts?

Dilation and erosion are image processing functions used to "grow" and
"shrink" objects and boundaries.  They are part of a group of image
operators based on the theory of mathematical morphology.  Overall,
they are very extremely useful for shape/size analysis on images.

Yes, they should certainly be part of any image processing toolbox for
Python.  Here is a link for a commercial math. morphology toolbox for
matlab: http://www.mmorph.com

- Joe

-- 
Joseph M. Reinhardt, Ph.D.   Department of Biomedical Engineering
joe-reinhardt at uiowa.edu      University of Iowa, Iowa City, IA  52242
Telephone: 319-335-5634      FAX:       319-335-5631


From jmr at engineering.uiowa.edu  Thu Dec 20 11:30:36 2001
From: jmr at engineering.uiowa.edu (Joe Reinhardt)
Date: Thu, 20 Dec 2001 10:30:36 -0600
Subject: [SciPy-dev] Debian package for SciPy
In-Reply-To: <038901c18966$64e567f0$777ba8c0@ericlaptop> ("eric"'s message
 of "Thu, 20 Dec 2001 09:55:41 -0500")
References: <Pine.LNX.4.33.0107231957590.15960-100000@oliphant.ee.byu.edu>
	<87snfmn8o1.fsf@jeeves.blindglobe.net>
	<87u1z1j90m.fsf@phantom.ecn.uiowa.edu>
	<87itb4huyn.fsf_-_@phantom.ecn.uiowa.edu>
	<038901c18966$64e567f0$777ba8c0@ericlaptop>
Message-ID: <lg1pu59am6r.fsf@pet.ecn.uiowa.edu>

"eric" <eric at enthought.com> writes:

> Thanks.  I've added the link to the SciPy website and posted a news item
> about it.  Did you build these from the latest CVS or are they from the same
> source base as 0.1?  I noticed the packages had a 0.2.0 name on
> them.

I built from the CVS distribution from Monday or Tuesday evening.

>>
>> I really like the plot tool - I now use it all the time for my image
>> processing work.  One thing that would be very useful for me is to see
>> what the pixel value is below the cursor -- any plans to add that?
>
> That would be nice.  I'll put it on the list.
>

I have a patch that does this.   I will try to clean it up and send it
on.

- Joe

-- 
Joseph M. Reinhardt, Ph.D.   Department of Biomedical Engineering
joe-reinhardt at uiowa.edu      University of Iowa, Iowa City, IA  52242
Telephone: 319-335-5634      FAX:       319-335-5631


From eric at scipy.org  Thu Dec 20 10:38:34 2001
From: eric at scipy.org (eric)
Date: Thu, 20 Dec 2001 10:38:34 -0500
Subject: [SciPy-dev] Debian package for SciPy
References: <Pine.LNX.4.33.0107231957590.15960-100000@oliphant.ee.byu.edu><87snfmn8o1.fsf@jeeves.blindglobe.net><87u1z1j90m.fsf@phantom.ecn.uiowa.edu><87itb4huyn.fsf_-_@phantom.ecn.uiowa.edu><038901c18966$64e567f0$777ba8c0@ericlaptop> <lg1pu59am6r.fsf@pet.ecn.uiowa.edu>
Message-ID: <03ca01c1896c$62a30a50$777ba8c0@ericlaptop>

>
> "eric" <eric at enthought.com> writes:
>
> > Thanks.  I've added the link to the SciPy website and posted a news item
> > about it.  Did you build these from the latest CVS or are they from the
same
> > source base as 0.1?  I noticed the packages had a 0.2.0 name on
> > them.
>
> I built from the CVS distribution from Monday or Tuesday evening.

Ok.  I'll make a note of this.

>
> >>
> >> I really like the plot tool - I now use it all the time for my image
> >> processing work.  One thing that would be very useful for me is to see
> >> what the pixel value is below the cursor -- any plans to add that?
> >
> > That would be nice.  I'll put it on the list.
> >
>
> I have a patch that does this.   I will try to clean it up and send it
> on.

Cool.  I still need to stick Jochen's zoom patch in and will add this at the
same time.

eric





From prabhu at aero.iitm.ernet.in  Sat Dec 22 00:02:54 2001
From: prabhu at aero.iitm.ernet.in (Prabhu Ramachandran)
Date: Sat, 22 Dec 2001 10:32:54 +0530
Subject: [SciPy-dev] A few gui_thread improvements.
Message-ID: <15396.5118.480322.940388@monster.linux.in>

hi,

I just committed some code to gui_thread that adds a __setattr__
method to the proxy classes.  Without these changes the following
example will not work.

import gui_thread
from scipy import plt
p = plt.plot([1,2,3])
# so far so good.
plt.xaxis([1,2])

at this point you should see the xaxes bounds change but nothing will
happen.  With the newly added __setattr__ this should behave
correctly.  This should also make the behaviour of proxied objects
nicer.

I've also added a simple unit test for the new method.  You can view
the changes here:

http://scipy.net/cgi-bin/viewcvs.cgi/scipy/gui_thread/

Cheers,
prabhu


From jmr at engineering.uiowa.edu  Sun Dec 23 18:11:30 2001
From: jmr at engineering.uiowa.edu (Joe Reinhardt)
Date: Sun, 23 Dec 2001 17:11:30 -0600
Subject: [SciPy-dev] Debian package for SciPy
In-Reply-To: <038901c18966$64e567f0$777ba8c0@ericlaptop> ("eric"'s message
 of "Thu, 20 Dec 2001 09:55:41 -0500")
References: <Pine.LNX.4.33.0107231957590.15960-100000@oliphant.ee.byu.edu>
	<87snfmn8o1.fsf@jeeves.blindglobe.net>
	<87u1z1j90m.fsf@phantom.ecn.uiowa.edu>
	<87itb4huyn.fsf_-_@phantom.ecn.uiowa.edu>
	<038901c18966$64e567f0$777ba8c0@ericlaptop>
Message-ID: <87elllh6ql.fsf@phantom.ecn.uiowa.edu>

I ran the scipy.test() unit tests for my debian package.   I got four
errors (see below).    Is this normal, or did I do something wrong?

Thanks - 

Joe


======================================================================
ERROR: check_basic (test_basic.test_trapz)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "debian/scipy/usr/lib/python2.1/site-packages/scipy/tests/test_basic.py", line 400, in check_basic
NameError: global name 'trapz' is not defined
======================================================================
ERROR: check_nd (test_basic.test_trapz)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "debian/scipy/usr/lib/python2.1/site-packages/scipy/tests/test_basic.py", line 407, in check_nd
NameError: global name 'trapz' is not defined
======================================================================
ERROR: check_basic (test_basic1a.test_roots)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "debian/scipy/usr/lib/python2.1/site-packages/scipy/tests/test_basic1a.py", line 19, in check_basic
  File "debian/scipy/usr/lib/python2.1/site-packages/scipy/basic1a.py", line 52, in roots
NameError: global name 'argsort' is not defined
======================================================================
ERROR: check_inverse (test_basic1a.test_roots)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "debian/scipy/usr/lib/python2.1/site-packages/scipy/tests/test_basic1a.py", line 25, in check_inverse
  File "debian/scipy/usr/lib/python2.1/site-packages/scipy/basic1a.py", line 52, in roots
NameError: global name 'argsort' is not defined
----------------------------------------------------------------------
Ran 176 tests in 0.882s

FAILED (errors=4)
<unittest.TextTestRunner instance at 0x834a74c>
>>>






From prabhu at aero.iitm.ernet.in  Tue Dec 25 10:14:02 2001
From: prabhu at aero.iitm.ernet.in (Prabhu Ramachandran)
Date: Tue, 25 Dec 2001 20:44:02 +0530
Subject: [SciPy-dev] [OT] MayaVi license issues.
Message-ID: <15400.38842.341474.214009@monster.linux.in>

hi,

I'm resuming part of the c.l.py thread on Scientific libraries on
Python over here.  Sorry about the cross posting and off topic nature
of the post.

MayaVi (http://mayavi.sf.net) is currently distributed under the GPL.
I wrote mayavi for the community and intend that it stays that way.
Although the GPL tries to ensure that software remain free, its a
little too restrictive at times.

SciPy is distributed under a BSD like(?) license.  That may be fine
for SciPy but I think the BSD license is too non-restrictive.  I would
very much like that all future enhancements to MayaVi stay free.  If
some company decides to put 5 folks on MayaVi and make it much nicer,
I'd *like* that the new version remain free.

However, forcing the person who links to or uses MayaVi as an
application or even component to also release their software under the
GPL is a little too restrictive.  It also prevents the scipy folks
from possibly bundling mayavi along with their package even though
their code is "free".  IIRC, several folks on c.l.py expressed their
desire that mayavi (and other things) should be bundled along with
scipy.

One possiblity suggested by Travis Oliphant was to release mayavi
under the LGPL.  This makes MayaVi itself distributed under a more
restrictive license and yet allows SciPy to bundle it with their code.
However, I still dont really understand the LGPL license.  What does
it allow and what doesn't it allow?  Specifically I have a few
questions.

  (1) Can someone subclass a MayaVi class and distribute the new code
  and yet keep the source closed?  Is it worth protecting mayavi from
  such attempts?  

  (2) What does the LGPL protect actually?  What type of changes are
  allowed and what are not?

  (3) What are the advantages/disadvantages of LGPL versus the
  GPL/BSD.  Is there anything to worry about?


Thanks,
prabhu


From oliphant.travis at ieee.org  Tue Dec 25 14:46:28 2001
From: oliphant.travis at ieee.org (Travis Oliphant)
Date: Tue, 25 Dec 2001 12:46:28 -0700
Subject: [SciPy-dev] Re: Scipy-dev digest, Vol 1 #47 - 1 msg
In-Reply-To: <200112241800.fBOI05P02420@scipy.org>
References: <200112241800.fBOI05P02420@scipy.org>
Message-ID: <E16IxQA-00031i-00@mail.xmission.com>

On Monday 24 December 2001 11:00 am, you wrote:
> Send Scipy-dev mailing list submissions to
> 	scipy-dev at scipy.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://www.scipy.net/mailman/listinfo/scipy-dev
> or, via email, send a message with subject or body 'help' to
> 	scipy-dev-request at scipy.net
>
> You can reach the person managing the list at
> 	scipy-dev-admin at scipy.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Scipy-dev digest..."
>
>
> Today's Topics:
>
>    1. Re: Debian package for SciPy (Joe Reinhardt)
>
> --__--__--
>
> Message: 1
> To: <scipy-dev at scipy.org>
> Subject: Re: [SciPy-dev] Debian package for SciPy
> From: jmr at engineering.uiowa.edu (Joe Reinhardt)
> Date: Sun, 23 Dec 2001 17:11:30 -0600
> Reply-To: scipy-dev at scipy.net
>
>
> I ran the scipy.test() unit tests for my debian package.   I got four
> errors (see below).    Is this normal, or did I do something wrong?
>
> Thanks -
>
> Joe

All is well.   This is due to some rapid upgrading taking place. trapz was 
moved from basic.py to the integrate package.

The name error in roots has been fixed.

-Travis


From rob at pythonemproject.com  Thu Dec 27 12:47:31 2001
From: rob at pythonemproject.com (Rob)
Date: Thu, 27 Dec 2001 09:47:31 -0800
Subject: [SciPy-dev] compiler
Message-ID: <3C2B5EB3.DF733228@pythonemproject.com>

I see a new compiler in CVS!  Rob.

ps. I'm now working on my FEM-MOM simulator stuff.  I'm porting into
Python the mesh generator called "sift".  Its a bear.  

-- 
The Numeric Python EM Project

www.pythonemproject.com



From eric at scipy.org  Fri Dec 28 13:23:56 2001
From: eric at scipy.org (eric)
Date: Fri, 28 Dec 2001 13:23:56 -0500
Subject: [SciPy-dev] compiler
References: <3C2B5EB3.DF733228@pythonemproject.com>
Message-ID: <003e01c190c1$680fac30$777ba8c0@ericlaptop>

Hey Rob,

> I see a new compiler in CVS!  Rob.

Yep, its there.  There is quite a bit more functionality such as inlining
C/C++ within Python, but I haven't done much testing on Unix at all.  Also,
the documentation isn't finished.  I'm hoping to finish in early January.

As far as changes to stuff you do in your FDTD code, the compiled_exec()
function has been renamed to blitz(), and you don't have to pass in the
locals() anymore if you don't want to.

So,

    scipy.compiled_exec(expr,locals())

can now be called with:

    scipy.blitz(expr)

So far, I think your the only one besides me that uses this thing, so the
change shouldn't cause many people problems.

>
> ps. I'm now working on my FEM-MOM simulator stuff.  I'm porting into
> Python the mesh generator called "sift".  Its a bear.

What kind of mesh generator is it?  Is there a web link?

eric




From rob at pythonemproject.com  Sun Dec 30 12:44:47 2001
From: rob at pythonemproject.com (Rob)
Date: Sun, 30 Dec 2001 09:44:47 -0800
Subject: [SciPy-dev] RE: new compiler
Message-ID: <3C2F528F.9823C58D@pythonemproject.com>

Its a very simple mesh generator.  It you follow the links on my web
page to the EMAP code, there is a new link there that takes you right to
the EMAP5 code and docs.  I'm trying to come up with a total python port
package.   So far the mesh generator, sift works with pure MOM or pure
FEM, but not with hybrids.  I had real trouble converting linked C
structures to python classes, since some of the structure members are
arrays.  There is no simple way of doing this.  Paul Dubois is helping
me, but i bit the bullet, and removed those array classes with the
result of having to add about 20 additional numpy arrays in one of my
program versions.  Here is an example of what I am trying to do.  It
doesn't work:

from Numeric import *

class CellUnit:

    def __init__(self):
        self.start=0
        self.stop=0
        self.end=0
        self.arr=zeros((20))
        self.cellu=map(lambda dummy: CellUnit, self.arr)

    def CellU(self):
        return self.cellu

u=CellUnit().CellU()
v=CellUnit().CellU()

u[0].start=3
u[0].step=5
v[0].start=8
v[0].step=18

print 3,5,8,18

print u[0].start
print u[0].step
print v[0].start
print u[0].step
--------------------------------------------------------
Hey Rob,

> I see a new compiler in CVS!  Rob.

Yep, its there.  There is quite a bit more functionality such as
inlining
C/C++ within Python, but I haven't done much testing on Unix at all. 
Also,
the documentation isn't finished.  I'm hoping to finish in early
January.

As far as changes to stuff you do in your FDTD code, the compiled_exec()
function has been renamed to blitz(), and you don't have to pass in the
locals() anymore if you don't want to.

So,

    scipy.compiled_exec(expr,locals())

can now be called with:

    scipy.blitz(expr)

So far, I think your the only one besides me that uses this thing, so
the
change shouldn't cause many people problems.

>
> ps. I'm now working on my FEM-MOM simulator stuff.  I'm porting into
> Python the mesh generator called "sift".  Its a bear.

What kind of mesh generator is it?  Is there a web link?

eric



-- 
The Numeric Python EM Project

www.pythonemproject.com