On Sun, Jan 08, 2012 at 08:23:40PM +0100, Peter Prettenhofer wrote: > thus, we have to change the memory layout of > `coef_` from c to fortran style?
This is an interesting solution. Its a double-edged sword: depending on what is done with coef_ C or Fortran order will be preferred. If we actually know what is going to be done with it, we can make an optimal decision, and optionaly copy, using np.asfortranarray. Depending on the application, it may be worth copying or not. So we have two decisions to make: 1. Should we add an (optional) np.asfortranarray that does a copy? 2. Should we store coef_ as fortran ordered. What do people think? Gaël PS: That old demon of ordering came back to bite when I was working on compressed persitence lately. It's a bit hidden in the following blog post http://gael-varoquaux.info/blog/?p=159 ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ Scikit-learn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
