From 8c4c6b2c34aa2b8b829f7a5516d8dca71d7a4b65 Mon Sep 17 00:00:00 2001 From: Filinto Duran Date: Wed, 20 Jul 2022 18:24:42 -0500 Subject: [PATCH 1/6] note about artifacts and that they are only saved when new --- docs/features/runs/2_Analyzing Runs/3_artifacts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/features/runs/2_Analyzing Runs/3_artifacts.md b/docs/features/runs/2_Analyzing Runs/3_artifacts.md index 9a7876cb..1bee31eb 100644 --- a/docs/features/runs/2_Analyzing Runs/3_artifacts.md +++ b/docs/features/runs/2_Analyzing Runs/3_artifacts.md @@ -12,7 +12,7 @@ Artifacts are the output produced by the training process. ## Saving artifacts -Anytime your script saves artifacts, Grid captures those for you. It does not matter which folder you save artifacts to... Grid will automatically detect them. +Anytime your script saves new artifacts, Grid captures those for you. It does not matter which folder you save artifacts to... Grid will automatically detect them. Grid only saves new artifacts, and any file that existed before training starts, even if modified during training, will not be saved. Grid uploads your artifacts to long-term storage while your experiment is running *and* at the end of your experiment. This is to ensure that even if your experiment crashes, your artifacts will be saved. From 80e2e715820ad18dc581c42904c997c159117515 Mon Sep 17 00:00:00 2001 From: Filinto Duran Date: Thu, 21 Jul 2022 08:09:42 -0500 Subject: [PATCH 2/6] Update 3_artifacts.md refactor phrase --- docs/features/runs/2_Analyzing Runs/3_artifacts.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/features/runs/2_Analyzing Runs/3_artifacts.md b/docs/features/runs/2_Analyzing Runs/3_artifacts.md index 1bee31eb..cd6fcbd2 100644 --- a/docs/features/runs/2_Analyzing Runs/3_artifacts.md +++ b/docs/features/runs/2_Analyzing Runs/3_artifacts.md @@ -12,7 +12,9 @@ Artifacts are the output produced by the training process. ## Saving artifacts -Anytime your script saves new artifacts, Grid captures those for you. It does not matter which folder you save artifacts to... Grid will automatically detect them. Grid only saves new artifacts, and any file that existed before training starts, even if modified during training, will not be saved. +Anytime your script saves new artifacts, Grid captures those for you. It does not matter which folder you save artifacts to... Grid will automatically detect them. + +Grid only saves new artifacts. Any file that existed before training starts, even if modified during training, will not be saved. Grid uploads your artifacts to long-term storage while your experiment is running *and* at the end of your experiment. This is to ensure that even if your experiment crashes, your artifacts will be saved. From 393c85912a5ab26227eea47db154baec0a4fc05d Mon Sep 17 00:00:00 2001 From: Femi <47154698+oojo12@users.noreply.github.com> Date: Thu, 21 Jul 2022 15:15:02 -0400 Subject: [PATCH 3/6] use ssh agent --- docs/features/sessions/9_vscode-with-sessions.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/docs/features/sessions/9_vscode-with-sessions.md b/docs/features/sessions/9_vscode-with-sessions.md index 06bb9640..89c1e8c2 100644 --- a/docs/features/sessions/9_vscode-with-sessions.md +++ b/docs/features/sessions/9_vscode-with-sessions.md @@ -12,10 +12,16 @@ Create an ssh key from the computer you'd like to connect from (skip this step i ```yaml # make the ssh key (if you don't have one) -ssh-keygen -t ed25519 -C "your_email@example.com" +ssh-keygen -b 2048 -t rsa -f ~/.ssh/grid_ssh_creds -q -N "" + +# add the key to the ssh-agent (to avoid having to explicitly state key on each connection) +# to start the agent, run the following +eval $(ssh-agent) +# then add the key +ssh-add ~/.ssh/grid_ssh_creds # add the keys to grid -grid ssh-keys add lit_key ~/.ssh/id_ed25519.pub +grid ssh-keys add key_1 ~/.ssh/grid_ssh_creds.pub ``` ## Step 1: Launch a session From ad62a5b270ad7ed78877731d087fbe8063063277 Mon Sep 17 00:00:00 2001 From: Femi <47154698+oojo12@users.noreply.github.com> Date: Thu, 21 Jul 2022 15:20:47 -0400 Subject: [PATCH 4/6] use ssh agent --- .../sessions/8_how-to-ssh-into-a-session.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/features/sessions/8_how-to-ssh-into-a-session.md b/docs/features/sessions/8_how-to-ssh-into-a-session.md index 4fea2239..9f0f91d4 100644 --- a/docs/features/sessions/8_how-to-ssh-into-a-session.md +++ b/docs/features/sessions/8_how-to-ssh-into-a-session.md @@ -12,22 +12,22 @@ Create an SSH key from the computer you'd like to connect from (skip this step i ```yaml # make the ssh key (if you don't have one) -ssh-keygen -t ed25519 -C "your_email@example.com" -or -ssh-keygen -b 2048 -t rsa -q -N "" +ssh-keygen -b 2048 -t rsa -f ~/.ssh/grid_ssh_creds -q -N "" ``` ## Step 1: Add the SSH key -Here we assume to have SSH keys named _ed25519.pub_, which are the default used by the command above. - -We're going to add the key and name it _lit_key_ +Here we use the ssh-agent to manage the keys and will add them to Grid. ```yaml +# add the key to the ssh-agent (to avoid having to explicitly state key on each connection) +# to start the agent, run the following +eval $(ssh-agent) +# then add the key +ssh-add ~/.ssh/grid_ssh_creds + # add the keys to grid -grid ssh-keys add lit_key ~/.ssh/id_ed25519.pub -or -grid ssh-keys add key_1 ~/.ssh/id_rsa.pub +grid ssh-keys add key_1 ~/.ssh/grid_ssh_creds.pub ``` If you go to [Grid settings](https://platform.grid.ai/#/settings?tabId=ssh), you'll see SSH keys you've added to Grid From d781b8ea057173bc1a490b4709e70c861dd30545 Mon Sep 17 00:00:00 2001 From: Femi <47154698+oojo12@users.noreply.github.com> Date: Fri, 22 Jul 2022 07:17:25 -0400 Subject: [PATCH 5/6] Update typical-workflow-cli-user.md --- docs/getting-started/typical-workflow-cli-user.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/getting-started/typical-workflow-cli-user.md b/docs/getting-started/typical-workflow-cli-user.md index 8b306126..5e2c45af 100644 --- a/docs/getting-started/typical-workflow-cli-user.md +++ b/docs/getting-started/typical-workflow-cli-user.md @@ -290,11 +290,14 @@ ssh into the interactive grid session ssh resnet-debugging ``` +Install remote ssh extension +![](/images/sessions/remote-ssh.png) + Now link up VSCode with the Session +![](/images/sessions/vscode-remote.gif) -```yaml -grid session ssh vscode -``` +Now VSCode is connected to the remote Session.. +![](/images/sessions/vscode-open-session.gif) **The model** From 3e5c2d1e7d9377538c7c92a9d3766a0d05de3577 Mon Sep 17 00:00:00 2001 From: Femi <47154698+oojo12@users.noreply.github.com> Date: Fri, 22 Jul 2022 07:23:48 -0400 Subject: [PATCH 6/6] fix --- docs/getting-started/typical-workflow-cli-user.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/docs/getting-started/typical-workflow-cli-user.md b/docs/getting-started/typical-workflow-cli-user.md index 5e2c45af..fbcd3e62 100644 --- a/docs/getting-started/typical-workflow-cli-user.md +++ b/docs/getting-started/typical-workflow-cli-user.md @@ -290,15 +290,9 @@ ssh into the interactive grid session ssh resnet-debugging ``` -Install remote ssh extension -![](/images/sessions/remote-ssh.png) - Now link up VSCode with the Session ![](/images/sessions/vscode-remote.gif) -Now VSCode is connected to the remote Session.. -![](/images/sessions/vscode-open-session.gif) - **The model** For this tutorial, I'm going to use a non-trivial project structure that is representative of realistic use cases \[[code link](https://github.com/williamFalcon/cifar5)\].