Commit 454cf141 authored by Cory Quammen's avatar Cory Quammen Committed by Kitware Robot

Merge topic 'chart_load_no_vars'

bc707fdb Build doc improvements - lessen duplication, make consistent.
c94a38c2 Initial doc of 'Load No Chart Variables' setting, add build.md.
Acked-by: Kitware Robot's avatarKitware Robot <kwrobot@kitware.com>
Merge-request: !35
parents 48b46add bc707fdb
Pipeline #27755 failed with stage
in 0 seconds
......@@ -16,5 +16,6 @@
!ParaViewCatalyst/Images/*
!README.md
!CONTRIBUTING.md
!build.md
ParaView/Extras
.*
......@@ -21,27 +21,34 @@ is as follows:
3. Clone the repository:
$ git clone https://gitlab.kitware.com/paraview/paraview-guide-ce.git ParaViewGuide
$ cd ParaViewGuide
$ mkdir ParaViewGuide; cd ParaViewGuide
$ git clone https://gitlab.kitware.com/paraview/paraview-guide-ce.git src
$ cd src
The main repository will be configured as your `origin` remote.
4. Add your fork as a the `gitlab` remote.
$ git remote add gitlab https://gitlab.kitware.com/username/paraview-guide-ce.git
You can use configure the remote to use SSH access instead, if needed.
5. Edit files and create commits (repeat as needed):
5. Install dependencies and [build][build.md]
$ mkdir ../build; cd ../build
$ ccmake ../src
$ make
6. Edit files and create commits (repeat as needed):
$ git checkout -b my-topic origin/master
$ edit file1 file2 file3
$ git add file1 file2 file3
$ git commit
6. Push commits in your topic branch to your fork in GitLab:
7. Push commits in your topic branch to your fork in GitLab:
$ git push gitlab HEAD
7. Visit your fork in GitLab, browse to the "**Merge Requests**" link on the
8. Visit your fork in GitLab, browse to the "**Merge Requests**" link on the
left, and use the "**New Merge Request**" button in the upper right to
create a Merge Request.
......@@ -51,7 +58,6 @@ for the guide.
[merge requests]: https://gitlab.kitware.com/paraview/paraview-guide-ce/merge_requests
[GitLab]: https://gitlab.kitware.com/paraview/paraview-guide-ce/
[Mailing List]: http://www.paraview.org/mailing-lists/
[ParaView Git]: https://gitlab.kitware.com/paraview/paraview/blob/master/CONTRIBUTING.md
[ContributorNotes.tex]: ParaView/ContributorNotes.tex
[GitLab Access]: https://gitlab.kitware.com/users/sign_in
[Fork ParaViewGuide-CE]: https://gitlab.kitware.com/paraview/paraview-guide-ce/fork/new
......
......@@ -131,7 +131,7 @@ animation covers a particular time domain of your choosing.
\begin{didyouknow}
You can change the precision (number of significant digits) displayed by the animation clock
by selecting the \ui{Load All Variables} checkbox under
by changing the \ui{Animation Time Precision} value under
\ui{Settings/Properties Panel Options/Advanced}.
\begin{center}
......
......@@ -962,6 +962,18 @@ an existing view to \ui{Line Chart View}. \ui{Line Chart View} will also be
automatically created if you apply a filter that needs this view, e.g., the
\ui{Plot Over Line} filter.
\begin{didyouknow}
If you generate lengthy data for the \ui{Line Chart View}, the default variables
that are selected may be slow to adjust. You can change \paraview's default
behavior to initially load no variables at all by selecting the
\ui{Load No Chart Variables} checkbox under
\ui{Settings/General/Properties Panel Options}.
\begin{center}
\includegraphics[width=0.4\linewidth]{Images/ChartNoVarSetting.png}
\end{center}
\end{didyouknow}
\subsubsection{Interactions}
Interactions with the chart view result in changing the plotted axes ranges.
......@@ -1175,7 +1187,7 @@ allows you to spot patterns in the small scatter plots, change focus to those
plots of interest, and perform basic selection. The principle is that, for all
selected arrays or series to be plotted, the view generates a scatter plot for
each pair. You can activate a particular scatter plot, in which case the active
plot is re-drawn at a bigger scale to make it easier to for inspection.
plot is re-drawn at a bigger scale to make it easier to inspect.
Additionally, the view shows a histogram for each plotted variable or series.
The view properties allow you to set colors to use for active plot, histograms,
......
......@@ -35,35 +35,15 @@ The printed editions of **The ParaView Guide** are released under [CC BY-ND 4.0]
Build Instructions
------------------
This is **CMake** based project and can be built similar to ParaView. We use **LaTeX**
for typesetting the guides. Thus, unless you are familiar with setting up LaTeX on your system,
This is a **CMake** based project and follows some of the same steps as building [ParaView][]. We use **LaTeX** for typesetting the guides. Thus, unless you are familiar with setting up LaTeX on your system,
you may want to simply download the pregenerated PDF from the [ParaView homepage][ParaView Books].
1. Clone the repository
Please see [CONTRIBUTING.md][] for detailed instructions on git, and [build.md][] for instructions on setting up prerequisites and building.
$ git clone https://gitlab.kitware.com/paraview/paraview-guide-ce.git ParaViewGuide
The main repository will be configured as your `origin` remote.
On a successful build, the **ParaView/ParaViewUsersGuide.pdf** and/or **ParaViewCatalyst/ParaViewCatalystUsersGuide.pdf** will be generated.
2. Run CMake. This step requires you have LaTeX (and necessary modules) installed
on your system. You can turn **ENABLE_PARAVIEW_GUIDE** (default: ON) and/or
**ENABLE_CATALYST_USERS_GUIDE** (default: OFF) ON or OFF based on your preference.
On Unix-based systems, the steps are:
$ mkdir ParaViewGuildBuild
$ cmake <PATH>/ParaViewGuide
$ make
3. On successful build, the **ParaView/ParaViewUsersGuide.pdf** and/or
**ParaViewCatalyst/ParaViewCatalystUsersGuide.pdf** will be generated based
on the options you chose in Step 2.
Note that Step 2 can take a long time, especially *rendering* the images.
To speed things, you can edit [ParaViewUsersGuide.tex][] file to change
the documentclass mode to `[draft]`.
\documentclass[draft]{InsightSoftwareGuide}
This will generate the the draft PDF without any images.
[ParaViewUsersGuide.tex]: ParaView/ParaViewUsersGuide.tex
[build.md]: build.md
[ParaView]: https://gitlab.kitware.com/paraview/paraview/blob/master/CONTRIBUTING.md
Reporting Bugs
---------------
......
Build ParaViewGuide
===================
The ParaView Guide Community Edition is a **LaTeX** document that uses **CMake** to generate a final .pdf file. The Catalyst User's Guide can be built at the same time, in the same way.
## Prerequisites
You need CMake, Make, LaTeX, and ImageMagick.
### CMake
* See the [ParaView docs][] for obtaining CMake.
### Windows
* To get LaTex, install [MiKTeX][]
- First, run the MiKTeX Update (Admin). You may have to run twice if it updates the updater binary.
- MiKTeX Package Manager (Admin), search and install packages:
> adjustbox, bclogo, catoptions, cite, collectbox, colortbl, enumitem, etoolbox, fancyhdr, floatflt, fncychap, frankenstein, ifoddpage, l3kernel, l3packages, listings, mdframed, mptopdf, ms, paralist, pgf, setspace, subfigure, symbol, url, wrapfig, xcolor, xstring
+ Unfortunately MiKTeX automatic install during build doesn't seem to work. If you discover a missing package during build, please add it to this list.
+ [mpm][] command line looks like a good option to do this all at once.
* Install [ImageMagick][], use the recommended download (Q16 precision is fine)
- In the installer, choose 'Install legacy utilities (convert)'
* Make. I suggest using 'Git Bash' from [Git for Windows][], and adding the [MinGW][] binaries, which include `make`, to your path.
### Linux (Ubuntu)
* To get LaTeX, install a TeXLive package. I tried this, on Ubuntu:
`sudo apt install texlive-latex-base`
** This doesn't include the extra packages, same as those missing on Windows. ToDo: how to install missing packages.
* ImageMagick seems to be installed by default on Ubuntu.
## Run Cmake
Follow the instructions in [CONTRIBUTING.md][] to clone the repository.
If you clone like this:
$ mkdir ParaViewGuide; cd ParaViewGuide
$ git clone https://gitlab.kitware.com/paraview/paraview-guide-ce.git src
then:
$ mkdir build; cd build
$ cd build
$ cmake-gui ../src -or- ccmake ../src
* click 'configure'
* You may change whether to build the ParaView Guide and/or the Catalyst User's Guide by changing the options **ENABLE_PARAVIEW_GUIDE** (default: ON) and/or **ENABLE_CATALYST_USERS_GUIDE** (default: OFF)
* Generator: I chose the 'MSYS makefiles' generator, after I added MinGW binaries to the path in my Git Bash shell.
* Click 'Advanced'. MIKTEX_BINARY_PATH should be set to something like "C:/Program Files (x86)/MiKTeX 2.9/miktex/bin/" to allow all the LaTeX binaries to be found.
* You may have to manually set the IMAGEMAGICK_CONVERT path, to something like "C:/Program Files/ImageMagick-7.0.3-Q16/convert.exe", if it complains about finding Windows convert.exe instead.
## Build
$ make
* If any packages are missing, MiKTeX will offer to fetch them. However, this failed for me. Copy the package name from the missing .sty dialog, and then in the main MiKTeX Package Manager, search for the package name and install it. Build again.
* You will have to build at least twice, so that references can be updated correctly. You will see many warnings during the build process.
* On a successful build, the **ParaView/ParaViewUsersGuide.pdf** and/or **ParaViewCatalyst/ParaViewCatalystUsersGuide.pdf** will be generated based on the options you chose in cmake.
Note that `make` can take a long time, especially *rendering* the images.
To speed things, you can edit [ParaViewUsersGuide.tex][] file to change
the documentclass mode to `[draft]`.
\documentclass[draft]{InsightSoftwareGuide}
This will generate the the draft PDF without any images.
[CONTRIBUTING.md]: CONTRIBUTING.md
[Git for Windows]: https://git-scm.com/downloads
[ImageMagick]: http://www.imagemagick.org/script/binary-releases.php
[MikTeX]: http://miktex.org/howto/install-miktex
[MinGW]: http://www.mingw.org/wiki/Getting_Started
[mpm]: http://docs.miktex.org/manual/mpm.html
[ParaView docs]: https://gitlab.kitware.com/paraview/paraview/blob/master/CONTRIBUTING.md
[ParaViewUsersGuide.tex]: ParaView/ParaViewUsersGuide.tex
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment