Cory, This is what I needed. It works. Many thanks,
Sonya Davydycheva <http://3demholding.com> (713)498-6139 On Mon, Oct 23, 2017 at 7:47 AM, Cory Quammen <cory.quam...@kitware.com> wrote: > Sonya, > > ParaView 5.2.0 does have a "Rescale" color map feature. It is circled in > red here: > > [image: Inline image 1] > > Best regards, > Cory > > On Mon, Oct 23, 2017 at 8:09 AM, Sonya Davydycheva <sda...@gmail.com> > wrote: > >> Cory, Alan and all ParaView experts, >> >> I keep playing with two versions of Paraview following your kind advice, >> thanks (see below, on Paraview 5.4.1 error message & freeze). >> >> The earlier versions freeze sometimes as well, but I found a way to >> isolate and avoid the bug (I just avoid making full screen or draw the >> screen edges). >> >> The recommended Paraview 4.4.0 I like the most, since it has button >> "Rescale", which I find very useful: when you do threshold to remove >> extreme values from the view, the picture looses contrast, and you can >> rescale the color again. >> >> BUT in Paraview 5.2.0 I do not see "Rescale" button. So, after >> "Threshold" all looks grayish & hard to understand what is what. >> >> I then would stick to Paraview 4.4.0, but it has another drawback or a >> bug: >> when I try to make visible Axas Grid & units, it works with 3D data sets >> and 1D data sets (along one line), but does not work with 2D data sets. >> Namely, it first appears, when I load the file, but after I click Glyph or >> Threshold, the picture emerges, but the Axas Grid & units disapper! With >> 3D/1D data it does not, and you can enjoy seeing your full geometry. But >> not with 2D, and I now mostly work with 2D data. Paraview 5.2.0 has no >> such problem. >> >> SUMMARY: >> Paraview 5.2.0 allows seeing Axas Grid & units, but does not allow >> Rescale color. >> Paraview 4.4.0 does not allow seeing Axas Grid & units with 2D data, but >> allows Rescale. >> >> Is there a way to enjoy both? >> >> Thank you, >> >> Sonya Davydycheva <http://3demholding.com> >> (713)498-6139 >> >> >> On Mon, Oct 9, 2017 at 1:54 PM, Scott, W Alan <wasc...@sandia.gov> wrote: >> >>> Sonya, >>> >>> If nothing else works, use ParaView 4.4.0. That release is a workhorse, >>> and was the version before we updated OpenGL requirements. >>> >>> >>> >>> Alan >>> >>> >>> >>> >>> >>> *From:* ParaView [mailto:paraview-boun...@paraview.org] *On Behalf Of *Sonya >>> Davydycheva >>> *Sent:* Monday, October 9, 2017 9:53 AM >>> *To:* Quammen, Cory (External Contacts) <cory.quam...@kitware.com> >>> *Cc:* ParaView <paraview@paraview.org> >>> *Subject:* [EXTERNAL] Re: [Paraview] Paraview 5.4.1 error message & >>> freeze >>> >>> >>> >>> Hello Cory & Paraview team, >>> >>> >>> >>> I am just giving below a SUMMARY on the errors I encountered while >>> working with ParaView. >>> >>> >>> >>> Version 4.0.1 installed on my old (2013) 64-bit Toshiba laptop under >>> Windows 7: works fine, shows images for model.vtk & glyph for data.vtk; >>> does not freeze. >>> >>> >>> >>> Version 5.4.1 just DOES NOT install on my old (2013) Toshiba laptop. >>> >>> >>> >>> Version 4.0.1 installed on a new (2016) Dell laptop under Windows 7: >>> shows images for model.vtk & glyph for data.vtk, but freezes while >>> attempting to do full screen or just to drug the screen edge in order to >>> increase screen with the following diagnostics: >>> >>> -------------------- >>> >>> Output messages >>> >>> QWidget:: repaint: Recursive repaint detected. >>> >>> --------------------- >>> >>> >>> >>> Version 5.4.1 installed on a 2016 Dell laptop under Windows 7: shows >>> images for model.vtk, BUT glyph for data.vtk STAYS EMPTY, and the >>> application ALSO freezes while attempting to do full screen or just to drug >>> the screen edge in order to increase screen, with no diagnostics. >>> >>> >>> >>> - - - - - - - >>> >>> So, for now I have to continue working with version 4.0.1, and it is >>> fine, so far, for the learning purpose. To prevent freezing, I simply avoid >>> to increase screen / full screen. >>> >>> >>> >>> The version 4.0.1 was my random choice, just the first version I saw >>> available for 64-bit system. >>> >>> Would you recommend for me to try any newer version? >>> >>> >>> >>> Many thanks for your help, >>> >>> >>> >>> Sonya Davydycheva >>> >>> >>> >>> >>> >>> On Wed, Oct 4, 2017 at 7:29 PM, Sonya Davydycheva <sda...@gmail.com> >>> wrote: >>> >>> Cory, >>> >>> >>> >>> The Glyph works just fine with my data.vtk and is very useful tool! It >>> was a good advice. >>> >>> >>> >>> As to not-responding and freezing of ParaView: let me accumulate >>> statistics and then I will let you know. >>> >>> >>> >>> I appreciate your help, >>> >>> >>> Sonya Davydycheva >>> >>> >>> >>> >>> >>> On Wed, Oct 4, 2017 at 6:27 PM, Cory Quammen <cory.quam...@kitware.com> >>> wrote: >>> >>> [cc'ing to the paraview mailing list so others may contribute to and >>> benefit from the discussion] >>> >>> >>> >>> On Tue, Oct 3, 2017 at 3:44 PM, Sonya Davydycheva <sda...@gmail.com> >>> wrote: >>> >>> Thank you Cory, >>> >>> >>> >>> For your prompt response. Good to know that the message is harmless. >>> >>> >>> >>> My Paraview 5.4.1 just stops responding sometimes. >>> >>> >>> >>> If it stops responding consistently after a specific event or sequence >>> of events, please let us know. It shouldn't do that :-) >>> >>> >>> >>> But, well, I installed on another (older) laptop an older version, 4.0.1 >>> (5.4.1 did not work there), and it does not freeze. So far, I think it is >>> ok for my learning purpose. >>> >>> >>> >>> Very good. >>> >>> >>> >>> Both versions (on both computers) allow me to visualize my sample >>> model.vtk file: in RenderView I can do Threshold, Slice and Clip and see >>> some 3D pictures. But something is wrong with my other sample data.vtk file >>> (or, with my approach?). It contains data points (3 coordinates) and the >>> resistivity values assigned to them. When I open it, I can see only the >>> resistivity colorbar, and I can add axes, but the image stays empty. >>> >>> Threshold does not work at all (and even the colorbar disappears when I >>> apply it). >>> >>> Slice somewhat works, but it stays gray/empty and does not change as I >>> move it along the box. >>> >>> And when I am in "Slice" mode, pressing "Apply" removes the colorbar as >>> well, and does not show anything meaningful. >>> >>> >>> >>> Any idea how can I activate Threshold or Slice for my resistivity >>> data.vtk? >>> >>> >>> >>> I am beginner and suspect I just miss something simple... >>> >>> Reading ParaViewGettingStarted-5.4.0.pdf and ParaViewTutorial54.pdf, >>> does not help, so far. >>> >>> >>> >>> I suspect that you do not have any cells in your 3-point data.vtk file. >>> Without cells, there is nothing for ParaView to visualize. This is a common >>> stumbling block for people trying to visualize point data.I suggest after >>> loading your data applying a Glyph filter. It should show you three spheres >>> colored according to your resistivity array. Now you should be able to >>> apply the Threshold and Slice filters as you would expect. >>> >>> >>> >>> Thanks, >>> >>> Cory >>> >>> >>> >>> Many thanks in advance, >>> >>> >>> >>> Best regards, >>> >>> >>> Sonya Davydycheva >>> >>> >>> >>> >>> >>> On Tue, Oct 3, 2017 at 4:12 PM, Cory Quammen <cory.quam...@kitware.com> >>> wrote: >>> >>> On Tue, Oct 3, 2017 at 3:31 PM, Sonya Davydycheva <sda...@gmail.com> >>> wrote: >>> > Hello, >>> > >>> > Does anybody know what this Output message mean? (appears when I press >>> > "Example Visuatizations"... thougth, some examples emerge), >>> > --------- >>> > QWindowsWindow::setGeometry: Unable to set geometry 996x403+228+226 on >>> > QWidgetWindow/'pqExampleVisualizationsDialogWindow'. Resulting >>> geometry: >>> > 996x412+228+226 (frame: 9, 36, 9, 9, custom margin: 0, 0, 0, 0, minimum >>> > size: 956x403, maximum size: 16777215x16777215).QWindowsWin >>> dow::setGeometry: >>> > Unable to set geometry 996x403+228+226 on >>> > QWidgetWindow/'pqExampleVisualizationsDialogWindow'. Resulting >>> geometry: >>> > 996x412+228+226 (frame: 9, 36, 9, 9, custom margin: 0, 0, 0, 0, minimum >>> > size: 956x403, maximum size: 16777215x16777215). >>> > ---------- >>> >>> The message is a warning from the Qt side. Aside from being annoying, >>> it should be harmless. Sorry, but we haven't figured out why this >>> appears on some systems and not others. >>> >>> > Also, my Paraview 5.4.1 (installed under 64-bit Windows 7, ) often >>> freezes. >>> > I wonder if this can be related to the issue above. >>> >>> Does it stop responding or does it crash? It's probably not related to >>> the warning message above. >>> >>> Cory >>> >>> > Thanks, >>> > >>> > Sonya Davydycheva >>> > >>> > >>> > >>> > _______________________________________________ >>> > 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. >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> Cory Quammen >>> Staff R&D Engineer >>> Kitware, Inc. >>> >>> >>> >>> >>> >> >> > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. >
_______________________________________________ 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