On Sun, Aug 29, 2010 at 12:54 PM, Stefan Evert <[email protected]> wrote:
>
> On 29 Aug 2010, at 16:13, P Kishor wrote:
>
>> I see several useful modules such as PDL::Graphics::LUT and
>> PDL::Transform::Cartography (both of which, surprisingly, do exist in
>> my build, in spite of no PGPLOT) use PDL::Graphics::PGPLOT. Why, oh
>> why didn't I build PGPLOT? Any cheat sheets out there?
>
> No cheat sheets ... I simply installed pgplot with MacPorts:
>
> sudo port -v install pgplot
>
> (then usually wait a couple of hours while MacPorts pulls a few GiB of
> unwanted software :), and it was automatically picked up by the PDL
> configuration (I'm building from current source code checked out from the Git
> repository).
Free advice -- take it or leave it. Never touch MacPorts or Fink. Just
don't. It messes up with your life, and really leaves misery in its
wake.
>
> I have never used PGPLOT, though, and trying the demo in the interactive
> perldl shell just now, I found to my surprise that it requires the external
> PGPLOT package in order to run. After installing this package from source
> code (automatic cpan installation doesn't work because the MacPorts
> include/library paths have to be specified manually when running
> Makefile.PL), everything looks fine.
>
> The only drawback is that MacPorts doesn't offer a universal variant, so
> PGPLOT will only be built for the main architecture (i.e. x86_64 on Snow
> Leopard); not too much of a problem in most cases.
>
> Question to all: Is the dependency on an external PGPLOT package really
> intentional? It's caused by a "use PGPLOT;" in PDL::Graphics::PGPLOT::Window
> (and perhaps other modules). If intentional, it should be tested by
> Makefile.PL and disable PGPLOT support unless the external package is
> installed.
All PDL graphics packages depend upon the external native libraries.
PDL::IO::GD needs libgd, PDL::Graphics::PLplot requires PLplot,
PDL::Graphics::Karma requires Karma, and so on. Makes sense that
PDL::Graphics::PGPLOT requires PGPLOT.
I still can't recall why I didn't enable PGPLOT. Maybe I should make a
pot of coffee and retry building PGPLOT.
On the other hand, I am not sure PGPLOT is going to be useful to me.
I need to write tiff, and I can do that with PDL::IO::Pic. It is quite
fast, and fairly simply. I just wish it could thread over 3D piddles.
I have a 500x400x100 piddle, and I want 100 images that are 500x400. I
am unable to do something like
$a->wpic('basefilename')
to get basefilename0.tif .. basefilename99.tif
So, for now, I am looping over my piddle, taking a slice out,
squeezing it, and then applying wpic. Seems so un-PDL-ish.
>
> Best wishes to everyone,
> Stefan
>
>
--
Puneet Kishor http://www.punkish.org
Carbon Model http://carbonmodel.org
Charter Member, Open Source Geospatial Foundation http://www.osgeo.org
Science Commons Fellow, http://sciencecommons.org/about/whoweare/kishor
Nelson Institute, UW-Madison http://www.nelson.wisc.edu
-----------------------------------------------------------------------
Assertions are politics; backing up assertions with evidence is science
=======================================================================
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
