#include <itkPathSource.h>
Inheritance diagram for itk::PathSource< TOutputPath >:
Public Types | |
| typedef PathSource | Self |
| typedef ProcessObject | Superclass |
| typedef SmartPointer< Self > | Pointer |
| typedef SmartPointer< const Self > | ConstPointer |
| typedef DataObject::Pointer | DataObjectPointer |
| typedef TOutputPath | OutputPathType |
| typedef OutputPathType::Pointer | OutputPathPointer |
| typedef OutputPathType::InputType | OutputPathInputType |
| typedef OutputPathType::OutputType | OutputPathOutputType |
| typedef OutputPathType::IndexType | OutputPathIndexType |
| typedef OutputPathType::OffsetType | OutputPathOffsetType |
Public Member Functions | |
| virtual const char * | GetClassName () const |
| virtual void | GraftNthOutput (unsigned int idx, OutputPathType *output) |
| virtual DataObjectPointer | MakeOutput (unsigned int idx) |
| OutputPathType * | GetOutput (void) |
| OutputPathType * | GetOutput (unsigned int idx) |
| virtual void | GraftOutput (OutputPathType *output) |
Static Public Member Functions | |
| Pointer | New () |
Protected Member Functions | |
| PathSource () | |
| virtual | ~PathSource () |
| void | PrintSelf (std::ostream &os, Indent indent) const |
PathSource is the base class for all process objects that output path data. Specifically, this class defines the GetOutput() method that returns a pointer to the output path. The class also defines some internal private data members that are used to manage streaming of data.
Definition at line 41 of file itkPathSource.h.
|
|||||
|
|||||
|
Smart Pointer type to a DataObject. Reimplemented from itk::ProcessObject. Definition at line 51 of file itkPathSource.h. |
|
|||||
|
|||||
|
|||||
|
|||||
|
|||||
|
|||||
|
|||||
|
|||||
|
|||||
|
|||||||||
|
|
|
|||||||||
|
Definition at line 174 of file itkPathSource.h. |
|
|||||||||
|
||||||||||
|
Get the output data of this process object. The output of this function is not valid until an appropriate Update() method has been called, either explicitly or implicitly. Both the filter itself and the data object have Update() methods, and both methods update the data. Here are three ways to use GetOutput() and make sure the data is valid. In these examples, image is a pointer to some Image object, and the particular ProcessObjects involved are filters. The same examples apply to non-image (e.g. Mesh) data as well.
anotherFilter->SetInput( someFilter->GetOutput() ); anotherFilter->Update(); In this situation, someFilter and anotherFilter are said to constitute a pipeline.
image = someFilter->GetOutput(); image->Update();
someFilter->Update(); image = someFilter->GetOutput(); Note that Update() is not called automatically except within a pipeline as in the first example. When streaming (using a StreamingImageFilter) is activated, it may be more efficient to use a pipeline than to call Update() once for each filter in turn. For an image, the data generated is for the requested Region, which can be set using ImageBase::SetRequestedRegion(). By default, the largest possible region is requested. Reimplemented from itk::ProcessObject.
|
|
||||||||||
|
Get the output data of this process object. The output of this function is not valid until an appropriate Update() method has been called, either explicitly or implicitly. Both the filter itself and the data object have Update() methods, and both methods update the data. Here are three ways to use GetOutput() and make sure the data is valid. In these examples, image is a pointer to some Image object, and the particular ProcessObjects involved are filters. The same examples apply to non-image (e.g. Mesh) data as well.
anotherFilter->SetInput( someFilter->GetOutput() ); anotherFilter->Update(); In this situation, someFilter and anotherFilter are said to constitute a pipeline.
image = someFilter->GetOutput(); image->Update();
someFilter->Update(); image = someFilter->GetOutput(); Note that Update() is not called automatically except within a pipeline as in the first example. When streaming (using a StreamingImageFilter) is activated, it may be more efficient to use a pipeline than to call Update() once for each filter in turn. For an image, the data generated is for the requested Region, which can be set using ImageBase::SetRequestedRegion(). By default, the largest possible region is requested. |
|
||||||||||||||||
|
Graft the specified data object onto this ProcessObject's idx'th output. This is the similar to GraftOutput method except is allows you specify which output is affected. The specified index must be a valid output number (less than ProcessObject::GetNumberOfOutputs()). See the GraftOutput for general usage information. |
|
||||||||||
|
Graft the specified DataObject onto this ProcessObject's output. This method grabs a handle to the specified DataObject's path data to use as its output's own path data. It also copies the region ivars (RequestedRegion, BufferedRegion, LargestPossibleRegion) and meta-data (Spacing, Origin) from the specified data object into this filter's output data object. Most importantly, however, it leaves the Source ivar untouched so the original pipeline routing is intact. This method is used when a process object is implemented using a mini-pipeline which is defined in its GenerateData() method. The usage is:
// setup the mini-pipeline to process the input to this filter firstFilterInMiniPipeline->SetInput( this->GetInput() ); // setup the mini-pipeline to calculate the correct regions // and write to the appropriate bulk data block lastFilterInMiniPipeline->GraftOutput( this->GetOutput() ); // execute the mini-pipeline lastFilterInMiniPipeline->Update(); // graft the mini-pipeline output back onto this filter's output. // this is needed to get the appropriate regions passed back. this->GraftOutput( lastFilterInMiniPipeline->GetOutput() ); For proper pipeline execution, a filter using a mini-pipeline must implement the GeneratseInputRequestedRegion(), GenerateOutputRequestedRegion(), GenerateOutputInformation() and EnlargeOutputRequestedRegion() methods as necessary to reflect how the mini-pipeline will execute (in other words, the outer filter's pipeline mechanism must be consistent with what the mini-pipeline will do). |
|
||||||||||
|
Make a DataObject of the correct type to used as the specified output. Every ProcessObject subclass must be able to create a DataObject that can be used as a specified output. This method is automatically called when DataObject::DisconnectPipeline() is called. DataObject::DisconnectPipeline, disconnects a data object from being an output of its current source. When the data object is disconnected, the ProcessObject needs to construct a replacement output data object so that the ProcessObject is in a valid state. So DataObject::DisconnectPipeline eventually calls ProcessObject::MakeOutput. Note that MakeOutput always returns a SmartPointer to a DataObject. If a subclass of ImageSource has multiple outputs of different types, then that class must provide an implementation of MakeOutput(). Reimplemented from itk::ProcessObject.
|
|
|||||||||
|
||||||||||||||||
1.3.8 written by Dimitri van Heesch,
© 1997-2000