Batch Computing Basics for DUNE - 2025 transition edition: Glossary

This tutorial is brought to you by the DUNE Computing Consortium.

The goals are to give you the computing basis to work on DUNE.

Always, always, always prestage input datasets. No exceptions.

When in doubt, ask! Understand that policies and procedures that seem annoying, overly complicated, or unnecessary (especially when compared to running an interactive test) are there to ensure efficient operation and scalability. They are also often the result of someone breaking something in the past, or of simpler approaches not scaling well.

Send test jobs after creating new workflows or making changes to existing ones. If things don’t work, don’t blindly resubmit and expect things to magically work the next time.

Only copy what you need in input tar files. In particular, avoid copying log files, .git directories, temporary files, etc. from interactive areas.

Take care to follow best practices when setting up input and output file locations.

Always, always, always prestage input datasets. No exceptions.

Always, always, always prestage input datasets. No exceptions.

Debugging requires a methodical and inquisitive mindset, gained through experience and good bookkeeping (write down how to you solved past issues!)

The DUNE Computing Consortium has presented this workshop so as to broaden the use of software tools used for analysis.