Hi Pablo,
Pablo Carneiro Elias wrote:
> Dirk, thank you for the reply,
>
> You´re not late. Actually, you´re just on time...
> As I´ve said we were at an analysis point of the project and so we were
> yet gathering some basic informations about OpenSG... I made a technical
> report about OpenSG (I´ve found many info in your Phd thesis, about
> basic things of OpenSG).
>
> But now, we´re thinking about how we´re going to deal with some basic
> problems, like VTK+OpenSG integration.. I think the way to solve this is
> pretty much as you´ve said, making a new OpenSG node that uses VTK for
> rendering.
>
> I´ve checked out OpenSG version 2.0 and I´ve found out that there is an
> OpenSG to VTK integration natively available in this version (as a
> contribution to OpenSG). I´ve compiled a demo of it but I don´t know if
> that is ready to work on a cluster yet. Because the strategy adopted by
> this, say, "vtk+opensg extension feature", is, as far as I know, to
> somehow translate a vtk actor to a OpenSG field container. But I think
> it doesn´t translate data from vtk to opensg (doesn´t stores vtk data on
> OpenSG node) , it only stores physical pointers to vtkActor at a
> fieldContainer so when OpenSG needs to render something, the data is
> taken from the pointers...
Yup, that version is not what I was thinking of.
> But I don´t know if this strategy will work on a Cluster (physical
> pointers distributable without special care). Plus, Its a different
> strategy than the one you ´ve suggested. Let´s see if I really
> understand what you´ve suggested:
>
> - The idea is to created a special kind of FieldContainer that some how
> stores vtk input data (using fieldContainer Editor?).
Yes and yes.
> - These special fieldContainers nodes can easily be distributed over
> the network using the native OpenSG clustering feature.
Yes.
> - When the node arrives at server and it is sent for rendering, the VTK
> input data is taken and sent to vtk engine, which will take care of
> rendering everything....
Yes.
> Is that right? If not, how should this Special OpenSG be?
The interesting problem is how to wrap VTK data in an OpenSG field container. I
don't know anything about how VTK stores data, but I would hope that there is a
way in VTK to serialize the necessary data into a simple stream of bytes that
can be stored in an MFUInt8, which would then need to be deserialized (once) on
the cluster nodes and used by the Actor.
Alternatively you could write a new FieldType that knows how to handle VTK data
and do the serialization/deserialization on the fly as data is transmitted to
the cluster.
Yours
Dirk
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
