From janne at avocado.pc.helsinki.fi  Tue Feb  9 16:59:18 1999
From: janne at avocado.pc.helsinki.fi (Janne Sinkkonen)
Date: 09 Feb 1999 23:59:18 +0200
Subject: [Matrix-SIG] Neural Networks
In-Reply-To: "Pedro Miguel Frazão F. Ferreira"'s message of "Tue, 09 Feb 1999 15:21:26 +0000"
References: <36C05276.6299952@ualg.pt>
Message-ID: <oa7ltr1bnt.fsf@avocado.pc.helsinki.fi>

"Pedro Miguel Fraz?o F. Ferreira" <pfrazao at ualg.pt> writes:

> 	Just subscribed. Just started looking to python. I am interested in
> code for Neural Networks (specialy RBF, GRBF). Is there any
> implementation ?

I have one in product use (i.e. tested). Has k-means, adaptive choice
of center widths, and regularization built in, and it includes the
beginnings of a regression model class hierarchy, but no
documentation. Send e-mail if you're interested.

-- 
Janne

_______________________________________________
Matrix-SIG maillist  -  Matrix-SIG at python.org
http://www.python.org/mailman/listinfo/matrix-sig



From Majordomo at olegacy.gsfc.nasa.gov  Tue Feb 16 13:00:09 1999
From: Majordomo at olegacy.gsfc.nasa.gov (Majordomo at olegacy.gsfc.nasa.gov)
Date: Tue, 16 Feb 1999 13:00:09 -0500 (EST)
Subject: Majordomo results: Re: Confirmation for subscribe astropy
Message-ID: <199902161800.NAA05629@olegacy.gsfc.nasa.gov>

--

>>>> auth f67b8a6c subscribe astropy managan at llnl.gov
Succeeded.
>>>> *-*-*-*-*-*-*-*-*-*-**-*-*-*-*-*-*-*-*-*-*-
**** Command '*-*-*-*-*-*-*-*-*-*-**-*-*-*-*-*-*-*-*-*-*-' not recognized.
>>>> Rob Managan       mailto://managan at llnl.gov
**** Command 'rob' not recognized.
>>>> LLNL                      ph:  925-423-0903
**** Command 'llnl' not recognized.
>>>> P.O. Box 808, L-098       FAX: 925-423-5804
**** Command 'p.o.' not recognized.
>>>> Livermore, CA  94551-0808
**** Command 'livermore,' not recognized.
>>>> 
**** Help for Majordomo at athena.gsfc.nasa.gov:


This help message is being sent to you from the Majordomo mailing list
management system at Majordomo at athena.gsfc.nasa.gov.

This is version 1.94.4 of Majordomo.

If you're familiar with mail servers, an advanced user's summary of
Majordomo's commands appears at the end of this message.

Majordomo is an automated system which allows users to subscribe
and unsubscribe to mailing lists, and to retrieve files from list
archives.

You can interact with the Majordomo software by sending it commands
in the body of mail messages addressed to "Majordomo at athena.gsfc.nasa.gov".
Please do not put your commands on the subject line; Majordomo does
not process commands in the subject line.

You may put multiple Majordomo commands in the same mail message.
Put each command on a line by itself.

If you use a "signature block" at the end of your mail, Majordomo may
mistakenly believe each line of your message is a command; you will
then receive spurious error messages.  To keep this from happening,
either put a line starting with a hyphen ("-") before your signature,
or put a line with just the word

	end

on it in the same place.  This will stop the Majordomo software from
processing your signature as bad commands.

Here are some of the things you can do using Majordomo:

I.	FINDING OUT WHICH LISTS ARE ON THIS SYSTEM

To get a list of publicly-available mailing lists on this system, put the
following line in the body of your mail message to Majordomo at athena.gsfc.nasa.gov:

	lists

Each line will contain the name of a mailing list and a brief description
of the list.

To get more information about a particular list, use the "info" command,
supplying the name of the list.  For example, if the name of the list 
about which you wish information is "demo-list", you would put the line

	info demo-list

