[Rd] using Paraview "in-situ" with R?

[Mike Marchywka]

I'm posting here instead of R-package since your response
was the most relevant :) I started using the "in-situ" workflow
and its very nice.  Thew viewer stays up between runs and across
data sources and its the same UI regardless of source :) 
fwiw. 

I started digging through some noisy data, dog diet data
in which the supplements were pulsed ( in essence PWM lol).
This made it hard to find the right average doses to correlate
with outcomes. I had to play with trailing average filtering but
ultimately some trends emerged that made sense with
subjective observations ( maybe they are not real but that is
not the point of this post ).

I did not use R or Visit but  I used my own code 
for filtering and MJMDatascope for viewing and expect
to do more sophisticated stuff in R soon. I can tell you
though that eliminating the annoyance and confusion of
temp files was very helpful. The workflow, and mind flow,
for the "in situ" mode makes you wonder how you ever did without
it. I will probably need to update my R interface package and
MJMDatascope is hardly ideal but improving both seems
worth the effort.

Thanks.


 Mike Marchywka 
44 Crosscreek Trail
Jasper GA 30143
was 306 Charles Cox Drive  Canton, GA 30115
470-758-0799
404-788-1216 




________________________________________
From: George Ostrouchov <georgeost using gmail.com>
Sent: Wednesday, January 10, 2024 3:06 PM
To: r-devel using r-project.org
Cc: Mike Marchywka
Subject: Re:  [Rd] using Paraview "in-situ" with R?

At ORNL, we worked with VisIt (a sibling of Paraview, both funded largely by DOE) around 2016 and made an in situ demo with R. We used packages pbdMPI (on CRAN) and pbdDMAT (on GitHub/RbigData), which were in part built for this purpose. Later also the package hola (on GitHub/RbigData) was built to connect with adios2, which can do buffered in situ connections with various codes.

But the VisIt developers were not interested in R (preferring to roll their own), so that direction fizzled. Paraview is a competetive sibling of VisIt, so I don’t know if they would be interested. The packages we developed are viable for that purpose. There is a lot in R that could benefit Paraview (or VisIt).

George

>
> Message: 1
> Date: Tue, 9 Jan 2024 14:20:17 +0000
> From: Mike Marchywka <marchywka using hotmail.com>
> To: R-devel <r-devel using r-project.org>
> Subject: [Rd] using Paraview "in-situ" with R?
> Message-ID:
>       <BL3PR11MB6338D814D9A3FF932D7E7F49BE6A2 using BL3PR11MB6338.namprd11.prod.outlook.com>
>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I had previously asked about R interfaces to various "other" visualization
> tools specifically lightweights for monitoring progress of
> various codes. I was working on this,
>
> https://github.com/mmarchywka/mjmdatascope
>
> but in the meantime found out that Paraview has an "in-situ"
> capability for similar objectives.
>
> https://discourse.paraview.org/t/does-or-can-paraview-support-streaming-input/13637/9
>
> While R does have a lot of plotting features,
> it seems like an excellent tool to interface to R allowing visualization without
> a bunch of temp files or
>
> Is anyone aware of anyone doing this interface or reasons its  a boondoggle?
>
> Thanks.
>
>
>
>  Mike Marchywka
> 44 Crosscreek Trail
> Jasper GA 30143
> was 306 Charles Cox Drive  Canton, GA 30115
> 470-758-0799
> 404-788-1216
>