{"_id":"5477c85f8deb230800808bf9","project":"5476bf0f817e8d080031f988","__v":16,"category":{"_id":"54e90194c8e0c00d007ac061","pages":["54e901d4f152c50d009b49ae","54e902a0f152c50d009b49b0","55405bf36a7d010d0057ca51","560c175ae6112f2300b8d9a1"],"project":"5476bf0f817e8d080031f988","version":"5476bf10817e8d080031f98b","__v":4,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-02-21T22:07:16.080Z","from_sync":false,"order":0,"slug":"concepts-and-capabilities","title":"Concepts and Capabilities"},"user":"5476beec817e8d080031f986","parentDoc":null,"version":{"_id":"5476bf10817e8d080031f98b","__v":17,"project":"5476bf0f817e8d080031f988","createdAt":"2014-11-27T06:05:04.263Z","releaseDate":"2014-11-27T06:05:04.263Z","categories":["5476bf10817e8d080031f98c","5477c46cf3736008009e9eb5","5477c474f3736008009e9eb6","5477c47ef3736008009e9eb7","5477c48ff3736008009e9eb8","5477c4948deb230800808bf0","54e68328154f8e0d0007b55c","54e90194c8e0c00d007ac061","54eed2275bf74a0d00ef4076","54f7a7be0a3cbb0d00d666fb","559b0ebf7ae7f80d0096d871","55d697f9ae529e0d00d34f03","562d4dcc8c6e5a0d00d6ed1d","562e591c4376430d006f17e0","568f0e73bdb9260d00149d8c","5719542aac1e2e0e001834c6","57a14a8ed778850e0047e230"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2014-11-28T00:57:03.525Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"settings":"","try":true,"basic_auth":false,"results":{"codes":[]},"auth":"never","params":[],"url":""},"isReference":false,"order":8,"body":"A run is a specific instance of the execution of a given protocol. A run is composed of a sequence of instructions, which will be executed in order (with some parallelization where possible). Once a run is created, it is added to our execution queue and will be started as soon as capacity becomes available on a work cell. \n\nAll runs, including those currently in progress, are listed within their associated project folder. For runs in progress, navigate to the run view to monitor their progress. Individual steps will turn green in real time as they are completed.\n\nThe \"conversation\" tab can be used to communicate with others in your team about a specific run.  Runs can also be flagged to alert Transcriptic staff that there might be an issue with how a run was executed. \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/Z21U3UuFQpyXxPCJC6mK_Transcriptic.png\",\n        \"Transcriptic.png\",\n        \"1173\",\n        \"808\",\n        \"#6797cd\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nThe \"containers\" tab shows you a representation of the containers used in your run and approximate volumes within them.  \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/sjsScAI2TeyPCvIt0K3r_Transcriptic.png\",\n        \"Transcriptic.png\",\n        \"1161\",\n        \"802\",\n        \"#6696d2\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nIf your run was data-producing, you can view what was returned via the \"results\" tab within a run\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/FFQ8OyU1Sk6GHlPqaRbk_Fullscreen_6_9_15__3_01_PM.png\",\n        \"Fullscreen_6_9_15__3_01_PM.png\",\n        \"1231\",\n        \"878\",\n        \"#587e95\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]","excerpt":"A run is a record of execution in Transcriptic's lab environment.","slug":"what-is-a-run","type":"basic","title":"What is a Run?"}

What is a Run?

A run is a record of execution in Transcriptic's lab environment.

A run is a specific instance of the execution of a given protocol. A run is composed of a sequence of instructions, which will be executed in order (with some parallelization where possible). Once a run is created, it is added to our execution queue and will be started as soon as capacity becomes available on a work cell. All runs, including those currently in progress, are listed within their associated project folder. For runs in progress, navigate to the run view to monitor their progress. Individual steps will turn green in real time as they are completed. The "conversation" tab can be used to communicate with others in your team about a specific run. Runs can also be flagged to alert Transcriptic staff that there might be an issue with how a run was executed. [block:image] { "images": [ { "image": [ "https://files.readme.io/Z21U3UuFQpyXxPCJC6mK_Transcriptic.png", "Transcriptic.png", "1173", "808", "#6797cd", "" ] } ] } [/block] The "containers" tab shows you a representation of the containers used in your run and approximate volumes within them. [block:image] { "images": [ { "image": [ "https://files.readme.io/sjsScAI2TeyPCvIt0K3r_Transcriptic.png", "Transcriptic.png", "1161", "802", "#6696d2", "" ] } ] } [/block] If your run was data-producing, you can view what was returned via the "results" tab within a run [block:image] { "images": [ { "image": [ "https://files.readme.io/FFQ8OyU1Sk6GHlPqaRbk_Fullscreen_6_9_15__3_01_PM.png", "Fullscreen_6_9_15__3_01_PM.png", "1231", "878", "#587e95", "" ] } ] } [/block]