|
From: Todd M. <jm...@st...> - 2006-01-04 18:38:57
|
I fixed a performance bug in numarray.strings so the lion's share of this problem is now gone in CVS: scipy -> numarray Int32 0.000634908676147 scipy -> numarray S1 0.000502109527588 numarray -> scipy S1 0.000125885009766 numarray -> numarray S1 0.00110602378845 Things could be further improved by adding "import" support for the newcore array protocol to numarray.strings. Todd Gary Strangman wrote: > >> Which brings up another curiosity: I'm all in favor of not having >> arbitrary limits on anything, but I'm curious what the largest rank >> NumPy array anyone has ever had a real use for is? I don't think I've >> ever used rank > 3, or maybe 4. >> >> Anyone have a use case for a very large rank array? > > > Depends on your definition of "very". In neuroimaging at least, rank 4 > is a standard dataset "unit" (3D+time). If you then include subjects, > replications (same day), and sessions (i.e., testing on different > days), that's rank=7. Can't say as I've ever reached 10 though. ;-) > > -best > Gary > > -------------------------------------------------------------- > Gary Strangman, PhD | Director, Neural Systems Group > Office: 617-724-0662 | Massachusetts General Hospital > Fax: 617-726-4078 | 149 13th Street, Ste 10018 > st...@nm... | Charlestown, MA 02129 > http://www.nmr.mgh.harvard.edu/NSG/ > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Numpy-discussion mailing list > Num...@li... > https://lists.sourceforge.net/lists/listinfo/numpy-discussion |