Class: CherrypickPipeline

Inherits:
CherrypickingPipeline show all
Defined in:
app/models/cherrypick_pipeline.rb

Overview

Note:

Cherrypicking is typically processed by an SSR, and the batch worksheet is passed over to the lab. Actual lab work is tracked via Robot::Verification::Base classes through the RobotVerificationsController

Processes CherrypickRequest Allows material from wells on one or more source plates to be laid out onto either a NEW plate of a specified PlatePurpose or onto a plate created as part of an earlier cherrypick.

WARNING! Cherrypick requests create their target wells upfront and are laid out onto otherwise well-less plates. This results in odd behaviour: - You cannot cherrypick onto plates with all their wells, even if those wells are empty - Prior to processing, wells attached to cherrypick requests will not be assigned to a plate. - Occasionally it is possible to pick two wells to the same location. This does not result in pooling or a tag clash, but rather two wells with the same location on the same plate.

Constant Summary

Constants inherited from CherrypickingPipeline

CherrypickingPipeline::PICKED_STATES

Instance Method Summary collapse

Methods inherited from CherrypickingPipeline

#pick_information?, #request_actions, #robot_verified!

Methods included from Pipeline::GroupByParent

#extract_requests_from_input_params, #input_labware, #output_labware, #requests_in_inbox

Methods included from Pipeline::InboxGroupedBySubmission

included

Methods inherited from Pipeline

#all_requests_from_submissions_selected?, #completed_request_as_part_of_release_batch, #detach_request_from_batch, #extract_requests_from_input_params, #input_labware, #is_flowcell_type_consistent_for_batch?, #is_read_length_consistent_for_batch?, #on_start_batch, #output_labware, #pick_information?, #request_actions, #request_count_in_inbox, #request_types_including_controls, #requests_in_inbox, #robot_verified!

Methods included from SharedBehaviour::Named

included

Methods included from Pipeline::BatchValidation

#validation_of_batch

Methods included from Uuid::Uuidable

included, #unsaved_uuid!, #uuid

Methods inherited from ApplicationRecord

alias_association, convert_labware_to_receptacle_for, find_by_id_or_name, find_by_id_or_name!

Methods included from Squishify

extended

Instance Method Details

#post_finish_batch(batch, user) ⇒ Object 



18
19
20
 
# File 'app/models/cherrypick_pipeline.rb', line 18

def post_finish_batch(batch, user)
  # Nothing, we don't want all the requests to be completed
end

#post_release_batch(batch, _user) ⇒ Object

rubocop:todo Metrics/MethodLength



22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
 
# File 'app/models/cherrypick_pipeline.rb', line 22

def post_release_batch(batch, _user) # rubocop:todo Metrics/MethodLength
  target_purpose = batch.output_plates.first.purpose.name

  # stock wells
  batch
    .requests
    .select(&:passed?)
    .each do |request|
      request.asset.stock_wells.each do |stock|
        EventSender.send_pick_event(stock, target_purpose, "Pickup well #{request.asset.id}")
      end
    end
  batch.release_pending_requests
  batch.output_plates.each(&:cherrypick_completed)
end