search

pombreda / pysal

Automatically exported from code.google.com/p/pysal
Other
0 stars 0 forks source link

optimize lag #66

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Create numpy only properties for the W.
This was shown at the DC code sprint to double the performance of the lag.

Do further profiling to identify other bottlenecks.

Original issue reported on code.google.com by schmi...@gmail.com on 23 Apr 2010 at 10:27

GoogleCodeExporter commented 9 years ago

Original comment by schmi...@gmail.com on 23 Apr 2010 at 11:19

GoogleCodeExporter commented 9 years ago 
Serge is implementing a sparseW property for W that's faster then that changes 
we made in DC.

Original comment by schmi...@gmail.com on 4 May 2010 at 9:20

GoogleCodeExporter commented 9 years ago 
lag_sparse is much faster than lag_array so eventually we might just drop 
lag_array. also, if we move the id check 
out of spatial lag and assume y is in the proper order (or have the user adjust 
y accordingly prior to calling lag) 
we can probably use just a single lag function here.

i'm holding off on these changes until the sparse builder gets optimized

Original comment by sjsrey on 17 May 2010 at 11:58

GoogleCodeExporter commented 9 years ago

Original comment by sjsrey on 23 Jul 2010 at 4:19