Miscellaneous Tips

Help with LDMX Variables

Miscellaneous tips for SLAC:

• Don't forget to include the -XY flag when logging in to SLAC! Without this, you won't be able to view the contents of ROOT files interactively through a TBrowser
• Use the -j flag when doing ldmx make install to expedite the process. A recommended setting is -j2, but you could go higher. Do keep the setting below -j10
• If you find that treeMaker.py isn't cooperating when you try to submit some batch jobs, it's probably because the container can't find cellmodule.txt or libFramework.so or both. To get around this, open up treeMaker.py and change lines 7 and 8 so that they use absolute file paths
• Use the bjobs command to monitor the status of all of your batch jobs. Alternatively, use bpeek <JOB_ID> to closely monitor the output of the job with the specified job ID
• If you're submitting a particularly large batch job and you need more time/memory, use the long queue and increase -W and -n appropriately. Do limit the number of cores you use to a reasonable amount
• If you absolutely must terminate all of your batch jobs, use bkill 0. Alternatively, use bkill <JOB_ID> to just kill the job with the specified job ID

Miscellaneous tips for Docker:

• To use an environmental variable inside the container, add -e YOURVARIABLE=value to the docker run command. For the LDMX framework, the docker run command is bundled into the alias ldmx. Search the ldmx-env.sh file for docker run and you can add your variable there. Make sure to source ldmx-env.sh after your changes.

Miscellaneous tips for Pod:

• Environmental variables are automatically used with the version of singularity on Pod. You just need to set the variable with export YOURVARIABLE=value.