udaykiran19491/user-stories-from-tawos-for-llm-fine-tuning huggingface dataset:
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: "At the DMLT telecon of 2017-06-26, we agreed to:    - Not provide LDM-472 to reviewers;  - Remove mention of LDM-472 from DMTN-020 (which will go to reviewers);  - Transfer all useful information from LDM-472 to LDM-294 (which will go to reviewers)."
Answer: 1880.0

User story: "Need to get text for software postdoc, software developer positions to Mindy by 2017-07-01, agree whether developer is an HR or DoF position."
Answer: 21725.0

User story: "TO update the README.md file to be in sync with our code status."
Answer: 136613.0

User story: "Create HSC-model donut images in Zemax (using HuygensPSF tool).  Convolve in some Kolmogorov seeing and sprinkle on some Gaussian pixel noise.  Fit said images using Zernike wavefront forward model.  Average together intra- and extra-focal wavefront coefficients.  Use average wavefront to produce a prediction for the in-focus PSF.  Compare with Zemax in-focus PSF (also produced using HuygensPSF tool).  Repeat for different focal plane positions.  Repeat with a misaligned Zemax model.  Profit.  "
Answer: 114947.0

User story: "After learning the basics of docker from https://www.safaribooksonline.com/library/view/learning-path-devops/9781786463937/ in this ticket I will create a Dockerfile for squash starting from the official image for python at https://hub.docker.com/_/python/   "
Answer: 5374.0

User story: "Implement a bare bones matching algorithm for DIAObjects/DIASources. Will likely be a simple nearest neighbor search with association of multiple objects ranked by distance only."
Answer: 104949.0

User story: "Create abstraction layer interface to persist DIAObjects and DIASource into a data structure. Data structure will either be the L1DB prototype or the butler. "
Answer: 124955.0

User story: "Implement the design as planned in DM-11038."
Answer: 50484.0

User story: "Come up with a skeleton design for DIAObjects in ap_association. Partly to be discuss during UW brownbag on 6/28/17"
Answer: 13021.0

User story: "Create a new, possibly temporary, repository for the source association task and related DIA data types. "
Answer: 1378.0

User story: "Gordon Richards has provided numerous cutouts  surrounding quasars from SDSS and Decals images. We want to see if the new DCR algorithm can correctly identify these quasars, but to do so I need to first force the data to look like LSST exposures. The result will be a brief report containing measurements of the detected objects using DM-6904."
Answer: 41897.0

User story: Extend the "Getting Started" tutorial series with a tutorial on using afw.display to display exposures and source tables from the processCcd.py step. This is a realistic step users will want to perform to understand the output of processCcd.py before proceeding with coaddition. The tutorial will also introduce table, dataset, and other Python API concepts.
Answer: 43449.0
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: "I recovered data taken by French team Marc Moniez and Jérémy neveu (LAL - CNRS) at CTIO 0.9-m telescope during 16 nights between May 26th and June 13th.  Both Ronchi and Holograms where tested.   I am mostly interested in the Ronchi data : in particular, a spatial scan of the Ronchi to check for transmission as a function of position.    "
Answer: 10027.0

User story: "Furusawa-san writes:  {quote}  Ikeda-san and I noticed that defects masking for ccd=43 set in the  hscPipe 5.0 was insufficient for recent data. Irregular counts in a  channel of ccd43 leak into the coadd image. Please see the attached  figure. Right panel is a resultant coadd (wide g tract=9813 patch=6,5)  with the default hscPipe 5.0, and the left panel is the reprocessed  data with a modified mask.     I am sorry for my last proposal of the mask, which was incomplete, and  to have not found this problem earlier. If possible we would like to  update the defects for ccd=43. We suggest to mask the whole channel  for all ccd=43 data since 2016-04-01, i.e., use the below for ccd=43  (in 2016-04-01, 2016-11-22, and 2016-12-23):  -----------------------------  43   0     0     512   4176  -----------------------------  {quote}"
Answer: 12.0

User story: "h1. Objectives    *ATTENTION*: This investigation relies on the infrastructure, tools and datasets developed in a context of [DM-10988].    Study parallel options for loading Qserv *secondary index* (assuming the present InnoDB-based implemented). The main objective of the study to see if there is a possibility to improve the performance of the (loading) process for large (multi-billion rows) catalogs.Test if input data pre-ordering will make any difference on the aggregate performance.    Also, in a context of this effort investigate an effect of various storage technologies (including hardware RAID of spinning disks, SSD and NVMe) on the performance of the loader.    Post a summary of observations and conclusions into the same Confluence document which was set up for [DM-10988]:  * [https://confluence.lsstcorp.org/pages/viewpage.action?pageId=62259715]    h1. Resources    Run the tests on *ccqserv150.in2p3.fr* (a member of the Qserv cluster in IN2P3).    h1. References    These are interesting ideas on speeding up the loading process from the key MySQL developer:  * [https://www.percona.com/blog/2007/05/24/predicting-how-long-data-load-would-take/]    "
Answer: 5570.0

User story: {{PsfAttributes}} were deprecated and replaced with Psf class methods.  This ticket is limited to instances in python (excluding the unit test in {{meas_algorithms}}), and including the unmaintained {{datarel}} and {{testing_pipeQA}} because they're both under "lsst" and I do not want instances of {{PsfAttributes}} showing up when I grep the stack.     Triggered by:  https://community.lsst.org/t/psf-matching-of-exposuref-image-cutouts-problem-with-xy0/2010
Answer: 7322.0
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: "An import typo in scisql was breaking the qserv container builds at the master/worker step under py2.  Incorporate upstream patch to fix this."
Answer: 28.0

