Uncertainty Regarding Workspace Allocation and Data Copy in Steps 2 and 3 #2

Closed
opened 2024-08-26 05:23:29 +00:00 by Felix Ruhnke · 2 comments
Member

In steps 2 and 3, it is indicated that the workspace should be allocated on the Hawk cluster and the data should be copied to the created directory. However, the goal is to execute the job on the Vulcan cluster.

Is it correct that the workspace needs to be allocated on the Hawk cluster and not on the Vulcan cluster?

In steps 2 and 3, it is indicated that the workspace should be allocated on the Hawk cluster and the data should be copied to the created directory. However, the goal is to execute the job on the Vulcan cluster. Is it correct that the workspace needs to be allocated on the Hawk cluster and not on the Vulcan cluster?
Rishabh Saxena was assigned by Felix Ruhnke 2024-08-26 05:23:29 +00:00

In steps 2 and 3, it is indicated that the workspace should be allocated on the Hawk cluster and the data should be copied to the created directory. However, the goal is to execute the job on the Vulcan cluster.

We need to fix the mismatch between workspace allocation and subsequent steps.

Is it correct that the workspace needs to be allocated on the Hawk cluster and not on the Vulcan cluster?

You must allocate a workspace on Vulcan if you want to work on Vulcan. The workspaces are not shared between the two systems.

> In steps 2 and 3, it is indicated that the workspace should be allocated on the Hawk cluster and the data should be copied to the created directory. However, the goal is to execute the job on the Vulcan cluster. We need to fix the mismatch between workspace allocation and subsequent steps. > Is it correct that the workspace needs to be allocated on the Hawk cluster and not on the Vulcan cluster? You must allocate a workspace on Vulcan if you want to work on Vulcan. The workspaces are not shared between the two systems.
26cb3ed722
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: SiVeGCS/dask_template#2
No description provided.