~$ cd $USER
@@ -53,7 +64,7 @@ Start by entering the @$USER@ directory created by @git clone@. Next create a s
Next, using @nano@ or your favorite Unix text editor, create a new file called @hash.py@ in the @crunch_scripts@ directory.
-notextile. ~/$USER/crunch_scripts$ nano hash.py
+notextile. ~/tutorial/crunch_scripts$ nano hash.py
Add the following code to compute the MD5 hash of each file in a collection (if you already completed "Writing a Crunch script":tutorial-firstscript.html you can just copy the @hash.py@ file you created previously.)
@@ -61,16 +72,16 @@ Add the following code to compute the MD5 hash of each file in a collection (if
Make the file executable:
-notextile. ~/$USER/crunch_scripts$ chmod +x hash.py
+notextile. ~/tutorial/crunch_scripts$ chmod +x hash.py
Next, add the file to the staging area. This tells @git@ that the file should be included on the next commit.
-notextile. ~/$USER/crunch_scripts$ git add hash.py
+notextile. ~/tutorial/crunch_scripts$ git add hash.py
Next, commit your changes. All staged changes are recorded into the local git repository:
-~/$USER/crunch_scripts$ git commit -m"my first script"
+~/tutorial/crunch_scripts$ git commit -m"my first script"
[master (root-commit) 27fd88b] my first script
1 file changed, 45 insertions(+)
create mode 100755 crunch_scripts/hash.py
@@ -79,12 +90,12 @@ Next, commit your changes. All staged changes are recorded into the local git r
Finally, upload your changes to the Arvados server:
-~/$USER/crunch_scripts$ git push origin master
+~/tutorial/crunch_scripts$ git push origin master
Counting objects: 4, done.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (4/4), 682 bytes, done.
Total 4 (delta 0), reused 0 (delta 0)
-To git@git.qr1hi.arvadosapi.com:$USER/$USER.git
+To git@git.qr1hi.arvadosapi.com:$USER/tutorial.git
* [new branch] master -> master
@@ -100,7 +111,7 @@ In the editor, enter the following template:
{% code 'tutorial_submit_job' as javascript %}
-* @"repository"@ is the name of a git repository to search for the script version. You can access a list of available git repositories on the Arvados Workbench under "Code repositories":{{site.arvados_workbench_host}}/repositories.
+* @"repository"@ is the name of a git repository to search for the script version. You can access a list of available git repositories on the Arvados Workbench in the *Repositories* page using the top navigation menu icon.
* @"script_version"@ specifies the version of the script that you wish to run. This can be in the form of an explicit Git revision hash, a tag, or a branch (in which case it will use the HEAD of the specified branch). Arvados logs the script version that was used in the run, enabling you to go back and re-run any past job with the guarantee that the exact same code will be used as was used in the previous run.
* @"script"@ specifies the filename of the script to run. Crunch expects to find this in the @crunch_scripts/@ subdirectory of the Git repository.
* @"runtime_constraints"@ describes the runtime environment required to run the job. These are described in the "job record schema":{{site.baseurl}}/api/schema/Job.html