llama dev data i3

Use llama dev data i3 to fetch archival neutrino data and store it securely on LLAMA’s AWS S3/DigitalOcean Spaces storage. You can use this script to see which archival neutrino releases are available from IceCube servers and to transfer that data to private S3 storage. The printed code can be added to the LLAMA codebase under llama.files.s3.json.ARCHIVAL_NEUTRINOS; it will allow you to access the archival neutrino data stored on LLAMA servers if you have proper LLAMA S3 authentication credentials on your computer (allowing for proper reproducibility and faster data access). That data is only downloaded from LLAMA S3 when it is needed and is persisted in LLAMA’s cache directory (see llama.utils.CACHEDIR).

usage: llama dev data i3 [-h] [-l LOGFILE]
                         [-v {debug,info,warning,error,critical,none}] [-a]
                         [-s ARCHIVE_VERSION] [-r ARCHIVE_ROOT]

Named Arguments

-a, --available

Fetch available IceCube neutrino archive versions from the IceCube servers, print them one-per-line, and exit.

Default: False

-s, --store-s3

Fetch IceCube neutrino archives specified by the ARCHIVE_VERSION, upload them to LLAMA S3 storage, and print a block of code that can be inserted into the llama.files.s3.json.ARCHIVAL_NEUTRINOS declaration to make these newly-stored archival neutrinos available to pipeline users with LLAMA S3 credentials (see llama.com.s3).

-r, --archive-root

The root directory on IceCube’s cobalt servers in which to search for archival neutrinos (using --store-s3 or --available).

Default: “/data/ana/analyses/gfu/”

logging settings

-l, --logfile

File where logs should be written. By default, all logging produced by llama run goes to both an archival logfile shared by all instances of the process as well as STDERR. The archival logfile can be overridden with this argument. If you specify /dev/null or a path that resolves to the same, logfile output will be suppressed automatically. Logs written to the logfile are always at maximum verbosity, i.e. DEBUG. (default: /dev/null)

Default: “/dev/null”

-v, --verbosity

Possible choices: debug, info, warning, error, critical, none

Set the verbosity level at which to log to STDOUT; the --logfile will ALWAYS receive maximum verbosity logs (unless it is completely supressed by writing to /dev/null). Available choices correspond to logging severity levels from the logging library, with the addition of none if you want to completely suppress logging to standard out. (default: info)

Default: “info”