This is really nice. A long standing functionality. When we move to
python3, the other bug can also be taken care of.
On Tuesday, October 23, 2012 10:24:26 PM UTC+8, Volker Braun wrote:
>
> I've added the missing parents and coercion bits in a patch at the trac
> ticket.
>
> On Tuesday, October
On Wednesday, October 24, 2012 10:32:25 AM UTC+8, kcrisman wrote:
>
>
>
> On Tuesday, October 23, 2012 8:42:42 PM UTC-4, Jason Grout wrote:
>>
>> On 10/23/12 4:29 PM, Ivan Andrus wrote:
>> > JOOC,
>>
>> Huh?
>>
>
> Just out of curiosity, says teh Interweb.
>
>
QFT :D
--
You received this
On Tuesday, October 23, 2012 8:42:42 PM UTC-4, Jason Grout wrote:
>
> On 10/23/12 4:29 PM, Ivan Andrus wrote:
> > JOOC,
>
> Huh?
>
Just out of curiosity, says teh Interweb.
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To post to this
On 10/23/12 4:29 PM, Ivan Andrus wrote:
JOOC,
Huh?
Does the Android app still use the old server?
I think so. As soon as the iOS app and the Android app migrate off of
it, we're shutting down aleph1.sagemath.org. As it is now, it won't be
upgraded at all.
Thanks,
Jason
--
You rece
On Oct 23, 2012, at 9:29 PM, Jason Grout wrote:
> On 10/23/12 2:11 PM, Ivan Andrus wrote:
>> I tried to install the new Sage cell server based on the instructions
>> on github [1] with Sage-5.4.beta2. It didn't work (the spkg
>> mentioned didn't exist, then the one I tried had patch rejections,
>>
Thanks
On Tuesday, October 23, 2012 11:37:38 AM UTC-4, Safia Yonker wrote:
>
> Hello Jason, If you wouldn't mind restarting the demo server one more
> time. I have one more round of documents shared with me by students that I
> need to download before I am completely switched to the main sagenb
On 10/23/12 2:11 PM, Ivan Andrus wrote:
I tried to install the new Sage cell server based on the instructions
on github [1] with Sage-5.4.beta2. It didn't work (the spkg
mentioned didn't exist, then the one I tried had patch rejections,
then ignoring those, zmq didn't install). Anyway, I tried
On Oct 22, 2012, at 5:41 PM, Jason Grout wrote:
> On 10/22/12 10:34 AM, Dima Pasechnik wrote:
>> On 2012-10-22, Vijay Sharma wrote:
>>> --e89a8ff2515038016404cca5cc72
>>> Content-Type: text/plain; charset=ISO-8859-1
>>>
>>> Dima,
>>>
>>> Thank you very much.
>>> I have SAGE Server locally instal
Ivan,
I can try things on simulator.
I can spend time mostly on weekends. Hope that is fine.
May be let me start from testing as of now and then I take up things
further.
Regards,
Vijay
On Wed, Oct 24, 2012 at 12:15 AM, Ivan Andrus wrote:
> That could be useful. What skills do you have? HTML
That could be useful. What skills do you have? HTML, Javascript, Objective-C?
Sadly my javascript skills are pretty 1998. :-) Even just testing would be
helpful, but it would require you having an Apple account and stuff to try it
on your device. Otherwise you can try it on the simulator.
On 10/23/12 1:38 PM, Nathan Yeung wrote:
Hi,
So the sage server that I was running went down and all the published
worksheets are gone now. Does anyone know how I can recover them?
Can you tell us more about your setup? Is it running in a virtual
machine? What version of Sage? Where is the
Hi,
So the sage server that I was running went down and all the published
worksheets are gone now. Does anyone know how I can recover them?
Thanks,
Nathan
On Tue, Oct 23, 2012 at 11:46 AM, wrote:
> Today's Topic Summary
>
> Group: http://groups.google.com/group/sage-support/topics
>
>-
On 10/23/12 12:37 PM, William Stein wrote:
On Tue, Oct 23, 2012 at 9:21 AM, Jason Grout
wrote:
On 10/23/12 10:37 AM, Safia Yonker wrote:
Hello Jason, If you wouldn't mind restarting the demo server one more
time. I have one more round of documents shared with me by students
that I need to do
On Tue, Oct 23, 2012 at 9:21 AM, Jason Grout
wrote:
> On 10/23/12 10:37 AM, Safia Yonker wrote:
>>
>> Hello Jason, If you wouldn't mind restarting the demo server one more
>> time. I have one more round of documents shared with me by students
>> that I need to download before I am completely swit
On 10/23/12 10:37 AM, Safia Yonker wrote:
Hello Jason, If you wouldn't mind restarting the demo server one more
time. I have one more round of documents shared with me by students
that I need to download before I am completely switched to the main
sagenb.org and I won't pester you about this aga
Hello Jason, If you wouldn't mind restarting the demo server one more time.
I have one more round of documents shared with me by students that I need
to download before I am completely switched to the main sagenb.org and I
won't pester you about this again.
Safia
On Thursday, September 27, 2
On Tuesday, October 23, 2012 3:45:56 PM UTC+1, Peter Mueller wrote:
> importing Sum from sage.numerical.mip and replacing all occurrences of sum
> with Sum fixed the problem of the long running times, thanks a lot
> Such important information should be in the docs, a naive user like I am
> never
Sure Jason,
I can try after one week.
Also let me know if you need a helping hand for some coding.
I am not that advanced but can give an attempt to contribute something.
Regards,
Vijay
On Tue, Oct 23, 2012 at 7:12 PM, Ivan Andrus wrote:
> Could you give a specific example? I am not seeing th
Dear Volker,
importing Sum from sage.numerical.mip and replacing all occurrences of sum
with Sum fixed the problem of the long running times, thanks a lot!
Such important information should be in the docs, a naive user like I am
never would have found that out!
All the best
Peter Mueller
--
Profiling info:
sage: P = MixedIntegerLinearProgram()
sage: x = P.new_variable(binary=True)
sage: %prun for i in [0..29]: c = sum(x[j]*(j-i) for j in [0..29])
608747 function calls (554747 primitive calls) in 0.430 seconds
Ordered by: internal time
ncalls tottime percall cumtim
I don't understand why all the copying goes on in mip.pyx, maybe Nathan can
comment? I think the method would be much faster without deepcopy(). Just
shallow copy stuff into new dicts. The coefficients of the linear functions
are immutable, so its not a problem to have them linked multiple times
I've added the missing parents and coercion bits in a patch at the trac
ticket.
On Tuesday, October 23, 2012 12:44:03 PM UTC+1, Nathann Cohen wrote:
>
> Here's a trac ticket that -- at least -- prints a bug report.
>
> http://trac.sagemath.org/sage_trac/ticket/13646
>
>
--
You received this mes
On 10/23/2012 05:26 PM, Nathann Cohen wrote:
Hello !!!
According to the doc, this seems to be a bug. Unfortunately, this
behavior produces wrong results. It took me some time to isolate the
problem! Bugs which just produce error messages are much friendlier ...
I totall
Could you give a specific example? I am not seeing the problem now that the
server has been restarted. Regardless, I think commands time out long before
an hour. I could be wrong though.
Anyway, I'm working on updating to the new protocol so that hopefully things
will work better. It's quit
Sorry for bombing this list with my MIP problems. Here is another thing,
again in Sage 5.3:
The following (senseless) test code
P = MixedIntegerLinearProgram()
x = P.new_variable(binary=True)
for i in [0..29]:
c = sum(x[j]*(j-i) for j in [0..29])
takes about 1.6 seconds, even though there a
Jason,
Now at least the computations like sum and simple commands are getting
executed.
But it took long like an hour.
But commands like plot3D etc. are taking huge time. Still running.
Regards,
Vijay
On Tue, Oct 23, 2012 at 12:41 AM, Vijay Sharma wrote:
> Jason,
>
> May I share that I access
Thanks for this. [?]
2012/10/22 Volker Braun
> You can always roll your own if you don't like it. You can also try to
> take apart the pieces that do the plot, for example,
>
> sage: proj = sage.geometry.polyhedron.plot.Projection(q)
> sage: proj.render_outline_2d(color='red')
>
>
>
> On Monday,
Hellooo !!
> I'd say there are two bugs:
There are always too many.
> 1) p.new_variable() should raise an error if it doesn't understand the
> argument, and not just silently do nothing.
Perfectly true. #13646 is meant to fix that :-)
> 2) the inequality operators should work both ways to
Here's a trac ticket that -- at least -- prints a bug report.
http://trac.sagemath.org/sage_trac/ticket/13646
Nathann
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To post to this group, send email to sage-support@googlegroups.com.
To unsubs
yes, should be equality.
Btw if anybody feels adventurous I have a big pile of trac tickets relating
to polyhedra that are sitting there for 1+ years.
On Tuesday, October 23, 2012 8:37:04 AM UTC+1, Harald Schilly wrote:
>
>
>
> On Monday, October 22, 2012 11:09:51 AM UTC+2, Volker Braun wrote
And, by the way, the MIP stuff has absolutely no support for any of the
Sage infrastructure. Everything just derives from object. Not even
SageObject.
On Tuesday, October 23, 2012 10:41:05 AM UTC+1, Volker Braun wrote:
> 2) the inequality operators should work both ways to create
> LinearConst
I'd say there are two bugs:
1) p.new_variable() should raise an error if it doesn't understand the
argument, and not just silently do nothing.
2) the inequality operators should work both ways to create
LinearConstraints
On Tuesday, October 23, 2012 9:36:54 AM UTC+1, Peter Mueller wrote:
>
>
Hello !!!
According to the doc, this seems to be a bug. Unfortunately, this behavior
> produces wrong results. It took me some time to isolate the problem! Bugs
> which just produce error messages are much friendlier ...
>
I totally agree. It has been reported before, and I definite
In Sage 5.3, I get the following:
sage: p = MixedIntegerLinearProgram()
sage: x = p.new_variable(integer=True)
sage: c = x[0]-x[1]
sage: p.add_constraint(10 <= c)
sage: p.show()
Maximization:
Constraints:
Variables:
x_0 is an integer variable (min=0.0, max=+oo)
x_1 is an integer variable (mi
On Monday, October 22, 2012 11:09:51 AM UTC+2, Volker Braun wrote:
>
> sage: q = Polyhedron(vertices=points, rays=[(0,1)])
>
>>
I just opened the documentation here:
http://www.sagemath.org/doc/reference/sage/geometry/polyhedron/constructor.html
because I wasn't sure what it is doing, and at the
35 matches
Mail list logo
