LArSoft

From Hans:

The people working on dual phase TPC's were able to get the full chain running and I think everything can be found in the dune repositories. I have attached the fcl and gdml file they used.

I am in the process of compiling an example that shows how to use the new workflow using a simplified liquid Argon Detector geometry. But I still have to complete some coding which completely splits the electron drift and detector response. That means the larsim:source:larsim/ElectronDrift/SimDriftElectrons_module.cc used by the example above will be split into the DriftElectronstoPlane_module.cc and another module that produces the simchannels.

Here the DriftElectronstoPlane_module will take the SimEnergyDeposits as input, drift the electrons to a surface and create the SimDriftedElectronClusters which then are the input for a new module that takes the SimDriftedElectronClusters as input and simchannels as output.

Hans, can you take care of this?

Currently an example is available as part of dunetpc. It was developed by the group working on a dual-phase TPC (Jose, Bea and Paul). So to look at the example one needs to setup dunetpc. Below is what I am doing until we find a place for a more generic example.

mkdir example 
cd example
mkdir larsim_dev
cd larsim_dev
source /cvmfs/fermilab.opensciencegrid.org/products/larsoft/setup
setup mrb
export MRB_PROJECT=larsim
mrb newDev -v v08_07_00 -q e17:prof
source localProducts_larsim_v08_07_00_e17_prof/setup
cd srcs
mrb g larsim
cd $MRB_BUILDDIR
mrbsetenv
mrb b -j 4
unsetup cetpkgsupport
source /cvmfs/dune.opensciencegrid.org/products/dune/setup_dune.sh
setup dunetpc -qe17:prof v08_20_00 
wget https://cdcvs.fnal.gov/redmine/attachments/download/53755/fcl.tgz
tar xzvf fcl.tgz
lar -c dune_refactored.fcl

to run the module by Bill seligman which does the simdrift and injects the charge into the simchannels. (Currently this still depends on the LArG4Parameters service but we will remove this dependency)

lar -c dune_refactored2.fcl

I took Gianluca's larcorealg:source:larcorealg/Geometry/gdml/MinimalLArTPCdetector_nowires.gdml file and modified it. The gdml file is attached.

Now everything is square as Gianluca intended. The gdml as well as some screenshots are attached. I am not quite done yet but the gdml file should be quite compact and easy to read and modify.

I am testing (with larsoft v08_55_02) the new minimal LArTPC detector example Hans created about 2 months ago for the purpose of illustrating how to use the refactored larg4. However it fails in GeometryCore::BuildGeometry at the following line:

Cryostats() = builder.extractCryostats(path);

Info in <TGeoManager::Import>: Reading geometry from file: ./MinimalLArTPCdetector_g4.gdml
Info in <TGeoManager::TGeoManager>: Geometry GDMLImport, Geometry imported from GDML created
Info in <TGeoManager::SetTopVolume>: Top volume is volWorld. Master volume is volWorld
Info in <TGeoNavigator::BuildCache>: --- Maximum geometry depth set to 100
Info in <TGeoManager::CheckGeometry>: Fixing runtime shapes...
Info in <TGeoManager::CheckGeometry>: ...Nothing to fix
Info in <TGeoManager::CloseGeometry>: Counting nodes...
Info in <TGeoManager::Voxelize>: Voxelizing...
Info in <TGeoManager::CloseGeometry>: Building cache...
Info in <TGeoManager::CountLevels>: max level = 5, max placements = 2591
Info in <TGeoManager::CloseGeometry>: 3563 nodes/ 12 volume UID's in Geometry imported from GDML
Info in <TGeoManager::CloseGeometry>: ----------------modeler ready----------------

 *** Break *** segmentation violation
    __boot()
    import os

Gianluca, could you please take a look, since this appears to be your code and you understand it better than the rest of us, to help us understand what's wrong so we can get this example working. I am attaching the fcl and the gdml files used by the geometry service. The gdml file used by larg4 is the same one Hans created and uploaded 2 months ago on this page.

As suggested by Kyle and Lynn at today's scisoft meeting, I repeated my test using larsoft v09_03_00. I see the same failure. Attached is a text file with the output from running lar showing more details of the failure.