[904] | 1 | <!-- ******************************************************** --> |
---|
| 2 | <!-- --> |
---|
| 3 | <!-- [History] --> |
---|
| 4 | <!-- 1st version created: Katsuya Amako, Dec-2006 --> |
---|
| 5 | <!-- --> |
---|
| 6 | <!-- ******************************************************** --> |
---|
| 7 | |
---|
| 8 | |
---|
| 9 | <!-- ********************* QandA Section ******************** --> |
---|
| 10 | <section id="qanda.Vis"> |
---|
| 11 | <title> |
---|
| 12 | Visualization |
---|
| 13 | </title> |
---|
| 14 | |
---|
| 15 | <qandaset defaultlabel="qanda"> |
---|
| 16 | |
---|
[1208] | 17 | |
---|
[904] | 18 | <!-- ******* QandA Entry ******** --> |
---|
| 19 | <qandaentry id="qanda.Vis.NoVisAppr"> |
---|
| 20 | |
---|
| 21 | <question><para> |
---|
| 22 | I have set G4VIS... environmental variables but visualization does not |
---|
| 23 | appear to be enabled. |
---|
| 24 | </para></question> |
---|
| 25 | |
---|
| 26 | <answer><para> |
---|
| 27 | This might be because you set the environment variables *after* already |
---|
| 28 | compiling. The environment variables control C-pre-processor macros of |
---|
| 29 | the same name and therefore influence what code gets compiled. It is |
---|
| 30 | suggested to proceed with the following manual procedure to correct the |
---|
| 31 | current installation: |
---|
| 32 | |
---|
| 33 | <itemizedlist spacing="compact"> |
---|
| 34 | <listitem><para> |
---|
| 35 | Configure the environment according to the installation making sure |
---|
| 36 | to -unset- the <literal>G4WORKDIR</literal> environment variable, |
---|
| 37 | if set. |
---|
| 38 | </para></listitem> |
---|
[1208] | 39 | <listitem><para> |
---|
[904] | 40 | Verify and eventually set the environment variables of the |
---|
| 41 | visualization module [name] concerned (setenv or export both |
---|
| 42 | <literal>G4VIS_BUILD_[name]_DRIVER</literal> and |
---|
| 43 | <literal>G4VIS_USE_[name]</literal> variables according to the UNIX |
---|
| 44 | shell used), and then proceed as follows: |
---|
| 45 | |
---|
| 46 | <informalexample><programlisting> |
---|
| 47 | cd $G4INSTALL/source/visualization |
---|
| 48 | gmake clean |
---|
| 49 | gmake |
---|
| 50 | cd $G4INSTALL/source/interfaces |
---|
| 51 | gmake clean |
---|
| 52 | gmake |
---|
| 53 | cd $G4INSTALL/source |
---|
| 54 | gmake libmap |
---|
| 55 | setenv G4WORKDIR [your working directory] (or export) |
---|
| 56 | cd [your application directory] |
---|
| 57 | gmake clean |
---|
| 58 | gmake |
---|
| 59 | </programlisting></informalexample> |
---|
[1208] | 60 | </para></listitem> |
---|
[904] | 61 | </itemizedlist> |
---|
| 62 | |
---|
| 63 | </para></answer> |
---|
| 64 | |
---|
| 65 | </qandaentry> |
---|
| 66 | |
---|
| 67 | |
---|
[1208] | 68 | <!-- ******* QandA Entry ******** --> |
---|
| 69 | <qandaentry id="qanda.Vis.BooleanProc"> |
---|
| 70 | |
---|
| 71 | <question><para> |
---|
| 72 | While visualizing my geometry setup I often see the following error |
---|
| 73 | message printed out: |
---|
| 74 | |
---|
| 75 | <informalexample><programlisting> |
---|
| 76 | BooleanProcessor: boolean operation failed . |
---|
| 77 | </programlisting></informalexample> |
---|
| 78 | </para></question> |
---|
| 79 | |
---|
| 80 | <answer><para> |
---|
| 81 | There is a known limitation for the visualization of Boolean solids |
---|
| 82 | in the so-called BooleanProcessor which is used to make polyhedra |
---|
| 83 | for visualisation. It does not affect the tracking which is done |
---|
| 84 | through such solids. So the error message you see does not affect |
---|
| 85 | the simulation in any way. The workaround is to move one of the |
---|
| 86 | affected solids by a small distance in order to avoid shared surfaces. |
---|
| 87 | </para></answer> |
---|
| 88 | |
---|
| 89 | </qandaentry> |
---|
| 90 | |
---|
| 91 | |
---|
[904] | 92 | </qandaset> |
---|
| 93 | </section> |
---|