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: "For the interactive qa plotting, I have been occasionally using a dask cluster running on the head node of lsst-dev.  However, I have been running this from my own special conda environment.  The command I have been executing is the following:  {noformat}  mpiexec -np 12 dask-mpi --scheduler-file scheduler.json  --nthreads 1  {noformat}  from {{/scratch/<USER>dask}}, and this has been starting up a dask cluster I can connect to when I'm dealing with large datasets.  However, as using a personal conda environment is clearly not sustainable, this needs to be possible to do in the context of the shared stack.  (Additionally, it ideally should be possible to start a dask cluster on the actual cluster, via slurm, but that is probably an issue for another ticket.)    When I try this with the current stack (currently being interactive-QA-enabled by [~<USER> in DM-13632), I get the following sorts of errors:    {noformat}  [<USER>lsst-dev01 dask]$ mpiexec -np 12 dask-mpi --scheduler-file scheduler.json  --nthreads 1  distributed.scheduler - INFO - Clear task state  distributed.scheduler - INFO -   Scheduler at: tcp://141.142.237.49:8786  distributed.scheduler - INFO -       bokeh at:                     :8787  distributed.nanny - INFO -         Start Nanny at: 'tcp://141.142.237.49:22996'  distributed.nanny - INFO -         Start Nanny at: 'tcp://141.142.237.49:31512'  distributed.nanny - INFO -         Start Nanny at: 'tcp://141.142.237.49:23697'  distributed.nanny - INFO -         Start Nanny at: 'tcp://141.142.237.49:26871'  distributed.nanny - INFO -         Start Nanny at: 'tcp://141.142.237.49:31404'  distributed.nanny - INFO -         Start Nanny at: 'tcp://141.142.237.49:2175'  distributed.nanny - INFO -         Start Nanny at: 'tcp://141.142.237.49:13582'  distributed.nanny - INFO -         Start Nanny at: 'tcp://141.142.237.49:28105'  distributed.nanny - INFO -         Start Nanny at: 'tcp://141.142.237.49:22621'  distributed.nanny - INFO -         Start Nanny at: 'tcp://141.142.237.49:22647'  distributed.nanny - INFO -         Start Nanny at: 'tcp://141.142.237.49:14319'  [cli_8]: write_line error; fd=37 buf=:cmd=init pmi_version=1 pmi_subversion=1  :  system msg for write_line failure : Bad file descriptor  [cli_8]: Unable to write to PMI_fd  [cli_8]: write_line error; fd=37 buf=:cmd=get_appnum  :  system msg for write_line failure : Bad file descriptor  Fatal error in PMPI_Init_thread: Other MPI error, error stack:  MPIR_Init_thread(474):  MPID_Init(152).......: channel initialization failed  MPID_Init(426).......: PMI_Get_appnum returned -1  [cli_8]: write_line error; fd=37 buf=:cmd=abort exitcode=1094159  :  system msg for write_line failure : Bad file descriptor  distributed.nanny - WARNING - Worker process 178401 was killed by unknown signal  distributed.nanny - WARNING - Restarting worker  [cli_8]: write_line error; fd=37 buf=:cmd=init pmi_version=1 pmi_subversion=1  :  system msg for write_line failure : Bad file descriptor  [cli_8]: Unable to write to PMI_fd  [cli_8]: write_line error; fd=37 buf=:cmd=get_appnum  {noformat}  etc.    I'm not sure who would be able to debug this, but ideally if there's anyone at NCSA who's familiar with dask and able to support me with this (and with the future dask@slurm issue), that would be great."
Answer: 418341.0