From: Wolfgang Bangerth Date: Wed, 15 Apr 2020 19:54:12 +0000 (-0600) Subject: Correct the spelling of the VisIt program. X-Git-Tag: v9.2.0-rc1~229^2 X-Git-Url: https://gitweb.dealii.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=refs%2Fpull%2F9900%2Fhead;p=dealii.git Correct the spelling of the VisIt program. --- diff --git a/doc/doxygen/headers/vector_valued.h b/doc/doxygen/headers/vector_valued.h index 99a60b950c..64530058ba 100644 --- a/doc/doxygen/headers/vector_valued.h +++ b/doc/doxygen/headers/vector_valued.h @@ -1099,7 +1099,7 @@ * trailing element of DataComponentInterpretation::component_is_scalar . The * array is then given as an extra argument to DataOut::add_data_vector to * explain how the data in the given solution vector is to be interpreted. - * Visualization programs like Visit and Paraview will then offer to show + * Visualization programs like VisIt and Paraview will then offer to show * these dim components as vector fields, rather than as * individual scalar fields. * diff --git a/doc/readme.html b/doc/readme.html index c5de0160c3..4f93d593e2 100644 --- a/doc/readme.html +++ b/doc/readme.html @@ -123,7 +123,7 @@ gnuplot and a postscript viewer (for eps) should be available almost everywhere. In the last few years, most new visualization programs have moved to support vtk/vtu format. There are a number of excellent programs that can read vtk and vtu, such as - Visit, + VisIt, ParaView, as well as others. Povray is freely available for almost all platforms. AVS is a commercial program available for most Unix flavors. Tecplot is a commercial program available for Windows and most Unix platforms.

