Hi Andrey and Volker,
On 22 Dez., 05:49, Andrey Novoseltsev wrote:
> I am satisfied with the current Chow group patches on that ticket, but
> I will not be able to review the FGP-related ones for a few weeks.
> Perhaps it makes sense to split off this refactoring into a separate
> ticket (in whic
Adjugate features in Muir's "A treatise on the theory of determinants",
1933.
--
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.googl
On Dec 21, 4:32 pm, Volker Braun wrote:
> As far as I am concerned, the patches at #9713 are finished. All doctests
> pass.
Simon and Volker,
I am satisfied with the current Chow group patches on that ticket, but
I will not be able to review the FGP-related ones for a few weeks.
Perhaps it makes
Alex,
Yes, that's right. You can post the Trac URL or just the ticket
number here if you would like to advertise it. Or you can add
relevant developers in the cc field of the ticket (maybe you have been
working on code written by another active developer who would be
interested). Choosing the r
On Dec 21, 3:06 pm, William Stein wrote:
> Question: Would it be
> possible to get higher quality stickers? My experience with the
> current stickers is that they wear out/off very quickly.
Those were "value line" stickers, which I think worked well on a name
badge for 4-5 days. But they were
Hi Simon,
I found that changing the __call__ methods was the easy part. The more
time-consuming bit is then to fix the ensuing doctest errors in derived
classes
As far as I am concerned, the patches at #9713 are finished. All doctests
pass.
As for organization, what did you already do? D
Hi Simon,
I found that changing the __call__ methods was the easy part. The more
time-consuming bit is then to fix the ensuing doctest errors in derived
classes
As far as I am concerned, the patches at #9713 are finished. All doctests
pass.
As for organization, what did you already do? D
On Tue, Dec 21, 2010 at 9:13 AM, Rob Beezer wrote:
> (Seems the original thread was too stale to allow continuing it?
> http://groups.google.com/group/sage-devel/browse_thread/thread/c738b3e1b464e1e2/)
>
> Do we want to pass out Sage stickers at booth at the US Joint
> Mathematics Meeting in New O
Hi all:
I just finished documenting and testing some new Sage code related to
analytic combinatorics. More specifically, the code is a collection
of functions designed to compute asymptotics of Maclaurin coefficients
of (special classes of) multivariate generating functions.
I'd like to share t
Hi Volker,
On 21 Dez., 21:12, Volker Braun wrote:
> I certainly don't want to preserve the old module class! But I found it too
> hard to port everything to the new Module/Parent in one step.
I think I managed that. From my experience, the most difficult was to
remove the custom __call__ method
Rob, it would be great if you could make stickers again. I meant to
bring this up earlier but I've been swamped with other duties.
Hopefully you can be reimbursed for it. Perhaps 500 stickers is
enough for this event.
I am going to place an order for sage business cards, but I was
thinking of pe
I certainly don't want to preserve the old module class! But I found it too
hard to port everything to the new Module/Parent in one step. Right now I'm
only doing the minimum required to port FGP_* forward, and its already
touching a lot of files. I felt that the transition needs to be broken do
Hi Volker,
On 21 Dez., 19:40, Volker Braun wrote:
> I recently ported the whole sage.modules.Module /
> sage.modules.fg_pid.FGP_Module to the new Parent and coercion system. The
> patch is trac_9713_fix_fg_pid.patch
> athttp://trac.sagemath.org/sage_trac/ticket/9713.
I wasn't aware of that.
I w
Hi Nick,
I'm very happy you look at this problem.
Two other french users get the same error.
I use an ubuntu laptop for emacs, but download and compile sage with
".configure" and "make".
I believe I install sage*.el by spkg some months ago.
could you tell me what emacs version you are runnin
(Seems the original thread was too stale to allow continuing it?
http://groups.google.com/group/sage-devel/browse_thread/thread/c738b3e1b464e1e2/)
Do we want to pass out Sage stickers at booth at the US Joint
Mathematics Meeting in New Orleans in a couple weeks time? I made 500
1-inch square ligh
I recently ported the whole sage.modules.Module /
sage.modules.fg_pid.FGP_Module to the new Parent and coercion system. The
patch is trac_9713_fix_fg_pid.patch
at http://trac.sagemath.org/sage_trac/ticket/9713. Though I must confess
that I didn't really think about the Homsets, I just made sure
Hi!
I am currently trying to implement the new coercion system for
modules. Doing so, I got some problems with
sage.modules.fg_pid.fgp_morphism.FGP_Homset
I thought (reading the documentation) that fg_pid means "finitely
generated modules over principal ideal domains", where some things in
fact o
Hi Francois,
On Dec 21, 2:40 am, Francois Maltey wrote:
> Hi,
>
> I use Sage in emacs in the shell buffer named *Sage-main*, in Inferior
> Sage Mode.
I am the author and maintainer of sage-mode. I tried your examples on
my emacs installation and I get precisely the opposite behaviour: your
firs
> The wonderful website "Earliest Known Uses of Some of the Words of
> Mathematics" (seehttp://jeff560.tripod.com/a.htmlfor the A page)
> does not mention adjugate unfortunately, but does have this entry:
>
Resolving this could be good Math Overflow bait.
Rob is right, at the very least there s
In the file sage/modular/ssmod/ssmod.py there is a doctest marked
#long time which takes 5 minutes (on a fast machine), despite being
marked
# long time (but still less than a minute!)
(See around line 37). Without this test, doctesting the file with
-long takes 4s; with it, 308 s!
This may b
Etymology does not help much. To say that two things are "adjugate"
means that they are "yoked or joined together" from the Latin word for
a yoke (such as you would use if your ox cart was being pulled by two
oxen and they needed to pull together). And to say that they are
"adjoint" means the sam
Hi,
I use Sage in emacs in the shell buffer named *Sage-main*, in Inferior
Sage Mode.
I get an error when I type this input bellow with indent spaces.
But the input is right without any indent space.
In a xterm Sage adds theses spaces after the prompt,
so I type the indented code without any
On 20 December 2010 14:39, Adam Voss wrote:
>
> On Dec 2, 5:45 am, David Kirkby wrote:
>> Perhaps this is something we could change when Sage 5.0 is released.
>> People can expect more compatibility issues when using a major
>> upgrade.
>
> Would it be proper then to open a trac ticket with a pat
Thanks, I suspected of this too.
I will reinstall sage with this command
$ /usr/bin/cpufreq-selector -g performance
$ ./sage
$ /usr/bin/cpufreq-selector -g ondemand
21.12.2010 06:50, Dima Pasechnik пишет:
to install Atlas well, you should switch to "performance" CPU mode.
"On demand" might p
24 matches
Mail list logo
