Rob Beezer wrote: > Jason: Thanks for the tune-up. I'm not surprised that there are some > efficiencies to be had. I'll get the wiki, and other copies of the > worksheet, updated this evening. >
I spent a lot more time working on this @interact (since I plan to use it in class today :), and published my result at http://www.sagenb.org/home/pub/256/ The enhancements include: * a quick class to use fast_float on vectors, so evaluations take about 1/10 to 1/100 the time * added osculating circles * minor other performance changes * Used a different function for the 3d interact to be a little faster on startup Thanks, Jason > Jason and Carl: It'd be great if vector-valued functions continued to > "just work" after being hit by fast_float so students could experiment > with them. In other words, if fast_float had an object of type vector > as input, the output would continue to have type vector. For example, > it would be confusing if "+" used between two "vectors" became the > list operation of concatenation, rather than the vector space > operation of component-wise addition. > > On Feb 16, 2:18 pm, jason-s...@creativetrax.com wrote: > >> Carl Witty wrote: >> >>> On Mon, Feb 16, 2009 at 1:36 PM, <jason-s...@creativetrax.com> wrote: >>> >>>> I found that vectors should be handled by fast_float to create callable >>>> vectors. I guess Carl is working on the fast_float code to do stuff >>>> like this (arrays in fast_float; I've CCd him in case he isn't >>>> subscribed here). >>>> >>> I haven't been thinking about the high-level interface so much, but >>> I'll certainly be working on that too. >>> >>> I think that currently if you give fast_float a list of expressions, >>> it returns a list of callables. I'm not sure what your request is; >>> you want to change it to return a single callable that returns a list? >>> >> That would be consistent usage with vectors. If I pass a symbolic >> vector (not a list) to fast_float, a "vector" should be returned, i.e., >> a single callable that returns a list, or even better, returns an RDF >> vector. >> >> I can see the use-case for passing a list of callables and receiving a >> list of callables, so I wouldn't change that behavior. >> >> Jason >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sage-edu" group. To post to this group, send email to sage-edu@googlegroups.com To unsubscribe from this group, send email to sage-edu+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-edu?hl=en -~----------~----~----~----~------~----~------~--~---
