Will there be any EGSnrc course soon? Anywere, anytime?
Hi, what is the problem about “Building the EGSnrc C++ class library … Failed”?
Hi, what is the problem about “Building the EGSnrc C++ class library … Failed”?
the compiled info:
yuan@ubuntu:~/EGSnrc/EGSnrc_with_egs_brachy$ ./HEN_HOUSE/scripts/configure
###############################################################################
configure
###############################################################################
Copyright (C) 2015 National Research Council Canada
This program comes with ABSOLUTELY NO WARRANTY. This is free software, and you
are welcome to redistribute it under certain conditions. See LICENCE file for
details or http://www.gnu.org/licenses/agpl.txt
###############################################################################
EGSnrc configuration script.
This script configures EGSnrc for use on your system. The configuration
options will be saved in a configuration file inside the $HEN_HOUSE/specs
directory. You can use this configuration by setting the environment variable
$EGS_CONFIG to the path of the configuration file.
You can use this script to generate as many different configurations as you
wish (for instance, you may have different compilers installed or various
operating systems on the same file system). If the environment variable
$HEN_HOUSE is set for previous EGSnrc installations, it should probably be
unset prior to calling this script.
This script will ask you questions to configure EGSnrc.
Any response you enter overrides the suggested default shown in brackets.
This implies that if you want to add something to the default answer, you
must re-type this default answer as part of your response.
To accept the default answer shown in brackets: just press enter.
To submit an empty answer, overriding the default: enter ‘–‘ as a response.
To get help for some questions requiring input: enter ‘?’ as a response.
###############################################################################
You can exit this script at any time by typing Ctrl-C.
Press enter to continue.
Checking system type … x86_64-unknown-linux-gnu
Checking for make … yes (/usr/bin/make)
Looking for installed fortran compilers … OK
Found the following FORTRAN compilers in your search path:
gfortran f77 f95
Input fortran compiler: [gfortran]
Testing if gfortran works … yes. Object extension is ‘o’
Testing if gfortran can create executables … yes. Extension is ”
Checking for compiler version … don’t know
Input standard compilation flags: [-fPIC]
Input optimization flags: [-O2]
Input flags for debugging: [-g]
Input libraries that your compiler may need:
Will use the following compiler settings:
F77 = gfortran
FCFLAGS = -fPIC
FDEBUG = -g
FOPT = -O2
FLIBS =
Testing if compilation flags work … yes
Checking for the availability of various system dependent functions:
Checking for a working ‘exit’ subroutine … yes (exit)
Checking if ‘system’ is a function … yes
Checking for the ‘date_and_time’ subroutine … yes
Checking for the ‘flush’ subroutine … yes (flush)
Checking for the ‘fdate’ subroutine … yes (fdate)
Checking for the ‘secnds’ function … yes (secnds)
Checking for the ‘date’ subroutine … no
Checking for the ‘time’ subroutine … no
Checking for the ‘etime’ function … yes (etime)
Checking for the ‘lnblnk’ function … yes
Checking for the ‘hostnm’ function … yes (hostnm)
Testing if hostnm works … yes (returns ubuntu)
Checking for the ‘lstat’ function … yes
Checking if lstat works … yes
Checking if inquire works on directories … yes
Checking for record length … 4
Checking for the endianess of the machine … little endian
Checking for integer*8 … yes
Checking for integer*2 … yes
Looking for C compilers installed on your system … gcc cc c89
Input the one you would like to use: [gcc]
Input C compiler flags to use: [-O2 -fPIC]
Checking for fortran name mangling scheme … lower case, _ and _
Input path to EGSnrc HEN_HOUSE directory: [/home/yuan/EGSnrc/EGSnrc_with_egs_brachy/HEN_HOUSE]
Choose a configuration file name: [linux.conf]
Using HEN_HOUSE = /home/yuan/EGSnrc/EGSnrc_with_egs_brachy/HEN_HOUSE
configuration file = linux.conf
configuration name = linux
Creating lib/linux directory … OK
Creating egs_config1.h … OK
Creating egs_c_utils.h and egs_c_utils.c … OK
Compiling egs_c_utils.c … OK
Creating load_beamlib.o … OK
Creating load_vculib.o … OK
Creating read_write_pardose … OK
Creating dosxyznrc_linux.spec … OK
Library needed for dlopen … -ldl
Creating config file linux.conf … OK
Creating machine.macros … OK
Creating machine.f … OK
Creating machine.mortran … OK
Creating bin directory … OK
Creating bin/linux directory … OK
Creating log directory … OK
Compiling mortran3 … OK
Compiling pegs4 … OK
Compiling beam_build … OK
Compiling beamdp … OK
Compiling ctcreate … Failed
Compiling statdose … OK
Compiling readphsp … OK
Compiling dosxyz_show … OK
Compiling addphsp … OK
Looking for installed C++ compilers … OK
Found the following C++ compilers in your search path:
g++
Input C++ compiler: [g++]:
Determining Fortran libraries for g++ linking … OK
Using the following compiler/linker switches for creating/linking against
dynamic shared objects (DSO, also known as shared library or DLL), where
$(abs_dso) or $(ABS_DSO) below will be replaced with the absolute path to the
EGSnrc DSO directory at compile/link time:
1) Optimization options: -O3 -ffast-math
2) Generation of position independent code: -fPIC
3) Preprocessor defines:
4) Flag for creating shared libraries: -shared
5) Output/dlopen library: -o $@ -ldl
6) DSO path encoded in the executable: -L$(abs_dso) -Wl,-rpath,$(abs_dso)
7) Linking against library some_lib: -lsome_lib
8) Fortran libraries needed by C++ linker: -lgfortran -lquadmath
Input option to change, or enter to proceed:
Creating C++ config file … OK
Building the IAEA phase space library … OK
Building the EGSnrc C++ class library … Failed
These settings did not work out. You may edit the source code
(in case you can see where the problem is when building the C++ libraries
from the configure.log file) and/or try different compiler/linker options.
Do you want to retry? (yes/no) yes
Determining Fortran libraries for g++ linking … OK
Using the following compiler/linker switches for creating/linking against
dynamic shared objects (DSO, also known as shared library or DLL), where
$(abs_dso) or $(ABS_DSO) below will be replaced with the absolute path to the
EGSnrc DSO directory at compile/link time:
1) Optimization options: -O3 -ffast-math
2) Generation of position independent code: -fPIC
3) Preprocessor defines:
4) Flag for creating shared libraries: -shared
5) Output/dlopen library: -o $@ -ldl
6) DSO path encoded in the executable: -L$(abs_dso) -Wl,-rpath,$(abs_dso)
7) Linking against library some_lib: -lsome_lib
8) Fortran libraries needed by C++ linker: -lgfortran -lquadmath
Input option to change, or enter to proceed:
Creating C++ config file … OK
Building the IAEA phase space library … OK
Building the EGSnrc C++ class library … Failed
These settings did not work out. You may edit the source code
(in case you can see where the problem is when building the C++ libraries
from the configure.log file) and/or try different compiler/linker options.
Do you want to retry? (yes/no)
http://www.gnu.org/licenses/agpl.txt//cdn.embedly.com/widgets/platform.js
Hi again
Hi again
I have problem with downloading the EGSnrc-configure-linux file. It’s not possible to download. Is it possible to share with me, if anyone have this file?
Hi everyone
Hi everyone
Is it possible to install #egs_brachy on windows? Installed folder is empty.
Hi all

Hi all,
I need some advice from people to use egs_view.
Creation does not work in ~ / EGSnrc / HEN_HOUSE / egs ++ / view $.
I’m trying to make makefile, I went to HEN_HOUSE / egs ++ / view to edit the path to qmake in make file, but the result I got was:
Best regards,
Hi everyone

Hi everyone,
I have a problem when configuring EGS on Windows 7. (see attached picture).
The configuration executable that I find on the suggested page on github is different than the one described on github.
Could anybody help me find the missing paths?
Cheers,
Abbas
If I run say egs_chamber it reports some dose for each geometry to me.
If I run say egs_chamber it reports some dose for each geometry to me. This dose is somehow normalized. For example its expected value does not depend on ncase. Its normalization seems to also depend on the simulation source. For instance scoring dose in the middle of a 5×5 and 40×40 beam give same dose up to maybe a factor of 2. My question is, how exactly is the dose reported by egs defined?
Hi everyone
Hi everyone,
I am using egs_brachy to simulate about 30 I-125 seeds in an egsphant generated from CT scans.
I used the “x and y” values displayed in dosxyz_show and arbitrary z coordinates with the Z-range of egsphant as source locations in the transformation blocks and a wrapper geometry.
I got the error message for 30 source locations;
“1EB_Application::simulateSingleShower() – Paticle initiated outside geometry! Please check your source locations”
and ” EGS_AEnvelope:: Failed to find any regions with inscribed geometries” for few source locations (10 seeds).
How are the seed locations define with respect to egsphant coordinate when viewed with dosxyz_show?
Is it possible to preview the simulation geometries (seeds in egsphant)?
Do I need to define a wrapper geometry for each seed?
Thanks very much in advance
Isong
Hi all
Hi all,
Now I’m new to EGSnrc, and I would like to ask your help.
I want to do parallel jobs in DOSXYZnrc using isource=9 with a single phase space file.
A single interactive job can be done with above condition, but the batch parallel jobs fail with no errors (at least I could not find).
It looks like that the jobs are terminated when the job is thrown to scheduler.
I think I could correctly compile the machine using BEAMnrc as a shared object.
I’m using batch scheduler of PBS.
Do you have any ideas?
A new getting-started manual is available!
A new getting-started manual is available! Even a seasoned EGSpert might learn a few tricks. Feel free to post feedback here if you have questions or find any mistakes in the text.
http://nrc-cnrc.github.io/EGSnrc/doc/getting-started.pdf//cdn.embedly.com/widgets/platform.js