Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[ice-dev] Fwd: Re: [Paraview] Mismatched image size returned from ViewPort image render
From my correspondence with the ParaView devs. Of particular importance:

"However, if the remote display is configured to have a maximum size of 640 x 480, then I do not believe there is any way to request a larger image from the client side.  Perhaps someone else knows otherwise though."
Jordan Deyton
Oak Ridge National Laboratory
Telephone: (865) 574-1091
Email: deytonjh@xxxxxxxx


-------- Forwarded Message --------
Subject: Re: [Paraview] Mismatched image size returned from ViewPort image render
Date: Thu, 2 Jul 2015 17:05:32 +0000
From: Deyton, Jordan H. <deytonjh@xxxxxxxx>
To: paraview@xxxxxxxxxxxx <paraview@xxxxxxxxxxxx>


I don't have access to the system right now, but I can try and report back.


Thanks,

Jordan


From: Sebastien Jourdain <sebastien.jourdain@xxxxxxxxxxx>
Sent: Wednesday, July 01, 2015 7:06 PM
To: Scott Wittenburg
Cc: Deyton, Jordan H.; paraview@xxxxxxxxxxxx
Subject: Re: [Paraview] Mismatched image size returned from ViewPort image render
 
Can you change the remote X setting to have a larger resolution?

Seb

On Wed, Jul 1, 2015 at 4:22 PM, Scott Wittenburg <scott.wittenburg@xxxxxxxxxxx> wrote:
The "viewport.image.render" rpc call includes the browser viewport size as a parameter, and the server-side peer window should resize itself so that you get the correct image in your browser.  However, if the remote display is configured to have a maximum size of 640 x 480, then I do not believe there is any way to request a larger image from the client side.  Perhaps someone else knows otherwise though.

Cheers,
Scott



On Wed, Jul 1, 2015 at 4:06 PM, Jordan Deyton <deytonjh@xxxxxxxx> wrote:
Scott, et al,

It appears nothing has changed in the latest nightly build.

However, I have found that the remote X display I'm using is set to a resolution of 640x480. Given that info, it might make sense that ParaView is not rendering anything bigger than 636x420 if it's restricted to the X display's size. Is it possible to get around the size of the remote X display when rendering something offscreen with ParaView?

Jordan
Jordan Deyton
Oak Ridge National Laboratory
Telephone: (865) 574-1091
Email: deytonjh@xxxxxxxx
On 3/4/2015 12:15 PM, Scott Wittenburg wrote:
Hi Jordan,

   I wonder if that is the issue that is addressed in this topic:


   If so, I think this fix may be merged soon, as it has already been approved.  If you built the ParaView release you're running yourself, you could always try to check out the topic and see if it fixes the issue you're seeing.

Cheers,
Scott




On Tue, Mar 3, 2015 at 1:32 PM, Jordan Deyton <deytonjh@xxxxxxxx> wrote:
ParaView gurus,

I am working on a project that uses the JSON RPC protocols provided by ParaViewWeb. I've noticed that the image quality for ViewPorts seems bad regardless of what is specified in the call to viewport.image.render (docs here: http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/api/protocols.ParaViewWebViewPortImageDelivery ).

After decoding the returned image from the Base64 encoding, the JPEG image comes out as 636x420, while the quality is listed as 100 and the original size is 1440x850.

The JSON object passed to viewport.image.render looks like

{"args":[{
    "localtime":1425413914878,
    "view":-1,
    "size":[1440,850],
    "quality":100}]
}

While the returned object from that RPC call looks like

{
    "image": "very long encoded image text here",
    "localTime": 0,
    "stale": false,
    "size": [1440,850],
    "format": "jpeg;base64",
    "global_id": "315",
    "mtime": 3068929,
    "workTime": 1
}

I've used two separate Base64 decoders, and both result in a JPEG image that is 636x420, not the reported 1440x850.

Any idea what could be the problem here? Is this a bug in ParaViewWeb? I'm running the latest stable ParaView release (4.3.1) on RHEL.

Thanks,
Jordan

--
Jordan Deyton
Oak Ridge National Laboratory
Telephone: (865) 574-1091
Email: deytonjh@xxxxxxxx

_______________________________________________
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



_______________________________________________
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



_______________________________________________
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




_______________________________________________
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

Back to the top