Re: [sage-devel] Re: Poll: make giacpy_sage a standard package

[Han Frederic]

First, thank you for this discussion.

About the sage pip install project. The problem is that I don't know at all 
what will be available.
But if you are done with sage's  pyx files in src/sage/libs then it should 
be similar with giacpy_sage. 

It is indeed rare for an spkg to be linked to the sage library and 
giacpy_sage is 
more similar to the cython files in src/sage/libs than to an external 
package.

The original ticket https://trac.sagemath.org/ticket/15226 six years ago 
about giacpy_sage
was a sage patch. It just ended with no answer but with the current 
giacpy_sage
it is still easy to put 4 files of giacpy_sage in sage's source tree 
src/sage/libs, adjust
src/module_list.py and let sage's setup.py build giacpy_sage. Then you 
don't need an external package at all.

This is related to Vincent's question. There are many cython files in 
sage/libs related
to cypari2. Currently giacpy_sage have none. We need one of the following
(to not lose any features) either giacpy_sage is an external package linked 
to the sage library
or a part of giacpy_sage (or all of it, because it is just few files) is 
inside sage. Any of these
solutions is fine for me. But being in between is more work and my skills 
and time are limited.


The python package have a different name: giacpy. This was the only request 
I had during the previous vote where all the focus turned on giac and where 
giacpy_sage was forgotten.
(cf https://groups.google.com/d/topic/sage-devel/HI0uZra5_iI/discussion)
I don't see any conflict in having both. Sage could load the python package 
but it is just less interesting than loading giacpy_sage.

A minimal python is able to use the giacpy package obtain a full computer 
algebra system. I don't want to break this with the in between solution (1 
python package and files in sage).
It is important for me that a window user with no development tools looks 
to be  able
to do with a minimal python installation:
python -m pip install giacpy

and have it. It was very difficult for me to provides these binaries, and I 
don't want to break this.

giac and sage are both computer algebra systems, so there have have many 
interactions that are meaningless in a standalone python. 


Another remark:  giac is a standard package and giacpy_sage test it more. 
For instance this ticket 
https://trac.sagemath.org/ticket/27306
was a giac bug in a new version of giac. It was not related to giacpy_sage 
and I guess that it would have been detected during the upgrade of the giac 
package if giacpy_sage was standard, while it was detected after.

Best 

Frederic

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f8f821da-50d7-4319-9477-57ff8a55fcfc%40googlegroups.com.

Re: [sage-devel] sage 8.9beta4 ntl

[Han Frederic]

Thank you!

Le vendredi 2 août 2019 21:55:14 UTC+2, Dima Pasechnik a écrit :
>
> On Fri, Aug 2, 2019 at 10:42 PM Dima Pasechnik  > wrote: 
> > 
> > On Fri, Aug 2, 2019 at 10:10 PM Han Frederic  > wrote: 
> > > 
> > > Hello, 
> > > I have something strange (fedora 29, amd64) 
> > > I have cloned sage 8.9beta4 
> > > and make it. All seems functionnal but I realised that ntl is not 
> built. This looks strange because giac is built and ntl is listed in the 
> file: 
> > > 
> > > build/pkgs/giac/dependencies 
> > > 
> > > Moreover I have ntl and other giac deps from fedora and now the system 
> ntl is used. 
> > > 
> > > (sage-sh) fred@localhost:sage$ ldd local/lib/libgiac.so 
> > > linux-vdso.so.1 (0x7ffc4ffc2000) 
> > > libntl.so.38 => /lib64/libntl.so.38 (0x7f312e038000) 
> > > libpari-gmp.so.6 => 
> /home/fred-dev/sage/develop/sage/local/lib/libpari-gmp.so.6 
> (0x7f312d791000) 
> > > libgsl.so.23 => 
> /home/fred-dev/sage/develop/sage/local/lib/libgsl.so.23 
> (0x7f312d50e000) 
> > > 
> > > I don't think it happened on sage 8.8. 
>
> in fact, https://trac.sagemath.org/ticket/27822 was already in 8.8 
> and system NTL is already usable there. But you need to rebuild from 
> scratch 
> or, at least, expicitly uninstall Sage's NTL (and rebuild) to use the 
> system NTL. 
>
> > > 
> > > Can you reproduce this? 
> > 
> > Well, this is how it is meant to be! 
> > See https://trac.sagemath.org/ticket/27330 
> > 
> > E.g. if you have a compatible NTL installed, it will be used instead 
> > of a vendored version. 
> > 
> > 
> > 
> > 
> > > 
> > > -- 
> > > 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-...@googlegroups.com . 
> > > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/d118a3dd-5a54-474b-8d2e-3af9149441aa%40googlegroups.com.
>  
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/0339710a-15b5-4b41-83e8-d63a7e2f82ca%40googlegroups.com.

[sage-devel] sage 8.9beta4 ntl

[Han Frederic]

Hello,
I have something strange (fedora 29, amd64)
I have cloned sage 8.9beta4
and make it. All seems functionnal but I realised that ntl is not built. 
This looks strange because giac is built and ntl is listed in the file:

build/pkgs/giac/dependencies

Moreover I have ntl and other giac deps from fedora and now the system ntl 
is used. 

