>
>
> Here is a workaround. It's not ideal, but does work.
>
> sage: sage:
> solve((sin(x)+cos(x)==cos(2*x)).trig_expand(),x,to_poly_solve=True)
> [sin(x) == cos(x) - 1, x == -1/4*pi + 2*pi*z571, x == 3/4*pi + 2*pi*z569]
>
The reason *this* doesn't work right away is because we were abusing Pyt
On Wednesday, June 12, 2013 9:31:43 PM UTC-4, Stephen Montgomery-Smith
wrote:
>
> On 06/11/2013 09:44 PM, robin hankin wrote:
> > OK thanks for this, bug reported [at least, I think it is. I
> > couldn't see it on trac].
> >
> > Now what about this:
> >
> >
> > sage: solve(sin(x) + co
On 06/11/2013 09:44 PM, robin hankin wrote:
> OK thanks for this, bug reported [at least, I think it is. I
> couldn't see it on trac].
>
> Now what about this:
>
>
> sage: solve(sin(x) + cos(x) == cos(2*x),x,to_poly_solve=True)
> [x == 2*pi*z264, x == 2*pi*z268 + 1/6004799503160661*I - 355/4
On Tuesday, June 11, 2013 10:44:38 PM UTC-4, robin wrote:
>
> OK thanks for this, bug reported [at least, I think it is. I
> couldn't see it on trac].
>
> No
>
Unfortunately, the bug tracker from the notebook does *not* automatically
create Trac tickets. (Actually, this is sort of good,
On 06/11/2013 10:44 PM, robin hankin wrote:
> OK thanks for this, bug reported [at least, I think it is. I
> couldn't see it on trac].
>
> Now what about this:
>
>
> sage: solve(sin(x) + cos(x) == cos(2*x),x,to_poly_solve=True)
> [x == 2*pi*z264, x == 2*pi*z268 + 1/6004799503160661*I - 355/4
OK thanks for this, bug reported [at least, I think it is. I
couldn't see it on trac].
Now what about this:
sage: solve(sin(x) + cos(x) == cos(2*x),x,to_poly_solve=True)
[x == 2*pi*z264, x == 2*pi*z268 + 1/6004799503160661*I - 355/452, x ==
2*pi*z266 + 1/1125899906842624*I - 355/226, x == 2*
On 06/11/2013 07:26 PM, robin hankin wrote:
> OK Michael, thanks for this.
>
> But my problem was
>
> solve(sin(x)/cos(x)==1,x,to_poly_solve="force")
>
>
> returns an empty solution set, implying that there are no solutions
> when in fact there are. Surely this is misleading?
>
> Worthy of a
OK Michael, thanks for this.
But my problem was
solve(sin(x)/cos(x)==1,x,to_poly_solve="force")
returns an empty solution set, implying that there are no solutions
when in fact there are. Surely this is misleading?
Worthy of a bug report? IDK
best wishes
Robin
On Wed, Jun 12, 2013 at
On 06/11/2013 04:43 PM, robin hankin wrote:
> hello. Sage 5.9:
>
> sage: solve(sin(x)/cos(x)==1,x,to_poly_solve="force")
> []
>
>
>
> I find this unexpected because pi/4 is a solution, and sage seems to
> indicate that there are no solutions.
>
>
> Sage can handle the equation if I do some
hello. Sage 5.9:
sage: solve(sin(x)/cos(x)==1,x,to_poly_solve="force")
[]
I find this unexpected because pi/4 is a solution, and sage seems to
indicate that there are no solutions.
Sage can handle the equation if I do some preprocessing:
sage: solve(tan(x)==1,x,to_poly_solve='force')
[x ==
10 matches
Mail list logo