in the body of the mail message.

II.	SUBSCRIBING TO A LIST

Once you've determined that you wish to subscribe to one or more lists on
this system, you can send commands to Majordomo to have it add you to the
list, so you can begin receiving mailings.

To receive list mail at the address from which you're sending your mail,
simply say "subscribe" followed by the list's name:

	subscribe demo-list

If for some reason you wish to have the mailings go to a different address
(a friend's address, a specific other system on which you have an account,
or an address which is more correct than the one that automatically appears 
in the "From:" header on the mail you send), you would add that address to
the command.  For instance, if you're sending a request from your work
account, but wish to receive "demo-list" mail at your personal account
(for which we will use "jqpublic at my-isp.com" as an example), you'd put
the line

	subscribe demo-list jqpublic at my-isp.com

in the mail message body.

Based on configuration decisions made by the list owners, you may be added 
to the mailing list automatically.  You may also receive notification
that an authorization key is required for subscription.  Another message
will be sent to the address to be subscribed (which may or may not be the
same as yours) containing the key, and directing the user to send a
command found in that message back to Majordomo at athena.gsfc.nasa.gov.  (This can be
a bit of extra hassle, but it helps keep you from being swamped in extra
email by someone who forged requests from your address.)  You may also
get a message that your subscription is being forwarded to the list owner
for approval; some lists have waiting lists, or policies about who may
subscribe.  If your request is forwarded for approval, the list owner
should contact you soon after your request.

Upon subscribing, you should receive an introductory message, containing
list policies and features.  Save this message for future reference; it
will also contain exact directions for unsubscribing.  If you lose the
intro mail and would like another copy of the policies, send this message
to Majordomo at athena.gsfc.nasa.gov:

	intro demo-list

(substituting, of course, the real name of your list for "demo-list").

III.	UNSUBSCRIBING FROM MAILING LISTS

Your original intro message contains the exact command which should be
used to remove your address from the list.  However, in most cases, you
may simply send the command "unsubscribe" followed by the list name:

	unsubscribe demo-list

(This command may fail if your provider has changed the way your
address is shown in your mail.)

To remove an address other than the one from which you're sending
the request, give that address in the command:

	unsubscribe demo-list jqpublic at my-isp.com

In either of these cases, you can tell Majordomo at athena.gsfc.nasa.gov to remove
the address in question from all lists on this server by using "*"
in place of the list name:

	unsubscribe *
	unsubscribe * jqpublic at my-isp.com

IV.	FINDING THE LISTS TO WHICH AN ADDRESS IS SUBSCRIBED

To find the lists to which your address is subscribed, send this command
in the body of a mail message to Majordomo at athena.gsfc.nasa.gov:

	which

You can look for other addresses, or parts of an address, by specifying
the text for which Majordomo should search.  For instance, to find which
users at my-isp.com are subscribed to which lists, you might send the
command

	which my-isp.com

Note that many list owners completely or fully disable the "which"
command, considering it a privacy violation.

V.	FINDING OUT WHO'S SUBSCRIBED TO A LIST

To get a list of the addresses on a particular list, you may use the
"who" command, followed by the name of the list:

	who demo-list

Note that many list owners allow only a list's subscribers to use the
"who" command, or disable it completely, believing it to be a privacy
violation.

VI.	RETRIEVING FILES FROM A LIST'S ARCHIVES

Many list owners keep archives of files associated with a list.  These
may include:
- back issues of the list
- help files, user profiles, and other documents associated with the list
- daily, monthly, or yearly archives for the list

To find out if a list has any files associated with it, use the "index"
command:

	index demo-list

If you see files in which you're interested, you may retrieve them by
using the "get" command and specifying the list name and archive filename.
For instance, to retrieve the files called "profile.form" (presumably a
form to fill out with your profile) and "demo-list.9611" (presumably the
messages posted to the list in November 1996), you would put the lines

	get demo-list profile.form
	get demo-list demo-list.9611

