Great, thanks for getting back to me!
Yes, it is a symbolic link. I'll try your suggestion when I have a
chance. I'll probably get back to you sometime in the first week of
January.
best,
Chris
On Dec 20, 12:27 pm, mabshoff wrote:
> On Dec 16, 1:31 pm, C wrote:
>
> > > what exactly did you
On Mon, Dec 22, 2008 at 9:55 PM, vivek wrote:
>
> Hi
>
> I know of a python script by name qasm2circ (http://www.media.mit.edu/
> quanta/qasm2circ/).
>
> This script takes a description of a quantum-circuit (called a QASM
> file) and converts it into a graphical depiction. This is done using
> l
Hi
I know of a python script by name qasm2circ (http://www.media.mit.edu/
quanta/qasm2circ/).
This script takes a description of a quantum-circuit (called a QASM
file) and converts it into a graphical depiction. This is done using
latex (specifically xypic) to produce high-quality output in eps
Dan Drake wrote:
>
> Also, what does "vanilla upstream" mean for SageTeX?
I figured that Sage would just package the current version from CTAN,
though obviously that would depend on what you wanted.
Jason
--~--~-~--~~~---~--~~
To post to this group, send em
On Mon, Dec 22, 2008 at 6:13 PM, mabshoff wrote:
>
>
>
> On Dec 22, 6:05 pm, Dan Drake wrote:
>> On Mon, 22 Dec 2008 at 10:42AM -0800, mabshoff wrote:
>
> Hi Dan,
>
>
>
>> > Everything but src must be under revision control - unclean repo in
>> > the spkg leads to automatic "needs work" from my
On Dec 22, 6:05 pm, Dan Drake wrote:
> On Mon, 22 Dec 2008 at 10:42AM -0800, mabshoff wrote:
Hi Dan,
> > Everything but src must be under revision control - unclean repo in
> > the spkg leads to automatic "needs work" from my end at review time
>
> Does that mean src/ must not be under revi
On Dec 22, 2008, at 3:56 PM, Nils Bruin wrote:
> On Mon, Dec 22, 2008 at 10:23 AM, Robert Bradshaw
>
> wrote:
>>> On Dec 22, 2008, at 6:20 AM, John Cremona wrote:
>>
You can do K(r.lift()), but it would be nicer if this was
handled by
coercion magic.
>>
>>> This isn't really a c
On Mon, 22 Dec 2008 at 10:42AM -0800, mabshoff wrote:
> I am not aware of any documentation, but
>
>src/-- *vanilla* upstream
>SPKG.txt -- describes the spkg in wiki format, each new revision
> needs an updated changelog entry or an automatic "needs work" from my
> end at rev
On Mon, Dec 22, 2008 at 4:26 PM, Dan Drake wrote:
> I'm always happy to see positive news about Sage, but there's a couple
> things in the article that bug me:
>
>> A core idea of open source is finding alternative ways to make
>> programs similar to ones that are copyrighed.
>
> Sage and its com
I'm always happy to see positive news about Sage, but there's a couple
things in the article that bug me:
> A core idea of open source is finding alternative ways to make
> programs similar to ones that are copyrighed.
Sage and its components *are* copyrighted!
(Also, the writer seems to be conf
On Mon, Dec 22, 2008 at 10:23 AM, Robert Bradshaw
wrote:
> > On Dec 22, 2008, at 6:20 AM, John Cremona wrote:
>
> >> You can do K(r.lift()), but it would be nicer if this was handled by
> >> coercion magic.
>
> > This isn't really a coercion issue per se, it's a question of adding
> > another ca
Ok, William did add the info to
http://wiki.sagemath.org/SPKG_Audit
and I then cleaned it up some more. If anybody has some more info to
add or something to complain about or questions please let us know.
Once that text has matured a little more we should push it into the
Developers' manual p
On Mon, Dec 22, 2008 at 4:47 PM, William Stein wrote:
>
> On Mon, Dec 22, 2008 at 1:09 PM, David Joyner wrote:
>>
>> Hi:
>>
>> A very nice article on Sage and open source:
>> http://www.math.washington.edu/newsletter/2008/sage.php
>> Should I add this to the wiki?
>>
>
> Sure, please do!
Done
h
On Mon, Dec 22, 2008 at 1:09 PM, David Joyner wrote:
>
> Hi:
>
> A very nice article on Sage and open source:
> http://www.math.washington.edu/newsletter/2008/sage.php
> Should I add this to the wiki?
>
Sure, please do!
> - David Joyner
>
> PS Later in that issue, it is mentioned that Okounkov
Hi:
A very nice article on Sage and open source:
http://www.math.washington.edu/newsletter/2008/sage.php
Should I add this to the wiki?
- David Joyner
PS Later in that issue, it is mentioned that Okounkov
(a 2006 Fields medalist) will be speaking. Since he is
quoted as being pro open source, I
Robert,
> Most of the graph theory functions have a bunch of options for the
> format of the output, I'd say this would follow that trend, taking the
> old behavior as default.
Ok. I will try to extract edge based paths from generic graph
functions, depending on a new option.
> > For now only a
> Welcome to the community! We look forward to your contributions.
>
> I'm not sure exactly what thoughts or advice you are looking for. Are
> you proposing a change to Sage? Are you asking about other efforts to
> do similar things in python or Sage?
Jason, thanks for fast reply.
Our immedia
Pavel,
> > I would happily review any patch that did this, and I've made it trac
> > ticket #4854.
>
> Thanks for blazing reply. I'm not sure yet how to do this
> consistently: one may need to walk trough path by vertices or by
> edges, should this depend on multi_edges availability, etc.
Most o
Robert!
> I completely agree! Much of this functionality was written as a
> wrapper for NetworkX a while ago, and hasn't been revisited since. I
> would happily review any patch that did this, and I've made it trac
> ticket #4854.
Thanks for blazing reply. I'm not sure yet how to do this
consist
On Dec 22, 11:28 am, "William Stein" wrote:
> > Yes, but reviews I do in that area contain detailed points which need
> > to be fixed.
>
> Making all spkg reviews have to be done by you since you're the only
> one who knows the format is bad for the busfactor of sage.
Well, I didn't do all
On Mon, Dec 22, 2008 at 11:11 AM, mabshoff wrote:
>
>
>
> On Dec 22, 11:05 am, "William Stein" wrote:
>> On Mon, Dec 22, 2008 at 10:42 AM, mabshoff wrote:
>>
>> > On Dec 22, 8:14 am, "William Stein" wrote:
>>
>> >
>>
>> >> Michael A. or anybody else -- does anybody know if the exact spkg
>> >
Pavel G. Sutyrin wrote:
> Dear Sage developers,
>
> Firstly, thanks for the great and beautiful system that is joy to work and
> play with.
>
> While trying to model deterministic finite automata over Sage
> (multi-)graphs,
> I've run into the following: paths are represented as lists of vertice
> ... paths should be considered as sequences of labeled edges, not
> vertices, as far as two vertices may be connected by differently labeled
> edges ...
I completely agree! Much of this functionality was written as a
wrapper for NetworkX a while ago, and hasn't been revisited since. I
would hap
Dear Sage developers,
Firstly, thanks for the great and beautiful system that is joy to work and
play with.
While trying to model deterministic finite automata over Sage
(multi-)graphs,
I've run into the following: paths are represented as lists of vertices,
regardless
of edges. Superficial inve
On Dec 22, 11:05 am, "William Stein" wrote:
> On Mon, Dec 22, 2008 at 10:42 AM, mabshoff wrote:
>
> > On Dec 22, 8:14 am, "William Stein" wrote:
>
> >
>
> >> Michael A. or anybody else -- does anybody know if the exact spkg
> >> format is written down anywhere. I definitely couldn't find it
On Mon, Dec 22, 2008 at 10:42 AM, mabshoff wrote:
>
>
>
> On Dec 22, 8:14 am, "William Stein" wrote:
>
>
>
>> Michael A. or anybody else -- does anybody know if the exact spkg
>> format is written down anywhere. I definitely couldn't find it with
>> 10 minutes of searching on the wiki, etc., a
On Dec 22, 8:14 am, "William Stein" wrote:
> Michael A. or anybody else -- does anybody know if the exact spkg
> format is written down anywhere. I definitely couldn't find it with
> 10 minutes of searching on the wiki, etc., and nobody responded to the
> above email with a link.
>
> Willia
On Mon, Dec 22, 2008 at 10:23 AM, Robert Bradshaw
wrote:
>
> On Dec 22, 2008, at 6:20 AM, John Cremona wrote:
>
>> You can do K(r.lift()), but it would be nicer if this was handled by
>> coercion magic.
>
> This isn't really a coercion issue per se, it's a question of adding
> another case to the
2008/12/22 Robert Bradshaw :
>
> On Dec 22, 2008, at 6:20 AM, John Cremona wrote:
>
>> You can do K(r.lift()), but it would be nicer if this was handled by
>> coercion magic.
>
> This isn't really a coercion issue per se, it's a question of adding
> another case to the _element_constructor_ method
On Dec 22, 2008, at 6:20 AM, John Cremona wrote:
> You can do K(r.lift()), but it would be nicer if this was handled by
> coercion magic.
This isn't really a coercion issue per se, it's a question of adding
another case to the _element_constructor_ method of number fields. Do
we want coercio
I have not tried DSage. The manager of the cluster did not think it
was an appropriate tool for the cluster as the description of DSage
suggested it is only for coarse distribution (i.e. projects that can
be largely broken into separate parts). Unfortunately, my project
involves a sequential serie
I don't know if it is SQLalchemy or MySQL, but I also suspect it is
MySQL. I'll give PostgreSQL a try (should be an easy change, right?)
Thanks for the help
Dan
On Dec 19, 1:24 pm, Jason Grout wrote:
> Dan wrote:
> > Thanks for directing me.
>
> > The bottleneck appears to be queries to a MySQ
On Sun, Dec 21, 2008 at 11:14 PM, Dan Drake wrote:
> On Fri, 19 Dec 2008 at 11:40PM -0800, William Stein wrote:
>> Anyway, the best thing to do is to look at one that is in
>> spkg/standard/ and copy the format:
>>
>>src/-- most of your stuff goes in this directory
>>SPKG.txt
On Mon, Dec 22, 2008 at 6:20 AM, John Cremona wrote:
>
> You can do K(r.lift()), but it would be nicer if this was handled by
> coercion magic.I don't know how that could be done in Sage, but
> mathematically it would make sense whenever the defining polynomial of
> K divided that of R.
>
> J
You can do K(r.lift()), but it would be nicer if this was handled by
coercion magic.I don't know how that could be done in Sage, but
mathematically it would make sense whenever the defining polynomial of
K divided that of R.
John
2008/12/22 Alex Ghitza :
> Hi,
>
> While working with number f
Hi,
While working with number fields, I've run into this:
sage: K. = NumberField(x^8+1)
sage: R = K.polynomial_quotient_ring()
sage: r = R.random_element()
And now the point of this: I would like to think of r as an element of K.
However:
sage: K(r)
-
36 matches
Mail list logo