(sage-sh) fred@localhost:sage$ ldd local/lib/libgiac.so
linux-vdso.so.1 (0x7ffc4ffc2000)
libntl.so.38 => /lib64/libntl.so.38 (0x7f312e038000)
libpari-gmp.so.6 => /home/fred-dev/sage/develop/sage/local/lib/libpari-
gmp.so.6 (0x7f312d791000)
libgsl.so.23 => /home/fred-dev/sage/develop/sage/local/lib/libgsl.so.23 
(0x7f312d50e000)

I don't think it happened on sage 8.8.

Can you reproduce this?

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d118a3dd-5a54-474b-8d2e-3af9149441aa%40googlegroups.com.

Re: [sage-devel] Giac fails to build

[Han Frederic]

Le vendredi 20 octobre 2017 05:38:57 UTC+2, Timo Kaufmann a écrit :
>
> After adding one more depencency (hevea) the compilation succeeds. Thank 
> you for your help.
>
> It needs quite some dependencies that are not mentioned on the README's 
> instructions though (like hevea and texlive). Are those just undocumented 
> or does it depend on some build options?
>

Hello,
My experience is the following:

In the giac source archive the doc is prebuilt (ie the html files built 
from the tex files are already in the archive) so after a configure if you 
cd in the doc dir
make does nothing and don't need all these dependencies (hevea...) and make 
install just copy files.

But your sed changed the Makefiles in the doc dir so now your built try to 
recreate all these html files from the tex files and you need many more 
dependencies. 

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: make giac/giacpy a standard package

[Han Frederic]

