On Jan 9, 2009, at 9:21 PM, John H Palmieri wrote:
>
> On Jan 9, 7:03 pm, "William Stein" wrote:
>> On Fri, Jan 9, 2009 at 6:42 PM, John H Palmieri
>> wrote:
>>
>>> Here's another question: what is the most efficient way of testing
>>> whether one Set is a subset of another? I can do
>>
>>>
Thank you!
to_poly_solve() is a strong function, and it works fast.
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support-unsubscr...@googlegroups.com
For more options, v
John H Palmieri wrote:
>
>
> On Jan 9, 3:40 pm, "William Stein" wrote:
>> On Fri, Jan 9, 2009 at 3:38 PM, Mike Hansen wrote:
>>
>>> On Fri, Jan 9, 2009 at 3:36 PM, John H Palmieri
>>> wrote:
Is this a bug?
sage: Set([])
{}
sage: Set(Set([]))
{}
sage: Set([]) ==
On Jan 10, 7:25 am, Jason Grout wrote:
> John H Palmieri wrote:
> >
> > Here's another question: what is the most efficient way of testing
> > whether one Set is a subset of another? I can do
>
> > S in list(T.subsets())
>
> > -- and it's a bit frustrating that I can't do S in T.subsets() --
John H Palmieri wrote:
> sage: timeit('set(S).issubset(set(T))')
>
> gives me very similar times to the first option (all(s in T for s in
> S)). So if I start with Sage sets, I don't seem to gain much by
> converting back to python sets for this (not to mention that if S = Set
> (ZZ), then set(S
thank you!
On Jan 9, 7:27 pm, "William Stein" wrote:
> On Fri, Jan 9, 2009 at 3:49 AM, Sand Wraith wrote:
>
> > Hi!
>
> > Is it possible to get order of root of equation? For example equation:
>
> > f(x)=(x+1)^2
> > and it's solution "solve(f,x)" will be "[x == -1]", but this is not
> > perfect
On Sat, Jan 10, 2009 at 9:22 AM, Jason Grout
wrote:
>
> John H Palmieri wrote:
>> sage: timeit('set(S).issubset(set(T))')
>>
>> gives me very similar times to the first option (all(s in T for s in
>> S)). So if I start with Sage sets, I don't seem to gain much by
>> converting back to python set
On Fri, Jan 9, 2009 at 9:05 AM, William Stein wrote:
> On Fri, Jan 9, 2009 at 9:01 AM, Robert Dodier wrote:
>>
>> On Jan 9, 6:51 am, Slava wrote:
>>
>>> I`m trying to solve such simple system of equations: [sqrt(x) == 1, x
>>> == y],
>>> so I type:
>>>
>>> x,y = var('x,y');
>>> solve([sqrt(x) =
Hi, all,
When using the Notebook interface on Mac OS X, I find that once the
cells have filled the visible part of a web page, the notebook becomes
somewhat difficult to deal with. Specifically, if I have an
@interact, and modify the slider, the content of the page shifts down,
obscuring
William Stein wrote:
> Is there any reason not to just *always* use topoly_solver? I.e.,
> maybe Sage's solve should just 100% always only call topoly_solver.
> What do you think?
to_poly_solve can only handle equations in polynomials and radicals,
while solve can handle a somewhat wider range
On Sat, Jan 10, 2009 at 2:26 PM, Justin C. Walker wrote:
>
> Hi, all,
>
> When using the Notebook interface on Mac OS X, I find that once the
> cells have filled the visible part of a web page, the notebook becomes
> somewhat difficult to deal with. Specifically, if I have an
> @interact, and mo
I've been having the same problem with both 3.2.2 and 3.2.3 on my
Intel MacBook running OS X.4.11.
-JoelS
kcrisman wrote:
> Dear Support,
>
> I built 3.2.2 and seem to have a worsening of the auto-evaluation of
> @interact worksheets. Up to 3.2.1 the worksheets only autoevaluate
> interacts if
Justin C. Walker wrote:
> Hi, all,
>
> When using the Notebook interface on Mac OS X, I find that once the
> cells have filled the visible part of a web page, the notebook becomes
> somewhat difficult to deal with. Specifically, if I have an
> @interact, and modify the slider, the content
On Jan 10, 2009, at 15:48 , William Stein wrote:
>
> On Sat, Jan 10, 2009 at 2:26 PM, Justin C. Walker
> wrote:
>>
>> Hi, all,
>>
>> When using the Notebook interface on Mac OS X, I find that once the
>> cells have filled the visible part of a web page, the notebook
>> becomes
>> somewhat d
On Jan 10, 2009, at 16:26 , Jason Grout wrote:
>
> Justin C. Walker wrote:
>> Hi, all,
>>
>> When using the Notebook interface on Mac OS X, I find that once the
>> cells have filled the visible part of a web page, the notebook
>> becomes
>> somewhat difficult to deal with. Specifically, if I
On Sat, Jan 10, 2009 at 4:26 PM, Jason Grout
wrote:
>
> Justin C. Walker wrote:
>> Hi, all,
>>
>> When using the Notebook interface on Mac OS X, I find that once the
>> cells have filled the visible part of a web page, the notebook becomes
>> somewhat difficult to deal with. Specifically, if I h
Justin C. Walker wrote:
>
> On Jan 10, 2009, at 16:26 , Jason Grout wrote:
>
>> Justin C. Walker wrote:
>>> Hi, all,
>>>
>>> When using the Notebook interface on Mac OS X, I find that once the
>>> cells have filled the visible part of a web page, the notebook
>>> becomes
>>> somewhat difficult
William Stein wrote:
> On Sat, Jan 10, 2009 at 4:26 PM, Jason Grout
> wrote:
>> Justin C. Walker wrote:
>>> Hi, all,
>>>
>>> When using the Notebook interface on Mac OS X, I find that once the
>>> cells have filled the visible part of a web page, the notebook becomes
>>> somewhat difficult to dea
I am having trouble using the polyfit function. Here are the
commands:
import numpy as np
import scipy as sc
vp = np.array([1.0, 5.0, 10.0, 20.0, 40.0, 60.0, 100.0, 200.0, 400.0,
760.0])
T = np.array([-36.7, -19.6, -11.5, -2.6, 7.6, 15.4, 26.1, 42.2, 60.6,
80.1])
(a,b,c,d) = np.polyfit(vp,T,3
Hello,
On Sat, Jan 10, 2009 at 8:29 PM, slybro wrote:
>
> I am having trouble using the polyfit function. Here are the
> commands:
>
> import numpy as np
> import scipy as sc
>
> vp = np.array([1.0, 5.0, 10.0, 20.0, 40.0, 60.0, 100.0, 200.0, 400.0,
> 760.0])
>
> T = np.array([-36.7, -19.6, -11.
slybro wrote:
> I am having trouble using the polyfit function. Here are the
> commands:
>
> import numpy as np
> import scipy as sc
>
> vp = np.array([1.0, 5.0, 10.0, 20.0, 40.0, 60.0, 100.0, 200.0, 400.0,
> 760.0])
>
> T = np.array([-36.7, -19.6, -11.5, -2.6, 7.6, 15.4, 26.1, 42.2, 60.6,
> 8
21 matches
Mail list logo
