You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was recently working with a spack build of sbndcode@09_91_02_01 and found that some of their .fcl files could not run due to the addition of PFPModuleLabel in larreco's GnocchiCalorimetry. This was due to sbncode and larsoft being out of step with larreco in our spack build.
I was able to rebuild using the appropriate larreco version, and the .fcl file now runs, but is there a plan to put in stricter versioning requirements in the default larsoft spack recipes to avoid similar scenarios in the future? Or is the intent for the user to specify specific versions of all "lar" packages when concretizing? Was mainly just wondering if there was an agreed upon solution to this general problem that had not yet been implemented.
The text was updated successfully, but these errors were encountered:
I was recently working with a spack build of sbndcode@09_91_02_01 and found that some of their .fcl files could not run due to the addition of PFPModuleLabel in larreco's GnocchiCalorimetry. This was due to sbncode and larsoft being out of step with larreco in our spack build.
I was able to rebuild using the appropriate larreco version, and the .fcl file now runs, but is there a plan to put in stricter versioning requirements in the default larsoft spack recipes to avoid similar scenarios in the future? Or is the intent for the user to specify specific versions of all "lar" packages when concretizing? Was mainly just wondering if there was an agreed upon solution to this general problem that had not yet been implemented.
The text was updated successfully, but these errors were encountered: