Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#24532 closed enhancement (wontfix)

Replace lcalc by PARI

Reported by: jdemeyer Owned by:
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: packages: standard Keywords:
Cc: embray Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: u/jdemeyer/replace_lcalc_by_pari (Commits, GitHub, GitLab) Commit: 57769fae12341d2c73ec59efe2314f1f5e4cf0cd
Dependencies: Stopgaps:

Status badges


Change History (7)

comment:1 Changed 4 years ago by embray

  • Cc embray added

comment:2 Changed 4 years ago by jdemeyer

  • Milestone changed from sage-8.2 to sage-duplicate/invalid/wontfix
  • Resolution set to wontfix
  • Status changed from new to closed

Tests are showing that (at least for some use cases) PARI is slower than lcalc. Part of the reason is that lcalc has optimizations for specific L-functions while PARI works in much larger generality.

So replacing lcalc is a bad idea.

comment:3 Changed 4 years ago by jdemeyer

  • Branch set to u/jdemeyer/replace_lcalc_by_pari

comment:4 Changed 4 years ago by jdemeyer

  • Commit set to 57769fae12341d2c73ec59efe2314f1f5e4cf0cd

I'm still pushing the branch in case somebody wants to play with it.

New commits:

57769faDeprecate lcalc; use PARI instead

comment:5 Changed 4 years ago by fbissey

That's a shame. lcalc will probably become a higher and higher maintenance cost in the future - unless upstream lcalc pick up maintenance again.

comment:6 Changed 4 years ago by embray

I don't know how lcalc works at all, but maybe said optimizations can be ported upstream to PARI?

comment:7 Changed 4 years ago by jdemeyer

lcalc is not a trivial package :-) The PARI developers are aware of lcalc and what it does. So, if it would be easy, they would already have done it.

Note: See TracTickets for help on using tickets.