Great! Thanks for testing, Andrew. Looks like we're pretty set for the
final 5.0.1 release. I'll tag it by the end of this week.
Utkarsh
On Mon, Mar 21, 2016 at 2:36 AM, Andrew wrote:
> ParaView 5.0.1 RC2 for Win-64 has been tested with my big EnSight case. I
> loaded case
ParaView 5.0.1 RC2 for Win-64 has been tested with my big EnSight case. I
loaded case successfully and created slice and vectors (glyphs) on it, no
any issues occured. Great thanks for debugging!
Meanwhile, I noticed that the color bar behavior is not as good as it was
in version 4.3. The color
*Utkarsh,*
Thanks for notification. I will try this version as soon as possible.
2016-03-21 4:41 GMT+03:00 Utkarsh Ayachit :
> Andrew,
>
> ParaView 5.0.1-RC2 binaries are now available for download. Please
> give them a try and let me know if are still seeing the
Andrew,
ParaView 5.0.1-RC2 binaries are now available for download. Please
give them a try and let me know if are still seeing the Ensight issue.
Thanks
Utkarsh
On Thu, Mar 17, 2016 at 10:20 AM, Utkarsh Ayachit
wrote:
> The binaries have not yet been generated.
Hello.
I recieved an email about corrected ParaView-5.0.1 and decided to test the
latest available official release for Win64:
ParaView-5.0.1-RC1-Qt4-OpenGL2-Windows-64bit.zip
I tried the same big EnSight case and the same error appeared (stat
failed). Should be this release "patched" or it's not
The binaries have not yet been generated. You'll have to use RC2, not
RC1 for this fix.
On Thu, Mar 17, 2016 at 5:52 AM, Andrew wrote:
> Hello.
> I recieved an email about corrected ParaView-5.0.1 and decided to test the
> latest available official release for Win64:
>
This merge request should address this issue:
https://gitlab.kitware.com/vtk/vtk/merge_requests/1320
Once it's tested, reviewed etc. it'll be merged and I'll have it
updated in ParaView release 5.0.1 as well.
Utkarsh
On Wed, Mar 9, 2016 at 9:47 AM, Utkarsh Ayachit
I didn't but I didn't have to :). Your investigation lead me to in the
right direction -- it just wasn't FILE_OFFSET_BITS that was the issue.
It was the fact that on Windows the stat function is different,
period. I am hoping to push a fix in for 5.0.1.
On Wed, Mar 9, 2016 at 7:32 AM, Andrew
Utkarsh Ayachit,
Hello. Did you try the trick with EnSight geometry file reader? Thanks.
2016-03-03 17:51 GMT+03:00 Utkarsh Ayachit :
> > About test file. It's simple, IMHO. Generate any garbage file or take any
> > existing big file. Rename it to have the geometry
Andrew/ Sam,
Thanks for exploring this as much as you did. I am afraid the issue is
not _FILE_OFFSET_BITS flag, however. As far as I can tell, the flag
gets set "globally" when CMake determinees during configure time that
"large file support" is possible. To follow the code here's how it
works:
Samuel, thanks for your experiment. File with size less than 2 GiB, of
course, can't expose this issue.
I read a bit more about stat() and it turned out that it should work as
64bit if FILE_OFFSET_BITS is set to 64. And it is set in other ParaView
sources but, IMHO, not in EnSight reader. Dear
Andrew,
Regarding your question, "Do you have any EnSight Gold-Format
files greater than 4GB?" No, the largest EnSight *.geom file I
have is 1 GB.
I just tried it in PV v5.0.0. Reading the datum set and running
through 67 time steps did not
Sorry for many posts, but, I think, I found something interesting (or I
just think so :)). I digged a *stat*() usage in ParaView at official GitHub
source repository. If I get it right, there are two types of this function:
*stat*() and *stat64*(). My only program that deals with large files is a
I took a look at the code. Te problematic fragment (line 114 in
vtkEnSightGoldBinaryReader) just checks the file's existance and opens it
in standard way. The problem occures in *stat*() function that is fed with
the full file name and the reference to structure to receive file params. I
tried to
Hello Samuel.
Sorry, but I can't undersatand how can the file fragmentation affect it's
readability and parsing. Even if the file has thousands of fragments and
"brain-damaging" :) runlist in many extended FILE records on NTFS
partition, your program, if it uses Win API, will see it like a solid
Another "experimental data". I was able to load this big case in ParaView
viat the CGNS format. It was neccesary to select CGNS 3.0 and HDF5 options
in CFX Converter. But when I apply the Extract Block filter I see no any
boundaries, only fluid domain (that is displayed OK). So CGNS format is not
I performed another test with *EnSight 6* (not Gold) format. Conversion was
made on Win-7 x64 machine. The same results: PV 4.3 crashed, PV 5.0 "cannot
stat" (full error message is in my first post on this topic). Sorry, now I
need to work on with my report...
2016-02-29 8:47 GMT+03:00 Andrew
Hello. Sorry for silence, I'm usually offline on holydays, although I have
internet connection and read your mail.
Samuel Key
Thanks for your attention.
About transferring files from Linux to Windows. I use binary EnSight files
because CFX converter fails to write so large files in ASCII
Andrew,
For what it is worth, I use ParaView
(ParaView-5.0.0-Qt4-OpenGL2-Windows-64bit) on Windows-7 64bit. I
just now tested two medium-sized, EnSight Gold-formatted
simulation results files (600,000 finite elements) and both
worked.
In
Adnrew,
Do you have a sample dataset to share to reproduce this issue?
Thanks
Utkarsh
On Fri, Feb 26, 2016 at 1:26 AM, Andrew wrote:
> Hello. We use Ansys CFX in our work but the standard post-processor CFD-Post
> consumes one of Ansys licenses while Paraview is free. So I
Hello. We use Ansys CFX in our work but the standard post-processor
CFD-Post consumes one of Ansys licenses while Paraview is free. So I often
make pictures for reports with ParaView to preserve Ansys license for
another users/needs (because other users are not familiar with ParaView and
CFD-Post
21 matches
Mail list logo