FANDOM


Compilation (with MinGW in the DOS console) Edit

  1. Open a console (Press "Windows-Key + R" and type "cmd" in the popup-Window)
  2. Navigate to the source code folder (Hint: Use Total Commander and Select from the Commands menu "Open command prompt window") C:\Programme\ImageNets\build\libImageNetExternal\MinGW
  3. Compile with this command in the console: make -f libImageNetExternal.mak all
  4. Test: Start the ImageNet Designer and create the block out of your just compiled plugin: Right click on the drawing area of ImageNet Designer and Testing/External/Threshold


Recommended Editors for editing the source code

  1. Notepad++
  2. Eclipse


Change the name of the Author of a Block (10 Minutes) Edit

  1. Navigate to the build folder (C:\Program Files\ImageNets\build\libImageNetExternal\MinGW) and open the file CTestBlock.cpp
  2. Change the text of m_Author to your name.
  3. Compile with the plugin as described before, restart the ImageNet Designer and create the Block again
  4. Take a look at the Block's Infos. Author should show your name now.


Change the title of a Block (5 Minutes) Edit

  1. Navigate to the build folder (C:\Program Files\ImageNets\build\libImageNetExternal\MinGW) and open the file CTestBlock.cpp
  2. Change the text of m_ClassName to TestFunction.
  3. Compile with the plugin as described before, restart the ImageNet Designer and create the Block again
  4. See that the entry in the right click menu changed to TestFunction and the title of the Block also.

Add a new property (20 Minutes) Edit

  1. Add an attribute in the CTestBlock.h - const QString WINDOW_SIZE, next to THRESHOLD_PROP
  2. Initialize the new attribute in CTestBlock.cpp in the initialize list (CTestBlock::CTestBlock() : THRESHOLD_PROP("Threshold"), WINDOW_SIZE("Window_Size")) (be careful not to use a space in the string)
  3. In the Constructor of CTestBlock.cpp add another property: m_Properties.AddChildProperty( WINDOW_SIZE, "3" )
  4. To make the property editable, add a new if-condition in the function editBlock for the new property:
... if condition of other property
}
else if ( property == WINDOW_SIZE )
{
	bool ok;
	value = QInputDialog::getInt(
		0,
		"Edit Integer",
		property,
		value.toInt(),
		0,
		255,
		1,
		&ok
		);
	
	if( ok )
	{
		propertyItem.m_Value = value; //Save the changed data
		block.process( &imageNet );   //Process the block
	}
	
	return true; //The property was handled
}

Now you could use this external property in the process function. You have access to your new property with this call: m_Properties[WINDOW_SIZE].m_Value.toInt(). Instead of toInt, there are also other functions like toString and toDouble, because internally the data is saved in a QVariant.

Add new ports (15 Minutes) Edit

Add as many input and output ports as you want. Choose a fitting ImageType from ImageNets_Wiki#ImageTypes.

  1. addPortIn( COLOR );
  2. addPortOut( COLOR );

You have access to the input ports with this call:

IplImage* pInputImage = getInputIplImage(
    0, //connected input port
    0, //layer (normally only layer 0 is used)
    net );

In the end of the processfunction the result is saved with this call:

//Save the new image
setIplImage( 
    pDstImage,                      //OpenCV IplImage, which should be saved in the port
    0,                              //port number
    0 );                            //layer

//Set the image type of the output as the same as the input image
setImageType( getInputImageType( 0, 0, net ), 0, 0 );

//Copy the input matrices from port 0 to port 0 (layer 0 is always assumed)
setMatrices( getInputMatrices( 0, net ), 0 );

Add help texts (15 Minutes) Edit

Tooltips

Integrated Help Texts

In ImageNets you can write help text directly into the code, which becomes visible if a mouse hovers above a block, its ports or its properties. There are three possibilities to add help texts:

  1. m_ToolTip = "Your general help text about the block"
  2. m_Properties.AddChildProperty( WINDOW_SIZE, "3", "Property Help Text" )
  3. addPortIn( COLOR, "Port Help Text" );

Create a new Block (30 Minutes) Edit

  1. Navigate to the build folder and copy the file CTestBlock.cpp to CExternalBlock.cpp, do the same for the respective .h file
  2. Adjust the .cpp and .h of the new copy to fit the new name. (Replace CTestBlock with CExternalBlock)
  3. Change the m_ClassName in the Constructor to "YourFunctionName"
  4. Add #include "CExternalBlock.h" in the Plugin header (CPluginExternal.h). This is needed because the management class CPluginExternal needs to know all blocks.
  5. Add "blocks.push_back( new CExternalBlock )" in the Constructor of the Plugin (CPluginExternal.cpp)
  6. Adjust the Makefile (libImageNetExternal.mak)
    1. Add to "OBJS= \" "CExternalBlock.o \"
    2. Add a new rule to make the Block (CExternalBlock.o : CExternalBlock.cpp CExternalBlock.h) (copy it from CTestBlock)
    3. Add to "clean:" $(RM) CExternalBlock.o

Create a new Plugin (45 Minutes) Edit

  1. Copy the whole folder libImageNetExternal in build and rename it to libImageNetSecondExample
  2. call make -f libImageNetExternal.mak clean to clean up all temporary files in libImageNetSecondExample
  3. Rename CPluginExternal.cpp and .h to CPluginSecondExample.cpp and .h. Replace this also in their contents.
  4. Remove CExternalBlock.cpp and .h from the last example
  5. Rename CTestBlock.cpp and .h to CSecondBlock.cpp and .h. Replace this also in their contents.
  6. Rename the Makefile libImageNetExternal.mak to libImageNetSecondExample.mak and change its contents to fit the previously renamed files.
  7. Change CPluginSecondExample.cpp: Q_EXPORT_PLUGIN2(libImageNetSecondExample, ImageNets::CPluginSecondExample);
  8. Change m_CategoryPath in CSecondBlock.cpp to "Testing/SecondExample" and m_ClassName = "Second" (Otherwise there will be two blocks in the same category and the second loaded block will be ignored)