in your mail to Majordomo at athena.gsfc.nasa.gov.

VII.	GETTING MORE HELP

To contact a human site manager, send mail to Majordomo-Owner at athena.gsfc.nasa.gov.
To contact the owner of a specific list, send mail to that list's
approval address, which is formed by adding "-approval" to the user-name
portion of the list's address.  For instance, to contact the list owner
for demo-list at athena.gsfc.nasa.gov, you would send mail to demo-list-approval at athena.gsfc.nasa.gov.

To get another copy of this help message, send mail to Majordomo at athena.gsfc.nasa.gov
with a line saying

	help

in the message body.

VIII.	COMMAND SUMMARY FOR ADVANCED USERS

In the description below items contained in []'s are optional. When
providing the item, do not include the []'s around it.  Items in angle
brackets, such as <address>, are meta-symbols that should be replaced
by appropriate text without the angle brackets.

It understands the following commands:

    subscribe <list> [<address>]
	Subscribe yourself (or <address> if specified) to the named <list>.
	
    unsubscribe <list> [<address>]
	Unsubscribe yourself (or <address> if specified) from the named <list>.
	"unsubscribe *" will remove you (or <address>) from all lists.  This
	_may not_ work if you have subscribed using multiple addresses.

    get <list> <filename>
        Get a file related to <list>.

    index <list>
        Return an index of files you can "get" for <list>.

    which [<address>]
	Find out which lists you (or <address> if specified) are on.

    who <list>
	Find out who is on the named <list>.

    info <list>
	Retrieve the general introductory information for the named <list>.

    intro <list>
	Retrieve the introductory message sent to new users.  Non-subscribers
	may not be able to retrieve this.

    lists
	Show the lists served by this Majordomo server.

    help
	Retrieve this message.

    end
	Stop processing commands (useful if your mailer adds a signature).

Commands should be sent in the body of an email message to
"Majordomo at athena.gsfc.nasa.gov". Multiple commands can be processed provided
each occurs on a separate line.

Commands in the "Subject:" line are NOT processed.

If you have any questions or problems, please contact
"Majordomo-Owner at athena.gsfc.nasa.gov".



From bridgman at lheapop.gsfc.nasa.gov  Thu Feb 18 12:05:52 1999
From: bridgman at lheapop.gsfc.nasa.gov (Dr. William T. Bridgman)
Date: Thu, 18 Feb 1999 12:05:52 -0500
Subject: AstroPy: Desired Platform Support
Message-ID: <v03102801b2f1c4e67daf@[128.183.19.179]>

After some discussions with Paul Barrett, here's a list of platforms that
we hope to support.  We need to determine who would be interested in doing
testing and/or porting to these various platforms.  If there's anything
we've left off, please notify us.  I'd like to build a matrix of packages
vs. platforms where we can say a given package has actually been tested on
a given platform.  I want to set this up as a table on a web page.

Here's the current platform/OS list:
* Solaris
* Alpha/DEC
* Linux/Alpha
* Linux x86
* Windows 95/98
* Windows NT
* MacOS
* MkLinux/LinuxPPC

Did we miss anyone?

I am doing some MacOS support and I also have MkLinux (though not fully
configured and operational yet - it did come with Python 1.5.1!).

I can say that the py_astro package seems to work fine under MacOS.
However, I've not been able to check out PyEphem since that seems to be
specifically X-windows (though a port using Tkinter may be possible?).  I'm
working on the Mac support for Paul's binary table reader in PyFITS.  I
believe he's covering Solaris and Linux x86 for PyFITS.

