[Paraview-developers] State Models, Data Models in ParaViewWeb

[Sebastien Jourdain]

Hi Mike,

Thanks for your questions on ParaViewWeb:

1) The ParaViewWeb diagram expect specific providers and data structure.
But the providers are built in a way that you can have some freedom
regarding the data retrieval implementation. Since those diagram expect
specific format, you can either compute them directly that way on the
server side or it could be your glue code that would be responsible for
doing the data conversion while ensuring a lower bandwidth usage if you
have more compact representation of the same information.
Usually we gather several providers into a single object using the
CompositeClosureHelper.newInstance within the closure. But depending on
your needs you may find other usage easier to manage.

2) Yes they are, but that does not mean you can not rely on ParaView to
build some of those data structures and rely on the WebSocket connection
between the JavaScript client and the ParaView server to feed those
providers.

3) The QueryDataModel infrastructure is a bit different but could be
used/adapted to work with some of the diagram/viewers. The QueryDataModel
is meant to issue GET request based on a specific URL pattern. It is true
that you could put a custom web server which could perform the computation
dynamically based on the request. But so far we've only used it to retrieve
static data of various type (See ArcticViewer:
https://kitware.github.io/arctic-viewer/). But a QueryDataModel could be
used to feed some of the providers.
Regarding tonic.io, we've migrated all the code from tonic.* into
ParaViewWeb to simplify access, usage and documentation.

4) I think the LineChartViewer was intended to be used as a component (a
piece in something bigger) while the ChartViewer use the AbstractViewerMenu
component to make it a first citizen in the ArcticViewer deployment. Also
ChartViewer expect a chartBuilder which will then be used by the
PlotlyRenderer for performing the rendering of the data, while the other
one is performing the rendering internally using the canvas API. So yes,
they are not meant for the same usage. But if you are looking for a library
for making charts you can give a look at https://github.com/Kitware/candela

Hope that answer most of your questions,

Seb

On Mon, Feb 6, 2017 at 7:51 AM, An, Michael K. <
MKAn at securemissionsolutions.com> wrote:

> ​Hello everyone,
>
>
> Some questions over using the ParaViewWeb API, related to state and data
> models:
>
>
> - What is the suggested procedure for loading our own data into
> a paraviewweb viewer/diagram? Specifically, do we have to create our own
> JSON for the state models based on the visualization components that we
> desire, and then load that using the CompositeClosureHelper.newInstance
> method, with the desired providers in the closure? Or are there other
> recommended workflows?
>
>
> - It seems like these state models are distinct from any ParaView format.
> Is that correct?
>
> ​
>
> - What about constructing our own QueryDataModel? Looking at the
> constructor, it seems like you need to have the data fields specified in
> JSON. Do we write these JSON ourselves, like the ones available in
> tonic.io?
>
>
> - Also, it looks like LineChartViewer follows a different pattern than
> other viewers, like ChartViewer, for example. The constructor doesn't take
> in a DataModel, rather just some data in an array. Does that mean that this
> Viewer isn't designed to be used like the others, perhaps just intended to
> be used in conjuction?
>
>
> Thanks much,
>
> Mike
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Search the list archives at: http://markmail.org/search/?q=
> Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170206/a00a3764/attachment.html>