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
improve FriCAS interface #21231
Comments
comment:1
It should be able to deal with very long lines, too, possibly be using file io. This involves use of ioHook and some regexps.
I think this could work as follows: we want to map fricas types to sage constructors, possibly recursively. Recall that what's really sent to fricas is something like Now what I propose is a method which takes a parsed type, e.g.,
and so on. So, if the type is
which might be something like
|
Commit: |
Branch: /u/mantepse/21231 |
New commits:
|
comment:4
This is very beta, but I'd be very happy to receive some comments. |
Author: Martin Rubey |
New commits:
|
Changed branch from /u/mantepse/21231 to u/mantepse/21231 |
comment:6
Branch name doesn't have leading slash New commits:
|
comment:7
Replying to @vbraun:
Howto? I used
|
Dependencies: #21209 |
comment:10
(it actually doesn't depend on #21209, since it works with any installation of FriCAS but never mind) |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Sage worksheet under 7.2 |
Attachment: sage-7.2-fricas.pdf.gz Attachment: sage-7.4.beta0-fricas.pdf.gz Sage worksheet under 7.4.beta0 (typeset output fails) |
comment:12
In Sage Worksheet typeset output or FriCAS object fails with this patch on 7.4.beta0. See attached pdf files. https://github.com/sagemath/sage-prod/files/10658907/sage-7.2-fricas.pdf.gz (typeset output OK) https://github.com/sagemath/sage-prod/files/10658908/sage-7.4.beta0-fricas.pdf.gz (typeset output fails) I am not sure whether or not this example worked under 7.4.beta0 without the patch. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:15
I have a question about the The question is: the doctests work without adapting the methods.
in
|
Branch pushed to git repo; I updated commit sha1 and set ticket back to needs_review. New commits:
|
comment:97
the latest push created a mega-patch for no good reason. What was the reason for this? |
comment:98
I am sorry, I thought I am supposed to merge when a new develop appears. Could you tell me how to revert? |
comment:99
Replying to @mantepse:
only if there are merge conflicts (which you would see by the Branch field in the ticket turning red). Just revert the last commit (and push again, with -f switch). Not sure how to do this using |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits: |
comment:101
Replying to @dimpase: Thank you! |
comment:102
OK, good, back to the positively reviewed patch. |
comment:103
You should not use a bare
by
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:105
I agree - I only adapted this part of the code. |
comment:106
could you set this back to positive review? I would really like to get this into sage soon, because there will be trivial, but tedious merge conflicts all the time otherwise. I'd be grateful... |
comment:107
Well, if you don't set it to |
Changed branch from u/mantepse/fricas_interface to |
The FriCAS interface is currently very rudimentary. In particular, converting the results of a computation into sage types is available only in very few special cases.
Depends on #21209
CC: @sagetrac-bpage @hemmecke @dkrenn @dimpase
Component: interfaces
Keywords: FriCAS
Author: Martin Rubey
Branch/Commit:
e281742
Reviewer: Bill Page, Emmanuel Charpentier
Issue created by migration from https://trac.sagemath.org/ticket/21231
The text was updated successfully, but these errors were encountered: