diff --git a/dev/.documenter-siteinfo.json b/dev/.documenter-siteinfo.json index dfce27272..ccf071c80 100644 --- a/dev/.documenter-siteinfo.json +++ b/dev/.documenter-siteinfo.json @@ -1 +1 @@ -{"documenter":{"julia_version":"1.10.2","generation_timestamp":"2024-04-15T02:31:06","documenter_version":"1.4.0"}} \ No newline at end of file +{"documenter":{"julia_version":"1.10.2","generation_timestamp":"2024-04-22T00:13:50","documenter_version":"1.4.0"}} \ No newline at end of file diff --git a/dev/getting-started/index.html b/dev/getting-started/index.html index 26b7a0ee1..46fc58f1c 100644 --- a/dev/getting-started/index.html +++ b/dev/getting-started/index.html @@ -48,7 +48,7 @@ ENV["RESULTS"] = string(mat_sum) """ sha256(project_toml) = 93a83d60d4a9c6a3d1438259fd506929eaad296b7e112e886b305781b85cb85b -sha256(manifest_toml) = 23e4f3a14ee7c1259424ba087975c33a4cc1f9fdffddb75dc32bdb0fd891ec5e
In most cases, you also submit a Julia package environment (i.e. Project.toml
and Manifest.toml
files together with a job). That environment then gets instantiated before the user-provided code is run.
The script""
string macro, by default, attaches the currently active environment to the job. This means that any packages that you are currently using should also be available on the job (although only registered packages added as non-development dependencies will work). You can use Base.active_project()
or pkg> status
to see what environment is currently active.
To submit a job, you can simply call submit_job
on it.
julia> j = JuliaHub.submit_job(s)
JuliaHub.Job: jr-xf4tslavut (Submitted) +sha256(manifest_toml) = 3ba5af2761d8fbdce2c23cdc3119a2ffb7294c8962a3c49f032ee123df14df43
In most cases, you also submit a Julia package environment (i.e. Project.toml
and Manifest.toml
files together with a job). That environment then gets instantiated before the user-provided code is run.
The script""
string macro, by default, attaches the currently active environment to the job. This means that any packages that you are currently using should also be available on the job (although only registered packages added as non-development dependencies will work). You can use Base.active_project()
or pkg> status
to see what environment is currently active.
To submit a job, you can simply call submit_job
on it.
julia> j = JuliaHub.submit_job(s)
JuliaHub.Job: jr-xf4tslavut (Submitted) submitted: 2023-03-15T07:56:50.974+00:00 started: 2023-03-15T07:56:51.251+00:00 finished: 2023-03-15T07:56:59.000+00:00
The submit_job
function also allows you to specify configure how the job gets run, such as how many CPUs or how much memory it has available. By default, though, it runs your code on a single node, picking the smallest instance that is available.
At this point, if you go to the "Jobs" page web UI, you should see the job there. It may take a few moments to actually start running. You can also call job
on the returned Job
object to refresh the status of the job.
julia> j = JuliaHub.job(j)
JuliaHub.Job: jr-xf4tslavut (Running) @@ -63,4 +63,4 @@ startOnLoad: true, theme: "neutral" }); -
Settings
This document was generated with Documenter.jl version 1.4.0 on Monday 15 April 2024. Using Julia version 1.10.2.