Mock Version: 2.9 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/TheP8I.spec'], chrootPath='/var/lib/mock/epel-7-x86_64-1611775033.207788/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=0uid=1001gid=135user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.hgzox7b5:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']unshare_net=FalseprintOutput=True) Using nspawn with args ['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.hgzox7b5:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11'] Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '704aa88d47604e29b5c6a877cfed2f2b', '-D', '/var/lib/mock/epel-7-x86_64-1611775033.207788/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.hgzox7b5:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;\\007"', '--setenv=PS1= \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/TheP8I.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0'} and shell False Building target platforms: x86_64 Building for target x86_64 Wrote: /builddir/build/SRPMS/TheP8I-2.0.1-1.el7.src.rpm Child return code was: 0 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/TheP8I.spec'], chrootPath='/var/lib/mock/epel-7-x86_64-1611775033.207788/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=0uid=1001gid=135user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.hgzox7b5:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']unshare_net=FalseprintOutput=True) Using nspawn with args ['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.hgzox7b5:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11'] Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '16581d33dfa04a8e8f9c3271b486aab1', '-D', '/var/lib/mock/epel-7-x86_64-1611775033.207788/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.hgzox7b5:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;\\007"', '--setenv=PS1= \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/TheP8I.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0'} and shell False Building target platforms: x86_64 Building for target x86_64 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.yVn4n6 + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf TheP8I-2.0.0 + /usr/bin/gzip -dc /builddir/build/SOURCES/TheP8I-2.0.0.tar.gz + /usr/bin/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd TheP8I-2.0.0 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.hWGqQ0 + umask 022 + cd /builddir/build/BUILD + cd TheP8I-2.0.0 + cat + scl enable devtoolset-8 -- checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether make supports nested variables... (cached) yes checking for style of include used by make... GNU checking for g++... g++ checking whether the C++ compiler works... yes checking for C++ compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... none checking for ar... ar checking the archiver (ar) interface... ar checking whether we are using the GNU C++ compiler... (cached) yes checking whether g++ accepts -g... (cached) yes checking dependency style of g++... (cached) none checking whether g++ supports C++11 features with -std=c++11... yes checking whether make sets $(MAKE)... (cached) yes checking whether ln -s works... yes checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking how to print strings... printf checking for gcc... gcc checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... none checking for a sed that does not truncate output... /usr/bin/sed checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for fgrep... /usr/bin/grep -F checking for ld used by gcc... /opt/rh/devtoolset-8/root/usr/libexec/gcc/x86_64-redhat-linux/8/ld checking if the linker (/opt/rh/devtoolset-8/root/usr/libexec/gcc/x86_64-redhat-linux/8/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /opt/rh/devtoolset-8/root/usr/bin/nm -B checking the name lister (/opt/rh/devtoolset-8/root/usr/bin/nm -B) interface... BSD nm checking the maximum length of command line arguments... 1572864 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop checking for /opt/rh/devtoolset-8/root/usr/libexec/gcc/x86_64-redhat-linux/8/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for dlltool... no checking how to associate runtime and link libraries... printf %s\n checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... ranlib checking command to parse /opt/rh/devtoolset-8/root/usr/bin/nm -B output from gcc object... ok checking for sysroot... no checking for mt... no checking if : is a manifest tool... no checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... no checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/opt/rh/devtoolset-8/root/usr/libexec/gcc/x86_64-redhat-linux/8/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking for shl_load... no checking for shl_load in -ldld... no checking for dlopen... no checking for dlopen in -ldl... yes checking whether a program can dlopen itself... yes checking whether a statically linked program can dlopen itself... yes checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no checking how to run the C++ preprocessor... g++ -std=c++11 -E checking for ld used by g++ -std=c++11... /opt/rh/devtoolset-8/root/usr/libexec/gcc/x86_64-redhat-linux/8/ld -m elf_x86_64 checking if the linker (/opt/rh/devtoolset-8/root/usr/libexec/gcc/x86_64-redhat-linux/8/ld -m elf_x86_64) is GNU ld... yes checking whether the g++ -std=c++11 linker (/opt/rh/devtoolset-8/root/usr/libexec/gcc/x86_64-redhat-linux/8/ld -m elf_x86_64) supports shared libraries... yes checking for g++ -std=c++11 option to produce PIC... -fPIC -DPIC checking if g++ -std=c++11 PIC flag -fPIC -DPIC works... yes checking if g++ -std=c++11 static flag -static works... no checking if g++ -std=c++11 supports -c -o file.o... yes checking if g++ -std=c++11 supports -c -o file.o... (cached) yes checking whether the g++ -std=c++11 linker (/opt/rh/devtoolset-8/root/usr/libexec/gcc/x86_64-redhat-linux/8/ld -m elf_x86_64) supports shared libraries... yes checking dynamic linker characteristics... (cached) GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking if THEPEGPATH is set... no (found /usr) checking if the installed ThePEG works... yes checking for gsl location... in system libraries checking for sqrt in -lm... yes checking for cblas_srot in -lgslcblas... yes checking for gsl_ran_poisson in -lgsl... yes checking for /usr/share/Pythia8/xmldoc/Index.xml... yes checking if Pythia8 library and headers are present and working... /usr checking for perl... /usr/bin/perl checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating test/Makefile config.status: creating doc/Makefile config.status: creating doc/refman.conf config.status: creating Makefile config.status: creating bin/fixinterfaces.pl config.status: creating bin/P8Particles.pl config.status: creating bin/interfaces.pl config.status: executing depfiles commands config.status: executing libtool commands bin/interfaces.pl --var include/TheP8I/Hadronization/StringFragmentation StringFragmentation StringZ StringPT StringFlav FragmentationSystems MiniStringFragmentation HadronLevel bin/interfaces.pl --init include/TheP8I/Hadronization/StringFragmentation StringFragmentation StringZ StringPT StringFlav FragmentationSystems MiniStringFragmentation HadronLevel bin/interfaces.pl --input include/TheP8I/Hadronization/StringFragmentation StringFragmentation StringZ StringPT StringFlav FragmentationSystems MiniStringFragmentation HadronLevel bin/interfaces.pl --output include/TheP8I/Hadronization/StringFragmentation StringFragmentation StringZ StringPT StringFlav FragmentationSystems MiniStringFragmentation HadronLevel bin/interfaces.pl --interfaces include/TheP8I/Hadronization/StringFragmentation StringFragmentation StringZ StringPT StringFlav FragmentationSystems MiniStringFragmentation HadronLevel bin/interfaces.pl --var include/TheP8I/BE/BoseEinsteinHandler BoseEinstein bin/interfaces.pl --init include/TheP8I/BE/BoseEinsteinHandler BoseEinstein bin/interfaces.pl --input include/TheP8I/BE/BoseEinsteinHandler BoseEinstein bin/interfaces.pl --output include/TheP8I/BE/BoseEinsteinHandler BoseEinstein bin/interfaces.pl --interfaces include/TheP8I/BE/BoseEinsteinHandler BoseEinstein make all-recursive make[1]: Entering directory `/builddir/build/BUILD/TheP8I-2.0.0' Making all in . make[2]: Entering directory `/builddir/build/BUILD/TheP8I-2.0.0' CXX libTheP8IBE_la-BoseEinsteinHandler.lo CXXLD libTheP8IBE.la CXX libTheP8IConfig_la-RndmEngine.lo CXX libTheP8IConfig_la-Pythia8Interface.lo CXXLD libTheP8IConfig.la CXX libTheP8IString_la-StringFragmentation.lo CXX libTheP8IString_la-StringPipe.lo CXX libTheP8IString_la-OverlapPythiaHandler.lo CXX libTheP8IString_la-ParameterHandler.lo CXX libTheP8IString_la-RandomAverageHandler.lo CXX libTheP8IString_la-RandomHandler.lo CXX libTheP8IString_la-Ropewalk.lo CXXLD libTheP8IString.la CXX libTheP8IStrategy_la-TheP8IStrategy.lo CXXLD libTheP8IStrategy.la CCLD libTheP8I.la bin/P8Particles.pl /usr/share/Pythia8/xmldoc/ParticleData.xml > share/TheP8IParticles.in mkdir -p lib; cd lib;\ for sofile in ../.libs/*.so* ../.libs/*.dylib* ../.libs/*.la; \ do if test -f $sofile; then ln -s -f $sofile .; fi; done; cd lib;\ for sofile in .libs/*.so* .libs/*.dylib*; \ do if test -f $sofile; then ln -s -f $sofile .; fi; done echo "stamp" > done-all-links /usr/bin/setupThePEG -Llib -L/usr/lib64/ThePEG --exitonerror --init -r /usr/lib64/ThePEG/ThePEGDefaults.rpo -o lib/TheP8IDefaults.rpo share/TheP8IDefaults.in Using duplicate PDGName d for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName d for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName dbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName dbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName u for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName u for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName s for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName s for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName t for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName t for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName b' for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName b' for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName b'bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName b'bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName t' for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName t' for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName t'bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName t'bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_e for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_e for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_ebar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_ebar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName mu- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName mu- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName mu+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName mu+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_mu for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_mu for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_mubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_mubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_tau for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_tau for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_taubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_taubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau'- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau'- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau'+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau'+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu'_tau for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu'_tau for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu'_taubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu'_taubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName g for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName g for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName gamma for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName gamma for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Z0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Z0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName h0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName h0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Z'0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Z'0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W'+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W'+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W'- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W'- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName A0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName A0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Graviton for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Graviton for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName R0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName R0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Rbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Rbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName LQ_ue for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName LQ_ue for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName LQ_uebar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName LQ_uebar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName a_20 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName a_20 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K_L0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K_L0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName a_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName a_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName a_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName a_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName omega for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName omega for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName f_2 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName f_2 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K_S0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K_S0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Kbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Kbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta' for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta' for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName phi for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName phi for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Dbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Dbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta_c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta_c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Jpsi for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Jpsi for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_2c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_2c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_20 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_20 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta_b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta_b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Upsilon for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Upsilon for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_2b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_2b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName dd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName dd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName dd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName dd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName n0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName n0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName uu_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName uu_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName uu_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName uu_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName p+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName p+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigmabar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigmabar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*bar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*bar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambdabar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambdabar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigmabar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigmabar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigmabar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigmabar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*bar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*bar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ss_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ss_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ss_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ss_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xibar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xibar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*bar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*bar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xibar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xibar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omegabar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omegabar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_c++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_c++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_cbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_cbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_c++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_c++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_cbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_cbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cc_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cc_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cc_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cc_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cc++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cc++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_ccbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_ccbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cc++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cc++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_ccbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_ccbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_ccc++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_ccc++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_b+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_b+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_bbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_bbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_b+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_b+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_bbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_bbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bcbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bcbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bcbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bcbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bcbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bcbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega'_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega'_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bcc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bcc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bcc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bcc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bb_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bb_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bb_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bb_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bb0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bb0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bb0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bb0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_00 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_00 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_0c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_0c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName h_1c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName h_1c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_00 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_00 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_0b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_0b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName h_1b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName h_1b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_1c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_1c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_1b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_1b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_L- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_L- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_L+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_L+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eL for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eL for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eLbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eLbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_L- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_L- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_L+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_L+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muL for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muL for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muLbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muLbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauL for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauL for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauLbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauLbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~g for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~g for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_20 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_20 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_30 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_30 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_40 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_40 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~Gravitino for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~Gravitino for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_2 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_2 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_2bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_2bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_2 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_2 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_2bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_2bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_R- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_R- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_R+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_R+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eR for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eR for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eRbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eRbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_R- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_R- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_R+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_R+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muR for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muR for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muRbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muRbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauR for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauR for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauRbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauRbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_tc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_tc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_tc- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_tc- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_tc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_tc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_tc- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_tc- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi'_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi'_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName omega_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName omega_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName V8_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName V8_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_22_1_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_22_1_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_11_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_11_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_22_8_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_22_8_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_12_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_12_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_21_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_21_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_22_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_22_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName d* for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName d* for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName d*bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName d*bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName u* for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName u* for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName u*bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName u*bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e*bar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e*bar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu*_e0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu*_e0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu*_ebar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu*_ebar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Graviton* for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Graviton* for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_Re for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_Re for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_Rmu for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_Rmu for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_Rtau for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_Rtau for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Z_R0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Z_R0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W_R+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W_R+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W_R- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W_R- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_L++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_L++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_L-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_L-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_R++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_R++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_R-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_R-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_diff0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_diff0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_diffr+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_diffr+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_diffr- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_diffr- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName omega_di for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName omega_di for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName phi_diff for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName phi_diff for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Jpsi_di for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Jpsi_di for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName n_diffr0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName n_diffr0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName n_diffrbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName n_diffrbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName p_diffr+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName p_diffr+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName p_diffrbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName p_diffrbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. make[2]: Leaving directory `/builddir/build/BUILD/TheP8I-2.0.0' Making all in test make[2]: Entering directory `/builddir/build/BUILD/TheP8I-2.0.0/test' CXX TestJunctions_la-TestJunctions.lo CXXLD TestJunctions.la libtool: link: warning: `-version-info/-version-number' is ignored for convenience libraries make[2]: Leaving directory `/builddir/build/BUILD/TheP8I-2.0.0/test' Making all in doc make[2]: Entering directory `/builddir/build/BUILD/TheP8I-2.0.0/doc' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/builddir/build/BUILD/TheP8I-2.0.0/doc' make[1]: Leaving directory `/builddir/build/BUILD/TheP8I-2.0.0' + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.rcFyJQ + umask 022 + cd /builddir/build/BUILD + '[' /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64 '!=' / ']' + rm -rf /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64 ++ dirname /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64 + mkdir -p /builddir/build/BUILDROOT + mkdir /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64 + cd TheP8I-2.0.0 + /usr/bin/make install DESTDIR=/builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64 /usr/bin/make install-recursive make[1]: Entering directory `/builddir/build/BUILD/TheP8I-2.0.0' Making install in . make[2]: Entering directory `/builddir/build/BUILD/TheP8I-2.0.0' /usr/bin/setupThePEG -Llib -L/usr/lib64/ThePEG --exitonerror --init -r /usr/lib64/ThePEG/ThePEGDefaults.rpo -o lib/TheP8IDefaults.rpo share/TheP8IDefaults.in Using duplicate PDGName d for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName d for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName dbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName dbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName u for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName u for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName s for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName s for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName t for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName t for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName b' for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName b' for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName b'bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName b'bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName t' for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName t' for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName t'bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName t'bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_e for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_e for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_ebar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_ebar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName mu- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName mu- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName mu+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName mu+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_mu for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_mu for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_mubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_mubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_tau for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_tau for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_taubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_taubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau'- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau'- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau'+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName tau'+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu'_tau for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu'_tau for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu'_taubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu'_taubar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName g for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName g for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName gamma for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName gamma for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Z0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Z0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName h0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName h0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Z'0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Z'0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W'+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W'+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W'- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W'- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName A0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName A0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Graviton for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Graviton for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName R0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName R0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Rbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Rbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName LQ_ue for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName LQ_ue for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName LQ_uebar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName LQ_uebar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName a_20 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName a_20 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K_L0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K_L0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName a_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName a_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName a_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName a_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName omega for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName omega for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName f_2 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName f_2 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K_S0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K_S0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Kbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Kbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName K*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta' for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta' for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName phi for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName phi for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Dbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Dbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta_c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta_c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Jpsi for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Jpsi for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_2c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_2c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_20 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_20 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_2c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta_b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta_b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Upsilon for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Upsilon for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_2b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_2b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName dd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName dd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName dd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName dd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ud_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName n0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName n0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName uu_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName uu_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName uu_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName uu_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName p+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName p+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Delta++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Deltabar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName sd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigmabar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigmabar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*bar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*bar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambdabar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambdabar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName su_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigmabar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigmabar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigmabar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigmabar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*bar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*bar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ss_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ss_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ss_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ss_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xibar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xibar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*bar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*bar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xibar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xibar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omegabar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omegabar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cu_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_c++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_c++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_cbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_cbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_c++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_c++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_cbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_cbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cs_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_c0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_cbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cc_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cc_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cc_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName cc_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cc++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_cc++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_ccbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_ccbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cc++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_cc++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_ccbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_ccbar-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_cc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_ccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_ccc++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_ccc++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bd_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Lambda_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bu_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_b+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_b+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_bbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma_bbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_b+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_b+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_bbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Sigma*_bbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bcbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bcbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bs_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_b0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_b- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_0bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bc_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bcbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi'_bcbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bcbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bcbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega'_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega'_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bcc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bcc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bcc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bcc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bccbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bb_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bb_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bb_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName bb_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bb0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bb0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi_bbbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bb0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bb0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Xi*_bbbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega_bbcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbcbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbb- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Omega*_bbbbar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_00 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_00 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_0s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D_1s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_0c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_0c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName h_1c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName h_1c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_00 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_00 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_0c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B_1c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_0b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_0b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName h_1b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName h_1b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1s+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName D*_1s- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_1c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_1c for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1bar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1s0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1sbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1c+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName B*_1c- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_1b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName chi_1b for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_L for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_Lbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_1 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_1bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_L- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_L- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_L+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_L+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eL for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eL for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eLbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eLbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_L- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_L- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_L+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_L+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muL for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muL for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muLbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muLbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauL for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauL for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauLbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauLbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~g for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~g for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_10 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_20 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_20 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_1+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_1- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_30 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_30 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_40 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_40 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~chi_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~Gravitino for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~Gravitino for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~d_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~u_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~s_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_R for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~c_Rbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_2 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_2 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_2bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~b_2bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_2 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_2 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_2bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~t_2bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_R- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_R- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_R+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~e_R+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eR for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eR for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eRbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_eRbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_R- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_R- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_R+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~mu_R+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muR for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muR for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muRbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_muRbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_2- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~tau_2+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauR for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauR for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauRbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName ~nu_tauRbar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_tc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_tc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_tc- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_tc- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_tc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_tc+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_tc- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_tc- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi'_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi'_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName omega_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName omega_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName eta_tc0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName V8_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName V8_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_22_1_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_22_1_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_11_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_11_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_22_8_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_22_8_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_12_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_12_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_21_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_21_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_22_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_22_tc for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName d* for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName d* for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName d*bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName d*bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName u* for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName u* for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName u*bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName u*bar for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e*- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e*bar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName e*bar+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu*_e0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu*_e0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu*_ebar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu*_ebar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Graviton* for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Graviton* for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_Re for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_Re for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_Rmu for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_Rmu for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_Rtau for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName nu_Rtau for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Z_R0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Z_R0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W_R+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W_R+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W_R- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName W_R- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_L++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_L++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_L-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_L-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_R++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_R++ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_R-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName H_R-- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_diff0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName rho_diff0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_diffr+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_diffr+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_diffr- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName pi_diffr- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName omega_di for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName omega_di for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName phi_diff for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName phi_diff for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Jpsi_di for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName Jpsi_di for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName n_diffr0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName n_diffr0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName n_diffrbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName n_diffrbar0 for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName p_diffr+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName p_diffr+ for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName p_diffrbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. Using duplicate PDGName p_diffrbar- for a new particle. This can cause problems and is not recommended. If this second particle is a new particle in a BSM Model we recommend you change the name of the particle. make[3]: Entering directory `/builddir/build/BUILD/TheP8I-2.0.0' /usr/bin/mkdir -p '/builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/lib64/ThePEG' /bin/sh ./libtool --mode=install /usr/bin/install -c libTheP8I.la '/builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/lib64/ThePEG' libtool: install: /usr/bin/install -c .libs/libTheP8I.so.0.0.0 /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/lib64/ThePEG/libTheP8I.so.0.0.0 libtool: install: (cd /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/lib64/ThePEG && { ln -s -f libTheP8I.so.0.0.0 libTheP8I.so.0 || { rm -f libTheP8I.so.0 && ln -s libTheP8I.so.0.0.0 libTheP8I.so.0; }; }) libtool: install: (cd /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/lib64/ThePEG && { ln -s -f libTheP8I.so.0.0.0 libTheP8I.so || { rm -f libTheP8I.so && ln -s libTheP8I.so.0.0.0 libTheP8I.so; }; }) libtool: install: /usr/bin/install -c .libs/libTheP8I.lai /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/lib64/ThePEG/libTheP8I.la libtool: install: warning: remember to run `libtool --finish /usr/lib64/ThePEG' /usr/bin/mkdir -p '/builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/share/TheP8I' /usr/bin/install -c -m 644 share/TheP8IDefaults.in share/TheP8IRemove.in share/OverlapStringFragmenter.in '/builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/share/TheP8I' /usr/bin/mkdir -p '/builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/share/TheP8I' /usr/bin/install -c -m 644 share/TheP8IParticles.in '/builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/share/TheP8I' make[3]: Leaving directory `/builddir/build/BUILD/TheP8I-2.0.0' make[2]: Leaving directory `/builddir/build/BUILD/TheP8I-2.0.0' Making install in test make[2]: Entering directory `/builddir/build/BUILD/TheP8I-2.0.0/test' make[3]: Entering directory `/builddir/build/BUILD/TheP8I-2.0.0/test' make[3]: Nothing to be done for `install-exec-am'. /usr/bin/mkdir -p '/builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/share/TheP8I' /usr/bin/install -c -m 644 SimpleLEP.in SimpleLHC.in HerwigLEP.in HerwigLEPTheP8I.in HerwigDIS.in HerwigDISTheP8I.in HerwigLHC.in HerwigLHCTheP8I.in TestJunctions.in '/builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/share/TheP8I' make[3]: Leaving directory `/builddir/build/BUILD/TheP8I-2.0.0/test' make[2]: Leaving directory `/builddir/build/BUILD/TheP8I-2.0.0/test' Making install in doc make[2]: Entering directory `/builddir/build/BUILD/TheP8I-2.0.0/doc' make[3]: Entering directory `/builddir/build/BUILD/TheP8I-2.0.0/doc' make[3]: Nothing to be done for `install-exec-am'. if test -d refman-html; then /usr/bin/mkdir -p /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/share/TheP8I/doc;\ find refman-html -follow -name '*.*' \ -exec /bin/sh /builddir/build/BUILD/TheP8I-2.0.0/install-sh -c -m 644 \{\} /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/share/TheP8I/doc/\{\} \;; \ /bin/sh /builddir/build/BUILD/TheP8I-2.0.0/install-sh -c -m 644 TheP8I-refman.tag /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/share/TheP8I/doc/TheP8I-refman.tag; fi if test -d refman-latex -a -f refman-latex/refman.pdf; then \ /bin/sh /builddir/build/BUILD/TheP8I-2.0.0/install-sh -c -m 644 refman-latex/refman.pdf /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/share/TheP8I/doc/refman.pdf; fi make[3]: Leaving directory `/builddir/build/BUILD/TheP8I-2.0.0/doc' make[2]: Leaving directory `/builddir/build/BUILD/TheP8I-2.0.0/doc' make[1]: Leaving directory `/builddir/build/BUILD/TheP8I-2.0.0' + /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /builddir/build/BUILD/TheP8I-2.0.0 extracting debug info from /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64/usr/lib64/ThePEG/libTheP8I.so.0.0.0 dwz: Too few files for multifile optimization /usr/lib/rpm/sepdebugcrcfix: Updated 1 CRC32s, 0 CRC32s did match. symlinked /usr/lib/debug/usr/lib64/ThePEG/libTheP8I.so.0.0.0.debug to /usr/lib/debug/usr/lib64/ThePEG/libTheP8I.so.debug symlinked /usr/lib/debug/usr/lib64/ThePEG/libTheP8I.so.0.0.0.debug to /usr/lib/debug/usr/lib64/ThePEG/libTheP8I.so.0.debug 502 blocks + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/redhat/brp-compress + /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1 + /usr/lib/rpm/redhat/brp-python-hardlink + /usr/lib/rpm/redhat/brp-java-repack-jars Processing files: TheP8I-2.0.1-1.el7.x86_64 Provides: TheP8I = 2.0.1-1.el7 TheP8I(x86-64) = 2.0.1-1.el7 libTheP8I.so.0()(64bit) libtool(/usr/lib64/ThePEG/libTheP8I.la) Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: libTheP8I.so.0()(64bit) libc.so.6()(64bit) libc.so.6(GLIBC_2.14)(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libgcc_s.so.1()(64bit) libgcc_s.so.1(GCC_3.0)(64bit) libpythia8-8.2.44.so()(64bit) rtld(GNU_HASH) Processing files: TheP8I-debuginfo-2.0.1-1.el7.x86_64 Provides: TheP8I-debuginfo = 2.0.1-1.el7 TheP8I-debuginfo(x86-64) = 2.0.1-1.el7 Requires(rpmlib): rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64 Wrote: /builddir/build/RPMS/TheP8I-2.0.1-1.el7.x86_64.rpm Wrote: /builddir/build/RPMS/TheP8I-debuginfo-2.0.1-1.el7.x86_64.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.R4htYU + umask 022 + cd /builddir/build/BUILD + cd TheP8I-2.0.0 + /usr/bin/rm -rf /builddir/build/BUILDROOT/TheP8I-2.0.1-1.el7.x86_64 + exit 0 Child return code was: 0