-
-
Notifications
You must be signed in to change notification settings - Fork 510
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
more testsuites for lazy series rings #34552
Comments
This comment has been minimized.
This comment has been minimized.
Author: Martin Rubey |
Last 10 new commits:
|
Changed keywords from none to LazyPowerSeries |
Dependencies: #34470 |
Commit: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:5
Apparently, reversion of symmetric functions with linear coefficient different from
|
comment:6
Obviously, there was a parenthesis missing. I thought I changed that already once. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:13
The following should work, but doesn't, because reversion is not lazy enough:
In this case, |
comment:14
Replying to Martin Rubey:
This one is harder because of the nature of the tests being done. Nothing can be promised about the coefficients of the undefined series. It comes down to how much we want to promise that the code will not break on bad input. I am thinking we can change - if not coeff_stream[1]:
+ if coeff_stream._approximate_order > 1:
raise ValueError("compositional inverse does not exist")
-
- if coeff_stream[0]:
- raise ValueError("cannot determine whether the compositional inverse exists") Then we run into an issue with computing the exact order in |
comment:15
In principle, I think it is more important that For the issue at hand, I think we can rewrite - # TODO: shift instead of (self / z) should be more efficient
- g.define(z / ((self / z)(g)))
+ # the following is mathematically equivalent to
+ # z / ((self / z)(g))
+ # but more efficient and more lazy
+ g.define((~self.shift(-1)(g)).shift(1)) Here is my thinking:
|
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:58
Essentially green bot. The pyflakes warnings |
comment:59
The codestylecheck warnings are as follows:
The first two wouldn't work with
The
|
comment:60
It is interesting that the github bots will not detect the unused variables. |
comment:61
Sorry, but the linter must pass, no choice. Even if E306 is in some sense a matter of taste, it is currently required. Your def without empty line before would be the only one in the whole sage code base. About the comparison to None, this is very strange. Could you use "if not prec" instead ? or some isinstance ? What is the type of "prec" that is equal but not |
comment:62
Hi Frédéric! Concerning the second question:
|
comment:63
I'll add the missing line. Could you please also respond to comment:58? (these pyflakes warnings were missed in a completely unrelated ticket) |
comment:64
the pyflakes warning are not your responsability, but you can fix them if you want For the comparison to None, maybe this could fixed using the complicated syntax
or by adding in general a way to extract the bare value of an option somehow. |
comment:65
simpler:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:67
Cool, thank you! |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Reviewer: Travis Scrimshaw, Frédéric Chapoton |
comment:69
I am assuming Frédéric is now happy. LGTM. We can do more on further tickets. |
Changed branch from u/mantepse/lazy_series_test_suite-34552 to |
In this ticket we implement systematic tests for operations on lazy series.
Depends on #34470
CC: @tscrim
Component: combinatorics
Keywords: LazyPowerSeries
Author: Martin Rubey
Branch/Commit:
3e84c90
Reviewer: Travis Scrimshaw, Frédéric Chapoton
Issue created by migration from https://trac.sagemath.org/ticket/34552
The text was updated successfully, but these errors were encountered: