Bug#894462: paraview: edges are blotted [regression]

[Drew Parsons]

On 2024-02-24 12:40, Francesco Poli wrote:

On Thu, 04 Jan 2024 12:18:21 +0100 Drew Parsons 


Can you confirm paraview 5.11 is meeting your image quality
expectations?


Only if I disable FXAA (which, by the way, is enabled by default, but
can luckily be disabled in the settings!).

...

Could you please forward it upstream, instead?
Thanks for your time and dedication!



I don't understand what bug you want forwarded upstream.

FXAA anti-aliasing is enabled by default, but if you don't like you can 
switch it off.
Upstream have provided an option in Edit/Settings/RenderView so that you 
can do that.

What else do you want them to do?

Do you mean you want them to remove antialiasing entirely?  That's not 
acceptable.  There are plenty of bug reports demanding antialiasing.  Do 
you want them to deactivate antialiasing by default?  I can't see that 
working well, for the same reason. Do you want them to offer alternative 
antialiasing algorithms?  Which ones?

Bug#894462: paraview: edges are blotted [regression]

[Drew Parsons]

Package: paraview
Followup-For: Bug #894462

The png generated by the procedure in this bug looks fine to me, using
current paraview (5.11).  It's slightly blurry but no more than you'd
expect for a png file (it's raster image format, not a vector image
format, you can't expect to main high resolution if you zoom into the
pixels).

Can you confirm paraview 5.11 is meeting your image quality
expectations?

As far as I can tell, we can close this bug now.

Bug#894462: paraview: edges are blotted [regression]

[Anton Gladky]

Hi Francesco,

2018-04-02 17:31 GMT+02:00 Francesco Poli :
...
> I noticed that you removed yourself from the uploader list, but I was
> hoping someone else from the Debian Science Team was going to step in
> soon... Is this not the case?  :-(
...

Well, I hope also.

>> I am not using it any more
>
> Because you no longer have the need to perform data visualizations?
> Or because you now use some other similar package?
> I am not aware of any other comparable package in Debian, but maybe you
> are: that's why I am asking...

Please see here [1].

[1] https://lists.debian.org/debian-science/2017/10/msg00078.html

>> If you really want it to be fixed (as well as export to AVI), feel free
>> to join our team and provide some patches.
>
> This is difficult, I lack the time and I don't know how long will it
> take to get the expertise required to maintain such a package...

Debian Science Team members are usually very helpful if somebody
is trying to solve technical questions.

>> Otherwise paraview is the good
>> candidate to be dropped from the next release.
>
> Assuming this is not an April Fool's Day prank, I am very worried by
> this danger. I really hope this won't happen!

Some packages can live many years without maintainer.
But ParaView is too large and complex to use this opportunity.
If RC-bugs will not be resolved on time - any package is being
removed from the testing, and later - does not go to release.

Best regards

Anton

Bug#894462: paraview: edges are blotted [regression]

[Francesco Poli]

On Sun, 1 Apr 2018 19:51:36 +0200 Anton Gladky wrote:

> Hi Francesco,

Hello Anton!   :-)

> 
> thanks for bugreport.

You are welcome.
Thanks for your prompt reply!

> The problem with paraview now is that it does
> not actually have any active maintainer
[...]

I noticed that you removed yourself from the uploader list, but I was
hoping someone else from the Debian Science Team was going to step in
soon... Is this not the case?  :-(

> I am not using it any more

Because you no longer have the need to perform data visualizations?
Or because you now use some other similar package?
I am not aware of any other comparable package in Debian, but maybe you
are: that's why I am asking...

> and the Gert (thanks to him!) is doing some technical uploads.

Yeah, that is much appreciated: thanks Gert!

> 
> If you really want it to be fixed (as well as export to AVI), feel free
> to join our team and provide some patches.

This is difficult, I lack the time and I don't know how long will it
take to get the expertise required to maintain such a package...

> Or at least the communication
> with upstream would be very helpful.

Could someone from the Debian Science Team at least forward this bug
report upstream (along with the other ones I filed)?

> Otherwise paraview is the good
> candidate to be dropped from the next release.

Assuming this is not an April Fool's Day prank, I am very worried by
this danger. I really hope this won't happen!


Thanks for your time and helpfulness.


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpYCzNFIoXLi.pgp
Description: PGP signature

Bug#894462: paraview: edges are blotted [regression]

[Francesco Poli]

Control: severity -1 important


On Sun, 01 Apr 2018 20:39:56 +0200 Gert Wollny wrote:

[...]
> These two upstream bugs might also be related: 
> 
> https://gitlab.kitware.com/paraview/paraview/issues/17202
> https://gitlab.kitware.com/paraview/paraview/issues/16882

I think the latter (issue 16882) is especially related: it really seems
to be the issue where the new anti-aliasing feature has been discussed
and implemented.

As I said, this new feature is really appreciated, but it has the flaw
of making edges (on surfaces and in wireframe representations) look
weird with "blotted" intersections.
Once this flaw is fixed, this new anti-aliasing feature will be great!

Luckily, while reading the above-cited upstream issue, I found out that
this new anti-aliasing feature is enabled by default, but it may be
disabled. For those following this bug log, the procedure to disable
the anti-aliasing is:

 • select Settings... from the Edit menu
 • in the "Render View" tab, uncheck "Use FXAA"

Since this feature may be disabled by the user, whenever it is
considered harmful, the paraview package no longer appears to be
unusable.
I am therefore lowering the severity of this bug report.

Thanks for your help so far.



-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpPP9_B_m8nD.pgp
Description: PGP signature

Bug#894462: paraview: edges are blotted [regression]

[Anton Gladky]

Hi Francesco,

thanks for bugreport. The problem with paraview now is that it does
not actually have any active maintainer [1]. I am not using it any more
and the Gert (thanks to him!) is doing some technical uploads.

If you really want it to be fixed (as well as export to AVI), feel free
to join our team and provide some patches. Or at least the communication
with upstream would be very helpful. Otherwise paraview is the good
candidate to be dropped from the next release.

[1] https://tracker.debian.org/pkg/paraview

Best regards

Anton


2018-03-30 18:01 GMT+02:00 Francesco Poli (wintermute)
:
> Package: paraview
> Version: 5.4.1+dfsg4-2
> Severity: grave
> Justification: renders package unusable
>
> Hello paraview Debian package maintainers,
> thanks for uploading a Debian revision that uses Qt5 rather than Qt4!
>
> I've just upgraded to it on my Debian testing box, but I found a bad
> regression that renders the package unusable to create beautiful and
> clear visualizations (this may be considered as basically the main
> purpose of paraview!).
>
>
> The attached test case is based on one of the data files generated
> by the little program included in the test case sent for bug #892293.
> The program source (written in Fortran) is included again for
> completeness' sake.
>
> Steps to reproduce the regression:
>
>   0) start paraview
>
>  $ paraview
>
>   1) click on the "Open" button and open "wave0001.xyz"
>
>   2) specify "PLOT3D Files" in the "Open Data With..." dialog window
>
>   3) click on the "Apply" button
>
>   4) change the representation from "Outline" to "Surface With Edges"
>
>   5) from the File menu, select Save State...
>
>   6) save the state as "wave_PARAVIEW-VERSION.pvsm"
>
>   7) from the File menu, select Save Screenshot...
>
>   8) save the screenshot as "wave_PARAVIEW-VERSION.png"
>
>
> By performing these steps with paraview/5.4.1+dfsg3-2 and
> with paraview/5.4.1+dfsg4-2, I obtained the two attached
> screenshots.
>
> In paraview/5.4.1+dfsg4-2 there seems to be a commendable attempt
> to apply some antialiasing to all the lines (including the edges
> on surfaces, the wireframe edges, but also the lines of the orientation
> axes, and so forth...).
> Unfortunately this new feature creates unsightly images, whenever
> the edges are shown from a distance. Please take a look yourself
> at the wave_5.4.1+dfsg4-2.png screenshot: all the intersections
> between edges seem to be somehow "blotted" and unpleasant to look at.
>
>
> Please fix this regression, as it makes paraview unusable.
>
> Thanks for your time!
> Bye.
>
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (800, 'testing'), (500, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US:en (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages paraview depends on:
> ii  libavcodec57   7:3.4.2-1+b1
> ii  libavformat57  7:3.4.2-1+b1
> ii  libavutil557:3.4.2-1+b1
> ii  libc6  2.27-2
> ii  libcgns3.3 3.3.0-6
> ii  libexpat1  2.2.5-3
> ii  libfreetype6   2.8.1-2
> ii  libgcc11:8-20180321-1
> ii  libgl1 1.0.0-2
> ii  libgl2ps1.41.4.0+dfsg1-2
> ii  libglew2.0 2.0.0-5
> ii  libhdf5-1001.10.0-patch1+docs-4
> ii  libjpeg62-turbo1:1.5.2-2+b1
> ii  libjsoncpp11.7.4-3
> ii  libnetcdf131:4.6.1-1
> ii  libogg01.3.2-1+b1
> ii  libopenmpi22.1.1-8
> ii  libpng16-161.6.34-1
> ii  libprotobuf10  3.0.0-9.1
> ii  libpython2.7   2.7.14-7
> ii  libqt5core5a   5.9.2+dfsg-12
> ii  libqt5gui5 5.9.2+dfsg-12
> ii  libqt5help55.9.2-6
> ii  libqt5network5 5.9.2+dfsg-12
> ii  libqt5widgets5 5.9.2+dfsg-12
> ii  libqt5x11extras5   5.9.2-1
> ii  libstdc++6 8-20180321-1
> ii  libswscale47:3.4.2-1+b1
> ii  libtheora0 1.1.1+dfsg.1-14+b1
> ii  libtiff5   4.0.9-4
> ii  libx11-6   2:1.6.5-1
> ii  libxml22.9.4+dfsg1-6.1
> ii  libxt6 1:1.1.5-1
> ii  python-autobahn17.10.1+dfsg1-2
> ii  python-matplotlib  2.1.1-2
> ii  python-mpi4py  2.0.0-3
> ii  python-six 1.11.0-2
> ii  python-twisted 17.9.0-1
> ii  tcl [tclsh]8.6.0+9
> ii  zlib1g 1:1.2.8.dfsg-5
>
> Versions of packages paraview recommends:
> ii  mpi-default-bin  1.10
> ii  paraview-doc 5.4.1+dfsg4-2
> ii  paraview-python  5.4.1+dfsg4-2
>
> Versions of packages paraview suggests:
> pn  h5utils 
> pn  hdf5-tools  
>
> -- no debconf information
>
> --
> debian-science-maintainers mailing list
> debian-science-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#894462: paraview: edges are blotted [regression]

[Gert Wollny]

Am Freitag, den 30.03.2018, 18:01 +0200 schrieb Francesco Poli
(wintermute):
> Package: paraview
> Version: 5.4.1+dfsg4-2
> Severity: grave
> Justification: renders package unusable
> 
> Hello paraview Debian package maintainers,
> thanks for uploading a Debian revision that uses Qt5 rather than Qt4!
> 
> I've just upgraded to it on my Debian testing box, but I found a bad
> regression that renders the package unusable to create beautiful and
> clear visualizations (this may be considered as basically the main
> purpose of paraview!).

Since I did this upload as a team upload I can give you one comment  (I
don't used the program myself, and I have no idea how to use it, I am
only somewhat familiar with VTK, but also only from the "get it to
compile" side and not so much from the "how to use it properly").

With this upload I switched the package from using the deprecated
"OpenGL" redering interface (based on OpenGL 1.1) to the new "OpenGL2"
rendering interface (based on openGL 3.2), which means that his might
be a fallout from this rather big upstream change. 

These two upstream bugs might also be related: 

https://gitlab.kitware.com/paraview/paraview/issues/17202
https://gitlab.kitware.com/paraview/paraview/issues/16882

Best, 
Gert

Bug#894462: paraview: edges are blotted [regression]

[Francesco Poli (wintermute)]

Package: paraview
Version: 5.4.1+dfsg4-2
Severity: grave
Justification: renders package unusable

Hello paraview Debian package maintainers,
thanks for uploading a Debian revision that uses Qt5 rather than Qt4!

I've just upgraded to it on my Debian testing box, but I found a bad
regression that renders the package unusable to create beautiful and
clear visualizations (this may be considered as basically the main
purpose of paraview!).


The attached test case is based on one of the data files generated
by the little program included in the test case sent for bug #892293.
The program source (written in Fortran) is included again for
completeness' sake.

Steps to reproduce the regression:

  0) start paraview

 $ paraview

  1) click on the "Open" button and open "wave0001.xyz"

  2) specify "PLOT3D Files" in the "Open Data With..." dialog window

  3) click on the "Apply" button
  
  4) change the representation from "Outline" to "Surface With Edges"

  5) from the File menu, select Save State...

  6) save the state as "wave_PARAVIEW-VERSION.pvsm"

  7) from the File menu, select Save Screenshot...

  8) save the screenshot as "wave_PARAVIEW-VERSION.png"


By performing these steps with paraview/5.4.1+dfsg3-2 and
with paraview/5.4.1+dfsg4-2, I obtained the two attached
screenshots.

In paraview/5.4.1+dfsg4-2 there seems to be a commendable attempt
to apply some antialiasing to all the lines (including the edges
on surfaces, the wireframe edges, but also the lines of the orientation
axes, and so forth...).
Unfortunately this new feature creates unsightly images, whenever
the edges are shown from a distance. Please take a look yourself
at the wave_5.4.1+dfsg4-2.png screenshot: all the intersections
between edges seem to be somehow "blotted" and unpleasant to look at.


Please fix this regression, as it makes paraview unusable.

Thanks for your time!
Bye.


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (800, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages paraview depends on:
ii  libavcodec57   7:3.4.2-1+b1
ii  libavformat57  7:3.4.2-1+b1
ii  libavutil557:3.4.2-1+b1
ii  libc6  2.27-2
ii  libcgns3.3 3.3.0-6
ii  libexpat1  2.2.5-3
ii  libfreetype6   2.8.1-2
ii  libgcc11:8-20180321-1
ii  libgl1 1.0.0-2
ii  libgl2ps1.41.4.0+dfsg1-2
ii  libglew2.0 2.0.0-5
ii  libhdf5-1001.10.0-patch1+docs-4
ii  libjpeg62-turbo1:1.5.2-2+b1
ii  libjsoncpp11.7.4-3
ii  libnetcdf131:4.6.1-1
ii  libogg01.3.2-1+b1
ii  libopenmpi22.1.1-8
ii  libpng16-161.6.34-1
ii  libprotobuf10  3.0.0-9.1
ii  libpython2.7   2.7.14-7
ii  libqt5core5a   5.9.2+dfsg-12
ii  libqt5gui5 5.9.2+dfsg-12
ii  libqt5help55.9.2-6
ii  libqt5network5 5.9.2+dfsg-12
ii  libqt5widgets5 5.9.2+dfsg-12
ii  libqt5x11extras5   5.9.2-1
ii  libstdc++6 8-20180321-1
ii  libswscale47:3.4.2-1+b1
ii  libtheora0 1.1.1+dfsg.1-14+b1
ii  libtiff5   4.0.9-4
ii  libx11-6   2:1.6.5-1
ii  libxml22.9.4+dfsg1-6.1
ii  libxt6 1:1.1.5-1
ii  python-autobahn17.10.1+dfsg1-2
ii  python-matplotlib  2.1.1-2
ii  python-mpi4py  2.0.0-3
ii  python-six 1.11.0-2
ii  python-twisted 17.9.0-1
ii  tcl [tclsh]8.6.0+9
ii  zlib1g 1:1.2.8.dfsg-5

Versions of packages paraview recommends:
ii  mpi-default-bin  1.10
ii  paraview-doc 5.4.1+dfsg4-2
ii  paraview-python  5.4.1+dfsg4-2

Versions of packages paraview suggests:
pn  h5utils 
pn  hdf5-tools  

-- no debconf information


waveplot3d_blotted-edges.tar.xz
Description: application/xz