CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > Visualization & Post-Processing Software > ParaView

[OpenFOAM] Is This A bug for Paraview 4.1.0 64bit

Register Blogs Members List Search Today's Posts Mark Forums Read

Like Tree5Likes
  • 1 Post By yym2014
  • 2 Post By wyldckat
  • 1 Post By gravis
  • 1 Post By wascott

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   September 4, 2014, 13:32
Default Is This A bug for Paraview 4.1.0 64bit
  #1
New Member
 
Yuanming Yu
Join Date: Sep 2014
Location: Windsor, Ontario
Posts: 7
Rep Power: 7
yym2014 is on a distinguished road
Hello,

When I practiced vector plot in the OpenFoam lid-driven tutorial, I found there is no colored by velocity in display panel, only have colored by p, Glyphvector, cellNormals and Solid color. my paraview version is 4.4.0 64bit, is there something I have missed or it is a bug in Paraview? Is there anyone having the same problem? Thanks.
Gallienus likes this.
yym2014 is offline   Reply With Quote

Old   September 5, 2014, 09:24
Default
  #2
Member
 
Laurent Fitschy
Join Date: May 2011
Posts: 40
Rep Power: 11
GDTech is on a distinguished road
Hi,

Glyphvector contains the data used to draw the glyph. So, if you made your glyph from velocity vector, glyphvector is velocity vector.

Regards,
Laurent.
GDTech is offline   Reply With Quote

Old   September 5, 2014, 11:40
Default About color by velocity
  #3
New Member
 
Yuanming Yu
Join Date: Sep 2014
Location: Windsor, Ontario
Posts: 7
Rep Power: 7
yym2014 is on a distinguished road
Hello, GDTech,

Thank you for the reply. I think the GlyphVector is same as velocity U in this case.
yym2014 is offline   Reply With Quote

Old   December 26, 2018, 03:20
Default Similar problem in ParaView 5.6.0
  #4
Member
 
Reine Granström
Join Date: Apr 2009
Location: Sweden
Posts: 43
Rep Power: 13
gravis is on a distinguished road
Hi,

I have a similar problem in ParaView 5.6.0. For a Glyph, I have not figured out how to color the vectors by velocity magnitude.

I first create a Slice that I can color either by velocity or pressure. When I create a Glyph based on this Slice, the available Coloring options for the Glyph are:
  • Solid Color
  • p
  • vtkCompositeIndex
  • CasePath
  • ctkBlockColors (partial)

Can someone please point out what I am missing here?

BR,
Reine
gravis is offline   Reply With Quote

Old   December 27, 2018, 11:04
Default
  #5
Super Moderator
 
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,956
Blog Entries: 43
Rep Power: 122
wyldckat is a name known to allwyldckat is a name known to allwyldckat is a name known to allwyldckat is a name known to allwyldckat is a name known to allwyldckat is a name known to all
Quote:
Originally Posted by gravis View Post
Can someone please point out what I am missing here?
Quick answer: I don't have ParaView 5.6 at hand yet, but my guess is that you haven't checked all of the existing Glyph settings that exist.
In version 5.4 there are options on which scale field to use and if the data is mapped or not...

Here is an example of how to select the U cell data field for the glyphs:


Notice under "Active Attributes" the "Vectors" selection of the correct field.
Attached Images
File Type: png glyph_54.png (38.6 KB, 82 views)
__________________
wyldckat is offline   Reply With Quote

Old   December 27, 2018, 11:58
Default Details on the settings in 5.6
  #6
Member
 
Reine Granström
Join Date: Apr 2009
Location: Sweden
Posts: 43
Rep Power: 13
gravis is on a distinguished road
Quote:
Originally Posted by wyldckat View Post
Quick answer: I don't have ParaView 5.6 at hand yet, but my guess is that you haven't checked all of the existing Glyph settings that exist.
In version 5.4 there are options on which scale field to use and if the data is mapped or not...

Here is an example of how to select the U cell data field for the glyphs:


Notice under "Active Attributes" the "Vectors" selection of the correct field.
Thanks for the reply. The settings in 5.6 look a bit different, I will attach a series of screenshots that show all settings for the Glyph.

As in your example, I set "Glyph Type" to "Arrow". For "Orientation Array" I select the U cell (or point) data field. The vector arrows shown are as expected. If I change the "Scale Array" to "U", "p" or "No scale array", the arrows are scaled as expected.

But for "Coloring", only the "p" point data field is available (as well as "Solid Color", "vtkCompositeIndex", "CasePath" and "ctkBlockColors (partial)" as I wrote in my previous post). I can not see any other obvious settings that would affect what data fields are available under "Coloring".

I should also mention that I am running ParaView on MacOS Mojave.

BR,
Reine
Attached Images
File Type: png Glyph01.png (58.7 KB, 13 views)
File Type: png Glyph02.png (41.1 KB, 10 views)
File Type: png Glyph03.png (35.0 KB, 9 views)
File Type: png Glyph04.png (22.5 KB, 9 views)
gravis is offline   Reply With Quote

Old   December 27, 2018, 14:33
Default
  #7
Super Moderator
 
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,956
Blog Entries: 43
Rep Power: 122
wyldckat is a name known to allwyldckat is a name known to allwyldckat is a name known to allwyldckat is a name known to allwyldckat is a name known to allwyldckat is a name known to all
Quick answer: Wow... I was not expecting this... I've gotten ParaView 5.6.0 from paraview.org and indeed the vector fields are missing... they were simply filtered out, as well as the "glyphVector" entry that used to be there for Glyphs...

The workaround is to use a Calculator filter in the middle, that calculates the "mag(U)" field as point data:



Then since it's then a point data scalar field, the field "Result" as shown above will appear in the "Coloring" options for the Glyph.

If you forget to add the calculator after you've already added the Glyph entry, you can still add the calculator to the slice or any other entry, then right-click on the Glyph entry and choose to "Change Input..."


Given that this is either a potential bug or a feature, you may want to ask about this at the Development sub-forum at ParaView's Discourse server: https://discourse.paraview.org/c/development - because I don't know if this is a ParaView bug/feature or if VTK (the main library ParaView depends on) is to blame here...
Attached Images
File Type: png use_calculator.png (34.5 KB, 81 views)
Gallienus and YCarv like this.
wyldckat is offline   Reply With Quote

Old   December 27, 2018, 15:02
Default
  #8
Member
 
Reine Granström
Join Date: Apr 2009
Location: Sweden
Posts: 43
Rep Power: 13
gravis is on a distinguished road
Quote:
Originally Posted by wyldckat View Post
The workaround is to use a Calculator filter in the middle, that calculates the "mag(U)" field as point data:
Nice, big thanks for suggesting this workaround. And thanks for taking the time to check this in 5.6.


Quote:
Given that this is either a potential bug or a feature, you may want to ask about this at the Development sub-forum at ParaView's Discourse server: https://discourse.paraview.org/c/development - because I don't know if this is a ParaView bug/feature or if VTK (the main library ParaView depends on) is to blame here...
I will post a question there.
JR22 likes this.
gravis is offline   Reply With Quote

Old   March 29, 2020, 19:53
Default
  #9
Senior Member
 
JR22's Avatar
 
Jose Rey
Join Date: Oct 2012
Posts: 134
Rep Power: 13
JR22 will become famous soon enough
I am using Paraview 5.8 now and have encountered the issue. Any resolution from them ? The calculate filter is a good patch solution in the meantime.
JR22 is offline   Reply With Quote

Old   April 17, 2020, 16:36
Question Paraview 5.6.0 64-bit won't display Velocity Vectors
  #10
New Member
 
John
Join Date: Nov 2013
Location: USA, Florida
Posts: 10
Rep Power: 8
Gallienus is on a distinguished road
I suppose I should call them Glyphs now. Anyhow, running XUbuntu 18.04, 64bit (a LTS) with ParaView 5.6.0. Actually it's ParaFoam but I think the app is pretty much the same thing.

