<div dir="ltr">As a matter of curiosity, have you tried it with Octave, <a href="https://www.gnu.org/software/octave/">https://www.gnu.org/software/octave/</a> ?<div><br></div><div>Doug</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 28, 2017 at 4:59 PM, Howard Butler <span dir="ltr"><<a href="mailto:howard@hobu.co" target="_blank">howard@hobu.co</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">A note to let you know this work is now complete.<div><br></div><div>* filters.matlab allows inline PDAL->Matlab->PDAL filter operations, much like filter.python. It requires the full Matlab environment to execute.</div><div>* writers.matlab now supports writing a single array struct with an optionally specified field list. It only requires the MX and MAT libraries.</div><div>* readers.matlab now supports reading a single array struct.</div><div>* filters.programmable and filters.predicate are now simply filters.python.</div><div><br></div><div>Please pull the latest master and configure with -DBUILD_PLUGIN_MATLAB=ON to test it out.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Howard</div></font></span><div><div class="h5"><div><br><div><blockquote type="cite"><div>On Jun 19, 2017, at 11:34 PM, Howard Butler <<a href="mailto:howard@hobu.co" target="_blank">howard@hobu.co</a>> wrote:</div><br class="m_-5206831610566742333Apple-interchange-newline"><div><div style="word-wrap:break-word">All,<div><br></div><div>Similar to PDAL's Python support <a href="https://www.pdal.io/python.html" target="_blank">https://www.pdal.io/<wbr>python.html</a>, 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?</div><div><br></div><div>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.</div><div><br></div><div>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? </div><div><br></div><div>Howard</div></div></div></blockquote></div><br></div></div></div></div><br>______________________________<wbr>_________________<br>
pdal mailing list<br>
<a href="mailto:pdal@lists.osgeo.org">pdal@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/pdal" rel="noreferrer" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/pdal</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div>Doug Newcomb</div><div>USFWS</div><div>551F Pylon Dr</div><div>Raleigh, NC</div><div>919-856-4520 ext. 14 <a href="mailto:doug_newcomb@fws.gov" target="_blank">doug_newcomb@fws.gov</a></div><div>---------------------------------------------------------------------------------------------------------</div><div>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. </div></div><div><b style="font-size:12.8px"><i><font color="#0000ff">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.</font></i></b><span style="color:rgb(0,0,255);font-family:"courier new",monospace;font-size:12.8px">​</span><br></div></div></div></div></div>
</div>