diff --git a/examples/step-18/doc/intro.dox b/examples/step-18/doc/intro.dox index 222436a664..9f07b357a0 100644 --- a/examples/step-18/doc/intro.dox +++ b/examples/step-18/doc/intro.dox @@ -373,7 +373,7 @@ where TTTT is the timestep number (starting from 1) and 0). These files contain the locally owned cells for the timestep and processor. The files solution-TTTT.visit is the visit record for timestep TTTT, while solution-TTTT.pvtu is -the same for ParaView. (More recent versions of Visit can actually read +the same for ParaView. (More recent versions of VisIt can actually read .pvtu files as well, but it doesn't hurt to output both kinds of record files.) Finally, the file solution.pvd is a special record only supported by ParaView that references diff --git a/examples/step-3/doc/results.dox b/examples/step-3/doc/results.dox index e69746fc90..082fa7f2e5 100644 --- a/examples/step-3/doc/results.dox +++ b/examples/step-3/doc/results.dox @@ -21,11 +21,11 @@ screen display. Apart from the output shown above, the program generated the file solution.vtk, which is in the VTK format that is widely used by many visualization programs today -- including the two -heavy-weights Visit and +heavy-weights VisIt and Paraview that are the most commonly used programs for this purpose today. -Using Visit, it is not very difficult to generate a picture of the +Using VisIt, it is not very difficult to generate a picture of the solution like this: @@ -45,7 +45,7 @@ are clamped to a square frame with no vertical variation; a constant force density will therefore intuitively lead to a membrane that simply bulges upward -- like the one shown above. -Visit and Paraview both allow playing with various kinds of visualizations +VisIt and Paraview both allow playing with various kinds of visualizations of the solution. Several video lectures show how to use these programs. @dealiiVideoLectureSeeAlso{11,32} diff --git a/examples/step-4/doc/results.dox b/examples/step-4/doc/results.dox index 2973128a2a..fc9382f206 100644 --- a/examples/step-4/doc/results.dox +++ b/examples/step-4/doc/results.dox @@ -30,7 +30,7 @@ solution steps when you actually run the program. The program produces two files: solution-2d.vtk and solution-3d.vtk, which can be viewed using the programs -Visit or Paraview (in case you do not have these programs, you can easily +VisIt or Paraview (in case you do not have these programs, you can easily change the output format in the program to something which you can view more easily). Visualizing solutions is a bit of an art, but it can also be fun, so @@ -86,7 +86,7 @@ A final remark on visualization: the idea of visualization is to give insight, which is not the same as displaying information. In particular, it is easy to overload a picture with information, but while it shows more information it makes it also more difficult to glean insight. As an example, the program I -used to generate these pictures, Visit, by default puts tick marks on every +used to generate these pictures, VisIt, by default puts tick marks on every axis, puts a big fat label "X Axis" on the $x$ axis and similar for the other axes, shows the file name from which the data was taken in the top left and the name of the user doing so and the time and date on the bottom right. None diff --git a/examples/step-42/step-42.cc b/examples/step-42/step-42.cc index 7a67669a3a..1963fc1ed2 100644 --- a/examples/step-42/step-42.cc +++ b/examples/step-42/step-42.cc @@ -2033,7 +2033,7 @@ namespace Step42 // set of output files can be read at once. These .pvtu // are used by Paraview to describe an entire parallel computation's // output files. We then do the same again for the competitor of - // Paraview, the Visit visualization program, by creating a matching + // Paraview, the VisIt visualization program, by creating a matching // .visit file. const std::string master_name = data_out.write_vtu_with_pvtu_record( output_dir, "solution", current_refinement_cycle, mpi_communicator, 2); diff --git a/examples/step-44/step-44.cc b/examples/step-44/step-44.cc index 97b37a7ce1..7b48067891 100644 --- a/examples/step-44/step-44.cc +++ b/examples/step-44/step-44.cc @@ -3343,7 +3343,7 @@ namespace Step44 // @sect4{Solid::output_results} // Here we present how the results are written to file to be viewed - // using ParaView or Visit. The method is similar to that shown in previous + // using ParaView or VisIt. The method is similar to that shown in previous // tutorials so will not be discussed in detail. template void Solid::output_results() const diff --git a/examples/step-6/doc/results.dox b/examples/step-6/doc/results.dox index f0063d996f..8cf353f81c 100644 --- a/examples/step-6/doc/results.dox +++ b/examples/step-6/doc/results.dox @@ -495,9 +495,9 @@ $\hat K$, and that it is one for squares and cubes. In practice, it might be interesting to visualize such quality measures. The function GridTools::compute_aspect_ratio_of_cells() provides one way to get this kind of information. Even better, visualization tools -such as Visit often allow you to visualize this sort of information +such as VisIt often allow you to visualize this sort of information for a variety of measures from within the visualization software -itself; in the case of Visit, just add a "pseudo-color" plot and select +itself; in the case of VisIt, just add a "pseudo-color" plot and select one of the mesh quality measures instead of the solution field. diff --git a/examples/step-62/doc/results.dox b/examples/step-62/doc/results.dox index a4170afaa5..bbe4d34152 100644 --- a/examples/step-62/doc/results.dox +++ b/examples/step-62/doc/results.dox @@ -106,7 +106,7 @@ through the device.

Mode profile

-We can inspect the mode profile with Paraview or Visit. +We can inspect the mode profile with Paraview or VisIt. As we have discussed, at resonance all the mechanical energy is transmitted and the amplitude of motion is amplified inside the cavity. It can be observed that the PMLs are quite effective to truncate the solution. diff --git a/examples/step-8/doc/results.dox b/examples/step-8/doc/results.dox index 5171fee9e5..4866fe2c54 100644 --- a/examples/step-8/doc/results.dox +++ b/examples/step-8/doc/results.dox @@ -2,7 +2,7 @@ There is not much to be said about the results of this program, other than -that they look nice. All images were made using Visit from the +that they look nice. All images were made using VisIt from the output files that the program wrote to disk. The first two pictures show the $x$- and $y$-displacements as scalar components: @@ -30,7 +30,7 @@ we said that this is not just a pressure and a concentration (two scalar quantities) but that the two components actually are the parts of a vector-valued quantity, namely the displacement. Absent this knowledge, the DataOut class assumes that all individual variables we print are separate -scalars, and Visit and Paraview then faithfully assume that this is indeed what it is. In +scalars, and VisIt and Paraview then faithfully assume that this is indeed what it is. In other words, once we have written the data as scalars, there is nothing in these programs that allows us to paste these two scalar fields back together as a vector field. Where we would have to attack this problem is at the root, @@ -38,7 +38,7 @@ namely in ElasticProblem::output_results(). We won't do so here but instead refer the reader to the step-22 program where we show how to do this for a more general situation. That said, we couldn't help generating the data anyway that would show how this would look if implemented as discussed in -step-22. The vector field then looks like this (Visit and Paraview +step-22. The vector field then looks like this (VisIt and Paraview randomly select a few hundred vertices from which to draw the vectors; drawing them from each individual vertex would make the picture unreadable): diff --git a/include/deal.II/base/data_out_base.h b/include/deal.II/base/data_out_base.h index 0ef384f8f1..007077b171 100644 --- a/include/deal.II/base/data_out_base.h +++ b/include/deal.II/base/data_out_base.h @@ -1168,8 +1168,8 @@ namespace DataOutBase * polynomials rather than simply linear or bilinear is a feature that was * only introduced in VTK sometime in 2017 or 2018. You will need at least * Paraview version 5.5 (released in the spring of 2018) or a similarly - * recent version of Visit for this feature to work (for example, - * Visit 2.13.2, released in May 2018, does not yet support this feature). + * recent version of VisIt for this feature to work (for example, + * VisIt 2.13.2, released in May 2018, does not yet support this feature). * Older versions of these programs are likely going to result in errors * when trying to read files generated with this flag set to @p true. * Experience with these programs shows that these error messages are likely diff --git a/include/deal.II/grid/grid_out.h b/include/deal.II/grid/grid_out.h index 3dc7ef5168..fac80cfa30 100644 --- a/include/deal.II/grid/grid_out.h +++ b/include/deal.II/grid/grid_out.h @@ -1325,7 +1325,7 @@ public: /** * Write triangulation in VTU format for each processor, and add a .pvtu file - * for visualization in Visit or Paraview that describes the collection of VTU + * for visualization in VisIt or Paraview that describes the collection of VTU * files as all part of the same simulation. The output is in the form * filename_without_extension.proc000*.vtu where * is * 0,1,...,n_proc-1 and filename_without_extension.pvtu. The input diff --git a/include/deal.II/numerics/data_postprocessor.h b/include/deal.II/numerics/data_postprocessor.h index 5bbed742fa..61752f7326 100644 --- a/include/deal.II/numerics/data_postprocessor.h +++ b/include/deal.II/numerics/data_postprocessor.h @@ -938,13 +938,13 @@ private: * are then supposed to be interpreted as a tensor, one has to (i) use a * visualization program that can visualize tensors, and (ii) teach it * how to re-combine the scalar fields into tensors. In the case of - * Visit -- see https://wci.llnl.gov/simulation/computer-codes/visit/ -- + * VisIt -- see https://wci.llnl.gov/simulation/computer-codes/visit/ -- * this is done by creating a new "Expression": in essence, one creates * a variable, say "grad_u", that is tensor-valued and whose value is * given by the expression {{grad_u_xx,grad_u_xy}, * {grad_u_yx, grad_u_yy}}, where the referenced variables are * the names of scalar fields that, here, are produced by the example - * below. Visit is then able to visualize this "new" variable as a + * below. VisIt is then able to visualize this "new" variable as a * tensor.) * * All derived classes have to do is implement a constructor and overload @@ -1048,7 +1048,7 @@ private: * * These pictures show an ellipse representing the gradient tensor at, on * average, every tenth mesh point. You may want to read through the - * documentation of the Visit visualization program (see + * documentation of the VisIt visualization program (see * https://wci.llnl.gov/simulation/computer-codes/visit/) for an interpretation * of how exactly tensors are visualizated. *