.kumac and gopaw core

Since 1.14.x, ioda can be built by incorporating the gopaw core. This permits to execute .kumac file, potentially able to work on .root, .fits, g4tools/hdf5 data files, and have at end similar plotting rendering as CERN-PAW. Releasee binaries, along the docker version, are built with gopaw core.

In the resource directory there is the pawex1.kumac working on VECTORs and pawex10.kumac coworking with the mandel.py function script. In the examples menu item there is also the paw_py_root/all.kumac executing all the examples found in gopaw/examples/PAW_py_root. See gopaw pages for more about these.

Your kumac

To run your own .kumac, you can deposit it in your ioda document directory and then load and execute it with :

     files > ioda > .kumac > <your .kumac>

If the .kumac refers a data file or another .kumac file, you have to do a local copy of them and refer them by using the IODA_DATA_DIR environment variable. For example with a my_b4.kumac working on data_B4.hdf5 file :

     exec $IODA_DATA_DIR/alldef
     zone 2 2
     opt stat
     h/file 1 $IODA_DATA_DIR/data_B4.hdf5   | file coming from Geant4.
     cd //lun1/default_histograms
     h/plot Eabs
     h/plot Egap
     h/plot Labs
     h/plot Lgap
     close 1

The release on github contains the ioda_doc_kumacs.zip file with examples :

     cd ~/Documents
     <get ioda_doc_kumacs.zip>
     unzip -q ioda_doc_kumacs.zip

You should have now in Documents/ioda the my_[vec,b4,root,m51].kumac files to play with along their coworking data and .kumac files (for example data_B4.hdf5 and alldef.kumac).