Le samedi 3 décembre 2016 13:55:30 UTC+1, Jeroen Demeyer a écrit :
>
> On 2016-07-03 21:08, Han Frederic wrote: 
> > Yes these binaries were left in upstream 1.2.2-37 source tarball, but it 
> > is a mistake. 
>
> How do you create those binaries? It should be done by a script ("make 
> dist" if you use autotools), not by hand. 
>

I don't create binaries, they were alerady in B.Parisse's tarball by 
mistake from (1.2.2-35 to 1.2.2-45) cf the bigger files in:
http://www-fourier.ujf-grenoble.fr/~parisse/debian/dists/stable/main/source/

But I have missed they were there, I should have deleted them.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: make giac/giacpy a standard package

[Han Frederic]

Hi ralf,
I am also lost because what you ask in this trac is what is done by the 
build/pkg/giac/spkg-src
{{{
VERSION="1.2.2"
VERSIONREV="103"

# The upstream tarball name is: giac"$SOURCEORIG".tar.gz
SOURCEORIG=_"$VERSION"-"$VERSIONREV"

...

# Downloading upstream source
sage-download-file 
"http://www-fourier.ujf-grenoble.fr/~parisse/debian/dists/stable/main/source/giac$SOURCEORIG.tar.gz;
 
"giac$SOURCEORIG.tar.gz"
}}}
and I can see that bzip2, gap and singular also use a spkg-src so it looks 
allowed for a standard package to use an spkg-src when there is a reason 
right?
In giac I delete all the french html doc to have a 15Mb gpl tarball instead 
of the 49Mb original one. (the french html doc is only on a non commercial 
licence that's why I delete it)

So may be there is a misunderstanding somewhere?

If anyone still have explicit requirement for the giac spkg let me know.

Best
Frederic


Le vendredi 2 décembre 2016 16:54:29 UTC+1, Ralf Stephan a écrit :
>
> I opened https://trac.sagemath.org/ticket/22011
> to prepare the giac package to use the official tarballs.
>
> Regards,
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: make giac/giacpy a standard package

[Han Frederic]

Le vendredi 2 décembre 2016 11:06:34 UTC+1, Ralf Stephan a écrit :
>
> On Friday, December 2, 2016 at 10:51:47 AM UTC+1, Han Frederic wrote:
>>
>> We had this argument already. If you prefer to keep it this way, please 
>>>> provide us a  VCS (git preferred) repo
>>>> off which we can label releases by the latest commit in the master 
>>>> branch, or something like this.
>>>> This way at least meaningful bug reports can be filed. Please...
>>>> We (or in fact any Linux/OSX distribution system) cannot work with 
>>>> different tarballs that are named the same, we do not have tools to 
>>>> support 
>>>> this. Each tarball change without name change triggers an alert screaming 
>>>> that it has been tampered with.
>>>>
>>>
>> But the giac spkg is always built from these sources via the spkg-src:
>>
>> http://www-fourier.ujf-grenoble.fr/~parisse/debian/dists/stable/main/source/
>> and they have a meaningful name. Ex: spkg 1.2.2.103 is from source 
>> 1.2.2-103.
>>
>
> I think numbering changes at level 4 are the problem that Dima (quote 
> above) meant.
> None of the toolos support it.
>
 
 I thought that dima was talking of the unstable file with only 1.2.2 in 
the name but was  OK with 1.2.2-xx?


> On 5/07/2016, at 17:13, parisse <bernard...@ujf-grenoble.fr> wrote: 

> > 
> > disable-gui should be working. If not, then I probably made a mistake 
> while copying the archive, you can try 
> http://www-fourier.ujf-grenoble.fr/~parisse/giac/giac-1.2.2.tar.gz 
> <http://www.google.com/url?q=http%3A%2F%2Fwww-fourier.ujf-grenoble.fr%2F%7Eparisse%2Fgiac%2Fgiac-1.2.2.tar.gz=D=1=AFQjCNHQd8S8bF4zC4pJFuh933lb3GvgDg>
>  
>
> Yes that tarball has the goods. I’ll wait for a new 1.2.2-xx tarball 
> though. No self respecting 
> packager wants to deal with an upstream tarball which changes all the 
> times. 


 


-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: make giac/giacpy a standard package

[Han Frederic]

Le vendredi 2 décembre 2016 08:37:20 UTC+1, Ralf Stephan a écrit :
>
> On Tuesday, July 5, 2016 at 9:31:04 AM UTC+2, Dima Pasechnik wrote:
>>
>> Yes that tarball has the goods. I’ll wait for a new 1.2.2-xx tarball 
>>> though. No self respecting 
>>> packager wants to deal with an upstream tarball which changes all the 
>>> times. 
>>
>>  
>> We had this argument already. If you prefer to keep it this way, please 
>> provide us a  VCS (git preferred) repo
>> off which we can label releases by the latest commit in the master 
>> branch, or something like this.
>> This way at least meaningful bug reports can be filed. Please...
>> We (or in fact any Linux/OSX distribution system) cannot work with 
>> different tarballs that are named the same, we do not have tools to support 
>> this. Each tarball change without name change triggers an alert screaming 
>> that it has been tampered with.
>>
>
>
But the giac spkg is always built from these sources via the spkg-src:
http://www-fourier.ujf-grenoble.fr/~parisse/debian/dists/stable/main/source/
and they have a meaningful name. Ex: spkg 1.2.2.103 is from source 
1.2.2-103.
it worked fine since the begining of this repo (in 2014) so I don't 
understand the need of a new libgiac package from git that
 will conflict with the optional giac spkg. 

Although giacpy_sage could be built from your package(sage/libs/giac.py),  
I guess that the pexpect interface (sage/interfaces/giac.py) won't work 
(need the built of icas).


 

> As it seems (#21963) linking problems cannot be resolved without a 
> standard Giac package I'd like to restart the argument here.
> I successully cloned the giac core from the geogebra repo given here and 
> today fetched current changes, all via "git svn".
> That anwers the question of availability of an actively maintained and 
> public giac repo. Git config:
>
> [svn-remote "svn"]
> url = https://dev.geogebra.org/svn/trunk/geogebra/giac/src/giac
> fetch = :refs/remotes/git-svn
>
> However, the code in that giac subdirectory is bare bones, i.e., without 
> any autotools. The other question is, is this code sufficient to support 
> both sage/interfaces/giac.py and sage/libs/giac.py and if not,what would be 
> needed? Would it be easy to add the parser to it in C++ (the one in 
> geogebra is in java)? If not I might be tempted to create a third giac 
> package (libgiac) just for linking with Pynac, and the other giac package 
> can stay optional for eternity.
>
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: singular update and interreduced_basis

[Han Frederic]

Le jeudi 17 novembre 2016 22:40:12 UTC+1, Dima Pasechnik a écrit :
>
>
> git show 5b8343be
>
>
Thank you for the link. For the moment I have summarized the problem in 
#21884, let's see jeroen thinks if it worth a new trac.

best regards
Frederic
 

> Hopefully Jeroen (in cc) can explain this change.
>  
>

>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: singular update and interreduced_basis

[Han Frederic]

But it looks that the normalisation was in sage singular interface:
The interred_libsingular function of  multi_polynomial_ideal_libsingular.pyx

ends in sage 7.4beta5 like this:

# divide head by coefficients
if r.ringtype == 0:
for j from 0 <= j < IDELEMS(result):
p = result.m[j]
if p:
n = p_GetCoeff(p,r)
n = r.cf.nInvers(n)
result.m[j] = pp_Mult_nn(p, n, r)
p_Delete(,r)
n_Delete(,r)

id_Delete(,r)

res = 
sorted(singular_ideal_to_sage_sequence(result,r,I.ring()),reverse=True)

id_Delete(,r)
return res

but in 7.5beta2 it is:
# divide head by 
coefficients 
if r.cf.type == 
n_unknown:
for j from 0 <= j < 
IDELEMS(result):  
p = 
result.m[j]   
if 
p: 
n = 
p_GetCoeff(p,r)   
n = 
r.cf.cfInvers(n,r.cf) 
result.m[j] = pp_Mult_nn(p, n, 
r) 

p_Delete(,r)


n_Delete(,r)


  


id_Delete(,r) 
  


  

res = 
sorted(singular_ideal_to_sage_sequence(result,r,I.ring()),reverse=True) 


  


id_Delete(,r)
  

return 
res


  

 

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] singular update and interreduced_basis

[Han Frederic]

With singular 4 on sage I have now:

sage: P. = PolynomialRing(QQ,3, order='lex')
sage: toto=ideal([7*a - 420*c^3 + 158*c^2 + 8*c - 7, 7*b + 210*c^3 - 79*c^2 
+ 3*c, 84*c^4 - 40*c^3 + c^2 + c])
sage: toto.interreduced_basis?
sage: g=toto.interreduced_basis()
sage: g[0].lc()
7
sage: toto.base_ring()
Rational Field
sage: g
[7*a - 420*c^3 + 158*c^2 + 8*c - 7, 7*b + 210*c^3 - 79*c^2 + 3*c, 84*c^4 - 
40*c^3 + c^2 + c]

while with singular 3 I had:
[a - 60*c^3 + 158/7*c^2 + 8/7*c - 1, b + 30*c^3 - 79/7*c^2 + 3/7*c, c^4 - 
10/21*c^3 + 1/84*c^2 + 1/84*c]

moreover the doc says:

  If this ideal is spanned by (f_1, ..., f_n) this method returns
   (g_1, ..., g_s) such that:

   * (f_1,...,f_n) = (g_1,...,g_s)

   * LT(g_i) != LT(g_j) for all i != j

   * LT(g_i) does not divide m for all monomials m of

{g_1,...,g_{i-1},g_{i+1},...,g_s}

   * LC(g_i) == 1 for all i if the coefficient ring is a field.



Am I missing something? (I need to know if I should change my doctest 
output or not in #21884)

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: make giac/giacpy a standard package

[Han Frederic]

I am opening  https://trac.sagemath.org/ticket/20946
to update the giac spkg

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] make giac/giacpy a standard package

[Han Frederic]

Le mardi 5 juillet 2016 10:43:52 UTC+2, François a écrit :
>
>
> Han, I have looked at both giacpy and giacpy-sage now. They hardly 
> have anything in common anymore. 
> At least, it is not obvious from the repos. 
>
> Given that the split is already that wide, would there be an objection 
> to them having different “name” in setup.py so they can be installed 
> side by side? 
>
> François

 
 Indeed  I think also that changing the name is slightly better than 
managing a non conflictual installation because one could install only the 
bad one.

May be giacpysage or giacpy_sage ? 
If so, should we change also the spkg name? (may be we should not, so 
people will really upgrade?)

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: make giac/giacpy a standard package

[Han Frederic]

Le lundi 4 juillet 2016 04:14:26 UTC+2, François a écrit :
>
> So I have been inspecting giac, as any discussion of making something 
> a standard package as an impact for sage-on-gentoo. 
> We have an old version in the science overlay so I am working on 
> upgrading it. 
>
> 1) current 1.2.2-63 and a few earlier versions need the gui, compiling 
> with "--disable-gui" is broken. 
>
 
I have noticed this also and reported it yesterday. I have tried a very 
short patch and it looks to solve this. 

I haven't gone through giacpy yet, but I don't like the fact there 
> is a sage specific version. Something could be done to only have one 
> source if my understanding of the issues and solution are correct. 
>
> This need works and it could ends with another split (Ex the non sage 
version have an experimental Qt output)
giacpy status is different from giac: Giac has regular users through xcas 
while giacpy is unknown, so the answer to Ralf's question could be 
different. Any help to merge the 2 versions would be welcome but I would 
like to still be able to cross build some giacpy for windows from linux.
 

> Francois 
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: make giac/giacpy a standard package

[Han Frederic]

Le samedi 2 juillet 2016 13:30:35 UTC+2, leif a écrit :
>
> leif wrote: 
> > Ralf Stephan wrote: 
> >> On Wednesday, June 1, 2016 at 10:00:34 AM UTC+2, Ralf Stephan wrote: 
> >> 
> >> The giac and giacpy packages are now one year optional (#12375). 
> Since 
> >> pynac-0.6.6 (#20742) has optional support for giac, and uses it to 
> >> fix a bug, 
> >> as well as a much faster GCD, I'm proposing to make the giac/giacpy 
> >> packages 
> >> a standard part of Sage. In a recent thread we could also read 
> about the 
> >> speed of its Gröbner basis implementation. 
> >> 
> >> 
> >> There were no negative arguments to this. Also meanwhile, a standard 
> >> installation 
> >> would ease Pynac's task of handling potentially different libgiac 
> versions 
> >> with different needs that may be installed system-wide. 
> >> 
> >> So what would be the next step in this procedure? 
> > 
> > Strip the latest version offered by Sage? ;-) 
> > 
> > 12Mgiac-1.2.0.19.tar.gz 
> > 44Mgiac-1.2.2.37.tar.gz 
> > 41Kgiacpy-0.5.6.tar.gz 
> > 
> > Haven't examined why it has grown by 300% in a minor version update 
> though. 
>
> There's at least 
>
> 28Mgiac-1.2.2.37/src/javagiac_linux32.tgz 
> 394Kgiac-1.2.2.37/src/javagiac_linux64.tgz 
> 28Mtotal 
>
> which we certainly don't have to ship, 
>

Yes these binaries were left in upstream 1.2.2-37 source tarball, but it is 
a mistake. I didn't notice this when I made the 1.2.2.37 spkg but the next 
spkg won't have this. I should update it soon.


For windows performance I can only test through virtual box, so it is not 
very significant. 

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Build system changes in 6.8.beta7

[Han Frederic]

Thank you!

Le mercredi 8 juillet 2015 12:41:03 UTC+2, Jeroen Demeyer a écrit :

 On 2015-07-08 12:37, Han Frederic wrote: 
  with the make method, is there something analogous to ./sage -i -c 
  pkgname ? 

 env SAGE_CHECK=yes make pkgname 

 (in bash, you can drop the env) 


-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Build system changes in 6.8.beta7

[Han Frederic]

Le vendredi 3 juillet 2015 09:41:02 UTC+2, Jeroen Demeyer a écrit :

 Hello all, 

 There were some important changes to the Sage build system in 6.8.beta7: 

 * All logs of running make will appear in install.log, including the 
 logs of the documentation and the Sage library build. Nothing changed 
 for the individual log files. 

 * The documentation can now be built in parallel with packages: if you 
 run make, then all packages will be built and the documentation will 
 be built. Packages which are not required for the documentation might be 
 built at the same time as the documentation. Note that the documentation 
 has a lot of dependencies, so in practice, the documentation will 
 usually be the last thing to finish building anyway. 

 

 * New-style packages can now be installed with dependency checking by 
 running make pkgname. This applies to all types (standard, optional, 
 experimental). I remind that new-style packages should define 
 dependencies in a build/pkgs/pkgname/dependencies file, this information 
 will be used by make pkgname. I think this should become the 
 recommended way to install packages, while ./sage -i (which does NOT 
 use dependencies) is a more low-level interface, analogous to ./sage -b 

 Hello,
with the make method, is there something analogous to ./sage -i -c pkgname 
? 

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: giac/giacpy packages

[Han Frederic]

I can help also for the giacpy syntax.
We need 2 cases: only for grevlex, prime fields of char p 2^31 or QQ
(I think that in other cases giac could be very bad)

may be the easiest for me is if you could start a branch with those 2 cases 
and some tags where I should insert the conversions and computations.
So that I will see quickly what files to modify

don't you mind?

Frederic

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: giac/giacpy packages

[Han Frederic]

I think I can start something it looks to be in
src/sage/rings/polynomial/multi_polynomial_ideal.py 
http://git.sagemath.org/sage.git/tree/src/sage/rings/polynomial/multi_polynomial_ideal.py?id=c0e721783317f205106c9c3c552e366ce4e6c50e
It may not be necessary to modify the cython interface for this.

best
Frederic

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] giac/giacpy packages

[Han Frederic]

I'd like to point out that recently  http://trac.sagemath.org/ticket/12375
 was closed. I'd like also to thank here all the participants.

Since sage 6.8.beta5, giac and its cython interface giacpy are avaible as 
optional packages.

It provides interesting features in symbolic computations (gcd, factor, 
solving more inequalites)
and also in groebner basis computation:

Ex: I was able to compute a groebner basis over QQ of cyclic9 in 7h of wall 
time (but 49h of cpu time). (7h30 wall and cpu time with magma)
http://webusers.imj-prg.fr/~frederic.han/xcas/giacpy/index.html#cyclic9


* the giacpy result was saved to a 1.1G file in 28s, loaded in 68s, 
converted to a list of sage polynomials in 170s.*computation of groebner 
basis over prime fields p2**31 are also avaible:
Ex: 

*Katsura12 mod 65521 took 90s with giacpy and 810s with 
libsingular.http://webusers.imj-prg.fr/~frederic.han/xcas/giacpy/grobner-libgiac.pdf*

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Slowness in comparing symbolic expressions

[Han Frederic]

Le jeudi 27 novembre 2014 02:46:26 UTC+1, Robert Dodier a écrit :

 On 2014-11-26, Han Frederic h...@math.jussieu.fr javascript: wrote: 

  Hi, I have tried the factorization with giacpy. (cf trac 12375). 
  I had to expexpand first before factoring and did this: 
  
  sage: from giacpy import libgiac 
  sage: x=libgiac('x') 
  sage: s=exp(1024*(x+1))-1 
  sage: %time s.expexpand().factor() 
  CPU times: user 0 ns, sys: 0 ns, total: 0 ns 
  Wall time: 1.32 ms 
  
 (exp(x+1)-1)*(exp(x+1)+1)*(exp(x+1)^2+1)*(exp(x+1)^4+1)*(exp(x+1)^8+1)*(exp(x+1)^16+1)*(exp(x+1)^32+1)*(exp(x+1)^64+1)*(exp(x+1)^128+1)*(exp(x+1)^256+1)*(exp(x+1)^512+1)
  


 That's terrific. Do you know anything about the implementation of Giac? 
 I downloaded the source code and after poking around a bit, I can't 
 tell where factoring such an expression actually occurs. Does Giac 
 handle that itself, or does it punt to PARI or something else? 
 What is the effect of expexpand in the example above? 

 Thanks for any information, 

 Robert Dodier 

 expexpand do this:

sage: s
exp(1024*(x+1))-1
sage: s.expexpand()
exp(x+1)^1024-1

so I guess that factor works as if it was a polynomial in one variable. (I 
have asked on giac forum to obtain confirmation about the implementation 
for one variable, but I think that for multivariable giac does it alone:
 so I have tried this:

sage: x,y=libgiac('x,y')
sage: s=exp(1024*(x+1))-exp(768*(y+2))
sage: %time s.expexpand().factor()
CPU times: user 1.21 s, sys: 16 ms, total: 1.23 s
Wall time: 1.22 s
-(exp(y+2)^3-exp(x+1)^4)*(exp(y+2)^3+exp(x+1)^4)*(exp(y+2)^6+exp(x+1)^8)*(exp(y+2)^12+exp(x+1)^16)*(exp(y+2)^24+exp(x+1)^32)*(exp(y+2)^48+exp(x+1)^64)*(exp(y+2)^96+exp(x+1)^128)*(exp(y+2)^192+exp(x+1)^256)*(exp(y+2)^384+exp(x+1)^512)

best
Frederic

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Slowness in comparing symbolic expressions

[Han Frederic]

 Incidentally I observe that Sympy has the same behavior, so we can't 
 just nick their factoring algorithm -- maybe some other package we can 
 try the same example to see if any of them handle it quickly? 

 best 

 Robert Dodier 

 Hi, I have tried the factorization with giacpy. (cf trac 12375). I had to 
expexpand first before factoring and did this:


sage: from giacpy import libgiac
sage: x=libgiac('x')
sage: s=exp(1024*(x+1))-1
sage: %time s.expexpand().factor()
CPU times: user 0 ns, sys: 0 ns, total: 0 ns
Wall time: 1.32 ms
(exp(x+1)-1)*(exp(x+1)+1)*(exp(x+1)^2+1)*(exp(x+1)^4+1)*(exp(x+1)^8+1)*(exp(x+1)^16+1)*(exp(x+1)^32+1)*(exp(x+1)^64+1)*(exp(x+1)^128+1)*(exp(x+1)^256+1)*(exp(x+1)^512+1)

or

sage: %time s.expexpand().factor().expexpand()
CPU times: user 4 ms, sys: 0 ns, total: 4 ms
Wall time: 1.13 ms
(exp(x)*exp(1)-1)*(exp(x)*exp(1)+1)*((exp(x)*exp(1))^2+1)*((exp(x)*exp(1))^4+1)*((exp(x)*exp(1))^8+1)*((exp(x)*exp(1))^16+1)*((exp(x)*exp(1))^32+1)*((exp(x)*exp(1))^64+1)*((exp(x)*exp(1))^128+1)*((exp(x)*exp(1))^256+1)*((exp(x)*exp(1))^512+1)

best

Frederic

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] space in trac login and ssh

[Han Frederic]

Hi All, 
sorry for the trouble, but I have some problems to fix my ssh connexion to 
the trac server for git.
(I am working on http://trac.sagemath.org/ticket/12375 )

1) My trac login is the same as my full name: Han Frederic
so it contains a space, could it be a problem?

Here is what I have tried:

macbookito(fred)$ git-trac config --user 'Han Frederic' --pass 'XX'
Saved trac username.
Saved trac password.
Trac xmlrpc URL:
http://trac.sagemath.org/xmlrpc (anonymous)
http://trac.sagemath.org/login/xmlrpc (authenticated)
realm sage.math.washington.edu
Username: Han Frederic
Password: X
Retrieving SSH keys...
2048 b4:a3:58:12:d8:ae:5d:51:36:1b:99:4b:77:1a:d3:b9  fred@macbookito (RSA)
macbookito(fred)$ git remote -v
origin  https://github.com/sagemath/git-trac-command.git (fetch)
origin  https://github.com/sagemath/git-trac-command.git (push)
tracgit://trac.sagemath.org/sage.git (fetch)
tracg...@trac.sagemath.org:sage.git (push)


so the trac server knows my public key. Now I check that my private key 
corresponds with:

macbookito(fred)$ ssh-keygen -l 
Enter file in which the key is (/home/fred/.ssh/id_rsa): 
/home/fred/.ssh/id_rsa-trac
2048 b4:a3:58:12:d8:ae:5d:51:36:1b:99:4b:77:1a:d3:b9  fred@macbookito (RSA)


but if I test the ssh connexion with:

macbookito(fred)$ ssh -v -i ~/.ssh/id_rsa-trac g...@trac.sagemath.org info
OpenSSH_5.9p1 Debian-5ubuntu1.1, OpenSSL 1.0.1 14 Mar 2012
debug1: Reading configuration data /home/fred/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to trac.sagemath.org [128.208.178.249] port 22.
debug1: Connection established.
debug1: identity file /home/fred/.ssh/id_rsa-trac type 1
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: identity file /home/fred/.ssh/id_rsa-trac-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.9p1 
Debian-5ubuntu1.3
debug1: match: OpenSSH_5.9p1 Debian-5ubuntu1.3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1.1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server-client aes128-ctr hmac-md5 none
debug1: kex: client-server aes128-ctr hmac-md5 none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ECDSA 21:ba:10:2a:59:cd:7d:36:f7:4c:52:bf:fc:5e:0e:07
debug1: Host 'trac.sagemath.org' is known and matches the ECDSA host key.
debug1: Found key in /home/fred/.ssh/known_hosts:54
debug1: ssh_ecdsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/fred/.ssh/id_rsa-trac
debug1: Authentications that can continue: publickey,password
...

then this key is never accepted and it goes to the next method. I have also 
tried with the option:

-o HostKeyAlgorithms=ssh-rsa  

and got the same RSA key from the server as dimpase so we are connecting 
onto the same server.

Any idea?

Frederic






 

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] libgiac, cython interface

