There are immediate plans to implement embedded number fields and qqbar in Flint/Antic (https://github.com/wbhart/antic). In fact, there will be a workshop and coding sprint in Kaiserslautern, 31 July - 4 August partially dedicated to this topic. The workshop hasn't been formally announced yet, but here is a wiki page: https://github.com/Nemocas/Nemo.jl/wiki/OSCAR-:-Antic-Workshop--and--coding-sprint
sage: a=SR(1/2)
sage: b=SR(3)
sage: %timeit _=a^b
The slowest run took 9.38 times longer than the fastest. This could mean that an intermediate result is being cached.
100000 loops, best of 3: 2.14 µs per loop
sage: %timeit _=b^a
10000 loops, best of 3: 62.1 µs per loop
The case that started me wasbut I think I can shortcutsage: a=SR(1/2) sage: b=SR(3) sage: %timeit _=a^b The slowest run took 9.38 times longer than the fastest. This could mean that an intermediate result is being cached. 100000 loops, best of 3: 2.14 µs per loop sage: %timeit _=b^a 10000 loops, best of 3: 62.1 µs per loop
Python/Cython usage here.I also wanted to scout the software landscape before any other decisions.
On Monday, May 29, 2017 at 8:39:59 AM UTC+2, Dima Pasechnik wrote:
On Monday, May 29, 2017 at 6:09:33 AM UTC+1, Ralf Stephan wrote:On Sunday, May 28, 2017 at 11:40:08 PM UTC+2, Jeroen Demeyer wrote:On 2017-05-26 15:19, Ralf Stephan wrote:
> The qqbar source does not use a lower-level library.
What do you mean with this? It actually uses quite a large fraction of
Sage (number fields, polynomials, interval arithmetic, ...)Make that "lower-language-level" i.e. C/C++. There was alsothe words "one" and "fast" in my original post.Is qqbar really so slow? Perhaps you could point out particularly slow for your purposes parts ?
--
You received this message because you are subscribed to the Google Groups "sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscribe@googlegroups.com.
Yes but if Pynac had such a type, and fast, the operations with any roots (as parts of expressions) would be much simplified. Relying on Python/Cython code from the C++ end is always tedious and slow.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
To post to this group, send email to sage-...@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "sage-devel" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sage-devel/3cSPt18Fv7Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sage-devel+...@googlegroups.com.
Yes but if Pynac had such a type, and fast, the operations with any roots (as parts of expressions) would be much simplified. Relying on Python/Cython code from the C++ end is always tedious and slow.