Who is interested in testing py_astro (should be easy - it's pure Python) &
PyEphem on their platforms and reporting the results to the list?  If you
encountered any differences in installation compared to the package
instructions, that would be nice to know as well so we can develop that
knowledge base.

Thanks,
Tom


--
Dr. William T."Tom" Bridgman          Raytheon ITSS
NASA/Goddard Space Flight Center
Code 664                              bridgman at lheapop.gsfc.nasa.gov
Greenbelt, MD 20771                   (301) 286-1346




From david.buscher at durham.ac.uk  Thu Feb 18 12:20:29 1999
From: david.buscher at durham.ac.uk (david.buscher at durham.ac.uk)
Date: Thu, 18 Feb 1999 17:20:29 +0000 (GMT)
Subject: AstroPy: Desired Platform Support
In-Reply-To: <v03102801b2f1c4e67daf@[128.183.19.179]>
Message-ID: <Pine.OSF.4.05.9902181716080.20429-100000@dugem1.dur.ac.uk>

I can do testing on SGI/Irix 6.2, but it will be only on a spare-time
effort basis (i.e. not a very rapid turn-round!). Automatic test scripts
would be a bonus in this case.

David

----------------------------------------+-------------------------------------
 David Buscher                          |  Phone  +44 191 374 7462
 Dept of Physics, University of Durham, |  Fax    +44 191 374 3709
 South Road, Durham DH1 3LE, UK         |  Email  david.buscher at durham.ac.uk
----------------------------------------+-------------------------------------




From godzilla at netmeg.net  Thu Feb 18 12:24:47 1999
From: godzilla at netmeg.net (Les Schaffer)
Date: Thu, 18 Feb 1999 12:24:47 -0500 (EST)
Subject: AstroPy: Desired Platform Support
In-Reply-To: <v03102801b2f1c4e67daf@[128.183.19.179]>
References: <v03102801b2f1c4e67daf@[128.183.19.179]>
Message-ID: <14028.19679.275228.675496@localhost>

> Who is interested in testing py_astro (should be easy - it's pure
> Python) & PyEphem on their platforms and reporting the results to
> the list?

i'll test it under linux/x86.

----------

by the way, i am working on a python module to read data from VICAR
file formats of data sent from the Galileo mission to Jupiter. my work
is on the Jovian ring system.

So far i have a simple module which reads the label headers,
determines the image size, reads the data in from file and creates a
Numeric array from same, eventually to be shipped into PIL or Khoros
or something for visualization.

what i need to do next is work on determining radial and longitudinal
coordinates from spacecraft position and orientation, and ultimately
will build a module that will allow me to determine pixel brightness
along narrow rings of constant radius. the jovian ring has some
interesting radial brightness variations which i am musing on. 

anyone else out there using VICAR/Python/PIL?

-- 
____        Les Schaffer              ___| --->> Engineering R&D <<---
Theoretical & Applied Mechanics          |  Designspring, Inc. 
Center for Radiophysics & Space Research |  http://www.designspring.com/
Cornell Univ.  schaffer at tam.cornell.edu  |  les at designspring.com


From bridgman at lheapop.gsfc.nasa.gov  Thu Feb 18 12:48:23 1999
From: bridgman at lheapop.gsfc.nasa.gov (Dr. William T. Bridgman)
Date: Thu, 18 Feb 1999 12:48:23 -0500
Subject: AstroPy: Desired Platform Support
In-Reply-To: <14028.19679.275228.675496@localhost>
References: <v03102801b2f1c4e67daf@[128.183.19.179]>
 <v03102801b2f1c4e67daf@[128.183.19.179]>
Message-ID: <v03102803b2f200ca8ff5@[128.183.19.179]>

Okay,

I've just added a few things to the web site.  A preliminary platform
matrix of what I currently know about and a link to the PyFITS paper.
Let's hope we can make this matrix a little less sparse fairly soon.

This is also a part time project for me, at least until I can get some
grant money for it. :^)

For those checking the packages on their various platforms - mention any
bugs or other enhancements.

Test scripts are definitely a plus.  Anyone knowledgeable in this?

Do we want to add any links to individuals for specific efforts, contacts,
or other projects, such as Les' VICAR work?

Tom