[Han Frederic]

Hello,

I have done a cython interface for the giac library. There is a version for 
python and another one for sage. 

I have opened the following trac:http://trac.sagemath.org/ticket/15226

Details and examples are available on my page : 
http://www.math.jussieu.fr/~han/xcas/giacpy

Best regards,

F.Han

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.

[sage-devel] extcode, giac interface

[Han Frederic]

Hello,
The directory data/extcode/giac/user  is not present after a built, so if the 
first user of the giac interface has not the rights to built this directory 
this interface can't be used.

For the other interfaces this directory is in the extcode spkg.

Should I open a trac for this?

Best regards

F.Han

-- 
-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Re: Sage and gcc 4.3.0

[Han Frederic]

On Tue, Apr 05, 2011 at 04:12:37PM +0100, Dr. David Kirkby wrote:
 On 04/ 5/11 03:06 PM, Bill Hart wrote:
 One possibly data point is that GCC 4.3.2 miscompiles GMP and MPIR on
 x86_64 and as far as I know cannot and will not be worked around.

 Thank you for that. I'm not going to address the issue now, but if that 
 is the case, we should check for gcc 4.3.2 and prevent it being used.

 There were also bugs in GCC 4.3.3 which miscompiled FLINT, but as far
 as I know that issue never affected Sage.

 OK, thanks for that too.



 Dave


