From: Hiroyasu Y. <h-y...@ce...> - 2007-05-22 06:15:21
|
Dear all: I have been using PLplot with fortran on Mac OSX and PLplot always helps my works. Although I output to ps or X-Window, I would like to output to Aquaterm and Jpeg. How to write the fortran cord with PLplot in oder to to use some output drivers, how to build the my code ? Please let me know. Hiro ------from Hiroyasu Yasuda Civil Engineering Research Institute Hiragishi 1-3, Toyohira, Sapporo,062-8602, JAPAN Phone; +81-11-841-1639, Fax; +81-11-820-4246 |
From: Arjen M. <arj...@wl...> - 2007-05-22 06:31:22
|
Hiroyasu YASUDA wrote: >Dear all: > >I have been using PLplot with fortran on Mac OSX and PLplot always >helps my works. > >Although I output to ps or X-Window, I would like to output to >Aquaterm and Jpeg. How to write the fortran cord with PLplot in oder >to to use some output drivers, how to build the my code ? Please let >me know. > > > Hello Hiro, that is easy: you use a different driver than the PS or Xterm drivers. If you look at the examples and run them, you will see that they first ask for the driver you want to use. Presumably you set the driver directly in your program(s). If you do not, that is, do not call plsdev(), then you should get a list of the available drivers too. Jpeg requires the GD library - I do not know whether that is standardly available on OSX, if not, you will have to install it yourself. Aquaterm ought to be supported without extra stuff, if I understand your platform correctly. Regards, Arjen |
From: Jerry <lan...@qw...> - 2007-05-23 04:45:25
|
I'm not sure what your requirements are that you need JPEG, but as you probably know, PDF is native across OS X (even the screen display is based on PDF). You can save directly from AquaTerm in either PDF or Postscript. If you want to convert to other file formats such as JPEG (and you don't have to do this many times), it is easy to copy directly from the front AquaTerm window (Command-C), switch to Preview.app, and hit New from Clipboard or just Command-N. From there you can save as any of BMP, GIF, JPEG, JPEG 2000, PDF, Photoshop, PICT, PNG, SGI, TGA, or TIFF. Of course, if you need to convert to other formats, there is always the venerable Graphic Converter which knows about every graphic format ever devised. Sorry if this is already known to you, but just in case.... Jerry On May 21, 2007, at 11:31 PM, Arjen Markus wrote: > >> Dear all: >> >> I have been using PLplot with fortran on Mac OSX and PLplot always >> helps my works. >> >> Although I output to ps or X-Window, I would like to output to >> Aquaterm and Jpeg. How to write the fortran cord with PLplot in oder >> to to use some output drivers, how to build the my code ? Please let >> me know. >> |
From: Alan W. I. <ir...@be...> - 2007-05-22 06:38:20
|
On 2007-05-22 15:15+0900 Hiroyasu YASUDA wrote: > Dear all: > > I have been using PLplot with fortran on Mac OSX and PLplot always > helps my works. > > Although I output to ps or X-Window, I would like to output to > Aquaterm and Jpeg. How to write the fortran cord with PLplot in oder > to to use some output drivers, how to build the my code ? Please let > me know. If you put "call plparseopts(1)" as the first plplot fortran call in your code (e.g., before call plinit()), you can use a command-line option, e.g., ./x01f -dev jpeg This method is used for all our many fortran examples, see examples/f77 and examples/f95. Alternatively, I believe you can hard-code a device in your fortran code using, e.g., call plsdev('jpeg'), but I never use that method since the command-line option is so much easier to use. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); PLplot scientific plotting software package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ |
From: Hiroyasu Y. <h-y...@ce...> - 2007-05-22 08:55:47
|
Thank you for the quick reply. My code always includes "call plparseopts(1)" before plinit(1). But, when I build the code as "g77 x01f.f `plplot-config --cflags --libs -- with-f77` -o x01f" and then the code shows "Requested device jpeg not available" when the code run as "./x01f -dev jpeg". Does that thing mean that my system doesn't have output driver and installation of PLplot was failed ? How to do that ? I have another question. If I use intel fortran 9.1 to build the cord with PLplot, the code shows "plparseopts: negative number of arguments" when the code run. But I can get right plot result. What is problem under this situation ? Regards, Hiro On May 22, 2007, at 3:38 PM, Alan W. Irwin wrote: > On 2007-05-22 15:15+0900 Hiroyasu YASUDA wrote: > >> Dear all: >> >> I have been using PLplot with fortran on Mac OSX and PLplot always >> helps my works. >> >> Although I output to ps or X-Window, I would like to output to >> Aquaterm and Jpeg. How to write the fortran cord with PLplot in oder >> to to use some output drivers, how to build the my code ? Please let >> me know. > > If you put "call plparseopts(1)" as the first plplot fortran call > in your > code (e.g., before call plinit()), you can use a command-line > option, e.g., > > ./x01f -dev jpeg > > This method is used for all our many fortran examples, see > examples/f77 and examples/f95. > > Alternatively, I believe you can hard-code a device in your fortran > code > using, e.g., call plsdev('jpeg'), but I never use that method since > the > command-line option is so much easier to use. > > Alan > __________________________ > Alan W. Irwin > > Astronomical research affiliation with Department of Physics and > Astronomy, > University of Victoria (astrowww.phys.uvic.ca). > > Programming affiliations with the FreeEOS equation-of-state > implementation > for stellar interiors (freeeos.sf.net); PLplot scientific plotting > software > package (plplot.org); the libLASi project (unifont.org/lasi); the > Loads of > Linux Links project (loll.sf.net); and the Linux Brochure Project > (lbproject.sf.net). > __________________________ > > Linux-powered Science > __________________________ > ------from 安田 浩保 寒地土木研究所 寒地河川チーム 〒062-8602 札幌市豊平区平岸1条3-1-34 Tel;011-841-1639 Fax;011-820-4246 E-mail;h-y...@ce... ------from Hiroyasu Yasuda Civil Engineering Research Institute Hiragishi 1-3, Toyohira, Sapporo,062-8602, JAPAN Phone; +81-11-841-1639, Fax; +81-11-820-4246 |
From: Arjen M. <arj...@wl...> - 2007-05-22 09:21:36
|
Hiroyasu YASUDA wrote: > Thank you for the quick reply. > > My code always includes "call plparseopts(1)" before plinit(1). But, > when I build the code as "g77 x01f.f `plplot-config --cflags --libs -- > with-f77` -o x01f" and then the code shows "Requested device jpeg not > available" when the code run as "./x01f -dev jpeg". That means that the libraries that the jpeg driver uses are not available on your system. Check the installation instructions for this and rebuild PLplot. > > Does that thing mean that my system doesn't have output driver and > installation of PLplot was failed ? How to do that ? No, the PLplot installation did not fail. PLplot optionally uses a number of third-party libraries. If these are not found during the build process, the resulting PLplot library/installation simply can not use the drivers and other facilities that depend on them. For instance: If you do not have a C++ compiler, then the C++ bindings will not be built. This is however independent of the Fortran bindings (they require a F77 or a F95 compiler). Similarly, some device drivers require extra libraries - GD for GIF. JPEG, PNG ... If the GD library is not found, these device drivers are turned off. > > I have another question. If I use intel fortran 9.1 to build the cord > with PLplot, the code shows "plparseopts: negative number of > arguments" when the code run. But I can get right plot result. What is > problem under this situation ? > The problem is that the wrong number of arguments is passed on from the runtime libraries. We have looked into the problem a few years ago but were unable to solve it - it is something deep inside the runtime libraries. Simply ignore it. Regards, Arjen |