--
Dr. William T."Tom" Bridgman          Raytheon ITSS
NASA/Goddard Space Flight Center
Code 664                              bridgman at lheapop.gsfc.nasa.gov
Greenbelt, MD 20771                   (301) 286-1346




From patrickd at magus.stx.com  Thu Feb 18 12:53:59 1999
From: patrickd at magus.stx.com (Patrick Dahiroc)
Date: Thu, 18 Feb 1999 12:53:59 -0500 (EST)
Subject: AstroPy: GnuSkies Project
In-Reply-To: <v03102801b2f1c4e67daf@[128.183.19.179]>
Message-ID: <Pine.HPP.3.91.990218123248.25603A-100000@magus.stx.com>

hi all

i was scouring the web last night looking for programming project to join 
in the near future, when i stumbled upon GnuSkies - a GPL'd xephem program.
it is still under development but it looks like that they are trying to 
write a  graphical oribit determination package. you can take a look at it at

	http://nanette.net

i am a python and astronomy newbie but would like to learn both well. i 
looked at the astropy website and saw that you need to write time and 
coordinates conversion modules. what time systems and coordinate systems 
are the conversions to be done in? i would not mind writing these modules 
if it is not written yet, although it might take some time since i am a 
newbie :)  

patrick


From npirzkal at eso.org  Thu Feb 18 13:35:20 1999
From: npirzkal at eso.org (Norbert Pirzkal)
Date: Thu, 18 Feb 99 19:35:20 +0100
Subject: AstroPy: Desired Platform Support
In-Reply-To: <v03102801b2f1c4e67daf@[128.183.19.179]>
References: <v03102801b2f1c4e67daf@[128.183.19.179]>
Message-ID: <199902181835.TAA00247@hq.eso.org>

A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 1716 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/astropy/attachments/19990218/02713dac/attachment.bin>

From godzilla at netmeg.net  Thu Feb 18 14:00:25 1999
From: godzilla at netmeg.net (Les Schaffer)
Date: Thu, 18 Feb 1999 14:00:25 -0500 (EST)
Subject: AstroPy: Test results: pyephem and py_astro: linux x86
In-Reply-To: <v03102803b2f200ca8ff5@[128.183.19.179]>
References: <v03102801b2f1c4e67daf@[128.183.19.179]>
	<v03102803b2f200ca8ff5@[128.183.19.179]>
Message-ID: <14028.25417.435363.877192@localhost>

1.) pyephem: pyephem-1.0.1.tar.gz

built, installed and tested successfully straight out of the box on
linux x86/glibc system. the libastro directory uses a Makefile
generated by xmkf, and if you are like me, your system uses gcc for
the libastro but egcs for the ephemcmodule, but this is of no
consequence and can  befixed by tinkering with the Makefile in
libastro, ie, change line 190:

               CC = gcc
to
	       CC = egcc

i havent tried the rpm's but if they are as well constructed as this
tar.gz kit, everything should be fine.


2.) py_astro: py_astro.tar

all python (no C/compiling).

the example runs okay. there are NO TEST SCRIPTS. the README has an
example which is incorrect as follows:

(gustav)~/system/py_astro/: grep astro README 

>>> import astro
>>> time=astro.Time(-70,40,0)
>>> sun=astro.Planet('sun',time)
>>> venus=astro.Planet('venus',sun_set.Time)

all these astro should be Astro, ie:

>>> import Astro
>>> time=Astro.Time(-70,40,0)
>>> sun=Astro.Planet('sun',time)
>>> venus=Astro.Planet('venus',sun_set.Time)


-- 
____        Les Schaffer              ___| --->> Engineering R&D <<---
Theoretical & Applied Mechanics          |  Designspring, Inc. 
Center for Radiophysics & Space Research |  http://www.designspring.com/
Cornell Univ.  schaffer at tam.cornell.edu  |  les at designspring.com


From Oliphant.Travis at mayo.edu  Tue Feb  9 11:49:08 1999
From: Oliphant.Travis at mayo.edu (Travis E. Oliphant)
Date: Tue, 09 Feb 1999 10:49:08 -0600
Subject: [Matrix-SIG] A full blown interactive data analysis environment. (resent)
Message-ID: <36C06704.B50AD87F@mayo.edu>

> We'd then pick one to use and
> write what we needed to get it to interface well.  That might be a
> SWIG wrapper or a piece of C/C++ code that translated the data to our
> interchange formats. 

To try and be precise, so that we understand each other, explain what
more we would do than what I did in producing the cephesmodule and the
fftw module, besides put them together into one package and write better
documentaion?

If that is the basic idea, just bigger scale and more packages,  than
let's go do it, I'm in.

Perhaps a good way to get this going is to take FFTW or cephes which
I've already got into a useable form and discuss what changes to make to
make them fit better into the desired scheme.  For that matter we could
start with LAPACK and see what could be done there.  It would help me,
if someone could clarify what is wrong (if anything) with the way all of
these libraries are currently used with Python.  (Is it just that they
don't all come in one big tar file and use individual-style make files
rather than one big one?)

As for packages we need at least these as far as I see (let's get the
list rolling):

FFT  (my vote is for FFTW)
LinearAlgebra
Random Numbers
Ordinary Differential Equations (ODEPACK?)
Integration (QUADPACK?)
Optimization (I know there's something on netlib)
Root finding (Equation solving)
Filter package (remez exchange algorithm, low level linear iir or fir
filter function, etc.) (I've got something like this in development).

Graphics and plotting:  This will be the problem I fear for
cross-platform.  How about we get going and talk about this one once we
have the Numerics happening....maybe something will surface elsewhere in
the meantime?

I vote for help written in LaTeX and translated to TeXinfo and HTML.

But again, it is also critical that we have some sort of interactive
help system implemented for the package to be useful to the novice.

Looking for feedback and someone to blow the whistle :-)

--Travis

P.S.  We really need to set up a CVS server somewhere and get going on
the code development.  That way we could actually have code to comment
to each other on instead of just ideas.  I've never set up CVS before. 
Could we get some space at the Starship and set it up there.  Alas, I
don't have a PSA membership at the moment...

_______________________________________________
Matrix-SIG maillist  -  Matrix-SIG at python.org
http://www.python.org/mailman/listinfo/matrix-sig



From pavlos at gaaros.msrc.sunysb.edu  Thu Feb 18 17:45:47 1999
From: pavlos at gaaros.msrc.sunysb.edu (Pavlos Christoforou)
Date: Thu, 18 Feb 1999 17:45:47 -0500 (EST)
Subject: AstroPy: Test results: pyephem and py_astro: linux x86
In-Reply-To: <14028.25417.435363.877192@localhost>
Message-ID: <Pine.LNX.3.96.990218174400.21696D-100000@gaaros.msrc.sunysb.edu>

On Thu, 18 Feb 1999, Les Schaffer wrote:

> 2.) py_astro: py_astro.tar
> 
> all python (no C/compiling).
> 
> the example runs okay. there are NO TEST SCRIPTS. the README has an
> example which is incorrect as follows:

What kind of test scripts should I include?
> 
> all these astro should be Astro, ie:
> 
> >>> import Astro
> >>> time=Astro.Time(-70,40,0)

I will fix it some time tomorrow

Thanks

Pavlos



From bridgman at lheapop.gsfc.nasa.gov  Wed Feb 24 08:25:33 1999
From: bridgman at lheapop.gsfc.nasa.gov (Dr. William T. Bridgman)
Date: Wed, 24 Feb 1999 08:25:33 -0500
Subject: AstroPy: Test results: py_astro.py module on Macintosh
Message-ID: <v03102800b2f9acb6fd21@[128.183.19.179]>

I tried to get to Pavlos' page to report this but it seems to be unaccessible.

Using MacOS 8.0 and Python 1.5.1, I basically encountered the same problem
as Les reported, that the description in the README file incorrectly loads
the module as 'astro' when it should be 'Astro'.