NB: On a 32bit computer I have compiled sage 4.6.2 without any problems
with gcc 4.3.2.

Linux  2.6.26-2-686 #1 SMP Sun Jun 21 04:57:38 UTC 2009 i686 GNU/Linux

gcc version 4.3.2 (Debian 4.3.2-1.1)


-- 

*  *
*  Han Frederic*
*  h...@math.jussieu.fr *
*  *
*  Universite Paris 7  *
*  Institut de Mathematiques de Jussieu*
*  Case Postale 7012   *
*  Batiment Chevaleret *
*  75205 Paris Cedex 13*
*  Tel  01 57 27 91 54 *
 

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] multivariate gcd and giac interface

[Han Frederic]

Hello,
I have done minor updates for the giac interface. (trac 10940)

I got the following bench with it:
On a: model name : Intel(R) Core(TM)2 Duo CPU E4700 @ 2.60GHz
with sage 4.6.2 compiled from sources and the giac spkg:
http://www-fourier.ujf-grenoble.fr/~parisse/giac/giac-0_9_1.spkg
(this spkg was installed without cocoa nor hevea nor extra tex)

I got the following bench for the interface for some multivariate gcd
Is there anotherway to compute gcd in sage?

best
Frederic
-

sage: R.x,y=QQ[]
sage:
l=[R.random_element(15,30),R.random_element(10,50),R.random_element(30,50),R.random_element(20,50)]
sage: gl=giac(l)
sage:
wt=walltime();t=giac.cputime();gf1=(gl[0]*gl[1]).normal();giac.cputime(t);walltime(wt)
-1.136868377221e-13
0.010113000869750977
sage: wt=walltime();t=cputime(); f1=l[0]*l[1] ;
cputime(t);walltime(wt)
0.0
0.0010118484497070312
sage: giac(f1).nops;gf1.nops();
sage:
wt=walltime();t=giac.cputime();gf2=(gl[3]*gl[1]).normal();giac.cputime(t);walltime(wt)
0.0099887
0.019656896591186523
sage: wt=walltime();t=cputime(); f2=l[3]*l[1] ;
cputime(t);walltime(wt)
0.004001002439483
0.0025229454040527344
sage:
sage:
wt=walltime();t=giac.cputime();gf12=gf1.gcd(gf2);giac.cputime(t);walltime(wt)
0.02
0.028865814208984375
sage: gf12.degree()-gl[1].degree()
0
sage: wt=walltime();t=cputime(); f12=gcd(f1,f2) ;
cputime(t);walltime(wt)
1.584099001511
1.5869238376617432
sage: (f12/gf12).normal()
1
sage:

###
#rapport 700 (3 essais)
sage: R.x,y,z=QQ[]
sage:
l=[R.random_element(7,30),R.random_element(10,15),R.random_element(10,30),R.random_element(10,30)]
sage: gl=giac(l)
sage:
wt=walltime();t=giac.cputime();gf1=(gl[0]*gl[1]).normal();giac.cputime(t);walltime(wt)
0.0099985
0.014853954315185547
sage: wt=walltime();t=cputime(); f1=l[0]*l[1] ;
cputime(t);walltime(wt)
0.0
0.00037312507629394531
sage: giac(f1).nops;gf1.nops();
sage:
wt=walltime();t=giac.cputime();gf2=(gl[3]*gl[1]).normal();giac.cputime(t);walltime(wt)
0.0
0.010710954666137695
sage: wt=walltime();t=cputime(); f2=l[3]*l[1] ;
cputime(t);walltime(wt)
0.0
0.00046610832214355469
sage:
wt=walltime();t=giac.cputime();gf12=gf1.gcd(gf2);giac.cputime(t);walltime(wt)
0.02
0.025274991989135742
sage: wt=walltime();t=cputime(); f12=gcd(f1,f2) ;
cputime(t);walltime(wt)
57.29557999518
58.063894987106323
sage: (f12/gf12).normal()
-1