User story: "The switch, pdu, + kvm for the macpros need to be unboxed, checked for basic function, have firmware updates installed and have basic network configuration."
Answer: 50335.0

User story: A common failure mode in {{measureCoaddSources.py}} is:  {code}  \[...\]    File "/global/common/cori/contrib/lsst/lsstDM/v13_0/Linux64/meas_deblender/13.0/python/lsst/meas/deblender/plugins.py", line 819, in _handle_flux_at_edge      psfim = psf.computeImage(afwGeom.Point2D(xc, yc))    File "/global/common/cori/contrib/lsst/lsstDM/v13_0/Linux64/afw/13.0/python/lsst/afw/detection/detectionLib.py", line 3767, in computeImage      return _detectionLib.Psf_computeImage(self, *args)  lsst.pex.exceptions.wrappers.RangeError:     File "src/WarpedPsf.cc", line 74, in lsst::afw::geom::Box2I lsst::meas::algorithms::{anonymous}::computeBBoxFromTransform(lsst::afw::geom::Box2I, const lsst::afw::geom::AffineTransform&)      Unexpectedly large transform passed to WarpedPsf {0}  lsst::pex::exceptions::RangeError: 'Unexpectedly large transform passed to WarpedPsf'  {code}    This usually signals bad astrometry in one of the inputs, but _which_ input? It would be helpful if {{CoaddPsf}} could identify the input image in question.
Answer: 135181.0

User story: "We don't have any master calibs since September 2016. Please build some."
Answer: 44712.0

User story: "The present AP Prototype Pipeline script {{decam_process.py}} has a few hard-wired settings to define repository names etc., requires an additional step outside of the script to ingest defects, and only uses visits as templates. In principle it should be a command-line python script that can be used on any DECam images. This ticket includes  * Changing hard-wired inputs in main() to be handled via argparse or similar  * Adding the ingestion of DECam defect images to the script  * Extending the script to handle either a visit or a coadd to be a template  * Think about the best way to handle datasets with more than one filter (ok not to implement this yet, but don't hard-wire any filter business)  * Updating the technote DMTN-039 and {{lsst-dm/decam_hits}} repo README to describe the new behavior"
Answer: 69462.0

User story: "Reprocess the HSC RC dataset using {{w_2017_25}} following the same steps as in DM-10129 "
Answer: 9925.0

User story: "Add README files for everything going into {{/datasets/hsc/}} to specify at least the relevant RFC.       {{cosmos}} → RFC-266.   {{ssp_extra}} → RFC-323  {{ssp_pdr1}} → RFC-297.    {{commissioning}} or {{newhorizons}}  predate the policy and arrived via DM-7985,"
Answer: 518863.0

User story: "RFC-25 triggered DM-7477 to increase the mask plane from 16 bits to 32 bits. Firefly has the function to display mask plane when it is part of teh extension. We need to double check to make sure the display still works. "
Answer: 207833.0
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: "Create a stand-alone documentation site for {{display_firefly}}; content is created in DM-10601."
Answer: 5739.0

User story: When DAX has problem as today (6/22/17), select the table "Forced photometry based on i-band coadds" table from "SDSS Stripe82" in http://localhost:8080/firefly/lsst-pdac-triview.html;a=layout.showDropDown, in the metadata table area SUIT throws out this error message:    "Catalog Fetch Error: edu.caltech.ipac.firefly.server.query.DataAccessException: DataAccessException:ERROR:DAX Error: OperationalError from:unknown"    We need to improve the error message, following exception convention implemented by Trey in ticket DM-10560, for our users.
Answer: 49074.0

User story: "Building on the work started by [~<USER> in DM-10801."
Answer: 1342.0

User story: "Publish [LDM-542|https://github.com/lsst/LDM-542] to LSST the Docs, with a landing page pointing to PDFs with the Lander project"
Answer: 33.0