Compilation with Rhapsody Edit

Adding a new plugin Edit

You need a new component in MachineVision/Components and a new package in MachineVision.rpy/GUI/ImageNets/Plugins. The easiest way is to copy an existing component and an existing plugin. Adjust the scope of the component so that only the parts of the new plugin are to be compiled if you select your new component as the active component.

In a plugin you can add as many blocks as you want.

Adding an edit dialog Edit

For simple things use QInputDialog.

  1. Integer
  2. Double
  3. String
  4. StringList (can also be used for Boolean)

If you have to edit more complex datatypes you will have to do changes in the component at these locations:

  1. Adjust the scope to add the dialog you want to use (e.g. ImageNets/PropertyEditors/CEditMatrixDialog)
  2. Add to files moc_CEditMatrixDialog (set stereotype: Moc-File, select implementation (so that is becomes *.cpp))
  3. Adjust Properties - CPP_CG/Linux/PreDependencies: ../../../resources/ImageNets/ui_EditMatrixDialog.h

This approach encapsulates the edit dialog into the plugin. This should have the advantage (later) that you can add complex dialogs without having to compile all plugins and the designer.

The Structure of Blocks Edit

ExternalStructure

Structure of a Plugin

Block

The base Block can have input and output ports. Only the output ports can have its CImage filled, which is a vector of CLayer. A CLayer has an IplImage, a vector of Matrices, a CvSequence and a vector of CINBody.


Constructor Edit

Specifiy the following

  1. m_ClassName = "Name of your block"
  2. m_CategoryPath = "Fitting Category"
  3. m_Author = Your svn account in capital letters. This is an enum specified in the root of the ImageNet package.
  4. m_ToolTip = "Explanation of what your block should do"
  5. InitSettings(); Necessary call of an inherited class to initiate the settings (also called properties)
  6. m_Settings.AddChildProperty( "Property" , "Value" ); Add as many properties as you want always as two strings. The second one can also be numbers inside a string
  7. addPortIn( COLOR, "ToolTip text about this port" ); Setup the imageType of this port and explain the port in the ToolTip. The text will be visible when the mouse hovers above the port.
  8. addPortOut( COLOR, "ToolTip text about this port" ); The same works for outgoing ports. Every time this function is called, the block will get a new outgoing port.


Destructor Edit

Due to a bug in Rhapsody you might get a compile error.

To fix the compile error select the Destructor of the problematic class and change the property from CPP_CG::Operation::Kind = "abstract" to "common".

editBlock Edit

QString property = QString( propertyItem.m_Property );
QVariant value = propertyItem.m_Value;

if( property ==  REF_COORD_SYSTEM )
{
	bool ok;     

	QStringList StringList;
	StringList << WORLD_COORD;
	StringList << CAMERA_COORD;
	
	value = QInputDialog::getItem(
		0,
		"QInputDialog::getItem()",
		property,
		StringList,
		StringList.lastIndexOf( value.toString() ),
		false,
		&ok
		);
	
	if( ok && !value.toString().isEmpty() )
	{
		propertyItem.m_Value = value;
		
		block.process( &imageNet );
	}
	return true;
}

return false;

Instead of getItem, you can also use

  1. QInputDialog::getInt
  2. QInputDialog::getDouble
  3. QInputDialog::getString

getCopy Edit

return new CYourClass( *this ); 
This is necessary due to the "Prototype Programming Paradigm" used in ImageNets.

process Edit

1. Check all inputs

With these numbers you do not have to write text for debugging. For example: log( "", -1 ).

  • -1: input image is missing
  • -2: preconditions are not fulfilled
IplImage* pInputImage = getInputIplImage( 0, 0, net );
if( pInputImage == 0 )
{
	log( "", -1 );
	return;
}

2. Initialize outputs

IplImage* pResultImage = cvCloneImage( pInputImage );

3. Do the processing (you can use the properties here)

cvSmooth(
	pInputImage,
	pResultImage,
	CV_GAUSSIAN,
	0,
	0,
	m_Settings[SIGMA].m_Value.toDouble()
);

4. Save the outputs

setImage( pResultImage, COLOR, 0, 0 );

5. Clean up temporary images and matrices (but do not clean up images or matrices which you saved before)

//cvReleaseImage( &pTempImage ); //This makes sense only if you have created temporary images.
//cvReleaseMat( &pFrameInverted ); //This makes sense only if you have created temporary matrices.

Useful functions Edit

Important Member Variables of CLayer Edit


All of the following functions do not copy or allocate any data.

From every block you can call the following functions (CBlock calls CPort, which calls CLayer):

Images Edit

getInputIplImage( inputPort, layer, imageNet ) returns a pointer to the image of the connected block

setIplImage( IplImage*, outputPort, layer ) saves an image and deletes the old one

Matrices Edit

getInputMat( inputPort, layer, matrix, imageNet ) returns a pointer to a matrix from a left connected block

addMat( CvMat*, outputPort, layer ) adds a matrix pointer (you have to allocate the memory yourself)

getMat( outputPort, layer, matrix ) returns a pointer to an own matrix

clearMatrices( outputPort, layer ) deletes all matrices of a CLayer

ImageTypes Edit

setImageType( imageType, outputPort, layer )


Noise Edit

Generally, you can call a noise function, which can return gaussian noise.

INCALC::noise( double sigma );

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.