[sage-support] using Matplotlib and sagetex
Hi,
I would like to add plots to a document using sagetex and my script
uses matplotlib to generate the plot. Is it possible to matplotlib
with sagetex? I understand that /sageplot{} wants a graphics obj
with a .save method. However, I have not found how to generate such an
object.
For example if I use the simple example:
sage: from pylab import *
sage: t = arange(0.0, 2.0, 0.01)
sage: s = sin(2*pi*t)
sage: P = plot(t, s, linewidth=1.0)
sage: xl = xlabel('time (s)')
sage: yl = ylabel('voltage (mV)')
sage: t = title('About as simple as it gets, folks')
sage: grid(True)
sage: savefig('sage.png')
Where is the graphics obj?
cheers,
Adam
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-support] Re: prevent complex numbers ?
On Nov 28, 1:28 pm, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
On Nov 28, 9:14 am, Robert Bradshaw [EMAIL PROTECTED]
wrote:
On Nov 27, 2008, at 6:58 AM, [EMAIL PROTECTED] wrote:
Hello,
the example below shows that a complex number ( i think the I stands
for it ? ) appears by doing a simplify_full. Is there a way to prevent
this and to get output in real number format?
sage: var('omgo zr ys cz')
sage: eqomgo = omgo == (sqrt(2*ys - 2*cz)*sqrt(2*zr - 2*cz))/(2*zr -
2*cz)
sage: eqomgo.rhs().simplify_full()
I*sqrt(cz - ys)/sqrt(zr - cz)
Is ys assumed to be larger than cz? What about zr and cz? You can use
the assume command
sage: assume(ys cz)
sage: assume(zr cz)
Then do
sage: sage: eqomgo.rhs().simplify_full().real()
-sqrt(ys - cz)/sqrt(zr - cz)
Thanks for your answer!
Sorry, i didn't wrote that we tried the assume command. We just forgot
to use the real() function...
Hello again,
my problem was / is the prevention of falling into complex numbers. Is
there also a way to define variables to be and stay in a real format
for a whole worksheet? So i could avoid the use of the real() function
after each equation.
Thanks,
Andreas
Is there also a way to define the variables at the start of a
worksheet to
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-support] Plot axis tick interval
Hi, How can I change the distance between axis ticks when plotting in the notebook. I want to plot a simple 2d graph where the tick interval would be an integer, eg. 1. For example: p = plot(sin, [-10, 10]) p.axes_range(-10, 10, -10, 10) Currently this will result in a plot where the interval is 2.5. In gnuplot my request would be possible by using: set xtics 1 set ytics 1 -exty --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: jsMath issue and solution with error code -7
The real problem is not the missing fonts, but the fact that sage doesn't include the jsMath image fonts that are supposed to be used when the jsMath TeX fonts aren't available. I'm sure this was not included because it was considered to be too large a component, but it really should be, as it would have avoided this problem that so many of you are having. On the other hand, if you choose not to install the image fonts, there is a noImageFonts plugin that should be used so that jsMath knows about the fact that you don't have the image fonts, and will not try to use them when they aren't there (which is what is causing the warning message). If sage uses the jsMath/easy/load.js file (and I don't whether it does or not), then there is a noImageFonts setting that should be changed to 1 if you don't have the image fonts. That will cause the noImageFonts plugin to be loaded at the proper time. The best solution is to install the image fonts available from http://sourceforge.net/project/showfiles.php?group_id=172663 but if you don't want to do that, then using the noImageFonts plugin is the next best thing. Davide --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Doc-testing cdef'd methods
Simon King wrote: Dear Robert, On Nov 29, 7:43 pm, Robert Bradshaw [EMAIL PROTECTED] wrote: You can't call cdef functions from the Python interpreter. You can write a test function, e.g. _test_mulint. Good idea! On the other hand, after writing I wouldn't like to make the method public, I asked myself *why* I wouldn't. Dunno. So, I made it 'cpdef', and then the doc test works. Question for all: is there a good reason for writing cdef functions? Or should we make all cython functions cpdef? Python convention seems to be to expose the internals of the class, but just mark (with _ or __) the functions that are considered internal and may change without warning. I'm facing the doctesting dilemma brought up here with some other cdef functions in another class. Thanks, Jason --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: JsMath issue
Stan Schymanski wrote: Just search for jsMath failed to set up in the sage-support forum and you find out what to do (need to install the tex fonts from jsMath). Many people had this problem and I believe that the solution is being incorporated into the documentation. It's also been in the FAQ for a little while: http://wiki.sagemath.org/faq#IgetanerrorfromjsMathorthemathsymbolsdon.27tlookrightwhendisplayinginthenotebook Thanks, Jason --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Editing html on notebooks
Marshall Hampton wrote: There has been some work on this recently, by Jason Grout, on adding the tinyMCE editor to the notebook. The idea is that a shift-click will create a html block that can be edited by tinyMCE. Unfortunately at the moment that feature addition is somewhat intertangled with a refactoring of various javascript things, and its unclear when it will get straightened out. Perhaps Jason can comment since he often reads this list. I am also looking forward to having that functionality. We are at the end of our semester (i.e., busy), so it will probably be several weeks before this is untangled. I'd really like to have it done by the Joint Meetings in the first part of January, though. Thanks, Jason --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: jsMath issue and solution with error code -7
dpvc wrote: The real problem is not the missing fonts, but the fact that sage doesn't include the jsMath image fonts that are supposed to be used when the jsMath TeX fonts aren't available. I'm sure this was not included because it was considered to be too large a component, but it really should be, as it would have avoided this problem that so many of you are having. On the other hand, if you choose not to install the image fonts, there is a noImageFonts plugin that should be used so that jsMath knows about the fact that you don't have the image fonts, and will not try to use them when they aren't there (which is what is causing the warning message). If sage uses the jsMath/easy/load.js file (and I don't whether it does or not), then there is a noImageFonts setting that should be changed to 1 if you don't have the image fonts. That will cause the noImageFonts plugin to be loaded at the proper time. The best solution is to install the image fonts available from http://sourceforge.net/project/showfiles.php?group_id=172663 but if you don't want to do that, then using the noImageFonts plugin is the next best thing. Davide Thanks for your reply, Davide. We have an optional sage package for the image fonts that is easy to install. You're right, we decided to not make it standard because of the size. Currently, if the jsmath image fonts are not installed, we add the following code to the header of the page: script type=text/javascript src=/javascript/jsmath/plugins/noImageFonts.js/script and then later, we have: script src=/javascript/jsmath/jsMath.js type=text/javascript Should the order of these lines be reversed? I'm pretty sure we don't use the easy/load.js (and I'm not sure why). Thanks, Jason For references on the optional spkg, see the discussion from http://groups.google.com/group/sage-support/browse_thread/thread/e186e7ce4f7253c5/2822d7e064b5bad2?lnk=gstq=1971#2822d7e064b5bad2 or the trac ticket at http://trac.sagemath.org/sage_trac/ticket/1971 --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Editing html on notebooks
Thanks for the reply. that is exactly the feunctionality I was hoping for! On 30 nov, 14:19, Marshall Hampton [EMAIL PROTECTED] wrote: There has been some work on this recently, by Jason Grout, on adding the tinyMCE editor to the notebook. The idea is that a shift-click will create a html block that can be edited by tinyMCE. Unfortunately at the moment that feature addition is somewhat intertangled with a refactoring of various javascript things, and its unclear when it will get straightened out. Perhaps Jason can comment since he often reads this list. I am also looking forward to having that functionality. You can track the status of this at:http://trac.sagemath.org/sage_trac/ticket/4267 -M. Hampton On Nov 30, 6:13 am, Flavio Coelho [EMAIL PROTECTED] wrote: Hi, I would like to know if there is plans to allow direct editing of the html on a notebook without having to go to the Edit tab and entering html there. I was thinking it would be nice to have a simple javascript html editor that would come up when one clicks on text outside eveluation boxes. Thanks, Flávio Coelho --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: JsMath issue
Thanks for your responses. The reason that I didn't install the extra Tex fonts explicitly is because I thought that the jsmath-fonts package contained them already, however, I'll try and explicitly download them into that directory. On Dec 1, 11:00 am, Jason Grout [EMAIL PROTECTED] wrote: Stan Schymanski wrote: Just search for jsMath failed to set up in the sage-support forum and you find out what to do (need to install the tex fonts from jsMath). Many people had this problem and I believe that the solution is being incorporated into the documentation. It's also been in the FAQ for a little while: http://wiki.sagemath.org/faq#IgetanerrorfromjsMathorthemathsymbolsdon... Thanks, Jason --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Sage 3.2 released
On Nov 30, 2008, at 3:34 PM, mabshoff wrote: On Nov 30, 1:58 pm, Jim Clark [EMAIL PROTECTED] wrote: I am puzzled by one of the binaries:http://sage.math.washington.edu/ sage/osx/powerpc/sage-3.2-G5-PowerMacintosh-Darwin.dmg Does the G5 in the name mean it's specific for the G5 processor? Usually the binaries are named according to the OSX version -- is this one for OSX 10.4 or 10.5? That is an OSX 10.4 binary build on a G4. I am not 100% sure if it will be running on a G4. That G5 is the only 10.4 box we have access to 24/7 and it is also substantially faster (and has multiple CPUs) than any G4. So if you are attempting to run it on a G4 I would be very interested to see what happens if you run make check Downloaded and ran make check on my G3 computer -- works fine! (slowly, however, but I'm used to that :-) Thanks for your help, Michael. Jim --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Where may that segfault come from?
Dear Sage support,
since a couple of hours I am fighting with a segmentation fault in a
Cython module. Can you help me?
I can boil it down to the following files:
1. Ccrash.h:
typedef unsigned char FEL;
typedef FEL *PTR;
typedef struct
{
long i;
long m;
} piv_t;
piv_t *_zfindpiv_(PTR row);
2. Ccrash.c:
#include Ccrash.h
piv_t *_zfindpiv_(PTR row)
{
piv_t *P;
P-i=0;
P-m=0;
return P;
}
3. Crash.pxd:
cdef extern from Ccrash.h:
ctypedef unsigned char FEL
ctypedef FEL *PTR
ctypedef struct piv_t:
long i
long m
piv_t *_zfindpiv_(PTR row)
4. Crash.pyx:
def test():
cdef PTR row
print Start
cdef piv_t *P = _zfindpiv_(row)
print Values, P.i, P.m
return (P.i,P.m)
I made a Crash.so, precisely:
sage -cython Crash.pyx
gcc -c -fPIC -I/home/king/SAGE/devel/sage-3.1.4/local/include/python2.5/
Crash.c -o Crash.o
gcc -shared Crash.o Ccrash.o -o Crash.so
I tried it with sage -gdb, but I need help for understanding its
output:
sage: from Crash import test
Error while mapping shared library sections:
./Crash.so: Datei oder Verzeichnis nicht gefunden.
Error while reading shared library symbols:
./Crash.so: Datei oder Verzeichnis nicht gefunden.
## Very strange, because ./Crash.so is present and is used in the next
line
sage: test()
Start
Values 0 0
(0, 0)
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47137655676112 (LWP 6674)]
0x004d0090 in frame_dealloc (f=0x3b04d00)
at Objects/frameobject.c:424
424 Objects/frameobject.c: Datei oder Verzeichnis nicht gefunden.
in Objects/frameobject.c
So, apparently the segmentation fault occurs *after* the values are
returned by test().
What has happened? Is Cython unable to deallocate P or row properly??
Thanks in advance for your help
Simon
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-support] Re: Where may that segfault come from?
On Dec 1, 2008, at 10:13 AM, Simon King wrote: since a couple of hours I am fighting with a segmentation fault in a Cython module. Can you help me? I can boil it down to the following files: [snip] I made a Crash.so, precisely: sage -cython Crash.pyx gcc -c -fPIC -I/home/king/SAGE/devel/sage-3.1.4/local/include/ python2.5/ Crash.c -o Crash.o gcc -shared Crash.o Ccrash.o -o Crash.so I tried it with sage -gdb, but I need help for understanding its output: sage: from Crash import test Error while mapping shared library sections: ./Crash.so: Datei oder Verzeichnis nicht gefunden. This is probably a stupid question, but did where you create Ccrash.o? The cython step creates Ccrash.c, and you don't show where you compile it. Depending on your system, it may be that binding is really late, so you don't get an error message where you might expect it. Justin -- Justin C. Walker, Curmudgeon-At-Large Institute for the Enhancement of the Director's Income When LuteFisk is outlawed, Only outlaws will have LuteFisk --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Doc-testing cdef'd methods
Question for all: is there a good reason for writing cdef functions? Or should we make all cython functions cpdef? Python convention seems to be to expose the internals of the class, but just mark (with _ or __) the functions that are considered internal and may change without warning. There are definitely some cases where you have to -- for instance, if the return type of your function is something like int *, you're not going to be able to cpdef that. (Or, if you can, it's news to me.) I'm sure there are other reasons -- Rob will probably chime in with some as I'm typing this message. :) That said, there are a *huge* number of functions that do just need cdef turned into cpdef in the sage library. I'm facing the doctesting dilemma brought up here with some other cdef functions in another class. Yeah, I agree that seeing def _doctest_this_cdef_function and writing a little wrapper can be annoying, but I just don't think there's another way around it in some cases. -cc --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Where may that segfault come from?
Dear Justin, On Dec 1, 7:51 pm, Justin C. Walker [EMAIL PROTECTED] wrote: This is probably a stupid question, but did where you create Ccrash.o? The cython step creates Ccrash.c, and you don't show where you compile it. Sorry, that was just a cut-and-paste error in my post. Before producing the Crash.so, I did gcc -c -fPIC -I/home/king/SAGE/devel/sage-3.1.4/local/include/python2.5/ Ccrash.c -o Ccrash.o However, the more I think on it, the more I believe that the problem comes from using piv_t *. If I do not return a pointer but an actual piv_t then it works fine. But still I'd like to understand what is wrong with the pointers. Yours Simon --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Where may that segfault come from?
Simon King wrote:
Dear Sage support,
since a couple of hours I am fighting with a segmentation fault in a
Cython module. Can you help me?
I can boil it down to the following files:
1. Ccrash.h:
typedef unsigned char FEL;
typedef FEL *PTR;
typedef struct
{
long i;
long m;
} piv_t;
piv_t *_zfindpiv_(PTR row);
2. Ccrash.c:
#include Ccrash.h
piv_t *_zfindpiv_(PTR row)
{
piv_t *P;
P-i=0;
P-m=0;
return P;
}
It looks like you are never allocating the actual piv_t struct that P is
supposed to point to. You are just creating the pointer P and then
assigning directly to it.
Shouldn't you have something like
piv_t *P = malloc(sizeof(piv_t));
You'll also probably want to be careful about deallocating that memory
sometime to prevent a leak.
Jason
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-support] Re: Where may that segfault come from?
Dear Jason On Dec 1, 9:24 pm, Jason Grout [EMAIL PROTECTED] wrote: It looks like you are never allocating the actual piv_t struct that P is supposed to point to. You are just creating the pointer P and then assigning directly to it. Yes, I think you're right. Thank you! And sorry that by my lack of C-knowledge I didn't find it myself. Yours, Simon --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] wiki ban?
Upon following a routine link from sagemath.org: Warning: You triggered the wiki's surge protection by doing too many requests in a short time. Please make a short break reading the stuff you already got. When you restart doing requests AFTER that, slow down or you might get locked out for a longer time! I don't think this is possible, given this is the first time I've gone to the wiki (not necessarily a sagemath page, but wiki) in over a week, and I didn't try to do anything other than surf to it just now. Anyway, not a big problem for me, but perhaps someone might want to check if there is an over-aggressive detector there - or perhaps if someone else (with malicious intent) has tried to make the wiki go down? I hope not, and hope this is not reproducible! - kcrisman --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: wiki ban?
On Tue, Dec 2, 2008 at 8:41 AM, kcrisman [EMAIL PROTECTED] wrote: Upon following a routine link from sagemath.org: Warning: You triggered the wiki's surge protection by doing too many requests in a short time. Please make a short break reading the stuff you already got. When you restart doing requests AFTER that, slow down or you might get locked out for a longer time! I don't think this is possible, given this is the first time I've gone to the wiki (not necessarily a sagemath page, but wiki) in over a week, and I didn't try to do anything other than surf to it just now. Anyway, not a big problem for me, but perhaps someone might want to check if there is an over-aggressive detector there - or perhaps if someone else (with malicious intent) has tried to make the wiki go down? I hope not, and hope this is not reproducible! I just came across the same problem now. :-( I first go to www.sagemath.org then navigate to wiki.sagemath.org -- Regards Minh Van Nguyen Web: http://nguyenminh2.googlepages.com Blog: http://mvngu.wordpress.com --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: wiki ban?
I'm seeing this too. On Mon, Dec 1, 2008 at 5:07 PM, Minh Nguyen [EMAIL PROTECTED] wrote: On Tue, Dec 2, 2008 at 8:41 AM, kcrisman [EMAIL PROTECTED] wrote: Upon following a routine link from sagemath.org: Warning: You triggered the wiki's surge protection by doing too many requests in a short time. Please make a short break reading the stuff you already got. When you restart doing requests AFTER that, slow down or you might get locked out for a longer time! I don't think this is possible, given this is the first time I've gone to the wiki (not necessarily a sagemath page, but wiki) in over a week, and I didn't try to do anything other than surf to it just now. Anyway, not a big problem for me, but perhaps someone might want to check if there is an over-aggressive detector there - or perhaps if someone else (with malicious intent) has tried to make the wiki go down? I hope not, and hope this is not reproducible! I just came across the same problem now. :-( I first go to www.sagemath.org then navigate to wiki.sagemath.org -- Regards Minh Van Nguyen Web: http://nguyenminh2.googlepages.com Blog: http://mvngu.wordpress.com --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: wiki ban?
Hi, Try using http://sagemath.org:9001/ and let me know if that helps. On Mon, Dec 1, 2008 at 2:12 PM, Timothy Clemans [EMAIL PROTECTED] wrote: I'm seeing this too. On Mon, Dec 1, 2008 at 5:07 PM, Minh Nguyen [EMAIL PROTECTED] wrote: On Tue, Dec 2, 2008 at 8:41 AM, kcrisman [EMAIL PROTECTED] wrote: Upon following a routine link from sagemath.org: Warning: You triggered the wiki's surge protection by doing too many requests in a short time. Please make a short break reading the stuff you already got. When you restart doing requests AFTER that, slow down or you might get locked out for a longer time! I don't think this is possible, given this is the first time I've gone to the wiki (not necessarily a sagemath page, but wiki) in over a week, and I didn't try to do anything other than surf to it just now. Anyway, not a big problem for me, but perhaps someone might want to check if there is an over-aggressive detector there - or perhaps if someone else (with malicious intent) has tried to make the wiki go down? I hope not, and hope this is not reproducible! I just came across the same problem now. :-( I first go to www.sagemath.org then navigate to wiki.sagemath.org -- Regards Minh Van Nguyen Web: http://nguyenminh2.googlepages.com Blog: http://mvngu.wordpress.com -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: wiki ban?
On Dec 1, 2:32 pm, William Stein [EMAIL PROTECTED] wrote: Hi, Try usinghttp://sagemath.org:9001/and let me know if that helps. Yep, that should generally work. It will bypass the problem since IP surge protection is on a per IP base and www.sagemath.org only sees on IP due to the proxy/rewrite rules. Notice that the surge protection is currently triggered at 100 hits/s, so this would surprise me if that were the case. Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: wiki ban?
On Tue, Dec 2, 2008 at 9:32 AM, William Stein [EMAIL PROTECTED] wrote: Hi, Try using http://sagemath.org:9001/ and let me know if that helps. Thanks, William. It works for me. I can now visit the wiki as well as edit pages. -- Regards Minh Van Nguyen Web: http://nguyenminh2.googlepages.com Blog: http://mvngu.wordpress.com --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: wiki ban?
mabshoff wrote: On Dec 1, 2:32 pm, William Stein [EMAIL PROTECTED] wrote: Hi, Try usinghttp://sagemath.org:9001/and let me know if that helps. Yep, that should generally work. It will bypass the problem since IP surge protection is on a per IP base and www.sagemath.org only sees on IP due to the proxy/rewrite rules. Notice that the surge protection is currently triggered at 100 hits/s, so this would surprise me if that were the case. Does this mean that if there are over 100 hits/s, then everyone gets the surge protection warning? How long is the wiki down in that case? Jason --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: wiki ban?
On Mon, Dec 1, 2008 at 3:05 PM, Jason Grout [EMAIL PROTECTED] wrote: mabshoff wrote: On Dec 1, 2:32 pm, William Stein [EMAIL PROTECTED] wrote: Hi, Try usinghttp://sagemath.org:9001/and let me know if that helps. Yep, that should generally work. It will bypass the problem since IP surge protection is on a per IP base and www.sagemath.org only sees on IP due to the proxy/rewrite rules. Notice that the surge protection is currently triggered at 100 hits/s, so this would surprise me if that were the case. Does this mean that if there are over 100 hits/s, then everyone gets the surge protection warning? How long is the wiki down in that case? Jason Hi, I followed the direction here and hopefully disabled surge protection for the wiki: http://moinmo.in/HelpOnConfiguration/SurgeProtection Let me know if you have problems again. William --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: prevent complex numbers ?
On Dec 1, 2008, at 5:11 AM, Stan Schymanski wrote:
Hi Robert,
I wasn't aware of the real() function; pretty cool. I tried it out
myself in the above example and found an error. Not sure whether this
is an error in the real() function or in simplify_full. I suspect the
latter. Could you comment on this? I would also be very interested in
a way of defining symbolic variables such that they can only be real.
Is this only possible by doing assume(omgo,'real')?
Yes.
sage: assume(x, 'real')
sage: x.imag()
0
Are you saying you would like to pass in a domain when creating the
variables? Something like
sage: var('omega', domain=RR)
Here is the error I found. The result given by omgo.simplify_full
().real() is different to the one obtained by omgo.factor().
Currently we're using maxima as a back end for all the calculus
operations. This is probably due to maxima's simplifications being
lax with branch cuts, similar to
-1 = sqrt(-1)^2 = sqrt(-1) * sqrt(-1) = sqrt(-1 * -1) = sqrt(1) = 1
Thanks for your help!
You're welcome.
- Robert
--
| Sage Version 3.2, Release Date: 2008-11-20 |
| Type notebook() for the GUI, and license() for information.|
--
sage: var('omgo zr ys cz')
(omgo, zr, ys, cz)
sage: omgo = (sqrt(-zr^2 + 2*ys*zr + (2*cz - zr)^2 - 2*ys*(2*cz - zr))
+ 2*zr- 2*cz)/(2*zr - 2*cz)
sage: assume(czys,czzr)
sage: omgo.factor()
(zr + sqrt(cz - ys)*sqrt(cz - zr) - cz)/(zr - cz)
sage: omgo.simplify_full().real()
(zr - sqrt(cz - ys)*sqrt(cz - zr) - cz)/(zr - cz)
On Nov 28, 9:14 am, Robert Bradshaw [EMAIL PROTECTED]
wrote:
On Nov 27, 2008, at 6:58 AM, [EMAIL PROTECTED] wrote:
Hello,
the example below shows that a complex number ( i think the I
stands
for it ? ) appears by doing a simplify_full. Is there a way to
prevent
this and to get output in real number format?
sage: var('omgo zr ys cz')
sage: eqomgo = omgo == (sqrt(2*ys - 2*cz)*sqrt(2*zr - 2*cz))/(2*zr -
2*cz)
sage: eqomgo.rhs().simplify_full()
I*sqrt(cz - ys)/sqrt(zr - cz)
Is ys assumed to be larger than cz? What about zr and cz? You can use
the assume command
sage: assume(ys cz)
sage: assume(zr cz)
Then do
sage: sage: eqomgo.rhs().simplify_full().real()
-sqrt(ys - cz)/sqrt(zr - cz)
- Robert
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-support] Re: Sage 3.2 released
On Dec 1, 10:09 am, Jim Clark [EMAIL PROTECTED] wrote: SNIP Hi Jim, That is an OSX 10.4 binary build on a G4. I am not 100% sure if it will be running on a G4. That G5 is the only 10.4 box we have access to 24/7 and it is also substantially faster (and has multiple CPUs) than any G4. So if you are attempting to run it on a G4 I would be very interested to see what happens if you run make check Downloaded and ran make check on my G3 computer -- works fine! (slowly, however, but I'm used to that :-) Good to know. I guess I will leave the G5 off next time I build a OSX 10.4 binary on a G5. Thanks for your help, Michael. Jim Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
