-
-
Notifications
You must be signed in to change notification settings - Fork 565
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
implement derivatives of lazy series #34413
Comments
Branch pushed to git repo; I updated commit sha1. New commits:
|
Commit: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Changed keywords from none to LazyPowerSeries |
This comment has been minimized.
This comment has been minimized.
Author: Martin Rubey |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Dependencies: #32324 |
comment:9
I don't think there is anything we need to worry about with regards to analytic stuff (since there is an assumption the derivatives commute), but I want to confirm you also think so too. Also you have empty |
Reviewer: Travis Scrimshaw |
comment:10
Replying to @tscrim:
That's correct.
Done. Besides, I now know of a way to make sense of
The natural thing is to set
makes sense. In fact, this is what we do all the time in the doctests anyway. |
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
|
comment:13
Replying to @mantepse:
I agree that it makes a little bit of sense to think of the variable as a the unique degree one element (up to scalar). However, this would be a hack IMO because the degree one elements do not generate the ring of symmetric functions (as it is a freely generated by ei). So the result of I still do not think this extra little agreement with a completely different class (where I expect no such compatibility) and implementation is worth all of this extra complexity and effort. Although I won’t oppose it because you are not going to create some extra class for the variables (at least, judging by what you’re saying). However, to me it adds to maintenance costs without a clear benefit. Actually, isn’t what is happening just a renaming of “skew_by“? Will that be implemented here too? |
comment:14
you never sleep, do you? Yes, this is Indeed, it is a bit unclear to me whether it makes sense to implement all the methods on However, that's almost certainly for a different project. |
comment:15
Replying to @mantepse:
I wanted to convey my thoughts while you were still awake in case you wanted to respond.
It seems like that is your mathematical model is disguise. It just happens to have all of the other usual derivative properties when doing
I think we can port them over as we find them to be useful. Anyways, for follow-up tickets. Can you add the following tests: (For exact series with nonzero constant)
Calculus rules (up to an implicit sign choice):
Side note: This doesn't work over
This is the only stream that is forcing the output to be in a particular ring and an explicit example about why we shouldn't do that in |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Changed commit from |
comment:21
The doctest fails due to changes in #34494. Trivial doctest update. |
Branch pushed to git repo; I updated commit sha1 and set ticket back to needs_review. Last 10 new commits:
|
Commit: |
comment:23
Slightly too fast with updating the ticket. |
Branch pushed to git repo; I updated commit sha1 and set ticket back to needs_review. Last 10 new commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Changed branch from u/tscrim/derivatives_lazy_series-34413 to u/mantepse/derivatives_lazy_series-34413 |
Changed branch from u/mantepse/derivatives_lazy_series-34413 to |
gh-35127: Fix a very slow doctest in `sage/data_structures/stream.py` This single test used to take ~ 200s. Now it takes ~ 1.5s and I marked it long time. This was introduced in 94219d4 (#34413). <!-- ^^^^^ Please provide a concise, informative and self-explanatory title. Don't put issue numbers in there, do this in the PR body below. For example, instead of "Fixes #1234" use "Introduce new method to calculate 1+1" --> ### 📚 Description <!-- Describe your changes here in detail --> <!-- Why is this change required? What problem does it solve? --> <!-- If it resolves an open issue, please link to the issue here. For example "Closes #1337" --> ### 📝 Checklist <!-- Put an `x` in all the boxes that apply. --> <!-- If your change requires a documentation PR, please link it appropriately --> <!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I have made sure that the title is self-explanatory and the description concisely explains the PR. - [x] I have linked an issue or discussion. ### ⌛ Dependencies <!-- List all open pull requests that this PR logically depends on --> <!-- - #xyz: short description why this is a dependency - #abc: ... --> URL: #35127 Reported by: Gonzalo Tornaría Reviewer(s): Gonzalo Tornaría, Martin Rubey, Travis Scrimshaw
We implement derivatives for LazyLaurentSeries, LazyTaylorSeries and LazySymmetricFunctions
Depends on #34383
CC: @tscrim
Component: combinatorics
Keywords: LazyPowerSeries
Author: Martin Rubey
Branch/Commit:
cdea820
Reviewer: Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/34413
The text was updated successfully, but these errors were encountered: