Best practices for single script files

[goerz]

If you search this forum, you will find previous threads on using Julia on a cluster, e.g.,

Julia on a cluster using SLURM, dependencies

Do I need my script to call the project module? That is do I need it to be of the form module TestProject greet() = print(“Hello World!”) using Statistics using Distributions open(“./testing_write_proj.txt”, “w”) do file write(file, “worked 1:03 edit”) end end # module TestProject

How to run Julia on Cluster?

This is what the last two lines in my example accomplish: I upload the code to the project directory with rsync. That way, I have a Project.toml and Manifest.toml in place that match my (tested) local version of the code. All the jl file needs to do then is using Pkg Pkg.instantiate() # in case some package is missing on the remote using MyPackage command_I_want_to_run()

You will also find general documentation on the web, e.g.,

SLURM Job Array Julia Example | RCpedia

Julia on the HPC Clusters

Using Julia

Lastly, the HPC staff of the cluster you’re planning to use should be able to give you advice for their specific system.

My general recommendation was that your job script should only call julia once. Beyond that, calling julia on the cluster isn’t that much different from running it on your workstation. Except maybe that you should be more aware of the exact resources you’re going to use, and carefully manage the number of processes/threads. The JULIA_EXCLUSIVE environment variable might be useful on a cluster.