{"__v":35,"_id":"5477c4dbf3736008009e9eb9","category":{"__v":4,"_id":"54e90194c8e0c00d007ac061","pages":["54e901d4f152c50d009b49ae","54e902a0f152c50d009b49b0","55405bf36a7d010d0057ca51","560c175ae6112f2300b8d9a1"],"project":"5476bf0f817e8d080031f988","version":"5476bf10817e8d080031f98b","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"},"parentDoc":null,"project":"5476bf0f817e8d080031f988","user":"5476beec817e8d080031f986","version":{"__v":17,"_id":"5476bf10817e8d080031f98b","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:42:03.692Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"basic_auth":false,"results":{"codes":[]},"settings":"","try":true,"auth":"never","params":[],"url":""},"isReference":false,"order":7,"body":"A protocol is a list of specific instructions for our automation to follow.  Our machines only understand these instructions in the form of [Autoprotocol](doc:autoprotocol).  You have several options for generating protocols through our website and using code of your own.  Protocols are used to generate [runs](doc:what-is-a-run), or individual incidences of execution of a given protocol. \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Using the UI to Launch a Protocol\"\n}\n[/block]\nTranscriptic provides a core library of protocols that will be visible by default when you click on the \"Launch a Run\" button from within any project.  Selecting one of these protocols allows you to change certain parameters for what will be executed and choose samples from your inventory to execute it on (if applicable). \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/HXPOwgnMQnO5tPeMvLku_Transcriptic.png\",\n        \"Transcriptic.png\",\n        \"1411\",\n        \"747\",\n        \"#4f7294\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nLaunching a Protocol is as simple as filling out a few fields by searching for aliquots in your inventory and/or entering values and clicking \"Next\".   \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/5FzIApZyTU6ewk02EbIH_Transcriptic.png\",\n        \"Transcriptic.png\",\n        \"1026\",\n        \"502\",\n        \"#59778b\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nOn the next screen you'll be able to see an overview of the steps that will be executed and the cost of your run before you launch it. \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/aLUCiO5DS6WKXgEWABJt_Transcriptic.png\",\n        \"Transcriptic.png\",\n        \"957\",\n        \"564\",\n        \"#4681ab\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Protocol Validation\"\n}\n[/block]\nIf a protocol has been thoroughly validated by Transcriptic, you'll see a check mark next to it in the Protocol Browser as above.   From a validated protocol's detail view, you can click on the \"Representative Data\" link to view a PDF \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/H8G4VkcTOWR3oNKZ5U5b_Transcriptic.png\",\n        \"Transcriptic.png\",\n        \"951\",\n        \"583\",\n        \"#b98e22\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/e4ho0GggTviGXSq5PTHO_https___static_transcriptic_com_protocol-rep-data_rep-data_plate-reading_pdf.png\",\n        \"https___static_transcriptic_com_protocol-rep-data_rep-data_plate-reading_pdf.png\",\n        \"730\",\n        \"792\",\n        \"#3b5363\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]","excerpt":"Transcriptic protocols are written using the Autoprotocol standard.","slug":"background","type":"basic","title":"What is a Protocol?"}

What is a Protocol?

Transcriptic protocols are written using the Autoprotocol standard.

A protocol is a list of specific instructions for our automation to follow. Our machines only understand these instructions in the form of [Autoprotocol](doc:autoprotocol). You have several options for generating protocols through our website and using code of your own. Protocols are used to generate [runs](doc:what-is-a-run), or individual incidences of execution of a given protocol. [block:api-header] { "type": "basic", "title": "Using the UI to Launch a Protocol" } [/block] Transcriptic provides a core library of protocols that will be visible by default when you click on the "Launch a Run" button from within any project. Selecting one of these protocols allows you to change certain parameters for what will be executed and choose samples from your inventory to execute it on (if applicable). [block:image] { "images": [ { "image": [ "https://files.readme.io/HXPOwgnMQnO5tPeMvLku_Transcriptic.png", "Transcriptic.png", "1411", "747", "#4f7294", "" ] } ] } [/block] Launching a Protocol is as simple as filling out a few fields by searching for aliquots in your inventory and/or entering values and clicking "Next". [block:image] { "images": [ { "image": [ "https://files.readme.io/5FzIApZyTU6ewk02EbIH_Transcriptic.png", "Transcriptic.png", "1026", "502", "#59778b", "" ] } ] } [/block] On the next screen you'll be able to see an overview of the steps that will be executed and the cost of your run before you launch it. [block:image] { "images": [ { "image": [ "https://files.readme.io/aLUCiO5DS6WKXgEWABJt_Transcriptic.png", "Transcriptic.png", "957", "564", "#4681ab", "" ] } ] } [/block] [block:api-header] { "type": "basic", "title": "Protocol Validation" } [/block] If a protocol has been thoroughly validated by Transcriptic, you'll see a check mark next to it in the Protocol Browser as above. From a validated protocol's detail view, you can click on the "Representative Data" link to view a PDF [block:image] { "images": [ { "image": [ "https://files.readme.io/H8G4VkcTOWR3oNKZ5U5b_Transcriptic.png", "Transcriptic.png", "951", "583", "#b98e22", "" ] } ] } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/e4ho0GggTviGXSq5PTHO_https___static_transcriptic_com_protocol-rep-data_rep-data_plate-reading_pdf.png", "https___static_transcriptic_com_protocol-rep-data_rep-data_plate-reading_pdf.png", "730", "792", "#3b5363", "" ] } ] } [/block]