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: "We saw a regression in the TE1 metric on Dec 6th: [https://chronograf-demo.lsst.codes/sources/2/dashboards/2?refresh=10s&tempVars%5BDataset%5D=validation_data_hsc&tempVars%5BFilter%5D=HSC-R&lower=2019-11-28T04%3A40%3A00.000Z&upper=2020-03-14T03%3A40%3A00.000Z]    Regression is in quotes because it's not really a regression;  the problem is only in validate_drp, and started with the commit  {code} commit 7397373f0857cefcbb27b649c4ea122956b5991  Merge: 7ea8e08 a28823f  Author: taranu <<EMAIL>>  Date:   Mon Dec 2 17:47:27 2019 -0600      Merge branch 'tickets/DM-21380'{code}     h3. More detail from investigation    -----------------------------------    Jenkins runs and corresponding chronograph output. (Status is my own assessment of the TE1 metric).  {code}Chronograph      TE1        v_drp#  r#     status  tag  12/2/19 9:18     0.00001    1852    832    good    d_2019_12_02  12/6/19 6:32     0.00001    1856    32     good    v19_0_0  12/6/19 16:38    0.00004    1857    836    bad     d_2019_12_06  12/7/19 15:00    0.00004    1858    262    bad     w_2019_49  12/8/19 14:53    0.00004    1859    837    bad     d_2019_12_08    {code}  Unfortunately we lost the output of d_2019_12_03, d_2019_12_04, d_2019_12_05, because the additional time to compute CModel mags made the Jenkins run's fail when they timed out. Also, even though the v19_0_0 build git chronograph on the 6th, does not mean that the metric was fine on the 6th. v19 is based on an older stack.     This means the error started in either d03, d04, d05, or d06.    To isolate, I ran {{validate_drp}} with the {{w_2019_49}} stack. This tag ( {{w_2019_49}} ) is from post-TE1 regression, so if the problem was in processCcd, it would show up here. Indeed, it was able to reproduce the post-regression numbers.    I then reset a local {{validate_drp}} back in time to see if I could get the pre-TE1 numbers with the w49 stack. Indeed I could (which means that the problem is not in the PSF estimation or in processCcd)    Action between w49 and w48:  {code}*   a6117da - (HEAD, tag: w.2020.01, tag: w.2019.52, tag: w.2019.51, tag: w.2019.50, tag: w.2019.49) Merge pull request #108 from lsst/tickets/DM-21950 (4 months ago) <eryko  |\    | | * cdda12b - (origin/tickets/DM-22138) First attempt fix of the printing errors (3 months ago) <<USER>  | | * 9575cc8 - Remove unused args and kwargs. (3 months ago) <<USER>  | |/    | * cae20c0 - Post-review clean-up. (4 months ago) <<USER>  | * 3e18709 - Clean up task running code to provide proper exit status. (4 months ago) <<USER>  | * 32c361c - Add configuration options to allow different external calibrations to be used. (4 months ago) <<USER>  |/    *   b527627 - Merge branch 'tickets/DM-22495' (4 months ago) <taranu>  |\    | * 8d9b136 - (origin/tickets/DM-22495) Update CfhtQuick tests after DM-21380 (4 months ago) <taranu>  | * a243415 - Skip reporting metrics without valid specs (4 months ago) <taranu>  |/    *   80568d2 - Merge remote-tracking branch 'origin/tickets/DM-14909' (4 months ago) <<USER>  |\    | * 56910ad - (origin/tickets/DM-14909) Add disableCc=True to SConstruct. (4 months ago) <<USER>  |/    *   7397373 - Merge branch 'tickets/DM-21380' (4 months ago) <taranu>  |\    | * a28823f - (origin/tickets/DM-21380) Run meas_modelfit CModel by default in all configs (4 months ago) <taranu>  | * 8fbc737 - Rename skipGalaxies to skipNonSrd (4 months ago) <taranu>  | * e6898a1 - Move repeatability measurements into own file (4 months ago) <taranu>  | * baaa35e - Add sample config using meas_modelfit (CModel) (5 months ago) <taranu>  | * f2cf730 - Compute model/galaxy/PSF photometric repeatability for fixed S/N bins (5 months ago) <taranu>  | * 9efdb04 - Fix log formatting (5 months ago) <taranu>  | * 575dc43 - Count failure on None spec (5 months ago) <taranu>  | * f6ee8f2 - Ignore specs with no metrics (5 months ago) <taranu>  | * cdb422c - Add methods to compute model/galaxy photometric repeatability (5 months ago) <taranu>  | * ce445dd - Avoid repeated evaluation of a constant (5 months ago) <taranu>  | * 523f536 - Use random.sample instead of copy + shuffle (5 months ago) <taranu>  |/    *   7ea8e08 - (tag: w.2019.48, tag: w.2019.47, tag: w.2019.46, tag: w.2019.45, tag: w.2019.44, tag: w.2019.43, tag: w.2019.42, tag: w.2019.41, tag: v19.0.0.rc1, tag: 19.0.0)   {code}  Results are in:    /project/<USER>test_TE1_backout/validate_drp/examples/80568d2 = already BAD    /project/<USER>test_TE1_backout/validate_drp/examples/7397373 = already BAD    /project/<USER>test_TE1_backout/validate_drp/examples/7ea8e08 = still GOOD    TE1:    80568d2 Y : 0.00016300953007042908   7397373 Y : 0.00016300953007042908   7ea8e08 Y : 0.00023879374525127478    80568d2 R : 3.714449965298656e-05   7397373 R : 3.714449965298656e-05   7ea8e08 R : 1.296386266161025e-05    80568d2 I : 4.457782063995298e-06   7397373 I : 4.457782063995292e-06   7ea8e08 I : 3.161328145013072e-06    *commit 7397373 is the culprit*    My guess is that you’re modifying {{matchedDataset}} [https://github.com/lsst/validate_drp/blob/master/python/lsst/validate/drp/validate.py#L369] before passing it to {{measureTEx}}.    In fact, {{--skipNonSrd}} brings the metrics back to normal. I propose we add that until you can get the the PA metric from messing with it."
Answer: 12297.0