comment cleanup

Author: mjhuff

app/src/organisms/Desktop/Devices/ProtocolRun/SetupLabwarePositionCheck/FlexSetupLPC/index.tsx

@@ -9,10 +9,6 @@ import { LPCSetupOffsetsTable } from './LPCSetupOffsetsTable'
 
 import type { SetupLabwarePositionCheckProps } from '..'
 
-// TOME TODO: The state updates don't seem to work if offsets are applied for some reason.
-//  Is there any way to sync that info? I guess it's not terrible if you can't, but
-//  applying offsets once to a run per app seems wise.
-
 export function FlexSetupLPC(
   props: SetupLabwarePositionCheckProps
 ): JSX.Element {

app/src/organisms/LabwarePositionCheck/LPCFlows/useLPCFlows.ts

@@ -63,8 +63,6 @@ export function useLPCFlows({
   const [isLaunching, setIsLaunching] = useState(false)
   const [hasCreatedLPCRun, setHasCreatedLPCRun] = useState(false)
 
-  // TOME TODO: Check that offset requests don't happen if we are looking at a historical
-  // run. Make sure run setup is disabled, too.
   const isFlex = robotType === FLEX_ROBOT_TYPE
   const deckConfig = useNotifyDeckConfigurationQuery().data
   const { data: runRecord } = useNotifyRunQuery(runId ?? null)

app/src/organisms/ODD/ProtocolSetup/ProtocolSetupOffsets/SetupOffsetsHeader.tsx

@@ -19,8 +19,6 @@ import {
 import { useAddLabwareOffsetToRunMutation } from '@opentrons/react-api-client'
 import { useState } from 'react'
 
-// TOME TODO: Test that you can't launch LPC if you have steps that need to be complete first?
-
 export function SetupOffsetsHeader({
   runId,
   setSetupScreen,

app/src/pages/ODD/ProtocolSetup/index.tsx

@@ -116,10 +116,6 @@ import type {
 
 const FETCH_DURATION_MS = 5000
 
-// TOME TODO: I think you HAVE to have the behavior that if someone else updates offsets,
-// for the run, you HAVE to consider those offsets as applied. Otherwise that could lead
-//  to offset confusion.
-
 const ANALYSIS_POLL_MS = 5000
 interface PrepareToRunProps {
   runId: string