Hi Toby, > I'm currently settling in my new home in Gothenburg, so things are a bit > hectic right now. I should be able to get a couple of days at the end of > the week to tidy PyViennaCL up. In particular, I need to keep writing > documentation, and a couple more tests for some bits of linalg > functionality.
thanks for letting us know - and enjoy your new home :-) > If there's anything you want me to concentrate on over the next > fortnight, e-mail me or ping me in IRC (I read the logs, even if I'm not > actually there most of the time!). There's the one email thread on viennacl-support which I'd like you to comment on... Other than that, there shouldn't be anything urgent. In a few days or weeks you'll also have to upload your GSoC work. > Regarding the discussion in IRC earlier today about supporting mixed > layouts etc: at least as far as PyViennaCL is concerned, it is easy to > log a warning or raise an exception given any set of operands that we > know not to be performant. Any warnings don't even need to be visible by > default; it is easy for a user to tweak the verbosity level of > PyViennaCL output at runtime (though that's not documented either, > yet!). That would be good to have. I estimate that users will be very interested in getting hints about potential performance improvements. Best regards, Karli PS: Just saw that you replied on viennacl-support. Thanks! ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ ViennaCL-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/viennacl-devel
