Re: [sage-support] Re: building fortran extensions on Mac OS X
Believe it or not, mpi has been standard on mac for several years and is pretty solid. I'm with you on the bug reporter. Here's the address (and for those that don't know it, ADC membership is free so anybody can submit a bug report): https://bugreport.apple.com On Wed, Jun 2, 2010 at 12:44 AM, Tim Lahey wrote: > On Wed, Jun 2, 2010 at 1:41 AM, Chris Kees wrote: > > Hey, thanks, that patch fixed it. Yes, I'm on a 64-bit mac. We've had a > lot > > of trouble with numpy distutils and fortran on the mac unrelated to sage. > I > > was hoping that sage would provide a way to avoid those hassles among > other > > things. Apple could make life a hell of a lot easier by including > > gfortran/mpif90, etc. Thanks again. > > I recommend submitting a request for gfortran to the ADC Bug Reporter. The > more > requests they get, the higher priority it will be for the XCode team. > Since Apple > doesn't include MPI by default (I think), I'm doubtful that they'd > care about mpif90. > > Cheers, > > Tim. > > --- > Tim Lahey > PhD Candidate, Systems Design Engineering > University of Waterloo > http://www.linkedin.com/in/timlahey > > -- > 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, visit this group at > http://groups.google.com/group/sage-support > URL: http://www.sagemath.org > -- 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, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
Re: [sage-support] Re: building fortran extensions on Mac OS X
On Wed, Jun 2, 2010 at 1:41 AM, Chris Kees wrote: > Hey, thanks, that patch fixed it. Yes, I'm on a 64-bit mac. We've had a lot > of trouble with numpy distutils and fortran on the mac unrelated to sage. I > was hoping that sage would provide a way to avoid those hassles among other > things. Apple could make life a hell of a lot easier by including > gfortran/mpif90, etc. Thanks again. I recommend submitting a request for gfortran to the ADC Bug Reporter. The more requests they get, the higher priority it will be for the XCode team. Since Apple doesn't include MPI by default (I think), I'm doubtful that they'd care about mpif90. Cheers, Tim. --- Tim Lahey PhD Candidate, Systems Design Engineering University of Waterloo http://www.linkedin.com/in/timlahey -- 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, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
Re: [sage-support] Re: building fortran extensions on Mac OS X
Hey, thanks, that patch fixed it. Yes, I'm on a 64-bit mac. We've had a lot of trouble with numpy distutils and fortran on the mac unrelated to sage. I was hoping that sage would provide a way to avoid those hassles among other things. Apple could make life a hell of a lot easier by including gfortran/mpif90, etc. Thanks again. Chris On Tue, Jun 1, 2010 at 11:37 PM, Felix Lawrence wrote: > Hi Chris, > > Are you on a 64-bit mac, i.e. core 2 duo or newer? I believe Sage's > implementation of f2py is broken on 64-bit macs - certainly it is > broken on mine too. > > There is a simple patch that fixes this problem at > http://trac.sagemath.org/sage_trac/ticket/8010 , if anyone wants to > review it. > > Unfortunately it's a little complicated to apply the patch manually, > since the change is to the numpy spkg - you'll have to follow the > instructions at http://sagemath.org/doc/developer/patching_spkgs.html > . If you don't want this hassle, then you'll have to wait for someone > else to review the patch before it gets included in a new version of > sage. > > Cheers, > Felix > > > On Jun 1, 11:45 pm, Chris Kees wrote: > > Hi, > > > > I'm trying to build a fortran extension module with f2py using and spkg > I've > > built for sage 4.4.2 on Mac OS X 10.6. When I just run 'python setup.py > > install' from the commandline (with SAGE_LOCAL at the front of my path, > > etc.) The module build/installs fine, but when in installing as an spkg I > > get > > > > gfortran:f77: build/src.macosx-10.6-i386-2.6/ftracking-f2pywrappers.f > > sage_fortran -Wall -shared > > > build/temp.macosx-10.6-i386-2.6/build/src.macosx-10.6-i386-2.6/ftrackingmod > ule.o > > > build/temp.macosx-10.6-i386-2.6/build/src.macosx-10.6-i386-2.6/fortranobjec > t.o > > build/temp.macosx-10.6-i386-2.6/proteus/ftracking.o > > > build/temp.macosx-10.6-i386-2.6/build/src.macosx-10.6-i386-2.6/ftracking-f2 > pywrappers.o > > -L/Applications/sage/local/bin/../lib/gcc/i686-apple-darwin8/4.2.3/x86_64 > > -lm -lgfortran -o build/lib.macosx-10.6-i386-2.6/proteus/ftracking.so -g > > -lblas > > i686-apple-darwin8-gfortran-4.2: unrecognized option '-shared' > > Undefined symbols: > > "_PyErr_Occurred", referenced from: > > _int_from_pyobj in ftrackingmodule.o > > _create_cb_arglist in ftrackingmodule.o > > _double_from_pyobj in ftrackingmodule.o > > _f2py_rout_ftracking_foo in ftrackingmodule.o > > ...(and more undefined refs) > > > > It seems to be missing the -undefined dynamic_lookup option that is added > > when I do 'python setup.py install' from the command line: > > > > sage_fortran -Wall -shared -Wall -shared -undefined dynamic_lookup > -bundle > > > build/temp.macosx-10.6-i386-2.6/build/src.macosx-10.6-i386-2.6/ftrackingmod > ule.o > > > build/temp.macosx-10.6-i386-2.6/build/src.macosx-10.6-i386-2.6/fortranobjec > t.o > > build/temp.macosx-10.6-i386-2.6/proteus/ftracking.o > > > build/temp.macosx-10.6-i386-2.6/build/src.macosx-10.6-i386-2.6/ftracking-f2 > pywrappers.o > > -L/Applications/sage/local/bin/../lib/gcc/i686-apple-darwin8/4.2.3/x86_64 > > -lm -lgfortran -o build/lib.macosx-10.6-i386-2.6/proteus/ftracking.so -g > > -lblas > > > > Any idea what I'm going wrong? > > > > Thanks, > > Chris > > -- > 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, visit this group at > http://groups.google.com/group/sage-support > URL: http://www.sagemath.org > -- 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, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
[sage-support] Re: building fortran extensions on Mac OS X
Hi Chris, Are you on a 64-bit mac, i.e. core 2 duo or newer? I believe Sage's implementation of f2py is broken on 64-bit macs - certainly it is broken on mine too. There is a simple patch that fixes this problem at http://trac.sagemath.org/sage_trac/ticket/8010 , if anyone wants to review it. Unfortunately it's a little complicated to apply the patch manually, since the change is to the numpy spkg - you'll have to follow the instructions at http://sagemath.org/doc/developer/patching_spkgs.html . If you don't want this hassle, then you'll have to wait for someone else to review the patch before it gets included in a new version of sage. Cheers, Felix On Jun 1, 11:45 pm, Chris Kees wrote: > Hi, > > I'm trying to build a fortran extension module with f2py using and spkg I've > built for sage 4.4.2 on Mac OS X 10.6. When I just run 'python setup.py > install' from the commandline (with SAGE_LOCAL at the front of my path, > etc.) The module build/installs fine, but when in installing as an spkg I > get > > gfortran:f77: build/src.macosx-10.6-i386-2.6/ftracking-f2pywrappers.f > sage_fortran -Wall -shared > build/temp.macosx-10.6-i386-2.6/build/src.macosx-10.6-i386-2.6/ftrackingmod > ule.o > build/temp.macosx-10.6-i386-2.6/build/src.macosx-10.6-i386-2.6/fortranobjec > t.o > build/temp.macosx-10.6-i386-2.6/proteus/ftracking.o > build/temp.macosx-10.6-i386-2.6/build/src.macosx-10.6-i386-2.6/ftracking-f2 > pywrappers.o > -L/Applications/sage/local/bin/../lib/gcc/i686-apple-darwin8/4.2.3/x86_64 > -lm -lgfortran -o build/lib.macosx-10.6-i386-2.6/proteus/ftracking.so -g > -lblas > i686-apple-darwin8-gfortran-4.2: unrecognized option '-shared' > Undefined symbols: > "_PyErr_Occurred", referenced from: > _int_from_pyobj in ftrackingmodule.o > _create_cb_arglist in ftrackingmodule.o > _double_from_pyobj in ftrackingmodule.o > _f2py_rout_ftracking_foo in ftrackingmodule.o > ...(and more undefined refs) > > It seems to be missing the -undefined dynamic_lookup option that is added > when I do 'python setup.py install' from the command line: > > sage_fortran -Wall -shared -Wall -shared -undefined dynamic_lookup -bundle > build/temp.macosx-10.6-i386-2.6/build/src.macosx-10.6-i386-2.6/ftrackingmod > ule.o > build/temp.macosx-10.6-i386-2.6/build/src.macosx-10.6-i386-2.6/fortranobjec > t.o > build/temp.macosx-10.6-i386-2.6/proteus/ftracking.o > build/temp.macosx-10.6-i386-2.6/build/src.macosx-10.6-i386-2.6/ftracking-f2 > pywrappers.o > -L/Applications/sage/local/bin/../lib/gcc/i686-apple-darwin8/4.2.3/x86_64 > -lm -lgfortran -o build/lib.macosx-10.6-i386-2.6/proteus/ftracking.so -g > -lblas > > Any idea what I'm going wrong? > > Thanks, > Chris -- 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, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
[sage-support] Re: Sage Server - displaying Matlab plots
On 6/1/10 8:57 PM, Vinod wrote: Yes, matlab does save the images properly to the directory. But the problem here is to get the image displayed on the web browser itself. Are you saying that in the Sage notebook: 1. You can use the above code to create a matlab plot and save it to a specific directory (the current python directory) but 2. the image is not picked up automatically by the Sage notebook? Any image created in a Sage notebook cell "current directory" should be displayed in the notebook under that cell. Thanks, Jason -- 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, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
[sage-support] Re: Sage Server - displaying Matlab plots
Yes, matlab does save the images properly to the directory. But the problem here is to get the image displayed on the web browser itself. Thanks, Vinod On Jun 1, 4:17 pm, Jason Grout wrote: > On 6/1/10 5:53 PM, Vinod wrote: > > > hello Jason, > > > This doesn't work either... :( > > matlab doesn't even start with xvfb-run command. > > it gives lot of errors. > > As William pointed out, is the original problem resolved by one of the > other messages? If not, can you precisely state the problem as it now > stands? > > Thanks, > > Jason -- 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, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
[sage-support] Re: Sage Server - displaying Matlab plots
On 6/1/10 5:53 PM, Vinod wrote: hello Jason, This doesn't work either... :( matlab doesn't even start with xvfb-run command. it gives lot of errors. As William pointed out, is the original problem resolved by one of the other messages? If not, can you precisely state the problem as it now stands? Thanks, Jason -- 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, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
[sage-support] Re: typesetting arrays
On 5/30/10 6:41 PM, Jim Ragsdale wrote: I tried something else that a saw online: input: a=matrix(QQ,2,3,[1,2,3, 4,5,6]) show(a) output: looks like what I would expect. So do NumPy arrays not display like a matrix in the notebook? That's correct, at least for "show". You could convert the numpy array to a matrix and then show it, as a workaround. Patches are also welcome! Jason -- 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, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
[sage-support] Re: Sage Server - displaying Matlab plots
hello Jason, This doesn't work either... :( matlab doesn't even start with xvfb-run command. it gives lot of errors. ~Vinod On May 28, 6:24 pm, Jason Grout wrote: > On 5/28/10 8:08 PM, William Stein wrote: > > > > > On Fri, May 28, 2010 at 5:52 PM, Jason Grout > > wrote: > >> On 5/28/10 7:47 PM, Vinod wrote: > > >>> X11 connection rejected because of wrong authentication. > >>> Warning: Unable to open display 'localhost:12.0'. You will not be > >>> able to display graphics on the screen. > > >> So now it's not a Sage question, but a question of how to run Matlab over > >> an > >> ssh session. That's something that should have an answer somewhere, either > >> through a google search or asking MathWorks. > > > No, that is not the problem at all. > > What's happening is that he's giving code to Matlab that asks it to > > pop up a plot. Matlab > > is then trying to make the plot appear on the screen using *XWindows*. > > Naturally, this fails > > in the notebook -- it simply doesn't make any sense to do this. > > Right. Thanks for reminding me the context of this conversation. The > same problem (needing to pop up a window) appears when trying to render > an image using OpenGL without X. In the OpenGL case, I believe there > are ways of getting an opengl context to work without trying to pop up > an XWindows window. I believe the typical way to do this is to use a > framebuffer. A google search "opengl without x11" turns up lots of hits > for doing such a thing. Instructions for doing such a thing are also in > the Mayavi > manual:http://code.enthought.com/projects/mayavi/docs/development/html/mayav... > > I've never done this, though. Whether or not OpenGL is the problem > here, using a framebuffer might solve the problem. Maybe. Assuming you > are using Ubuntu, can you try following the instructions in the Mayavi > manual? > > $ sudo apt-get install xvfb > ssh in as the sage worksheet user > $ xvfb-run matlab > > then try the plotting command > > Jason -- 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, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
[sage-support] Re: zeros of the Riemann zeta function
Did you read the documentation of the function? It makes it quite clear: Definition: lcalc.zeros(self, n, L='') Docstring: Return the imaginary parts of the first n nontrivial zeros of the L-function in the upper half plane, as 32-bit reals. INPUT: * ``n`` - integer * ``L`` - defines L-function (default: Riemann zeta function) This function also checks the Riemann Hypothesis and makes sure no zeros are missed. This means it looks for several dozen zeros to make sure none have been missed before outputting any zeros at all, so takes longer than ``self.zeros_of_zeta_in_interval(...)``. You could always define your own function to return the complete zero: sage: [1/2+I*y for y in lcalc.zeros(10)] [0.5 + 14.1347251*I, 0.5 + 21.0220396*I, 0.5 + 25.0108576*I, 0.5 + 30.4248761*I, 0.5 + 32.9350616*I, 0.5 + 37.5861782*I, 0.5 + 40.9187190*I, 0.5 + 43.3270733*I, 0.5 + 48.0051509*I, 0.5 + 49.7738325*I] ! On Jun 1, 4:13 pm, Anne Driver wrote: > Hello, > > I am new to this list, and relatively new to Sage. I'm puzzled by the logic > of one part of Sage though. > > Although I don't have access to Mathematica at the minute on this computer, > I know if I compute the first zero, I get something like > > In[1] = ZetaZero[1] //N (to get a numerical value) > Out[1] = 1/2 + I*14.134... > > Trying this in Sage, I get: > > sage: lcalc.zeros(1) > [14.1347251] > > Why does Sage not do the sensible thing like Mathematica and return the > complex number 0.5 + I 14.1347251 ? It would seem much more logical. > > Of course, it is not proven that the real part is 1/2, so how would the case > be handled if a root was not found to have a real part of 1/2 ? > > Anne -- 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, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
Re: [sage-support] zeros of the Riemann zeta function
On Jun 1, 2010, at 11:05 AM, William Stein wrote: On Tue, Jun 1, 2010 at 10:58 AM, Robert Bradshaw wrote: On Jun 1, 2010, at 8:13 AM, Anne Driver wrote: Hello, I am new to this list, and relatively new to Sage. I'm puzzled by the logic of one part of Sage though. Although I don't have access to Mathematica at the minute on this computer, I know if I compute the first zero, I get something like In[1] = ZetaZero[1] //N (to get a numerical value) Out[1] = 1/2 + I*14.134... Trying this in Sage, I get: sage: lcalc.zeros(1) [14.1347251] Why does Sage not do the sensible thing like Mathematica and return the complex number 0.5 + I 14.1347251 ? It would seem much more logical. Of course, it is not proven that the real part is 1/2, so how would the case be handled if a root was not found to have a real part of 1/2 ? I believe both algorithms assume the Riemann hypothesis in computing them (otherwise, for example, it would be ambiguous to talk about the n- th zero anyways). Often such computations actually prove the Riemann hypothesis up to a given height (see, e.g., http://numbers.computation.free.fr/Constants/Miscellaneous/zetazeros1e13-1e24.pdf I've cc'd Mike Rubinstein, so he can respond if he wants, since I'm not sure lcalc is actually doing this or not. IIRC, the broad idea is to compute sign changes and then perform a contour integral to prove that you have located all the zeros. If no, refine the grid and try again. Of course this is a huge oversimplification, but if there are zeros not on the critical line than this would simply fail to terminate, and otherwise it would prove the hypothesis. - Robert -- 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, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
Re: [sage-support] zeros of the Riemann zeta function
On Tue, Jun 1, 2010 at 10:58 AM, Robert Bradshaw wrote: > On Jun 1, 2010, at 8:13 AM, Anne Driver wrote: > >> Hello, >> >> I am new to this list, and relatively new to Sage. I'm puzzled by the >> logic of one part of Sage though. >> >> Although I don't have access to Mathematica at the minute on this >> computer, I know if I compute the first zero, I get something like >> >> In[1] = ZetaZero[1] //N (to get a numerical value) >> Out[1] = 1/2 + I*14.134... >> >> Trying this in Sage, I get: >> >> sage: lcalc.zeros(1) >> [14.1347251] >> >> >> Why does Sage not do the sensible thing like Mathematica and return the >> complex number 0.5 + I 14.1347251 ? It would seem much more logical. >> >> Of course, it is not proven that the real part is 1/2, so how would the >> case be handled if a root was not found to have a real part of 1/2 ? > > I believe both algorithms assume the Riemann hypothesis in computing them > (otherwise, for example, it would be ambiguous to talk about the n-th zero > anyways). Often such computations actually prove the Riemann hypothesis up to a given height (see, e.g., http://numbers.computation.free.fr/Constants/Miscellaneous/zetazeros1e13-1e24.pdf) I've cc'd Mike Rubinstein, so he can respond if he wants, since I'm not sure lcalc is actually doing this or not. -- William > I would guess the reason that lcalc returns the imaginary part > only is that otherwise the first thing one would do to actually do anything > interesting with this data would be to take the imaginary part, so this just > saves the effort and overhead. > > - Robert > > -- > 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, visit this group at > http://groups.google.com/group/sage-support > URL: http://www.sagemath.org > -- William Stein 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 sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
Re: [sage-support] zeros of the Riemann zeta function
On Jun 1, 2010, at 8:13 AM, Anne Driver wrote: Hello, I am new to this list, and relatively new to Sage. I'm puzzled by the logic of one part of Sage though. Although I don't have access to Mathematica at the minute on this computer, I know if I compute the first zero, I get something like In[1] = ZetaZero[1] //N (to get a numerical value) Out[1] = 1/2 + I*14.134... Trying this in Sage, I get: sage: lcalc.zeros(1) [14.1347251] Why does Sage not do the sensible thing like Mathematica and return the complex number 0.5 + I 14.1347251 ? It would seem much more logical. Of course, it is not proven that the real part is 1/2, so how would the case be handled if a root was not found to have a real part of 1/2 ? I believe both algorithms assume the Riemann hypothesis in computing them (otherwise, for example, it would be ambiguous to talk about the n-th zero anyways). I would guess the reason that lcalc returns the imaginary part only is that otherwise the first thing one would do to actually do anything interesting with this data would be to take the imaginary part, so this just saves the effort and overhead. - Robert -- 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, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
[sage-support] Re: building fortran extensions on Mac OS X
On 1 June, 14:45, Chris Kees wrote: > Hi, > > I'm trying to build a fortran extension module with f2py using and spkg I've > built for sage 4.4.2 on Mac OS X 10.6. When I just run 'python setup.py > install' from the commandline (with SAGE_LOCAL at the front of my path, > etc.) The module build/installs fine, but when in installing as an spkg I > get > > gfortran:f77: build/src.macosx-10.6-i386-2.6/ftracking-f2pywrappers.f > sage_fortran -Wall -shared > build/temp.macosx-10.6-i386-2.6/build/src.macosx-10.6-i386-2.6/ftrackingmodule.o > build/temp.macosx-10.6-i386-2.6/build/src.macosx-10.6-i386-2.6/fortranobject.o > build/temp.macosx-10.6-i386-2.6/proteus/ftracking.o > build/temp.macosx-10.6-i386-2.6/build/src.macosx-10.6-i386-2.6/ftracking-f2pywrappers.o > -L/Applications/sage/local/bin/../lib/gcc/i686-apple-darwin8/4.2.3/x86_64 > -lm -lgfortran -o build/lib.macosx-10.6-i386-2.6/proteus/ftracking.so -g > -lblas > i686-apple-darwin8-gfortran-4.2: unrecognized option '-shared' > Undefined symbols: > "_PyErr_Occurred", referenced from: > _int_from_pyobj in ftrackingmodule.o > _create_cb_arglist in ftrackingmodule.o > _double_from_pyobj in ftrackingmodule.o > _f2py_rout_ftracking_foo in ftrackingmodule.o > ...(and more undefined refs) > > It seems to be missing the -undefined dynamic_lookup option that is added > when I do 'python setup.py install' from the command line: > > sage_fortran -Wall -shared -Wall -shared -undefined dynamic_lookup -bundle > build/temp.macosx-10.6-i386-2.6/build/src.macosx-10.6-i386-2.6/ftrackingmodule.o > build/temp.macosx-10.6-i386-2.6/build/src.macosx-10.6-i386-2.6/fortranobject.o > build/temp.macosx-10.6-i386-2.6/proteus/ftracking.o > build/temp.macosx-10.6-i386-2.6/build/src.macosx-10.6-i386-2.6/ftracking-f2pywrappers.o > -L/Applications/sage/local/bin/../lib/gcc/i686-apple-darwin8/4.2.3/x86_64 > -lm -lgfortran -o build/lib.macosx-10.6-i386-2.6/proteus/ftracking.so -g > -lblas > > Any idea what I'm going wrong? > > Thanks, > Chris sage_fortran is a shell script, which calls the fortran compiler. I assume it resides in $SAGE_LOCAL/bin. That has the patch to the real Fortran compiler, along with an option or two. You might try editing that script and adding what option you think is needed. I'm personally not keen how Sage handles Fortran, as that sage_fortran script hides what options are passed. But I suspect you can get around it by editing the script manually. -- 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, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
[sage-support] zeros of the Riemann zeta function
Hello, I am new to this list, and relatively new to Sage. I'm puzzled by the logic of one part of Sage though. Although I don't have access to Mathematica at the minute on this computer, I know if I compute the first zero, I get something like In[1] = ZetaZero[1] //N (to get a numerical value) Out[1] = 1/2 + I*14.134... Trying this in Sage, I get: sage: lcalc.zeros(1) [14.1347251] Why does Sage not do the sensible thing like Mathematica and return the complex number 0.5 + I 14.1347251 ? It would seem much more logical. Of course, it is not proven that the real part is 1/2, so how would the case be handled if a root was not found to have a real part of 1/2 ? Anne -- 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, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
[sage-support] pyhdf
Hi together, I'm trying to install pyhdf to work with NASA's HDF-EOS files. Unfortunately it does not work, if I follow these instructions: http://pysclint.sourceforge.net/pyhdf/install.html So I compiled szlib and hdf4 succesfully and did in the sage shell (I have sage 4.3.3 and Suse 11.1): $ export LIBRARY_DIRS=/usr/local/hdf4-4.2.5/lib/ $ export INCLUDE_DIRS=/usr/local/hdf4-4.2.5/include/ $ python setup.py install and got: running install running bdist_egg running egg_info running build_src building extension "pyhdf._hdfext" sources writing pyhdf.egg-info/PKG-INFO writing top-level names to pyhdf.egg-info/top_level.txt writing dependency_links to pyhdf.egg-info/dependency_links.txt reading manifest file 'pyhdf.egg-info/SOURCES.txt' writing manifest file 'pyhdf.egg-info/SOURCES.txt' installing library code to build/bdist.linux-x86_64/egg running install_lib running build_py running build_ext customize UnixCCompiler customize UnixCCompiler using build_ext building 'pyhdf._hdfext' extension compiling C sources C compiler: gcc -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict- prototypes -fPIC compile options: '-I/usr/local/hdf4-4.2.5/include/ -I/home/max/ sage-4.3.3-linux-64bit-opensuse_11.1_x86_64-x86_64-Linux/local/lib/ python2.6/site-packages/numpy/core/include -I/home/max/sage-4.3.3- linux-64bit-opensuse_11.1_x86_64-x86_64-Linux/local/include/python2.6 - c' extra options: '-DNOSZIP' gcc -pthread -shared build/temp.linux-x86_64-2.6/pyhdf/hdfext_wrap.o - L/usr/local/hdf4-4.2.5/lib/ -lmfhdf -ldf -ljpeg -lz -o build/lib.linux- x86_64-2.6/pyhdf/_hdfext.so /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ ld: /usr/local/hdf4-4.2.5/lib//libmfhdf.a(mfsd.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC /usr/local/hdf4-4.2.5/lib//libmfhdf.a: could not read symbols: Bad value collect2: ld returned 1 exit status /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ ld: /usr/local/hdf4-4.2.5/lib//libmfhdf.a(mfsd.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC /usr/local/hdf4-4.2.5/lib//libmfhdf.a: could not read symbols: Bad value collect2: ld returned 1 exit status error: Command "gcc -pthread -shared build/temp.linux-x86_64-2.6/pyhdf/ hdfext_wrap.o -L/usr/local/hdf4-4.2.5/lib/ -lmfhdf -ldf -ljpeg -lz -o build/lib.linux-x86_64-2.6/pyhdf/_hdfext.so " failed with exit status 1 Thanks, Max -- 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, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
[sage-support] building fortran extensions on Mac OS X
Hi, I'm trying to build a fortran extension module with f2py using and spkg I've built for sage 4.4.2 on Mac OS X 10.6. When I just run 'python setup.py install' from the commandline (with SAGE_LOCAL at the front of my path, etc.) The module build/installs fine, but when in installing as an spkg I get gfortran:f77: build/src.macosx-10.6-i386-2.6/ftracking-f2pywrappers.f sage_fortran -Wall -shared build/temp.macosx-10.6-i386-2.6/build/src.macosx-10.6-i386-2.6/ftrackingmodule.o build/temp.macosx-10.6-i386-2.6/build/src.macosx-10.6-i386-2.6/fortranobject.o build/temp.macosx-10.6-i386-2.6/proteus/ftracking.o build/temp.macosx-10.6-i386-2.6/build/src.macosx-10.6-i386-2.6/ftracking-f2pywrappers.o -L/Applications/sage/local/bin/../lib/gcc/i686-apple-darwin8/4.2.3/x86_64 -lm -lgfortran -o build/lib.macosx-10.6-i386-2.6/proteus/ftracking.so -g -lblas i686-apple-darwin8-gfortran-4.2: unrecognized option '-shared' Undefined symbols: "_PyErr_Occurred", referenced from: _int_from_pyobj in ftrackingmodule.o _create_cb_arglist in ftrackingmodule.o _double_from_pyobj in ftrackingmodule.o _f2py_rout_ftracking_foo in ftrackingmodule.o ...(and more undefined refs) It seems to be missing the -undefined dynamic_lookup option that is added when I do 'python setup.py install' from the command line: sage_fortran -Wall -shared -Wall -shared -undefined dynamic_lookup -bundle build/temp.macosx-10.6-i386-2.6/build/src.macosx-10.6-i386-2.6/ftrackingmodule.o build/temp.macosx-10.6-i386-2.6/build/src.macosx-10.6-i386-2.6/fortranobject.o build/temp.macosx-10.6-i386-2.6/proteus/ftracking.o build/temp.macosx-10.6-i386-2.6/build/src.macosx-10.6-i386-2.6/ftracking-f2pywrappers.o -L/Applications/sage/local/bin/../lib/gcc/i686-apple-darwin8/4.2.3/x86_64 -lm -lgfortran -o build/lib.macosx-10.6-i386-2.6/proteus/ftracking.so -g -lblas Any idea what I'm going wrong? Thanks, Chris -- 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, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
[sage-support] definition and composition of maps with several variables
I would like to compute the composition (f o g) where f, g are polynomial maps from R^2 to R^2. For example, if f(x,y) = (y, y^2 + x), I would like to obtain (f o f)(x,y) = (y^2 + x, (y^2 + x)^2 + y) In Maple the code is more or less : f := (x,y) -> (y, y^2 + x); (f...@f)(x,y); Is there a way to do a similar code with Sage ? Thanks, Stephane -- 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, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
