give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "While testing the M1M3 component at NCSA I noticed a couple things that needs fixing. These are mostly related to the SAL component behavior so, as far as I understand, it should apply to the component as a whole and not only the simulator.          1 - Component crashes if it doesn't find configuration file during start command.       Expected behavior: If I send a start command a {{settingsToApply}} that is not valid the CSC should reject the command with ack = {{CMD_FAILED: -302}} and stay in STANDBY.      Current behavior: component core dumps.   {code:java}  m1m3                  | [2020-05-06 20:20:57.811] [loggername] [info] DigitalInputOutput: turnCellLightsOn()  m1m3                  | [2020-05-06 20:20:57.812] [loggername] [info] DigitalInputOutput: turnAirOn()  m1m3                  | [2020-05-06 21:04:15.490] [loggername] [info] StandbyState: start()  m1m3                  | [2020-05-06 21:04:15.490] [loggername] [info] Model: loadSettings(foo)  m1m3                  | [2020-05-06 21:04:15.490] [loggername] [info] Model: Loading ILC application settings  m1m3                  | [2020-05-06 21:04:15.491] [loggername] [info] Model: Loading force actuator application settings  m1m3                  | [2020-05-06 21:04:15.493] [loggername] [info] Model: Loading force actuator settings  m1m3                  | terminate called after throwing an instance of 'std::runtime_error'  m1m3                  |   what():  Cannot load /home/saluser/ts_m1m3support/SettingFiles/Sets///ForceActuatorSettings.xml: File was not found  m1m3                  | /home/saluser/.setup.sh: line 5:     9 Aborted                 (core dumped) /home/saluser/ts_m1m3support/ts_M1M3Support -c /home/saluser/ts_m1m3support/SettingFiles  {code}            2 - Component is not doing state transitions appropriately. The only transition that the CSC is performing is going from STANDBY to DISABLE. After that it is not possible to take to any other state, not even back to STANBY. Also, it is acknowledging the commands as complete but are not executing them.     I am attaching a script that will reproduce the problem. This is an example output:  {code:java}  Initial state is <State.STANDBY: 5> expected <State.STANDBY: 5>  got 303 expected 303  Next state is <State.DISABLED: 1> expected <State.DISABLED: 1>  got 303 expected 303  Timed out waiting for summary state. Expected <State.ENABLED: 2>  got 303 expected 303  Timed out waiting for summary state. Expected <State.DISABLED: 1>  got 303 expected 303  Timed out waiting for summary state. Expected <State.STANDBY: 5>{code}  3 - Component not rejecting commands when in STANDBY or DISABLED.    When sending commands for the CSC in standby it should reject the commands with ack=<SalRetCode.CMD_FAILED: -302>, instead it is accepting the commands with 303.     I'm attaching a script that will reproduce the problem. This is an example output.   {code:java}  Create domain  Create remote for M1M3  Initial state is <State.STANDBY: 5> expected <State.STANDBY: 5>  Testing command abort...  got msg='Timed out waiting for command acknowledgement', ackcmd=(ackcmd private_seqNum=26072628, ack=<SalRetCode.CMD_NOACK: -301>, error=0, result='No command acknowledgement seen')  Testing command abortProfile...  got 303 expected -302  Testing command abortRaiseM1M3...  got 303 expected -302  Testing command applyAberrationForces...  got 303 expected -302  Testing command applyAberrationForcesByBendingModes...  got 303 expected -302  Testing command applyActiveOpticForces...  got 303 expected -302  Testing command applyActiveOpticForcesByBendingModes...  got 303 expected -302  Testing command applyOffsetForces...  got 303 expected -302  Testing command applyOffsetForcesByMirrorForce...  got 303 expected -302  Testing command clearAberrationForces...  got 303 expected -302  Testing command clearActiveOpticForces...  got 303 expected -302  Testing command clearOffsetForces...  got 303 expected -302  Testing command disable...  got 303 expected -302  Testing command disableHardpointChase...  got 303 expected -302  Testing command disableHardpointCorrections...  got 303 expected -302  Testing command enable...  got 303 expected -302  Testing command enableHardpointChase...  got 303 expected -302  Testing command enableHardpointCorrections...  got 303 expected -302  Testing command enterControl...  got msg='Timed out waiting for command acknowledgement', ackcmd=(ackcmd private_seqNum=809273431, ack=<SalRetCode.CMD_NOACK: -301>, error=0, result='No command acknowledgement seen')  Testing command enterEngineering...  got 303 expected -302  Testing command exitControl...  got msg='Timed out waiting for command acknowledgement', ackcmd=(ackcmd private_seqNum=937073474, ack=<SalRetCode.CMD_NOACK: -301>, error=0, result='No command acknowledgement seen')  Testing command exitEngineering...  got 303 expected -302  Testing command lowerM1M3...  got 303 expected -302  Testing command modbusTransmit...  got 303 expected -302  Testing command moveHardpointActuators...  got 303 expected -302  Testing command positionM1M3...  got 303 expected -302  Testing command programILC...  got 303 expected -302  Testing command raiseM1M3...  got 303 expected -302  Testing command resetPID...  got 303 expected -302  Testing command runMirrorForceProfile...  got 303 expected -302  Testing command setLogLevel...  got msg='Timed out waiting for command acknowledgement', ackcmd=(ackcmd private_seqNum=1366699677, ack=<SalRetCode.CMD_NOACK: -301>, error=0, result='No command acknowledgement seen')  Testing command setThermalSetpoint...  got msg='Timed out waiting for command acknowledgement', ackcmd=(ackcmd private_seqNum=1410333065, ack=<SalRetCode.CMD_NOACK: -301>, error=0, result='No command acknowledgement seen')  Testing command setValue...  got msg='Timed out waiting for command acknowledgement', ackcmd=(ackcmd private_seqNum=1470788897, ack=<SalRetCode.CMD_NOACK: -301>, error=0, result='No command acknowledgement seen')  Testing command shutdown...  got 303 expected -302  Testing command standby...  got 303 expected -302  Testing command stopHardpointMotion...  got 303 expected -302  Testing command testAir...  got 303 expected -302  Testing command testForceActuator...  got 303 expected -302  Testing command testHardpoint...  got 303 expected -302  Testing command translateM1M3...  got 303 expected -302  Testing command turnAirOff...  got 303 expected -302  Testing command turnAirOn...  got 303 expected -302  Testing command turnLightsOff...  got 303 expected -302  Testing command turnLightsOn...  got 303 expected -302  Testing command turnPowerOff...  got 303 expected -302  Testing command turnPowerOn...  got 303 expected -302  Testing command updatePID...  got 303 expected -302  {code}   "
Answer: 6731.0