Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify that command-line switches need to be manually set in addprocs #50843

Merged
merged 4 commits into from
Feb 11, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion doc/src/manual/arrays.md
Original file line number Diff line number Diff line change
Expand Up @@ -889,7 +889,7 @@ in their implementations, other arrays — like [`Diagonal`](@ref) — need the
full set of cartesian indices to do their lookup (see [`IndexStyle`](@ref) to
introspect which is which).

!!! warnings
!!! warning

When iterating over all the indices for an array, it is
better to iterate over [`eachindex(A)`](@ref) instead of `1:length(A)`.
Expand Down
9 changes: 5 additions & 4 deletions doc/src/manual/distributed-computing.md
Original file line number Diff line number Diff line change
Expand Up @@ -270,10 +270,11 @@ julia> addprocs(2)
Module [`Distributed`](@ref man-distributed) must be explicitly loaded on the master process before invoking [`addprocs`](@ref).
It is automatically made available on the worker processes.

Note that workers do not run a `~/.julia/config/startup.jl` startup script, nor do they synchronize
their global state (such as global variables, new method definitions, and loaded modules) with any
of the other running processes. You may use `addprocs(exeflags="--project")` to initialize a worker with
a particular environment, and then `@everywhere using <modulename>` or `@everywhere include("file.jl")`.
!!! note
Note that workers do not run a `~/.julia/config/startup.jl` startup script, nor do they synchronize
their global state (such as command-line switches, global variables, new method definitions, and loaded modules) with any
of the other running processes. You may use `addprocs(exeflags="--project")` to initialize a worker with
a particular environment, and then `@everywhere using <modulename>` or `@everywhere include("file.jl")`.

Other types of clusters can be supported by writing your own custom `ClusterManager`, as described
below in the [ClusterManagers](@ref) section.
Expand Down