[pdal] Matlab filters and Python refactoring

[Newcomb, Doug]

As a matter of curiosity, have you tried it with Octave,
https://www.gnu.org/software/octave/ ?

Doug

On Wed, Jun 28, 2017 at 4:59 PM, Howard Butler <howard at hobu.co> wrote:

> A note to let you know this work is now complete.
>
> * filters.matlab allows inline PDAL->Matlab->PDAL filter operations, much
> like filter.python. It requires the full Matlab environment to execute.
> * writers.matlab now supports writing a single array struct with an
> optionally specified field list. It only requires the MX and MAT libraries.
> * readers.matlab now supports reading a single array struct.
> * filters.programmable and filters.predicate are now simply filters.python.
>
> Please pull the latest master and configure with -DBUILD_PLUGIN_MATLAB=ON
> to test it out.
>
> Howard
>
> On Jun 19, 2017, at 11:34 PM, Howard Butler <howard at hobu.co> wrote:
>
> All,
>
> Similar to PDAL's Python support https://www.pdal.io/python.html, I have
> embarked on providing the ability to embed Matlab in the form of a
> filters.matlab stage. A client has requested this capability, and while I'm
> quite familiar with Python embedding scenarios, I hope the community can
> provide some guidance on what the must-haves would be for Matlab
> capability. The first attempt will simply allow users to touch a special
> "pdal" array with their script and update the point values as needed with
> no ability to change the schema in any way. The typical processing scenario
> would use filters.matlab in a pipeline operation. Assuming that is working
> in the upcoming 1.6 PDAL release, what other features would PDAL's Matlab
> connections need to make them extremely useful and powerful?
>
> Additionally, as part of the Matlab effort, it's clear the PDAL Python
> stuff is spread about a bit too much. The filters.predicate and
> filters.programmable nomenclature is confusing, and I propose that we
> simply rename it all to filters.python, and if the returned dictionary of
> Numpy arrays has a "mask" array on it, it will behave like
> filters.predicate does to cull the points. Otherwise, not much else will
> change for PDAL's Python stuff besides the filter name.
>
> Would Matlab interaction in PDAL pipelines be useful to you? What other
> PDAL/Matlab interaction scenarios give you the power of PDAL's processing
> pipelines married with Matlab's deep prototyping environment? My client
> would like to use intricate Matlab algorithms in the context of PDAL
> pipelines for data processing orchestration. How do we expose PDAL to the
> Matlab user in a way that would be useful for them?
>
> Howard
>
>
>
> _______________________________________________
> pdal mailing list
> pdal at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/pdal
>



-- 
Doug Newcomb
USFWS
551F Pylon Dr
Raleigh, NC
919-856-4520 ext. 14 doug_newcomb at fws.gov
---------------------------------------------------------------------------------------------------------
The opinions I express are my own and are not representative of the
official policy of the U.S.Fish and Wildlife Service or Dept. of the
Interior.   Life is too short for undocumented, proprietary data formats.
*NOTE: This email correspondence and any attachments to and from this
sender is subject to the Freedom of Information Act (FOIA) and may be
disclosed to third parties.*​
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pdal/attachments/20170628/5421589e/attachment.html>