#Un exemple limite pour sage: rapport 4
sage: A.x,y,z,t=QQ[]
sage: R.x,y,z,t=ZZ[]
sage:
l=[A(R.random_element(7,10)),A(R.random_element(10,15)),A(R.random_element(10,20))]
sage: gl=giac(l)
sage:
wt=walltime();t=giac.cputime();gf1=(gl[0]*gl[1]).normal();giac.cputime(t);walltime(wt)
0.0
0.0075490474700927734
sage: wt=walltime();t=cputime(); f1=l[0]*l[1] ;
cputime(t);walltime(wt)
0.0
0.00021696090698242188
sage: giac(f1).nops;gf1.nops();
sage:
wt=walltime();t=giac.cputime();gf2=(gl[2]*gl[1]).normal();giac.cputime(t);walltime(wt)
0.0
0.0078761577606201172
sage: wt=walltime();t=cputime(); f2=l[2]*l[1] ;
cputime(t);walltime(wt)
0.0
0.00025606155395507812
sage:
wt=walltime();t=giac.cputime();gf12=gf1.gcd(gf2);giac.cputime(t);walltime(wt)
0.02
0.038819789886474609
sage: wt=walltime();t=cputime(); f12=gcd(f1,f2) ;
cputime(t);walltime(wt)
1635.178192003
1637.7164239883423
sage: (f12/gf12).normal()
-1


--
| Sage Version 4.6.2, Release Date: 2011-02-25 |
| Type notebook() for the GUI, and license() for information. |
--
sage: x,y,z=tuple(giac('x,y,z'))
sage: f=(x+y+z+1)^33+1
sage: time p=(f*(f+1)).normal()
CPU times: user 0.00 s, sys: 0.00 s, total: 0.00 s
Wall time: 0.52 s
sage: p.nops()
52394
sage: time p.factor().nops()
CPU times: user 0.00 s, sys: 0.00 s, total: 0.00 s
Wall time: 7.85 s
5

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: giac interface

[Han Frederic]

On 4 mar, 11:49, Han Frederic h...@math.jussieu.fr wrote:
 Hello,

 I'm new to sage,

 I have tried to adapt the maple.py interface to obtain a giac
 interface for sage.

 The current version is there:http://www.math.jussieu.fr/~han/xcas/giac.py

 one needs a recent giac program. (this week, giac --sage should gives
 a working session) . Bernard parisse updated the spkg 
 there:http://www-fourier.ujf-grenoble.fr/~parisse/giac/giac-0_9_1.spkg

 Things like this work after a: from giac import giac

 giac.normal?
 (tab completion also)
 f=giac('x+1')
 (f*f).normal()
 R.x,y=QQ[]
 f=(x+y)^5
 f2=giac(f)
 f2.factor()
 x,y,z=giac('x'),giac('y'),giac('z')
 f=(x+y+z+1/3)^5;(f^2).normal()
 giac.int(1/(cos(2*x)+cos(x)),x,0,'pi/4').simplify()

 Can someone help me for the following problems?
 -element of the symbolic ring need to be quoted. Ex pi/4 in the
 giac.int
 -(z+1)^2 works but not z+sqrt(5)
 -import a sage matrix to giac()
 Ex: m=matrix(2,3,range(6))  should be translated to: matrix([[0,1,2],
 [3,4,5]])  or [[0,1,2],[3,4,5]] to be properly evaluated. (vectors
 should be translated to things like this [1,2,3] )
 -giac.sum('k','k')  doesn't do giac('sum(k,k)')


I have found the files to solve those problems.

best

Frederic


 Best

 Frederic

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] giac interface

[Han Frederic]

Hello,

I'm new to sage,

I have tried to adapt the maple.py interface to obtain a giac
interface for sage.


The current version is there:
http://www.math.jussieu.fr/~han/xcas/giac.py

one needs a recent giac program. (this week, giac --sage should gives
a working session) . Bernard parisse updated the spkg there:
http://www-fourier.ujf-grenoble.fr/~parisse/giac/giac-0_9_1.spkg

Things like this work after a: from giac import giac

giac.normal?
(tab completion also)
f=giac('x+1')
(f*f).normal()
R.x,y=QQ[]
f=(x+y)^5
f2=giac(f)
f2.factor()
x,y,z=giac('x'),giac('y'),giac('z')
f=(x+y+z+1/3)^5;(f^2).normal()
giac.int(1/(cos(2*x)+cos(x)),x,0,'pi/4').simplify()

Can someone help me for the following problems?
-element of the symbolic ring need to be quoted. Ex pi/4 in the
giac.int
-(z+1)^2 works but not z+sqrt(5)
-import a sage matrix to giac()
Ex: m=matrix(2,3,range(6))  should be translated to: matrix([[0,1,2],
[3,4,5]])  or [[0,1,2],[3,4,5]] to be properly evaluated. (vectors
should be translated to things like this [1,2,3] )
-giac.sum('k','k')  doesn't do giac('sum(k,k)')


Best

Frederic



-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org