Otherwise, everything seems to work as advertised.

One recommended enhancement: allow setting of the equinox for equatorial
coordinate conversions.  I believe the Duffett-Smith book used Equinox 1950
throughout when most instruments today are using Equinox 2000.

Hope we can get some more platform tests performed.

Tom

--
Dr. William T."Tom" Bridgman          Raytheon ITSS
NASA/Goddard Space Flight Center
Code 664                              bridgman at lheapop.gsfc.nasa.gov
Greenbelt, MD 20771                   (301) 286-1346


__________________________________________________
AstroPy mailing list  -  astropy at athena.gsfc.nasa.gov
http://lheawww.gsfc.nasa.gov/~bridgman/AstroPy/


From pavlos at gaaros.msrc.sunysb.edu  Wed Feb 24 15:17:38 1999
From: pavlos at gaaros.msrc.sunysb.edu (Pavlos Christoforou)
Date: Wed, 24 Feb 1999 15:17:38 -0500 (EST)
Subject: AstroPy: Test results: py_astro.py module on Macintosh
In-Reply-To: <v03102800b2f9acb6fd21@[128.183.19.179]>
Message-ID: <Pine.LNX.4.04.9902241513390.493-100000@gaaros.msrc.sunysb.edu>

The Zope reporting site should be now accessible.

Unfortunately we had problems with malicious crackers and I spend last
night re-installing linux. For those of you using linux I suggest you
upgrade to the latest kernel and ftp servers. 


Thanks for the suggestion. I will be away until monday. I will look into
it as soon as I come back.

Good Luck to you all.

Pavlos

On Wed, 24 Feb 1999, Dr. William T. Bridgman wrote:

> I tried to get to Pavlos' page to report this but it seems to be unaccessible.
> 
> Using MacOS 8.0 and Python 1.5.1, I basically encountered the same problem
> as Les reported, that the description in the README file incorrectly loads
> the module as 'astro' when it should be 'Astro'.
> 
> Otherwise, everything seems to work as advertised.
> 
> One recommended enhancement: allow setting of the equinox for equatorial
> coordinate conversions.  I believe the Duffett-Smith book used Equinox 1950
> throughout when most instruments today are using Equinox 2000.
> 
> Hope we can get some more platform tests performed.
> 

__________________________________________________
AstroPy mailing list  -  astropy at athena.gsfc.nasa.gov
http://lheawww.gsfc.nasa.gov/~bridgman/AstroPy/


From bridgman at lheapop.gsfc.nasa.gov  Thu Feb 25 12:34:15 1999
From: bridgman at lheapop.gsfc.nasa.gov (Dr. William T. Bridgman)
Date: Thu, 25 Feb 1999 12:34:15 -0500
Subject: AstroPy: WWW Page updates, etc.
Message-ID: <v03102802b2fb3842ec68@[128.183.19.179]>

I've added the MacOS platform test of the pyastro module to Pavlos' nifty
AstroPy module tracking page.  Works nice.

I've also added a link on the main AstroPy page to Travis Oliphant's
Numerical Python page.  His cephesmodule & Sigtoolsmodule may have
applications in astronomy.  He also reports that they should be fairly
platform independent.  We might want to conduct some platform tests on
these as well.

Thanks,
Tom

--
Dr. William T."Tom" Bridgman          Raytheon ITSS
NASA/Goddard Space Flight Center
Code 664                              bridgman at lheapop.gsfc.nasa.gov
Greenbelt, MD 20771                   (301) 286-1346


__________________________________________________
AstroPy mailing list  -  astropy at athena.gsfc.nasa.gov
http://lheawww.gsfc.nasa.gov/~bridgman/AstroPy/


From bridgman at lheapop.gsfc.nasa.gov  Fri Feb 12 16:48:08 1999
From: bridgman at lheapop.gsfc.nasa.gov (Dr. William T. Bridgman)
Date: Fri, 12 Feb 1999 16:48:08 -0500
Subject: [Matrix-SIG] Announcing the Astronomical Python mailing list
Message-ID: <v03102806b2ea32726907@[128.183.19.179]>