I encountered the error in that Velocity Vectors cannot be colored with Velocity: only with Pressure, [also vtk Composite Index, CasePath, vtk BlockColors, and of course Solid Color]. I can display countours of Velocity so I guess this means the data set is loaded.

Wyldkat provides a workaround to use a Calulator filter in the middle. I've tried this and the Calculator Results still are not displayable. I'll attach a screenshot:



For the Calculator I tried using the U as a Result accoring to the Scalers:
Attrib. type: point data
Result: sqrt(U_X^2+U_Y^2+U_Z^2)

since I really have a 2-D model I also tried
Result: sqrt(U_X^2+U_Y^2)

Neither worked. I also downloaded the ParaView 5.8 but I notice that a user here states that it has the exact same problem so I haven't fooled with it yet.
Gallienus is offline   Reply With Quote

Old   May 5, 2020, 21:13
Default Vectors are missing in ParaView - by design
  #11
New Member
 
Alan
Join Date: May 2020
Posts: 1
Rep Power: 0
wascott is on a distinguished road
Interesting thread. A bit of background, then what is happening, then how to solve it.

ParaView has a design philosopy that we will attempt to never do something hidden or under the covers. There are three examples I found in this case. We won't magically convert cells to points, or points to cells. (Not sure what OpenFOAM calls these - Cells are Elements, Points are Nodes.) Another example is we will never create vector magnitudes from vectors. You have to do this manually, or tell ParaView to override default behavior.

I believe that the root cause of the issue is that ParaView wants a point for Glyphs. Further, I believe it isn't passing cells through the Glyph filter, glyphs which are placed at points, not cells. In the cases where you do have the correct data, i.e., point vectors, ParaView doesn't have magnitudes.

Note that one case where ParaView will make the conversion from vectors to magnitudes is when you want to color by a variable.

How do we work around these issues? Let me give you the manual methods, then the shortcut (that hides what is going on.). If you have cells and need points (such as contour filter), run the Cell Data to Point Data filter. Point Data to Cell Data works in reverse. Note that default won't pass through the variables coming into this filter, but there is an option to do so. If you need magnitudes, run the Calculator filter, and mag(vector_name). That is 90% of the cases, you get the idea. Alternatively, there's a setting to turn on automatic conversions. It is Edit/ Settings/ AutoConvert Properties.

Note that the tutorials are online, and much of this is covered. In Paraview, go Help/ Sandia National Labs Tutorials.

I tried voodooing up an example, but couldn't get PV to fail. Anyway, I hope that adds some clarity.
Gallienus likes this.
wascott is offline   Reply With Quote

Old   May 5, 2020, 21:35
Default
  #12
New Member
 
John
Join Date: Nov 2013
Location: USA, Florida
Posts: 10
Rep Power: 8
Gallienus is on a distinguished road
Quote:
Originally Posted by wascott View Post
Interesting thread. A bit of background, then what is happening, then how to solve it.
.
Actually this thread was continued on the Paraview support forum and one of the developers kept making helpful comments and eventually I got it to work, -or at least appear to work!

There are continuing comments by more knowledgeable users following mine and there may be some sort of bug. Here is the link (my name there is Julius Nepos as I tired of Gallienus):

https://discourse.paraview.org/t/vel...?u=juliusnepos
Gallienus is offline   Reply With Quote

Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
mapFields major bug alchem OpenFOAM Bugs 11 November 28, 2019 05:24
Bug in Workbench CFX Pierre1 CFX 6 August 2, 2017 00:18
[Helyx OS] Installing HelyxOS on 32 and 64bit Linux Distributions wyldckat OpenFOAM Community Contributions 16 December 23, 2016 06:37
Linux+CFD: is 64bit really a need? CAVT Hardware 2 August 27, 2010 17:12
Dissimilarity in compiling new BC in 32bit OpenSuSE 103 versus 64bit CentOS 50 versus 64bit SLED 100 sponiar OpenFOAM Running, Solving & CFD 3 February 26, 2008 06:31


All times are GMT -4. The time now is 20:14.