{"_id":"5722931ade10810e0015399e","__v":1,"parentDoc":null,"user":"56f57b8eab3f610e000a6596","category":{"_id":"568f0e73bdb9260d00149d8c","pages":["568f0ea29ebef90d0087276a","568f0eafb700ce0d002f4a32","568f0ebbbdb9260d00149d8d","568f0edeb700ce0d002f4a34","568f0ef3bdb9260d00149d8f","568f12099ebef90d0087276d","568f121abeb2700d00471839","568f20e49ebef90d0087277e","568f446d9ebef90d0087278f","56c79a728bf67e0d00734767","56cb8830c675f50b00a4b834","56d47e99a4a9211b00c8f0d2","56d4af6c1c4de4130005d74e","56d52a131c4de4130005d80b","56de001b3db43f2000d9a765","56de1087f25ce60e002e31ad","56e314c46e602e0e00700b35"],"__v":17,"project":"5476bf0f817e8d080031f988","version":"5476bf10817e8d080031f98b","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-01-08T01:18:43.343Z","from_sync":false,"order":1,"slug":"protocols","title":"Premade Protocols"},"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"},"project":"5476bf0f817e8d080031f988","updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-04-28T22:47:54.178Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":14,"body":"[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Description\"\n}\n[/block]\nThis protocol allows the transfer of volumes of aliquots from specific locations in a source plate to specific locations in a destination plate.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Sample requirements\"\n}\n[/block]\n\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Sample\",\n    \"h-1\": \"Explanation\",\n    \"0-0\": \"Source Container\",\n    \"0-1\": \"A container from your Inventory with aliquots that you wish to transfer.\",\n    \"1-0\": \"Destination Container\",\n    \"1-1\": \"A container, new or from your Inventory, to which you wish to transfer aliquots.\"\n  },\n  \"cols\": 2,\n  \"rows\": 2\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Required parameters\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"Cherry pick uses a single channel pipette to perform the liquid handling. To learn more about single channel liquid handling and the `transfer` command please see [here](https://developers.transcriptic.com/docs/liquid-handling#section-transfer)\",\n  \"title\": \"Cherry pick uses `transfer`\"\n}\n[/block]\n\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Parameter\",\n    \"h-1\": \"Explanation\",\n    \"0-0\": \"Cherry Pick Sets\",\n    \"2-0\": \"Destination Container\",\n    \"3-0\": \"New Plate Name (new container)\",\n    \"4-0\": \"Storage Condition\",\n    \"1-0\": \"Confirm Source Volumes\",\n    \"0-1\": \"A cherry pick set defines all parameters for a set of transfers from one source plate to one destination plate. Additional cherry pick sets may be specified by clicking the 'Add Cherry Pick Sets' link at the bottom of the current cherry pick set.\",\n    \"1-1\": \"Confirm that your source wells have sufficient volume to execute the specified transfer. If unchecked the protocol will be executed even if some wells do not have the required volume.\",\n    \"2-1\": \"Select either a new container or a container from your inventory to contain the transfer volume from the source quadrant. \\n\\n'Create a new destination plate' allows you to transfer aliquots to any location in the new container or combine aliquots in the new container.\\n\\n'Sequentially transfer cherry picked samples to a new container' will automatically transfer aliquots one by one to successive wells in a new container.\",\n    \"3-1\": \"The name for the resulting new container.\",\n    \"4-1\": \"The storage temperature you require for the new container: either `cold_80`, `cold_20`, `cold_4` or `ambient`.\",\n    \"5-0\": \"Container Type (new container)\",\n    \"5-1\": \"The container type for the new container. Select from `96-pcr`, `96-flat`, `96-deep`, `384-pcr`, `384-flat`, or `384-echo`.\",\n    \"6-0\": \"Upload Transfer Map\",\n    \"6-1\": \"For 'Create a new destination plate', specify the source well, destination well, and transfer volume (see 'Use this template' next to the upload box).\\n\\nFor 'Sequentially transfer cherry picked samples to a new container', specify the source well and transfer volume (see 'Use this template' next to the upload box).\"\n  },\n  \"cols\": 2,\n  \"rows\": 7\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Protocol Outputs\"\n}\n[/block]\nThis protocol outputs a either a new container or an existing container with the specified aliquots and volumes transferred from the source container to the destination container. New containers will be stored in your Inventory at the specified storage condition. Existing containers will be returned to the storage condition from which they came.\n\nNo measurement data is returned by this protocol.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Recommended guidelines\"\n}\n[/block]\nEnsure you are aware of the dead volume in your source container. Dead volumes can be found in the containers section [here](https://developers.transcriptic.com/docs/containers#compatible-container-types). Failure to take into account dead volumes can result in insufficient volume being pipetted.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Further reading\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"success\",\n  \"body\": \"For further advice on your protocol please ask questions to the community at https://forum.transcriptic.com\",\n  \"title\": \"Check out the forum if you have more questions.\"\n}\n[/block]","excerpt":"","slug":"pipetting-tools-cherry-pick","type":"basic","title":"Pipetting Tools - Cherry Pick"}

Pipetting Tools - Cherry Pick


[block:api-header] { "type": "basic", "title": "Description" } [/block] This protocol allows the transfer of volumes of aliquots from specific locations in a source plate to specific locations in a destination plate. [block:api-header] { "type": "basic", "title": "Sample requirements" } [/block] [block:parameters] { "data": { "h-0": "Sample", "h-1": "Explanation", "0-0": "Source Container", "0-1": "A container from your Inventory with aliquots that you wish to transfer.", "1-0": "Destination Container", "1-1": "A container, new or from your Inventory, to which you wish to transfer aliquots." }, "cols": 2, "rows": 2 } [/block] [block:api-header] { "type": "basic", "title": "Required parameters" } [/block] [block:callout] { "type": "info", "body": "Cherry pick uses a single channel pipette to perform the liquid handling. To learn more about single channel liquid handling and the `transfer` command please see [here](https://developers.transcriptic.com/docs/liquid-handling#section-transfer)", "title": "Cherry pick uses `transfer`" } [/block] [block:parameters] { "data": { "h-0": "Parameter", "h-1": "Explanation", "0-0": "Cherry Pick Sets", "2-0": "Destination Container", "3-0": "New Plate Name (new container)", "4-0": "Storage Condition", "1-0": "Confirm Source Volumes", "0-1": "A cherry pick set defines all parameters for a set of transfers from one source plate to one destination plate. Additional cherry pick sets may be specified by clicking the 'Add Cherry Pick Sets' link at the bottom of the current cherry pick set.", "1-1": "Confirm that your source wells have sufficient volume to execute the specified transfer. If unchecked the protocol will be executed even if some wells do not have the required volume.", "2-1": "Select either a new container or a container from your inventory to contain the transfer volume from the source quadrant. \n\n'Create a new destination plate' allows you to transfer aliquots to any location in the new container or combine aliquots in the new container.\n\n'Sequentially transfer cherry picked samples to a new container' will automatically transfer aliquots one by one to successive wells in a new container.", "3-1": "The name for the resulting new container.", "4-1": "The storage temperature you require for the new container: either `cold_80`, `cold_20`, `cold_4` or `ambient`.", "5-0": "Container Type (new container)", "5-1": "The container type for the new container. Select from `96-pcr`, `96-flat`, `96-deep`, `384-pcr`, `384-flat`, or `384-echo`.", "6-0": "Upload Transfer Map", "6-1": "For 'Create a new destination plate', specify the source well, destination well, and transfer volume (see 'Use this template' next to the upload box).\n\nFor 'Sequentially transfer cherry picked samples to a new container', specify the source well and transfer volume (see 'Use this template' next to the upload box)." }, "cols": 2, "rows": 7 } [/block] [block:api-header] { "type": "basic", "title": "Protocol Outputs" } [/block] This protocol outputs a either a new container or an existing container with the specified aliquots and volumes transferred from the source container to the destination container. New containers will be stored in your Inventory at the specified storage condition. Existing containers will be returned to the storage condition from which they came. No measurement data is returned by this protocol. [block:api-header] { "type": "basic", "title": "Recommended guidelines" } [/block] Ensure you are aware of the dead volume in your source container. Dead volumes can be found in the containers section [here](https://developers.transcriptic.com/docs/containers#compatible-container-types). Failure to take into account dead volumes can result in insufficient volume being pipetted. [block:api-header] { "type": "basic", "title": "Further reading" } [/block] [block:callout] { "type": "success", "body": "For further advice on your protocol please ask questions to the community at https://forum.transcriptic.com", "title": "Check out the forum if you have more questions." } [/block]