You are correct about the issue. The document and VTK are out of sync temporarily. I have a fix that makes VTK do what the document says but I was waiting for modularization to settle down before pushing it to Gerrit. I'll accelerate that and push them to Gerrit tomorrow. I'll add you as a reviewer :-)<div>
<br></div><div>The answer to the second question: Yes. It is by design (not mine). When a new data object is setup as the output, all pipeline specific keys are removed from the output port. So you need to call UpdateInformation (I know it is really UpdateDataObject but I am going to tell anyone to use that method directly) once before you can set requests.</div>
<div><br></div><div>-berk</div><div><br><br><div class="gmail_quote">On Thu, Apr 12, 2012 at 5:07 PM, Pat Marion <span dir="ltr"><<a href="mailto:pat.marion@kitware.com">pat.marion@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I ran into an issue while performing the migration described here:<br><br><a href="http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Removal_of_Methods_for_Manipulating_Update_Extent" target="_blank">http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Removal_of_Methods_for_Manipulating_Update_Extent</a><br>
<br>In VTK 5<br><br>void vtkDataObject::SetUpdateExtent(int piece, int numPieces, int ghostLevel) executed:<br>{<br> ...<br> sddp->SetUpdateExtent<br> (sddp->GetOutputInformation()->GetInformationObject<br>
(this->GetPortNumber()), piece, numPieces, ghostLevel);<br> ...<br>}<br><br><br>In VTK 6<br><br>void vtkAlgorithm::SetUpdateExtent(int port, int connection,<br> int piece,<br>
int numPieces,<br> int ghostLevel)<br>{<br> ...<br> vtkStreamingDemandDrivenPipeline::SetUpdateExtent(<br> this->GetInputInformation(port, connection),<br>
piece,<br> numPieces,<br> ghostLevel);<br> ...<br>}<br><br><br>In VTK 5, the output information is used, in VTK 6, the input information is used which results in incorrect behavior.<br><br><br>So I am now using code that looks like this:<br>
<br> aFilter->UpdateInformation();<br> vtkStreamingDemandDrivenPipeline::SetUpdateExtent(<br> aFilter->GetOutputInformation(0),<br> pieceIndex, numberOfPieces, ghostLevel);<br><br><br>Another question- is it by design that you must call UpdateInformation() before SetUpdateExtent()? If you fail to do so, the information set by SetUpdateExtent() will be erased. I have found that the actual requirement is that you must call calling aFilter->GetOutputDataObject(0) which forces a call to GetExecutive()->UpdateDataObject() to initialize the output information.<span class="HOEnZb"><font color="#888888"><br>
<br>Pat</font></span><div class="HOEnZb"><div class="h5"><br><br><div class="gmail_quote">On Thu, Apr 12, 2012 at 3:29 PM, Berk Geveci <span dir="ltr"><<a href="mailto:berk.geveci@kitware.com" target="_blank">berk.geveci@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I don't have any objections to expanding this guide to include modularization as long as I am not asked to do it :-)<div><div><br><br><div class="gmail_quote">On Tue, Apr 10, 2012 at 6:45 PM, Pat Marion <span dir="ltr"><<a href="mailto:pat.marion@kitware.com" target="_blank">pat.marion@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">With the recent merge of the new modular build system, I suppose we should expand this guide to cover all the build system changes? For example, libraries have been renamed, python modules renamed, default install directory has changed, the vtkstd namespace and headers are removed... is this wiki page the best place to accumulate these items?<br>
<br>Pat<br><br><br><div class="gmail_quote"><div><div>On Sat, Apr 7, 2012 at 6:41 PM, Andrew Maclean <span dir="ltr"><<a href="mailto:andrew.amaclean@gmail.com" target="_blank">andrew.amaclean@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>
<br>Hi Berk,<div><br><div>On an initial read this looks pretty good.<div><br></div><div>Regards</div><div> Andrew</div><div><div><div><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>---------- Forwarded message ----------<br>From: Berk Geveci <<a href="mailto:berk.geveci@kitware.com" target="_blank">berk.geveci@kitware.com</a>><br>To: VTK Developers <<a href="mailto:vtk-developers@vtk.org" target="_blank">vtk-developers@vtk.org</a>>, VTK Users <<a href="mailto:vtkusers@vtk.org" target="_blank">vtkusers@vtk.org</a>><br>
Cc: <br>Date: Fri, 6 Apr 2012 15:41:44 -0400<br>Subject: [vtk-developers] First pass of VTK 6 migration guide posted<br><a href="http://www.vtk.org/Wiki/VTK/VTK_6_Migration_Guide" target="_blank">http://www.vtk.org/Wiki/VTK/VTK_6_Migration_Guide</a><div>
<br></div><div>Please send comments, fixed, questions etc.</div><div><br></div><div>Best,</div><div>-berk</div>
<div><br></div>
<br><br></blockquote></div></div></div><span><font color="#888888">-- <br>___________________________________________<br>Andrew J. P. Maclean<br><br>___________________________________________<br>
</font></span></div></div></div>
<br></div></div>_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
<br>
<br></blockquote></div><br>
</blockquote></div><br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br></div>