[Paraview] [EXTERNAL] Re: [Paraview-developers] Scripting image compression parameters

Faiz Abidi fabidi89 at vt.edu
Sat Feb 11 18:40:33 EST 2017


I see your point, and that's what I figured too. The trace is not meant to
track those settings.

Not sure what path I'll take from here, either try to somehow custom script
the image compression parameters or do it manually (a big pain!).

Thanks for your help though.

On Sat, Feb 11, 2017 at 5:56 PM, Cory Quammen <cory.quammen at kitware.com>
wrote:

> Faiz,
>
> The Python trace is not expected to record application-level settings.
> For some settings, it could possibly be reasonable to record them in a
> trace and play them back, but other settings it doesn't make much
> sense because they require an application restart, for example, or
> only affect aspects of the user interface.
>
> Best,
> Cory
>
>
> On Tue, Feb 7, 2017 at 4:57 PM, Faiz Abidi <fabidi89 at vt.edu> wrote:
> > You mean create a bug ticket?
> >
> > Let me try to clarify a bit more on what I am doing. I am using my Ubuntu
> > machine for this.
> >
> > 1. I start the trace just like normal from "Tools -> Start Trace". I
> choose
> > all properties to track.
> > 2. I go to "Edit -> Settings -> Render View" and select settings from the
> > "Remote/Parallel Rendering Options."
> > 3. I stop trace, but nothing actually gets traced.
> >
> > Does this make sense? I am not sure if this is a bug, or the trace
> > functionality was never meant to trace the settings but only the
> properties
> > of the scene.
> >
> > If you or anyone has any more insights to this, please do share. I won't
> > mind writing my own scripts to do this if it is even possible.
> >
> > On Mon, Feb 6, 2017 at 9:14 PM, Scott, W Alan <wascott at sandia.gov>
> wrote:
> >>
> >> Sounds like a bug.  Mind writing it up?  If you want, if you give me
> step
> >> by step details on what is failing, I can also write it up for you.
> >>
> >>
> >>
> >> Alan
> >>
> >>
> >>
> >> From: Faiz Abidi [mailto:fabidi89 at vt.edu]
> >> Sent: Friday, February 3, 2017 10:13 AM
> >> To: Scott, W Alan <wascott at sandia.gov>
> >> Cc: paraview-developers at paraview.org; paraview at paraview.org
> >> Subject: Re: [EXTERNAL] Re: [Paraview-developers] Scripting image
> >> compression parameters
> >>
> >>
> >>
> >> Hi Alan,
> >>
> >>
> >>
> >> Sorry for a delayed response, but I missed this email somehow.
> >>
> >>
> >>
> >> So, I actually have tried the trace function ParaView supports, but
> >> unfortunately, it doesn't trace the settings I set for the image
> compression
> >> settings.
> >>
> >>
> >>
> >> I guess I'll have to do it manually then, but I would be interested to
> >> know if anyone else has tried to script the compression parameters. I am
> >> kind of surprised if this is not possible to script.
> >>
> >>
> >>
> >> Best,
> >>
> >>
> >>
> >> On Mon, Jan 30, 2017 at 4:55 PM, Scott, W Alan <wascott at sandia.gov>
> wrote:
> >>
> >> My best guess would be to try to trace the save screenshot
> functionality,
> >> and see what is set.  Sorry, that’s the best I have...
> >>
> >>
> >>
> >> Alan
> >>
> >>
> >>
> >> From: Paraview-developers
> >> [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Faiz
> Abidi
> >> Sent: Monday, January 30, 2017 2:14 PM
> >> To: paraview-developers at paraview.org; paraview at paraview.org
> >> Subject: [EXTERNAL] Re: [Paraview-developers] Scripting image
> compression
> >> parameters
> >>
> >>
> >>
> >> Not having heard back from anyone, I am guessing no one has done this
> kind
> >> of scripting before? Anyone?
> >>
> >>
> >>
> >> On Wed, Jan 25, 2017 at 9:43 AM, Faiz Abidi <fabidi89 at vt.edu> wrote:
> >>
> >> Hello ParaView community,
> >>
> >>
> >>
> >> ParaView provides various image compression configuration options. I was
> >> wondering how to go about scripting this so that I can test setting
> various
> >> parameters in a script.
> >>
> >>
> >>
> >> I did check some of ParaView modules but couldn't find anything helpful.
> >>
> >>
> >>
> >> Any pointers from anyone would be helpful.
> >>
> >>
> >>
> >> Best,
> >> --
> >>
> >> Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com |
> >> +1-540-998-6636
> >>
> >>
> >>
> >>
> >>
> >> --
> >>
> >> Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com |
> >> +1-540-998-6636
> >>
> >>
> >>
> >>
> >>
> >> --
> >>
> >> Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com |
> >> +1-540-998-6636
> >
> >
> >
> >
> > --
> > Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com |
> > +1-540-998-6636
> >
> > _______________________________________________
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the ParaView Wiki at:
> > http://paraview.org/Wiki/ParaView
> >
> > Search the list archives at: http://markmail.org/search/?q=ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview
> >
>
>
>
> --
> Cory Quammen
> Staff R&D Engineer
> Kitware, Inc.
>



-- 
Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com |
+1-540-998-6636
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170211/54f08f27/attachment.html>


More information about the ParaView mailing list