User story: "{{Footprint.transform}} contains the following code:  {code}  std::shared_ptr<Footprint> Footprint::transform(geom::XYTransform const& t, ...      ...      // now populate the new Footprint with transformed Peaks      for (auto const& peak : getPeaks()) {          // Transform the x y Point          auto newPoint = t.forwardTransform(geom::Point2D(peak.getFx(), peak.getFx()));          newFootprint->addPeak(newPoint.getX(), newPoint.getY(), peak.getPeakValue());      }  {code}    I strongly suspect it should be transforming Fx, Fy instead of Fx, Fx. If so, the code would be simpler and less error-prone as:  {code}  auto newPoint = t.forwardTransform(peak.getF());  {code}    In the same vein: a variant of {{addPeak}} that took a {{Point2D}} for the position would be a useful addition."
Answer: 21420.0
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: On Slack, [~<USER> reports the following error:    {code}  makeCoaddTempExp INFO: directWarp has 3644518 good pixels (20.7%)  Traceback (most recent call last):    File "/sps/lsst/software/lsst_distrib/w_2017_24/stack/miniconda2-4.2.12-7c8e67/Linux64/jointcal/master-gc935ebf72c+3/bin/jointcalCoadd.py", line 5, in       JointcalCoaddTask.parseAndRun()    File "/sps/lsst/software/lsst_distrib/w_2017_24/stack/miniconda2-4.2.12-7c8e67/Linux64/pipe_base/13.0-9-g1c7d9c5+3/python/lsst/pipe/base/cmdLineTask.py", line 514, in parseAndRun      resultList = taskRunner.run(parsedCmd)    File "/sps/lsst/software/lsst_distrib/w_2017_24/stack/miniconda2-4.2.12-7c8e67/Linux64/pipe_base/13.0-9-g1c7d9c5+3/python/lsst/pipe/base/cmdLineTask.py", line 223, in run      resultList = list(mapFunc(self, targetList))    File "/sps/lsst/software/lsst_distrib/w_2017_24/stack/miniconda2-4.2.12-7c8e67/Linux64/pipe_base/13.0-9-g1c7d9c5+3/python/lsst/pipe/base/cmdLineTask.py", line 373, in __call__      result = task.run(dataRef, **kwargs)    File "/sps/lsst/software/lsst_distrib/w_2017_24/stack/miniconda2-4.2.12-7c8e67/Linux64/pipe_base/13.0-9-g1c7d9c5+3/python/lsst/pipe/base/timer.py", line 121, in wrapper      res = func(self, *args, **keyArgs)    File "/sps/lsst/software/lsst_distrib/w_2017_24/stack/miniconda2-4.2.12-7c8e67/Linux64/pipe_tasks/13.0-37-g58c8d4e+3/python/lsst/pipe/tasks/makeCoaddTempExp.py", line 282, in run      exps = self.createTempExp(calexpRefList, skyInfo, visitId).exposures    File "/sps/lsst/software/lsst_distrib/w_2017_24/stack/miniconda2-4.2.12-7c8e67/Linux64/pipe_tasks/13.0-37-g58c8d4e+3/python/lsst/pipe/tasks/makeCoaddTempExp.py", line 390, in createTempExp      inputRecorder[warpType].finish(coaddTempExps[warpType], totGoodPix[warpType])    File "/sps/lsst/software/lsst_distrib/w_2017_24/stack/miniconda2-4.2.12-7c8e67/Linux64/pipe_tasks/13.0-37-g58c8d4e+3/python/lsst/pipe/tasks/coaddInputRecorder.py", line 134, in finish      apCorrMap = makeCoaddApCorrMap(self.coaddInputs.ccds, coaddTempExp.getBBox(afwImage.PARENT), wcs)    File "/sps/lsst/software/lsst_distrib/w_2017_24/stack/miniconda2-4.2.12-7c8e67/Linux64/meas_algorithms/13.0-13-gf5c99ad+3/python/lsst/meas/algorithms/makeCoaddApCorrMap.py", line 52, in makeCoaddApCorrMap      everything[name].append(CoaddBoundedFieldElement(bf, wcs, validPolygon, weight))  TypeError: __init__(): incompatible constructor arguments. The following argument types are supported:      1. lsst.meas.algorithms.coaddBoundedField.CoaddBoundedFieldElement(field: lsst.afw.math._boundedField.BoundedField, wcs: lsst.afw.image.wcs.wcs.Wcs, validPolygon: lsst::afw::geom::polygon::Polygon, weight: float=1.0)    Invoked with: BoundedField(ChebyshevBoundedField ((3,3,) coefficients in y,x) on Box2I(Point2I(0, 0), Extent2I(2048, 4612))), , None, 1.0  {code}    This is because we don't define {{validPolygon}}​s for CFHT, and that makes the {{CoaddBoundedFieldElement}} constructor unhappy.
Answer: 8878.0
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: "This ticket addresses some clean up issues with the documenteer package to make it easier to use with DM's different Sphinx documentation projects.    - Convert dependencies for specific types of documents (pipelines.lsst.io vs tech notes, for example) to use {{extras_require}} (http://setuptools.readthedocs.io/en/latest/setuptools.html#id14)  - Use Travis's PyPI deployments to make it easier to create new releases.    This ticket will create a 0.2.0 release so that existing technotes aren't affected (they are pinned to documenteer < 0.2)"
Answer: 27091.0

User story: Jenkins is intermittently failing while building {{lsst_ci}} with the complaint "Unequal schemas between input record and mapper". Simply running Jenkins again almost always suffices for it to pass. The problem is usually (perhaps always) seen on the Python 3 build.    Here is an example build:  https://ci.lsst.codes/job/stack-os-matrix/23916/label=centos-7,python=py3/console    Another issue is that when the problem occurs the build continues for a long time, so the error message is buried deep in the log and hard to find. Perhaps a task is being run without {{--doraise}}? If so, please consider changing this, so that the failure is quick and obvious.    The problem is very common and potentially costly in developer time, because it can take awhile to realize what's wrong and to realize it is not the fault of whatever software changes are being tested.
Answer: 67600.0

User story: "The pipelines.lsst.io build tool will coordinate builds of the pipelines.lsst.io Sphinx site. Its main functionality is:    - Symlink doc/ directories of packages into a pipelines.lsst.io clone  - Add configuration information (like the current tag, or if working on master, the branches and most recent tag)  - Run the Sphinx build    Some of this functionality is already coded in LTD Mason, however, it should be moved to https://github.com/lsst-sqre/documenteer, our core package for DM Sphinx projects. (I'm slowly breaking LTD Mason apart; I think having a single package that was both an LTD upload tool and a build tool was a wrong fit)."
Answer: 41602.0

User story: "With the Git LFS updates, the Git LFS documentation (https://developer.lsst.io/tools/git_lfs.html) as written seems to be unclear. This ticket will clean that up."
Answer: 519.0

User story: "In DM-10801, [~<USER> has started the process of converting DMTN-020 from reST to TeX. Although the basic text is in place, some of the structure (cross references, citations, glossary, etc) did not survive the transition. Please fix it up."
Answer: 100.0

User story: "The recent pyyaml change to build on top of libyaml busted the Qserv base container builds.      It looks like a necessary -L option for libyaml is missing of the CFLAGS additions in the build() override in the eupspkg.cfg.sh; in miniconda installs this goes unnoticed since the lib is picked up from miniconda.  Since the Qserv base containers are non-miniconda builds, they broke."
Answer: 919.0
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: There are a couple of small issues with {{lsst-sqre/buildbot-scripts}} that could be improved, including:    * Inconsistent use of true/false, 0/1, and "yes"/"no" for boolean values.  * printing of variables that are no longer in use (DEMO_ROOT & DEMO_TGZ).  * inconsistent use of posix and bash style conditional expressions
Answer: 1300.0

User story: "At this point, no package should be dependent on inheriting deps from {{lsst/lsst}} nor using any environment variables declared in its table file."
Answer: 1285.0

User story: "Create one-stop save-shutdown-logout command for JupyterLab"
Answer: 11603.0

User story: "Consult DES operators what features they consider essential/important when it comes to dealing with workflow management, what capabilities they would see as significant improvements over the currently available ones."
Answer: 21594.0

User story: "During production job failures are to be expected either due to infrastructure failures such as network or node failures but also due to faulty applications. The goal is to understand:  * what are conditions making _Pegasus_ to consider a job as failed one,  * what happens after a job enters a failed state, i.e.:  ** how a failure affect transferring job's intermediate/output files (if any),  ** what happens if failure occurs in a job cluster,  * how retries work in practice, i.e.:  ** can an operating organization control number of retries,   ** can an operating organization make _Pegasus_ retry on certain failures but not other,"
Answer: 113718.0

User story: "There are always overheads when scheduling jobs, commonly related to scheduling, data transfers, state notifications, and task book keeping. These overheads can be very noticeable for short jobs. The solution recommended by _Pegasus_ team to minimize those overhead is to use *task clustering*.  The goal is to explore this mechanism and access if it is flexible enough to address common operational requirements."
Answer: 21634.0

User story: "During the planning stage, _Pegasus_ traverses the graphs multiple times, and some of the graph transforms can be slow depending on if the graph is large. Pegasus developers suggest using *hierarchical workflows* in such cases. The goal is to:  * how those workflows work in practice,  * find out if they allow for creating dynamical workflows."
Answer: 103404.0

User story: "[~<USER> raised the issue on slack that some of recent changes to {{newinstall.sh}} install paths have complicated automated builds.    In particular, {{<eups_path>/site/startup.py}} has changed to incorporate the python env as a path component, which is difficult to predict.  Also, the {{./eups/current}} symlink is absolute instead of relative."
Answer: 420.0
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: "h1. Objectives    Evaluating implications of various storage technologies (including hardware RAID of spinning disks, SSD and NVMe) on the performance of the *secondary index* loading (assuming the present *InnoDB*-based implemented).    Compile a detailed report for the study at:  * [https://confluence.lsstcorp.org/pages/viewpage.action?pageId=62259715]    Post technical details and a progress of the study in comments attached by this issue.    h2. Resources    The study will be conduced on a special node *ccqserv150.in2p3.fr* of the *Qserv* cluster in *IN2P3*. This node is equipped with the following file systems:  * a redundant array (RAID6) of conventional spinning disks (*7.3 TB*)  * a single SSD disk (*3.0 TB*)  * a singe NVMe storage module (*1.9 TB*)    All three file systems are listed below:  {code:bash}  % df -h   Filesystem                   Size  Used Avail Use% Mounted on  /dev/nvme0n1                 1.9T   99G  1.8T   6% /qserv_nvm  /dev/sdb                     3.0T   96G  2.9T   4% /qserv_ssd  /dev/sdc                     7.3T   97G  7.2T   2% /qserv  {code}    Other key parameters of the machine:  * Memory: 512 GB  * CPU model: Intel(R) Xeon(R) CPU E5-2680 v4  * CPU (base) frequency: 2.40GHz  * L3 cache size: 32 MB   * Number of processors/cores: dual CPU, 16 physical cores per CPU (32 in total), HT enabled (64 hardware threads in total)    "
Answer: 10165.0

User story: "Read up on {{lsst.verify}}.  Good links to know are [verify|http://github.com/lsst/verify] and [https://sqr-019.lsst.io]."
Answer: 12706.0

User story: "Read up on {{lsst.verify}}.  Good links to know are [verify|http://github.com/lsst/verify] and {{https://sqr-019.lsst.io}}."
Answer: 112399.0

User story: In addition to the existing Python docstring documentation in {{firefly_client}}, it would be desirable to have "user guide"-type documentation, including examples, available.
Answer: 325562.0

User story: "We need some sort of mocked up interface to the level 1 database.  Specifically, this requires the ability to retrieve DIAObjects based on spatial position and the ability to put potentially updated versions of those DIAObjects back from multiple threads.    Ideas were to either use a sqlite database and interact directly through SQL, but it might be informative to have a shimmed butler interface to do this interaction.    In either case, the schema are defined and reside in the {{cat}} package."
Answer: 10119.0

User story: "Make sure configs for ImageDifference.py include the decorrelation step."
Answer: 51701.0

User story: "This is a multi step process:  # Copy relevant products from 2014 output repositories to 2015 input repository  ** This will include but may not be limited to: skymap, goodSeeingCoadd, goodSeeingCoadd_results (or is it meas, I don't remember)  # Update config for ImageDifference.py to use a coadd template instead of a science image.  # Run ImageDifference.py on 2015 data  # Likely we will have to somehow throw out very good seeing data."
Answer: 113542.0
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: "Bring the good seeing ImageSelector from the Twinkles branch into the {{decam_hits}} repository.  Add a {{goodSeeingCoadd}} config parameter to use it."
Answer: 156967.0

User story: * Get HiTS data for 2014 fields matching 2015 fields for the prototype AP system (DM-7925), to be used for template generation  * Once the dataset exists, make a git-lfs repo for it and/or add it to /datasets on lsst-dev (along with the 2015 field data to be used as "science").  This should adhere to the layout defined in DM-11116.
Answer: 63170.0

User story: "* Update lsst-dev butler repository to include Gaia ref cat (my be a no-op).  * Update DMTN instructions, if necessary.  * Update configs used by the prototype to use Gaia as the astrometric ref and PS1 (or SDSS) as the photometric ref"
Answer: 75118.0

User story: "Linearization was implemented in DM-6356. Make sure that linearity is still applied given the full decam ISR task."
Answer: 46159.0

User story: "At present {{SkyWcs}} is a subclass of {{Transform<Point2Endpoint, SpherePointEndpoint>}} and this means that {{pixelToSky}} transforms to {{SpherePoint}}. However {{SkyWcs}} is always normalized to ICRS and so {{pixelToSky}} should probably produce {{IcrsCoord}}.    The simplest way to change this is to change {{SpherePointEndpoint}} to {{IcrsCoordEndpoint}}. One obvious alternative is to keep both and change the endpoint class {{SkyWcs}} uses. However, we have no identified need for {{Transform}} to transform to {{SpherePoint}} (nor {{IcrsCoord}} except as a base class for {{SkyWcs}}). Furthermore if we have N {{Endpoint}} classes then we instantiate N^2 {{Transform}} classes. So I propose to simply rename for now."
Answer: 3081.0

User story: "as described on this wiki page https://confluence.lsstcorp.org/pages/editpage.action?pageId=58950873  update daf_persistence according to  RFC-215 and RFC-229"
Answer: 30195.0

User story: "Use jemalloc in hopes that it improves memory usage on the czar and may provide better debugging information. "
Answer: 40510.0

User story: "When a job is cancelled, all rows from that attempt of the job need to be removed from the userQuery result table or there could be duplicates."
Answer: 15948.0

User story: "Implement Python threading into while loops for checking messages on topics using DDS/OpenSplice."
Answer: 91976.0

User story: "Upgrade pybind11 version to 2.1.1 to pull in fix for DM-10916."
Answer: 1476.0

User story: "Implement Python threading into while loops for checking messages on topics using DDS/OpenSplice."
Answer: 51911.0

User story: "Continue the development of the obsCTIO_0m9 package started by Merlin.  Out of processCcd task :  - Evaluate the astrometric solution found on non-dispersed and dispersed images.  Then :  - From a correct solution, locate the object of interest and extract the footprints of both m+1 and m-1 spectra."
Answer: 308566.0

User story: "LDM-503 talks about LDM-534, the test plan for L2 productions. That document doesn't exist.    Create a draft version of it."
Answer: 20084.0
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: The LDM-294 build automatically extracts products from {{productlist.csv}} and lists them against the appropriate WBS element. However, this matching is exact: a product will only be listed against "02C.04.01", say, if the WBS recorded with the product is that string exactly.    In some cases, e.g. 02C.05, we only list the WBS in LDM-294 to the fourth level, while products are further subdivided. We should roll up products in fifth level (and deeper) elements and list them against the corresponding fourth level, unless there's a separate description of the fifth level element.
Answer: 228.0

User story: "As a pre-processing step before extracting other LaTeX commands, metasrc should filter the latex source:    - remove comments  - add input/included tex files.  - replace simple macros (those made with {{\def}} and {{\newcommand}})."
Answer: 36207.0

User story: "Publish [LSE-319|https://github.com/lsst-dmsst/LSE-319] to LSST the Docs, with a landing page pointing to PDFs with the Lander project"
Answer: 1065048.0

User story: "Publish [LDM-148|https://github.com/lsst/LDM-148] to LSST the Docs, with a landing page pointing to PDFs with the Lander project"
Answer: 3131.0

User story: "Ultra-faint dwarf galaxies are usually found from photometry of their bright member stars. However, these stars can be superimposed on the faint, unresolved light of the galaxy, which biases the measurement. We need to measure the PSF flux with a local background subtracted.    I originally started writing this as a background-subtracted PSF flux measurement algorithm, until I realised that simply measuring the background is all that's required (and dealing with inheritance in the measurement algorithms is annoying), and it can be subtracted from other measurements as well as the PSF flux."
Answer: 358490.0

User story: "Add WBS descriptions to the git repository [here|https://github.com/lsst/LDM-294] for the UW WBS elements."
Answer: 106867.0

User story: "Add accounts and install software necessary to begin benchmarking the L1 system on the phase 1 test platform. Formulate test plan."
Answer: 74615.0
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: Ticket named " 'Psf' object has no attribute 'resized'" as filed.     {{ModelPsfMatchTask}} calls {{Psf.resized}}, but that method is only defined for certain specialised {{Psf}} classes ({{SingleGaussianPsf}} and {{DoubleGaussianPsf}}). It should have a default implementation, and be defined for {{CoaddPsf}}.    {code}   > python modelPsfMatchTask.py --template 'data/SDSSJ0920+0034/calexp-HSC-I-9564-7,3.fits' --science 'data/SDSSJ0920+0034/calexp-HSC-R-9564-7,3.fits'    psfMatch INFO: compute Psf-matching kernel  psfMatch INFO: Adjusting dimensions of reference PSF model from (43, 43) to (41, 41)  Traceback (most recent call last):    File "modelPsfMatchTask.py", line 160, in <module>      run(args)    File "modelPsfMatchTask.py", line 130, in run      result = psfMatchTask.run(templateExp, scienceExp)    File "modelPsfMatchTask.py", line 45, in run      return ModelPsfMatchTask.run(self, scienceExp, templateExp.getPsf())    File "/Users/aisun/anaconda/envs/lsst/opt/lsst/pipe_base/python/lsst/pipe/base/timer.py", line 121, in wrapper      res = func(self, *args, **keyArgs)    File "/Users/aisun/anaconda/envs/lsst/opt/lsst/ip_diffim/python/lsst/ip/diffim/modelPsfMatch.py", line 274, in run      result = self._buildCellSet(exposure, referencePsfModel)    File "/Users/aisun/anaconda/envs/lsst/opt/lsst/ip_diffim/python/lsst/ip/diffim/modelPsfMatch.py", line 388, in _buildCellSet      referencePsfModel = referencePsfModel.resized(lenPsfScience, lenPsfScience)    File "/Users/aisun/anaconda/envs/lsst/opt/lsst/afw/python/lsst/afw/detection/detectionLib.py", line 3745, in <lambda>      __getattr__ = lambda self, name: _swig_getattr(self, Psf, name)    File "/Users/aisun/anaconda/envs/lsst/opt/lsst/afw/python/lsst/afw/detection/detectionLib.py", line 89, in _swig_getattr      raise AttributeError("'%s' object has no attribute '%s'" % (class_type.__name__, name))  AttributeError: 'Psf' object has no attribute 'resized'  {code}    Bug reported by [Ai-Lei Sun|mailto:<EMAIL>].
Answer: 40471.0

User story: "Develop an example notebook showing how an instance of {{firefly_client.FireflyClient}} to widgets from {{firefly_widgets}}."
Answer: 330193.0

User story: "This will make it much easier to change the runtime behavior without having to spin a new container."
Answer: 159.0

User story: "Create a firefly entry point that appears as a blank canvas. The user (via api or drop downs) then add add images, tables, and charts at any position and move them around.  This is for use with the remote API.    The user should have a very fine grain control over his layout and what appears together.    This layout should scroll that the users can stack many cells together."
Answer: 59123.0

User story: "{{newinstall.sh}} should be updated to use eups 2.1.3 to reduce the time required to install binary tarballs.  {{lsstsw}} should be updated at the same time to keep our build envs in sync."
Answer: 5693.0
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: "Qserv doesn't work with macOS Sierra because {{libcrypto}} is no longer present. It is not needed for the link."
Answer: 8125.0

User story: "Based on a request from Brian Selvy to all subsystems, update the ICD status tracking sheet Document-19424 to reflect appropriate need dates, issues, etc."
Answer: 1433514.0

User story: Search through the stack for uses of {{Err}} and {{Sigma}} and note whether they are correct per the DPDD (see RFC-333). Once they are found, decide how to fix them all (via a "search and replace swap" function?), and fix them all.    We probably want to do this "bottom up", similar to the process that was used for the python3 and pybind11 conversions: fix everything in {{base}}, then {{meas}}, then {{afw}}
Answer: 636174.0

User story: "Find all uses of {{Err}} and {{Sigma}} in the schemas (cat, SourceCatalogs, ReferenceCatalogs, anywhere else that database schema definitions live) determine if they are correct or not, and fix the ones that are incorrect.    We probably want to write some code that will convert old RefCats to the new terminology. One might be able to do this with a schema mapper and the butler."
Answer: 1541061.0

User story: "Find all uses of {{Err}} and {{Sigma}} in the version controlled DM documents (hopefully just LDMs?), determine if they are correct or not, and fix the ones that are incorrect.    How many LDMs are there (of order 20 on the page below), and where do they all live? This document is a good start at finding them:    https://confluence.lsstcorp.org/display/DM/Requirements+and+Design+Hierarchy    This git repo should encompass all the important ones:    https://github.com/lsst-dm/dm-docs.git"
Answer: 979368.0

User story: "Find all uses of {{Err}} and {{Sigma}} in the stack documentation (pipeline, developer), determine if they are correct or not, and fix the ones that are incorrect."
Answer: 636388.0
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: The {{TestParentRepository}} unit test can sometimes fail:  {code}  price@master:/data3a/work/price/hscPipe5/lsstsw/build/daf_persistence/tests[(detached from 5.0-hsc)] $ python repository.py   .............E....  ======================================================================  ERROR: test (__main__.TestParentRepository)  Tests 1. That an sqlite registry in a parent repo is used as the  ----------------------------------------------------------------------  Traceback (most recent call last):    File "repository.py", line 790, in tearDown      shutil.rmtree(self.testDir)    File "/data3a/work/price/hscPipe5/lsstsw/miniconda/lib/python2.7/shutil.py", line 247, in rmtree      rmtree(fullname, ignore_errors, onerror)    File "/data3a/work/price/hscPipe5/lsstsw/miniconda/lib/python2.7/shutil.py", line 256, in rmtree      onerror(os.rmdir, path, sys.exc_info())    File "/data3a/work/price/hscPipe5/lsstsw/miniconda/lib/python2.7/shutil.py", line 254, in rmtree      os.rmdir(path)  OSError: [Errno 39] Directory not empty: '/data3a/work/price/hscPipe5/lsstsw/build/daf_persistence/tests/TestParentRepository/repoA'    ----------------------------------------------------------------------  Ran 18 tests in 0.695s    FAILED (errors=1)  {code}    I believe this is due to NFS dot-files hanging around, and doesn't reflect any real problem with the butler code.
Answer: 17.0

User story: "Lander (https://github.com/lsst-sqre/lander) uses metasrc (https://github.com/lsst-sqre/metasrc) to discover document metadata from the document source itself. Normalizing LaTeX into plain unicode text is a non-trivial challenge.    An approach that [~<USER> suggested is to use pandoc to convert the document into HTML first, and then extract metadata from the HTML. HTML is generally an easier format to exrtact information from since it's standards-based.    https://pypi.python.org/pypi/pypandoc might be useful since it's a package that includes pandoc.    We might need to install pandoc in the lsst-texmf docker container so that pandoc can run inside a real latex environment with the lsstdoc class pre-installed."
Answer: 153019.0

User story: "Deploy DMTN-020 to dmtn-020.lsst.io using Lander."
Answer: 33.0
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: Per [this report on CLO|https://community.lsst.org/t/difficulty-installing-on-python-3-6/1961], our test suite fails when run against NumPy 1.13.0:    {code}  File "tests/testSimpleTable.py", line 346, in testExtract  self.assertFloatsEqual(d["a_b_c2"], catalog.get("a_b_c2")[idx])  File "/home/mnewsome/envs/lsst_maf/lsst/Linux64/utils/13.0/python/lsst/utils/tests.py", line 652, in assertFloatsEqual  return assertFloatsAlmostEqual(testCase, lhs, rhs, rtol=0, atol=0, **kwargs)  File "/home/mnewsome/envs/lsst_maf/lsst/Linux64/utils/13.0/python/lsst/utils/tests.py", line 568, in assertFloatsAlmostEqual  diff = lhs - rhs  TypeError: numpy boolean subtract, the - operator, is deprecated, use the bitwise_xor, the ^ operator, or the logical_xor function instead.  {code}    This has been promoted from a {{DeprecationWarning}} to a {{TypeError}} as of [NumPy 1.13.0|https://github.com/numpy/numpy/releases/tag/v1.13.0], which was recently released.
Answer: 15349.0

User story: "As a consequence of RFC-345, this ticket adds the {{verify}} and {{verify_metrics}} packages to {{lsst_distrib}}. "
Answer: 1148.0

User story: "The original implementation of the uservice-ccutter for bootrstrapping cookiecutter-based projects didn't anticipate that project creation, notably Travis CI integration, would take longer than 30 seconds. Since it does, the microservice call times out and sqrbot returns an error to the user in Slack. The service also typically fails to complete the Travis integration. This has rendered it largely unusable for project and document creation.    I think the solution is to make the project provisioning asynchronous from the acknowledgement to the user on Slack. This ticket will modify uservice-ccutter to make that so. We'll use celery to implement a distributed asynchronous queue between the microservice api server and the worker processes. http://docs.celeryproject.org/en/latest/index.html"
Answer: 185145.0

User story: "Outline range of metrics needed in verify_ap."
Answer: 34660.0

User story: "Deploy LDM-503 to ldm-503.lsst.io using Lander."
Answer: 577.0

User story: "DM's LaTeX authors make use of whitespace in command invocations that weren't anticipated by metasrc's regular expressions. For example:    {code}  \title    [Test Plan]  { \product ~Test Plan}  {code}    This ticket adds flexibility to the regular expressions to work with this whitespace.    *Eventually we really need to replace the regular expressions with a fully-fledged TeX tokenizer.*"
Answer: 63.0

User story: "Update LDM-294 so that, given a textual description of the WBS, it:    - Automatically includes that in the document  - Associates each WBS element with a set of products from {{productlist.csv}}"
Answer: 1.0

User story: "Propose upstream change to the behavior of {{~error_already_set}}, which would then require an explicit call to {{restore}} when you want to re-raise in Python instead of an explicit call to {{clear}} when you do not."
Answer: 10823.0
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: "The large number of jobs / folders at the top level jenkins view is visually cluttered and confusing to end users."
Answer: 2953.0

User story: "Make user sessions persist across Hub restarts."
Answer: 2858.0

User story: "Verify systems are configured to meet testing needs,."
Answer: 352.0

User story: "Install CentOS 7 on each node and configure with standard LSST install and Puppet"
Answer: 2.0

User story: "*    Request 10G BaseT networking drops for node from NetEng (<USER>or Matthew Kollross)  *    Assign and setup IPMI networking and cables for each node  *    Connect to network  "
Answer: 5.0

User story: "Build unit test infrastructure which can instantiate butler and make a minimal dataset for testing.  Each test case to have input, which specifies the query, and output which is the image (full or cutout).  Test case succeeds if the generated output matches the SHA256 signature of what to be expected, and fails otherwise.  The first unit tests to contain 2 scenarios (full/cutout image) from the following image types: 1) raw 2) calexp 3) deepcoadd. "
Answer: 107990.0

User story: "Pull Butler instantiation code further up in imgserv, so it can be done externally to the ImgServ library when the ImgServ library is split into its own module (will enable use to cache Butlers in the Flask/CLI layers for improved performance)"
Answer: 20388.0

User story: "Implement Python threading into while loops for checking messages on topics using DDS/OpenSplice."
Answer: 39126.0

User story: "The jobId and retry number need to be added to the result table so that the rows from cancelled tasks can be removed from the result set. This information should not show up in the results returned to users."
Answer: 18883.0

User story: "The S17B HSC reprocessing (DM-10404) generated some butler repos with processed data:   {code:java}  /datasets/hsc/repo/rerun/DM-10404/SFM  /datasets/hsc/repo/rerun/DM-10404/DEEP  /datasets/hsc/repo/rerun/DM-10404/UDEEP  /datasets/hsc/repo/rerun/DM-10404/WIDE  {code}    We would like to know, for example, how many files are there, what are the sizes of the files (mostly small files?), what data products are taking up the space (likely images, but which ones?), and so on.  Write up a brief summary. "
Answer: 69210.0

User story: "I'm planning to publicize this document at the Lyon meeting next week as a part of a tutorial session on how to use the stack, but it has some instructions that no longer work.    I know [~<USER> has been working through this and fixing things (and probably putting it in a new, more permanent location), but I don't want to assume anything about that yielding results by next week."
Answer: 8177.0

User story: "Per DM-9955 (and confirmed by me on {{lsst-dev01}}), we see numerical values falling outside the expected tolerances when running the lsst_dm_stack_demo build with devtooset-6 (GCC 6.2.1).    Please figure out what's going on and fix it."
Answer: 119915.0
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: "To create calibration files you sometimes need to specify fields in the {{calibId}} than can be deduced from the {{id}}.  Please do so.  "
Answer: 37129.0

User story: "ie, describe [~<USER>'s workflow in a reproducible (and simple) way."
Answer: 278429.0

User story: "Generate a list of the tests that we want to prioritise with DM code on the test stand data.    This will include:    - DM Staff (ie, [~<USER>, [~<USER>) reading the existing list of tests and deciding which they reckon are important.  - Consulting with the camera team to understand what their priorities are."
Answer: 62292.0

User story: "Work with the other T/CAMs to provide a flowdown of L3 milestones from L2 test plans, as defined in LDM-503."
Answer: 15834.0

User story: "Need to include both AP (02C.03) and DRP (02C.04) in this activity, although the reporting formats are likely different. (I understand 02C.03 goes through Nikolina Horvat, but the mechanism is hazy)."
Answer: 157183.0

User story: "Need to include both AP (02C.03) and DRP (02C.04) in this activity."
Answer: 150389.0

User story: "Get autoscaling working."
Answer: 1089.0

User story: "Make things-that-should-be-configurable Kube deployment variables/secrets; be consistent about using secrets for secret things and env vars otherwise.  Generally make the deployment more useful for people-who-aren't-SQuaRE."
Answer: 1263.0

User story: "Implement a V1 REST API for metaserv.    We plan on utilizing SQLAlchemy for the model, Marshmallow for the JSON marshalling, and our current Flask infrastructure."
Answer: 34295.0

User story: "We need a CLI to populate and modify metaserv's database catalogs."
Answer: 34298.0

User story: "Metaserv's database information will be based on the model in VOResource so that we can implement RegTAP. Our implementation of RegTAP will be based on views, as our underlying tables may need additional columns that should not be exposed through the RegTAP interface,"
Answer: 34300.0

User story: "Independently tests the SUIT portal and visualization implementation. "
Answer: 33363.0

User story: "For use in FGCM we need a filter object that captures variability with both wavelength and position. Put together a prototype which unblocks the work on FGCM and can feed into future design work for a more generic {{Filter}} replacement across the codebase."
Answer: 384659.0

User story: "Interface the prototype system developed in DM-10619 with the results of processing HSC data on the verification cluster, and build the first version of a useful QA plotting system.    Originally the goal of this ticket was to connect the results of DM-10619, but this has now evolved to relate closer to DM-11682."
Answer: 198480.0

User story: "To interoperate with the stack and command line tasks, FGCM should not do any internal fits reading or writing unless explicitly asked for.  "
Answer: 77953.0
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: "Client side UI to access use workspace data:  * listing of the files   * simple management of the files  * display the file properly    Please also reference IRSA tickets https://caltech-ipac.atlassian.net/browse/IRSA-474                                                https://caltech-ipac.atlassian.net/browse/IRSA-729 ( workspace server commend)       XW: This turned out to be more work than I expected. Please see comment from Cindy for more information."
Answer: 239549.0

User story: "We need to decide the API to use to access user workspace (storage).  DAX team will implement a WedDAV API first, VOSpace API will be implemented later.    Work with DAX team during their implementation phase on the issues coming up.         [https://jira.ipac.caltech.edu/browse/FIREFLY-94]"
Answer: 1130874.0

User story: "Obtain DECam donut data.  Run donut pipeline on that data.    Compare fits to Roodman fits.  "
Answer: 864337.0

User story: Camera tilts and decenters impart offsets to low-order Zernikes (how low?) that are affine in field position.  So to combine Zernikes from different exposures, we should first "flatten" the maps by subtracting the best-fit plane (in unrotated focal plane coords) to the fits.  So do that.  And then see how successful this is by comparing the residuals from different exposures.  If it worked, then these residuals should more-or-less line up.
Answer: 547362.0

User story: "donut currently measures Zernikes with respect to focal plane coordinates.  Only a handful of HSC optics actually rotate though, so it makes more sense to develop a reference wavefront in this unrotated frame.  I think this is best done by applying a transform to the Zernike values (and locations), rather than by rotating the donuts before fitting."
Answer: 80943.0

User story: "Define and implement how we'll be making Synpipe available within the LSST stack. That may include treating it as a regular third party package, or tracking it via an LSST fork, or adopting the package entirely.    Although [~<USER> will lead this work, [~<USER> will coordinate with the upstream maintainer (Song Huang) to figure out how we can best cooperate with him.    This ticket is to make SynPipe able to be installed through the LSST distribution system. Success will be marked when the repository is is put in place such that the fake object insertion tasks are usable be used in the course of LSST processing. Full functionality of all scripts in the repository is not necessary, as that work will be completed on other tickets.  "
Answer: 219226.0

User story: "The success criteria of this tickets is to get the following tasks from SynPipe working with the LSST fake object pipe line:  * randomStarFakes  * randomGalSimFakes  * positionStarFakes  * positionGalSimFakes"
Answer: 78038.0

User story: "In conjunction with [~<USER> and [~<USER>, produce an outline of the various options for models, fitters, etc which will be explored in the context of F17 galaxy fitting."
Answer: 201843.0