Why use Python in astronomy?

Many astronomers use scripting and scripting-type languages in astronomical
data analysis.  Some are very expensive.  Others lack portability between
different operating system and processor architectures.  Still others lack
powerful methods for manipulating numerical data.  Python is free, runs on
a multitude of system architectures, and can handle numerical processing.
What Python currently lacks is a large library of fundamental routines
needed by the astronomical community.

That is the goal of this mailing list.

We want to establish a nexus for development and distribution of
Python-based  routines and other software to address the needs of the
astronomical community.  You can find out more about what's been done and
what is planned at our website (which is still under construction)

http://lheawww.gsfc.nasa.gov/~bridgman/AstroPy/

If you are interested in participating in this project, send mail to
majordomo at athena.gsfc.nasa.gov with

subscribe astropy

as the message text. You will be sent a confirmation request to which you
must respond before being added to the list.

Thanks for your attention.

--
Dr. William T."Tom" Bridgman          Raytheon STX
NASA/Goddard Space Flight Center
Code 664                              bridgman at lheapop.gsfc.nasa.gov
Greenbelt, MD 20771                   (301) 286-1346



_______________________________________________
Matrix-SIG maillist  -  Matrix-SIG at python.org
http://www.python.org/mailman/listinfo/matrix-sig



From ryszard at moldyn.com  Tue Feb  9 13:47:11 1999
From: ryszard at moldyn.com (Ryszard Czerminski)
Date: Tue, 9 Feb 1999 13:47:11 -0500 (EST)
Subject: [Matrix-SIG] Re: a full-blown interactive data analysis environment
In-Reply-To: <199902091746.SAA02706@dirac.cnrs-orleans.fr>
Message-ID: <Pine.LNX.3.95.990209132459.831D-100000@mpc3>


It would help a lot to start to develop some document
which would describe what do we want from this new package
(i.e. requirements).

This can be a good basis for further discussion.

It should probably include as well on some general
level analysis and description of existing packages
in this field (matlab, idl, root (http://root.cern.ch),
scilab - to name the few) and what makes them inadequate
enough to justify development of
yet-another-data-analysis-package.

One basic reason - at least for this group - is lack of
Python front-end (:-).

Ryszard

Ryszard Czerminski         phone : (617)354-3124 x 10
Moldyn, Inc.               fax   : (617)491-4522
955 Massachusetts Avenue   e-mail: ryszard at moldyn.com
Cambridge MA, 02139-3180   or      ryszard at photon.com

On Tue, 9 Feb 1999, Konrad Hinsen wrote:

> > My goal here is to get a core of standard routines that are used in
> > many fields of science into a coherent package with good docs, and to
> > integrate it initially with Python.  The point is that then *any*
> 
> Sorry, but I still don't see what you are planning to do...
> My impression is that generic low-level libraries already exist.
> How exactly does your idea differ from combining LAPACK, FFTPACK, etc.
> into one tar file and write wrappers and documentation for all of it?
> 
> Konrad.
> -- 
> -------------------------------------------------------------------------------
> Konrad Hinsen                            | E-Mail: hinsen at cnrs-orleans.fr
> Centre de Biophysique Moleculaire (CNRS) | Tel.: +33-2.38.25.55.69
> Rue Charles Sadron                       | Fax:  +33-2.38.63.15.17
> 45071 Orleans Cedex 2                    | Deutsch/Esperanto/English/
> France                                   | Nederlands/Francais
> -------------------------------------------------------------------------------
> 
> _______________________________________________
> Matrix-SIG maillist  -  Matrix-SIG at python.org
> http://www.python.org/mailman/listinfo/matrix-sig
> 


_______________________________________________
Matrix-SIG maillist  -  Matrix-SIG at python.org
http://www.python.org/mailman/listinfo/matrix-sig