Trying to upgrade to v11.1.1 from v10.7.4

[villaa]

Please fill out the following information to help in answering your question, and also see tips for posting code snippets

Geant4 Version: moving from v10.7.4 to v11.1.1
Operating System: Ubuntu 20
Compiler/Version: gcc 9.4.0

---

I am have compiled the code and linked external libraries (ROOT) successfully, with everything installed under the cxx17 standard–note I had to install root from source for this reason b/c the binary used cxx14.

In any case all compiled, user code seems to run OK at first but I get the following error, any ideas?

Some /vis commands (optionally) take a string to specify colour.
"/vis/list" to see available colours.

**************************************************************
 Geant4 version Name: geant4-11-01-patch-01 [MT]   (10-February-2023)
                       Copyright : Geant4 Collaboration
                      References : NIM A 506 (2003), 250-303
                                 : IEEE-TNS 53 (2006), 270-278
                                 : NIM A 835 (2016), 186-225
                             WWW : http://geant4.org/
**************************************************************

He isotope 1 is A = 3, relative abundance: 1.37e-06
He isotope 2 is A = 4, relative abundance: 0.999999
Is the He natural abundance distribution? 1
G4Material WARNING: duplicate name of material Aluminum

-------- EEEE ------- G4Exception-START -------- EEEE -------
*** G4Exception : mat205
      issued by : G4MaterialPropertiesTable::AddProperty()
Attempting to create a new material property key SCINTILLATION without setting
createNewKey parameter of AddProperty to true.
*** Fatal Exception *** core dump ***
 **** Track information is not available at this moment
 **** Step information is not available at this moment

-------- EEEE -------- G4Exception-END --------- EEEE -------

[mkelsey]

This looks like one of the new features of Geant4 11, which is going to create problems for CDMS and for G4CMP. The materials property stuff now has a hardcoded list of name strings that it knows. It’ll throw an error if you try to set a key with a misspelled name (very useful!), and will also throw and error if you try to add a key that isn’t on the list.

If I read the error message correctly, there’s now an optional extra argument to AddProperty(), which you have to pass “true” if you’re sure you want to set a different key.

In your case, you may want to check the Release Notes, because SCINTILLATION may no longer be a valid key, replaced by a more complex set of keys.