[sage-support] Re: Questions about solve()
Hello, I've posted a patch for # -- http://sagetrac.org/sage_trac/ticket/ --Mike On Nov 26, 2007 3:34 PM, Ted Kosan <[EMAIL PROTECTED]> wrote: > > William wrote: > > > I think one student working for two weeks could greatly enhance solve, > > but making it: > > > >(1) try the maxima solve, and > >(2) if the maxima solve returns no solutions, do something further that > > involves numerics, e.g., calling to scipy's iterative solver. > > > > In particular, if you could give a list of the sort of problems you want to > > make > > sure solve could solve, we can make sure it does. > > > > Students here work for about $13/hour for up to 19 hours/week, so two weeks > > would be $494. Possibly Bobby and/or Josh would be interested? > > I just received permission from my University to spend $1000 to have > the SAGE project fix the following bug: > > http://trac.sagemath.org/sage_trac/ticket/1235 > > and add the following enhancement: > > http://sagetrac.org/sage_trac/ticket/ > > The only difficulty is that the money needs to be sent in the form of > a Purchase Order. If this is possible then I can begin the paperwork > immediately :-) > > Ted > > > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: Questions about solve()
William wrote: > I think one student working for two weeks could greatly enhance solve, > but making it: > >(1) try the maxima solve, and >(2) if the maxima solve returns no solutions, do something further that > involves numerics, e.g., calling to scipy's iterative solver. > > In particular, if you could give a list of the sort of problems you want to > make > sure solve could solve, we can make sure it does. > > Students here work for about $13/hour for up to 19 hours/week, so two weeks > would be $494. Possibly Bobby and/or Josh would be interested? I just received permission from my University to spend $1000 to have the SAGE project fix the following bug: http://trac.sagemath.org/sage_trac/ticket/1235 and add the following enhancement: http://sagetrac.org/sage_trac/ticket/ The only difficulty is that the money needs to be sent in the form of a Purchase Order. If this is possible then I can begin the paperwork immediately :-) Ted --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: inconsistent subobjects
On Nov 26, 2007 12:55 PM, Francis Clarke <[EMAIL PROTECTED]> wrote: > > Subgroups of abelian groups: > > sage: G. = AbelianGroup(2) > sage: A = G.subgroup([a]) > sage: B = G.subgroup([b]) > sage: A == B > True > > Surely not! I agree that this is dumb, and have made it trac ticket #1284. http://trac.sagemath.org/sage_trac/ticket/1284 The problem is that the cmp method is just comparing the groups abstract structure: if not is_AbelianGroup(right): return -1 return cmp(self.invariants(), right.invariants()) It should also take into account the embedding. --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] inconsistent subobjects
Subgroups of abelian groups: sage: G. = AbelianGroup(2) sage: A = G.subgroup([a]) sage: B = G.subgroup([b]) sage: A == B True Surely not! On the other hand for vector spaces: sage: W. = QQ^2 sage: U = W.subspace([u]) sage: V = W.subspace([v]) sage: U == V False As expected. -- Francis Clarke Department of Mathematics University of Wales Swansea Swansea SA2 8PP --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Fwd: #712
-- Forwarded message -- From: Jan Willemson <[EMAIL PROTECTED]> Date: Nov 26, 2007 8:24 AM Subject: #712 To: [EMAIL PROTECTED] Dear Professor Stein, 2 months ago I opened the bug #712 and we tried to work a little bit on it during a bug day. We found out that it was an upstream bug in Maxima and You generated several Maxima scripts that tried to reproduce the bug in Maxima, but as far as I remember there were some problems with these scrips and we decided not to file a Maxima bug report just yet. Some time has passed and #712 is still standing and it is still very much stopping me from doing what I need, so I would be grateful if You could allocate some of Your valuable time to help me a bit further and close the bug at least in the sense of an upstream bug report. Thanks in advance, Jan Willemson -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: problems with sage-vmware-2.8.12.zip
Hi, > http://sagemath.org/SAGEbin/vmware/ > has been modified so that all files are < 2GB. So you might > want to try it out and see if it works on your system, and report > back either way. actually I followed Jason's suggestion, namely I installed NTFS-3G on my linux box and then converted the FAT32 partition to NTFS and everything worked out fine (well, at least after downloading the 2GB image from the sage web site since my zip file was prolly corrupted), so it's too late for me to test the FAT32 'compatibility'. I'll bother you in the future with new bugs then :-) Cheers, Roberto --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] solving matrix equations
Hello, I am trying to solve a system of matrix equations of the form: transpose(B)*(Mi)*B==Ni where i is in range(p) for some fixed p > 9, Mi and Ni have integer entries, and all matrices are of size p by p. I want to solve for B (it need not have integer entries). I have tried a brute force approach. I can make a list of equations corresponding to each entry, and in test cases (p=2) it will solve for B. In general, I would like to define a new command that inputs p and uses the "solve( , )" function. Something like the following def matrix_solve( , ,p) solutions=solve(list of equations from entries, x1,x2, ... xp) return solutions The first input is a list of equations which I can create and input into solve. The trouble is that the second input must be of the form x1,x2, ... xp and cannot be a list, string, or tuple. Question 1: Is there a clever way to input x1,x2, ... xp into the solve function given some p? Question 2: Is there a more clever/efficient way to solve systems of matrix equations? Thank you in advance for any help, M. Miller --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Fwd: [sage-devel] Re: Banner not updated
On Nov 26, 2007 1:42 AM, Simon King <[EMAIL PROTECTED]> wrote:
>
> Dear Sage team,
>
> i just upgraded sage on two machines. One has gcc 4.1.2 on it, the
> other has gcc 4.2.1.
> On the machine with 4.1.2, starting sage still looks like this:
> > sage
> --
> | SAGE Version 2.8.10, Release Date: 2007-10-28 |
> | Type notebook() for the GUI, and license() for information.|
> --
>
> although the update was essentially successful:
>
> sage: version()
> 'SAGE Version 2.8.14, Release Date: 2007-11-24'
>
> On the machine with 4.2.1, the 2.8.14 banner on starting sage looks as
> it should.
>
> Certainly this is no serious bug, but i was a bit surprised when i
> started sage.
This was discussed on sage-devel. I've forwarded the conversation to you.
Basically you have to do something manual to merge in the new
verison of the sage_scripts package. See below.
Forwarded conversation
Subject: [sage-devel] Banner not updated
From: *Nathan Dunfield* <[EMAIL PROTECTED]>
Date: Nov 22, 2007 7:17 AM
To: [EMAIL PROTECTED]
I encountered the following minor bug while upgrading to 2.8.13,
namely the file
$SAGEROOT/local/bin/sage-banner
was not updated. So when I started sage after doing "sage -upgrade"
it claimed that I was still on 2.8.8.1:
PBook ~ (12) sage
--
| SAGE Version 2.8.8.1, Release Date: 2007-10-21 |
| Type notebook() for the GUI, and license() for information.|
--
even though within the interpreter the function "version()" correctly
returns 2.8.13.
sage: version()
'SAGE Version 2.8.13, Release Date: 2007-11-21'
Details: OS X, version 10.4.10/Core Duo 2/original version of sage
2.7.1, upgraded several times.
Best,
Nathan
--
From: *William Stein* <[EMAIL PROTECTED]>
Date: Nov 22, 2007 3:37 PM
To: [EMAIL PROTECTED]
Try doing
sage: hg_scripts.merge()
sage: hg_scripts.commit()
and answer any interactive questions. We recently switched to "sage
-upgrade"
*merging* in the scripts and several other hg repo's included in sage,
instead of
just overwriting them -- this is great, because it means people won't
accidently
loose work when upgrading; however, it requires some slight manual
intervention
when upgrading older installs.
William
--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org
--
From: *Nathan Dunfield* <[EMAIL PROTECTED]>
Date: Nov 22, 2007 7:59 PM
To: sage-devel <[EMAIL PROTECTED]>
This doesn't seem to do anything:
sage: hg_scripts.merge()
cd "/pkgs/sage-2.7.1/local/bin" && hg merge
abort: there is nothing to merge - use "hg update" instead
sage: hg_scripts.commit()
cd "/pkgs/sage-2.7.1/local/bin" && hg diff | less
cd "/pkgs/sage-2.7.1/local/bin" && hg commit
nothing changed
If I follow the suggestion of .merge() I get
sage: hg_scripts.update()
cd "/pkgs/sage-2.7.1/local/bin" && hg update
abort: untracked local file 'sage-wiki' differs from remote version
More to the point, I do recall being asked some questions by "hg"
during the upgrade process ("(k)eep or (d)iscard" or similar). I
didn't pay much attention to them, but I guess I should have ;-).
--
From: *mabshoff* <[EMAIL PROTECTED]>
Date: Nov 23, 2007 2:20 AM
To: sage-devel <[EMAIL PROTECTED]>
Hello Nathan,
It might have been captured in the log. Could you check there? It has
come up at least twice with 2.8.13 and we should really get this issue
resolved.
> Nathan
Cheers,
Micheal
--
From: *William Stein* <[EMAIL PROTECTED]>
Date: Nov 23, 2007 9:18 AM
To: [EMAIL PROTECTED]
...
See where it says "abort: ". It's aborting at that point.
If you do
rm SAGE_ROOT/local/bin/sage-wiki
then do hg_scripts.update() again, it won't abort for that reason
and you'll get the new hg repo for scripts merged in.
-- William
--
From: *Nathan Dunfield* <[EMAIL PROTECTED]>
Date: Nov 25, 2007 9:33 AM
To: sage-devel <[EMAIL PROTECTED]>
> > during the upgrade process ("(k)eep or (d)iscard" or similar). ...
I didn't see anything relevant in SAGE_ROOT/install.log. I've put
the file at
http://dunfield.info/temp/install.log
if anyone wants to have a look.
Thanks, that fixed the problem. Having done the above, the upgrade to
2.8.14 went smoothly, with the correct updated banner.
Best,
--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage
[sage-support] Re: Banner not upgraded
On Nov 26, 10:42 am, Simon King <[EMAIL PROTECTED]> wrote: > Dear Sage team, > > i just upgraded sage on two machines. One has gcc 4.1.2 on it, the > other has gcc 4.2.1. > > On the machine with 4.1.2, starting sage still looks like this:> sage > > -- > | SAGE Version 2.8.10, Release Date: 2007-10-28 | > | Type notebook() for the GUI, and license() for information.| > -- > > although the update was essentially successful: > Hello Simon, check the repo in $SAGE_ROOT/devel/sage/ - you probably have outstanding commits. Cheers, Michael > sage: version() > 'SAGE Version 2.8.14, Release Date: 2007-11-24' > > On the machine with 4.2.1, the 2.8.14 banner on starting sage looks as > it should. > > Certainly this is no serious bug, but i was a bit surprised when i > started sage. > > Yours > Simon --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Banner not upgraded
Dear Sage team, i just upgraded sage on two machines. One has gcc 4.1.2 on it, the other has gcc 4.2.1. On the machine with 4.1.2, starting sage still looks like this: > sage -- | SAGE Version 2.8.10, Release Date: 2007-10-28 | | Type notebook() for the GUI, and license() for information.| -- although the update was essentially successful: sage: version() 'SAGE Version 2.8.14, Release Date: 2007-11-24' On the machine with 4.2.1, the 2.8.14 banner on starting sage looks as it should. Certainly this is no serious bug, but i was a bit surprised when i started sage. Yours Simon --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
