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: "A pass must be made over the codebase and some of the 'FIXME' exception comments fixed. The DMCS and the PromptProcessDevice has extensie exception handling so that if the app were to quit, maintainers will know why.  At the October Pathfinder meeting, it was decided that ErrorCodes should be set up between each project group in a consistent manner. DM L1 has been given codes 5000 - 5999. A plan for utilizing the error code range is being put into place with this story.  When a Critical Error occurs and one or all of the L1 Devices are unable to continue, a fault message with message type FAULT is sent by any component that detects a fault and is sent to a specific message queue on the DMCS. The DMCS them marks that device as in a FAULT state unable to continue and informs the OCS. The Device must be restarted to leave Fault state."
Answer: 136898.0

User story: "See RFC for description.    IMO, this has bitten too many DRP team members recently to just put it on the backlog; I think it's really costing us time and money.  Even if the RFC needs to stew for a while before merging, I'd like to get at least a partial implementation on a branch while it's fresh in my mind.  "
Answer: 22228.0

User story: "[~<USER> has requested that in addition to the {{master}} branch, that the {{tickets/DM-12253}} branch of {{lsst/validate_drp}} also be run.    As the output of this branch is not expected to be compatible with {{post-qa}}, and squash has no facility for tracking input from multiple branches, the output of the alternative branch should be archived and not submitted to squash."
Answer: 47438.0

User story: Set default configs for makeCoaddTempExp, assembleCoadd, and coaddDriver in pipe_tasks and obs_subaru based on testing results.    These include the usual obs_subaru defaults for AssembleTask and SafeClipAssembleTask and more.  For example, these will probably include these configs:    {code}  config.makeCoaddTempExp.makePsfMatched=True  config.makeCoaddTempExp.warpAndPsfMatch.psfMatch.kernel['AL'].kernelSize=29  config.makeCoaddTempExp.warpAndPsfMatch.psfMatch.kernel['AL'].alardSigGauss=[1.0, 2.0, 4.5]  config.makeCoaddTempExp.modelPsf.defaultFwhm=6.1    from lsst.pipe.tasks.assembleCoadd import CompareWarpAssembleCoaddTask  config.assembleCoadd.retarget(CompareWarpAssembleCoaddTask)  config.assembleCoadd.badMaskPlanes = ("BAD", "EDGE", "SAT", "INTRP", "NO_DATA",)  config.assembleCoadd.doSigmaClip = False  config.assembleCoadd.subregionSize = (10000, 200) # 200 rows (since patch width is typically < 10k pixels)  config.assembleCoadd.doMaskBrightObjects = True  config.assembleCoadd.sigmaClip = 1.5  config.assembleCoadd.clipIter = 3  config.assembleCoadd.assembleStaticSkyModel.sigmaClip = 1.5  config.assembleCoadd.assembleStaticSkyModel.clipIter = 3  config.assembleCoadd.assembleStaticSkyModel.statistic = 'MEANCLIP'  config.assembleCoadd.doNImage=True  config.assembleCoadd.doWrite=True  {code}
Answer: 31725.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: "At the level that will enable a non-[~<USER> user to run FCGM on {{lsst-dev01}}."
Answer: 199460.0

User story: "Following DM-12430, we should rerun the large dataset used in DM-10396 through the updated matcher (with distortion correction)."
Answer: 136648.0

User story: "See if it breaks anything to take out our chowns."
Answer: 6905.0

User story: "hack_volume is no longer needed"
Answer: 13.0

User story: "Remove py2 support from:    - jenkins ({{stack-os-matrix}} + assorted publishing/release related jobs)  - {{newinstall.sh}}  - {{lsstsw}}"
Answer: 249119.0

User story: "This is an aggregation ticket to track CI related issues that are intended to be completed prior to or as part of a {{v15}} release."
Answer: 642066.0

User story: "Add bokeh extension into the Lab build."
Answer: 20.0

User story: I believe that it would be relatively simple modification of the nightly/weekly release pipelines to support the "rc" workflow that is currently use for the per cycle/major releases.  The principle modification needed would be to build from a git ref, instead of always building master.  Additionally, it would be very convenient to set a {{latest}} {{eups distrib tag}}.
Answer: 322501.0

User story: "Verify the matching performance of the matchPessimisticB code with simplified matching heuristics and rotation matrix distortion allowances.    This will be run on the same data set and visits as DM-9751 namely:  HSC (3358), DECam (406285, 410827), CFHT (793169, 896070, 980526)."
Answer: 138234.0

User story: "The pervious version of matchPessimisiticB did not allow for distortions in the 3D rotation matrix applied to the source and reference datasets before matching. Adding such an allowance improves the quality of the associated sources and references sent to the astrometry fitter, improving matchAndFit performance.    This ticket encapsulates work done on the u/morriscb/testMatcherDistortion, implementing this and also simplifying the heuristics in matchPessimisticB."
Answer: 26113.0

User story: "obs_comCam's policy file is written in the old .paf policy file, and that's annoying to use when changing it. Migrate it to the nice shiny new yaml style.     This should be trivial using DM-12417 now that the !!python/unicode bug is gone.    To test, instantiate the policy from the old file, translate it, write it out, re-instantiate from the yaml, and check everything is the same."
Answer: 8636.0

User story: "Attend a class offered at Princeton university which covers galaxy morphology and properties to prepare for upcoming work in galaxy modeling."
Answer: 53377.0

User story: "Write up the findings of DM-12426 into a short document with examples."
Answer: 230197.0

User story: "Using the tools and plots produced in DM-12425, investigate and categorize failures modes in shape determination."
Answer: 142742.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 code to investigate and plot the sources, measured shapes, and fit as determined by the code created in DM-12424. Use this to produce a large number plots for randomly selected objects from the population of known failures."
Answer: 142744.0

User story: "Create a framework and objective function used to run an MCMC algorithm on the library of objects which failed shape modeling as determined in [DM-12423|https://jira.lsstcorp.org/browse/DM-12423]."
Answer: 142747.0

User story: "Given the outliers from [DM-12422|https://jira.lsstcorp.org/browse/DM-12422], create code which generates a library of postage stamps and a measurement catalog of objects which fail shape measurement in some way.    These failures may be related to:    - size vs. magnitude  - shapes smaller than the PSF  - Objects which are flagged"
Answer: 56332.0

User story: "Write code that extracts HSM, SDSS Shape, and simple shape measurements along with relevant flags from the catalog produced in [DM-12421|https://jira.lsstcorp.org/browse/DM-12421]. Use this information to determine catalog cuts which define outlier objects"
Answer: 56335.0

User story: "Create a single patch of a cosmos coadd that has HSM, SDSS Shape, and simple shape all run."
Answer: 31615.0

User story: "Create a short document or community post which outlines the steps necessary for using synpipe to add fake sources to to real data."
Answer: 272130.0

User story: "Add the catalog that contains fake galaxy parameters generated from COSMOS to synpipe and update the config file for the fake object catalog generator to point to this file."
Answer: 21648.0

User story: "Calling {{dumpToFile}} on a daf_persistence.policy causes !!python/unicode to get prepended to everything. As per https://stackoverflow.com/questions/1950306/pyyaml-dumping-without-tags it seems that changing {{yaml.dump()}} to {{yaml.safe_dump()}} should fix this."
Answer: 367.0

User story: "Attend Michael Strauss and Jenny Greene's observational galactic astronomy class to better understand the scientific applications of the deblender."
Answer: 39122.0

User story: "Details of the latest image sequence plan were nailed down at the Pathfinder Integration Activity meeting held from Oct. 9 - Oct. 12 at the NCSA.    After the meeting, amendments to the initial Level One sequence plan were designed and captured in the attached diagram. The story points here represent Pathfinder meeting time plus time spent generating the new plan for the image ingest sequence.    https://confluence.lsstcorp.org/display/JP/Amended+Sequence+Diagram"
Answer: 1.0

User story: "This captures the ongoing work to fix the problems in PSFEx on good-seeing images.    This could be handed off to [~<USER> when [~<USER> has finished his part, or we could spawn a new ticket for it, depending on how much work/code [~<USER> has to do before handing it off."
Answer: 744909.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: "[~<USER> is updating the API for the 3rd party deblender, specifically changing the name of the package and improving the interface for adding peaks with multiple components and different constraints. Once that has been completed, this ticket will implement the improved API in the LSST stack."
Answer: 243438.0

User story: "Attend Michael Strauss and Jenny Greene's observational galactic astronomy class to better understand the scientific applications of the deblender."
Answer: 123.0

User story: "On Slack, [~<USER> writes:    {quote}  suggested improvement for LDM-294: I don't see any mention of `verify`, `ap_verify`, or `ap_pipe` in the Appendix A table of products (though `verify_metrics` is listed as part of Level 2 Quality Control). I know `verify`, at least, has a designated product owner...  (it would also help if the table repeated its header on each page, I think most long-table LaTeX packages have an option for it)  {quote}    These all sound like good suggestions to me."
Answer: 542204.0

User story: "Now that the {{v14_0}} release has shipped, the conda version / packages in the canoncial build env can be upgraded.  In addition, the list of tarball build platforms can be trimmed down to only the current python env."
Answer: 1039.0

User story: "Summarize the storage usage in reprocessing HSC RC dataset in DM-12392  "
Answer: 70450.0

User story: "Summarize the CPU usage in reprocessing HSC RC dataset in DM-12392"
Answer: 70452.0

User story: "When Stack v14.0 is available in the shared stack in {{/software}}, reprocess the HSC RC dataset, as defined in [DMTR-31 Sect. 4.1 |https://docushare.lsst.org/docushare/dsweb/Get/DMTR-31], using Stack v14.0.  Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}},, {{coaddDriver.py}}, and {{multiBandDriver.py}} (DM-10129/DM-11020).    "
Answer: 121030.0

User story: This message means that no psfMatched warps were found, and a static sky model could not be built but a user might not deduce that from:    ```Traceback (most recent call last):    File "/software/lsstsw/stack/Linux64/ctrl_pool/13.0-6-gf96f8ec+54/python/lsst/ctrl/pool/parallel.py", line 496, in logOperation      yield    File "/software/lsstsw/stack/Linux64/pipe_drivers/13.0-21-g61c0bd4+9/python/lsst/pipe/drivers/coaddDriver.py", line 261, in coadd      coaddResults = self.assembleCoadd.run(patchRef, selectDataList)    File "/software/lsstsw/stack/Linux64/pipe_base/13.0-14-g8b3bf66+40/python/lsst/pipe/base/timer.py", line 150, in wrapper      res = func(self, *args, **keyArgs)    File "/home/<USER>lsst_devel/LSST/DMS/pipe_tasks/python/lsst/pipe/tasks/assembleCoadd.py", line 388, in run      supplementaryData = self.makeSupplementaryData(dataRef, selectDataList)    File "/home/<USER>lsst_devel/LSST/DMS/pipe_tasks/python/lsst/pipe/tasks/assembleCoadd.py", line 1629, in makeSupplementaryData      templateCoadd = self.assembleStaticSkyModel.run(dataRef, selectDataList).coaddExposure  AttributeError: 'NoneType' object has no attribute 'coaddExposure'```
Answer: 33218.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: If you supply insufficient data in the dataId for a butler to {{put()}} the data, it will just pretend to have done it (_i.e._ it doesn't raise or warn, it just silently returns as if all was fine).    If one does  {noformat}  butler.put(img, 'postISRCCD', dataId={'visit':123,'filter':'r'})   {noformat}  where the {{postISRCCD}} template looks like  {{template: "postISRCCD/postISRCCD_v%(visit)d_f%(filter)s.fits"}}  then this will work. However, if you provide an empty dataId dict, it will not complain, but nothing will get written (of course).    This seems like a moderately serious problem, as it is easy to accidentally under-specify or mis-specify a dataId.    (FWIW, if I change 'postISRCCD' to an undefined dataset type I _do_ get an error).
Answer: 527307.0

User story: "DMTN-057 has been written and is available at https://dmtn-057.lsst.io/. Its proposals should now be discussed by stakeholders in {{verify}} and its clients ({{ap_verify}} and {{jointcal}}) and the Tasks framework.    This ticket may be closed once I've responded to all feedback and had it reviewed. Once DMTN-057 is in its final form, an RFD will be issued to discuss the best proposal (or hybrid thereof) to adopt."
Answer: 102619.0

User story: "Reprocess the HSC RC dataset, as defined in [DMTR-31 Sect. 4.1 |https://docushare.lsst.org/docushare/dsweb/Get/DMTR-31], using Stack w_2017_44.  Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}} (DM-10129/DM-11020)."
Answer: 20259.0

User story: "Jointcal should exit or raise when the number of data points is less than the number of fitting parameters (e.g., constrained 4th order polynomial) with only 3 stars). I thought there was once such a check for astrometry, but I can't find it now."
Answer: 786999.0

User story: Try using "travis_wait" in docker pull step of the qserv travis.yml to see if that will allow us to work around recent timeout failures.
Answer: 2527.0

User story: "For the interactive QA plots, it would be very useful to be able to easily query down the displayed data based on flags in the tables (e.g., to select only {{calib_PsfUsed}}).  The QA user interface should make this easy, either via interactive widgets (e.g. checkboxes) or by function arguments."
Answer: 125493.0

User story: "The base DCR algorithm assumes that there is negligible DCR across each DCR model plane's bandwidth. That is typically a good assumption, but very high airmass observations may have DCR with an amplitude of a pixel or more across model planes in g-band. This ticket is to test for and write an approximate correction for those cases. One solution is to increase the number of model planes to reduce the bandwidth of each, but that may not always be possible from lack of data."
Answer: 8939.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 point of this ticket is to get an understanding of the adaptive moments algorithm used in the LSST stack for generating shape measurements. This work involves:  * Understanding the math behind the algorithm  * Read the relevant sections in the HSC pipeline paper  * Experimenting with the sdss implementation to understand practical use of the algorithm    This work is to lay the ground work for the development of a larger, detailed, and more focused test suit of the various failure modes of the adaptive moment algorithm."
Answer: 34595.0

User story: "Add the small support classes needed to prototype Registries: DatasetType, the DatasetRef hierarchy, DataUnits, StorageClass, Quantum, and Run."
Answer: 33506.0

User story: "Create test data for a Registry database corresponding to what's in ci_hsc: tables for Datasets, DataUnits (including SkyMaps).    For now, this will make it much easier to write unit tests for Registry and is support classes.  In the long term, it should let us test conversion of CmdLineTasks to SuperTasks."
Answer: 33508.0

User story: "Use SQLAlchemy Core to develop a minimal butler Registry. It should support everything except, subsetting/merging, transfers, general query and graphs."
Answer: 79579.0

User story: "Add an abstract base class for spatially-varying transmission curves to the stack, attach them to Exposure/ExposureRecord, implement a concrete subclass for HSC filters based on [~<USER>'s recent work, and add another concrete subclass for coadds that combines per-epoch transmission curves.    Work on this ticket is ultimately necessary for LSST but is being driven by HSC priorities; I'm calling my work on it science time for now, but [~<USER> is welcome to recategorize it if he likes.    Sub-tickets and story point estimates to follow."
Answer: 286824.0

User story: "Container builds are using outdated v13 newinstall URL and this needs to be fixed"
Answer: 1447.0

User story: "For some reason new SCons 3 wants to rebuild all binaries (shared objects included) on every scons invocation."
Answer: 48.0

User story: "In DM-12308 we changed the names of some shared objects that come from xrootd. There are still references to other shared object in xrootd config file that needs similar change."
Answer: 50.0

User story: "We have SUBMIT implemented but no tests for that new feature. Would be nice to extend our integration tests to also test this new feature."
Answer: 10311.0

User story: "Send Task {{lsst.log}} output to stdout instead of stderr.    This is the implementation ticket for RFC-402."
Answer: 386.0

User story: "The GitHub extension is published.  I will be investigating to see how much work we have to do to make it work with our magic GH stuff we already have."
Answer: 30453.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 new change-controlled document release workflow uses the {{master}} branch as the integration branch, and {{v<major>.<minor>}} tags as releases. We'd like to have the latest release for documents featured as the primary version shown on a document's {{handle.lsst.io}} landing page. This will require some new functionality in https://github.com/lsst-sqre/ltd-keeper and possibly https://github.com/lsst-sqre/ltd-dasher.    See also the document branch and tag API newly defined in DM-11952 and RFC-401."
Answer: 77694.0

User story: "While processing some cosmos data on lsst-dev it became necessary to run data sequentially using the multibandDriver to diagnose a problem. This can be done by using the --batch-type=None option.     Most of the processing preceded fine, however I noticed that openMP was not being disabled. This was most evident when the deblender was using several hundred percent cpu. Occasionally a processing job would seed to get stuck (not get past the deblending stage, yet still using 100% cpu) even when left for 24 hours. I attached to the process using gdb and found that some numpy routine was making some openblas calls. These calls would get into a state where libopenblas ,which is compiled into numpy, was issuing calls to sleep a tread, which would then turn over control to the kernel. The kernel would complete the sleep and immediately turn control back to openblas, which would then issue a thread sleep call. This kept the cpu using 100% cpu, but no work ever got done, and the loop could not exit.    Killing the process and restarting could get the processing past the particular patch/tract that was getting stuck, but sometimes a different tract/patch would get stuck. It was not deterministic but happened several times when processing all the patches in a tract.    Some relevant lines from the traceback when the program was in the sleep loop are below:  {code}  #0  0x00007fa6496d0e47 in sched_yield ()      at ../sysdeps/unix/syscall-template.S:81  #1  0x00007fa63ddbf365 in exec_blas_async_wait ()     from /software/lsstsw/stack/Linux64/miniconda2/3.19.0.lsst4/bin/../lib/libopenblas.so  #2  0x00007fa63ddbfa02 in exec_blas ()     from /software/lsstsw/stack/Linux64/miniconda2/3.19.0.lsst4/bin/../lib/libopenblas.so  #3  0x00007fa63ddbfd9d in blas_level1_thread ()     from /software/lsstsw/stack/Linux64/miniconda2/3.19.0.lsst4/bin/../lib/libopenblas.so  {code}"
Answer: 228665.0

User story: "Currently, {{ap_pipe}} has some hardcoded assumptions that it is working on DECam data, and the ingestion step is specific to HiTS. Both of these assumptions should be lifted (likely delegating much of the work to a standards-compliant {{obs_*}} package) to allow {{ap_pipe}} to be run on arbitrary datasets."
Answer: 419294.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: "Currently, {{ap_pipe}} assumes that each dataId passed to it contains exactly one visit (e.g., in {{doProcessCcd}}). {{ap_pipe}} should be extended to support ranges and other combinations of visits.    This ticket may be partially or entirely superseded by DM-11372."
Answer: 220611.0

User story: "With DM-10923, write documentation in developer.lsst.io about how to create a technote with sqrbot. A few other items that should be included:    - Using bibliographies in Sphinx technotes  - How to create a LaTeX technote"
Answer: 675.0

User story: "Nearly all many-visit HSC datasets that I've tried to process fail to fit photometry because the chi2 starts out as NaN, resulting in all stars being rejected as outliers and (after a long time) Eigen blowing up. We can't proceed with the photometric part of the meas_mosaic comparison until I can produce a fit.    Some steps to try:    # make jointcal fail immediately if chi2 is NaN (write a testcase for this)  # fit the SimplePhotometryModel instead, to see if that doesn't produce NaN  # print various input values to look for NaNs  # Is it worth writing the astrometry output before starting the photometry fit, so we at least have it in case of failure?"
Answer: 18433.0

User story: "Begin researching HiPS viewing in Firefly. Do the following:    * Learn about Healpix  * Learn about HiPS  * Determine how a viewer would fit into Firefly  * Look at Aladin Lite code and tool  * Look at Aladin Lite API  * If straightforward, add a proof of concept HiPS viewing into Firefly."
Answer: 36078.0

User story: In the baselined LDM-294 document, the "DM documentalist" position is listed as a member of SQuaRE (<USER>. In reality, this baseline hasn't been implemented. <USER>doesn't have DocuShare upload access and has never been tasked with any DM documentalist activities in SQuaRE's epics. I think it's fair to say that the management and systems engineering teams have actually been carrying out the role of documentalist. Besides this, "DM Documentalist" is not a defined role in LDM-294, beyond being included in Figure 5.    Prompted by [~<USER>'s comments in RFC-401, this matter should be resolved and LDM-294 should be updated.    Key questions are:    - What does the DM documentalist do?  - Should DM Documentalist be part of the SQuaRE WBS (if <USER>is doing the work, as currently listed), or does the Documentalist role belong to a different team (such as DM Systems Engineering)? Or should Documentalist duties be shared by multiple people?    If these questions can be resolved, the Change-controlled document workflow introduced by RFC-401 can be clarified.
Answer: 615065.0

User story: "Ensure that we get a fresh copy of lsst-sqre/notebook-demo branch prod on each logon."
Answer: 10285.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: "You can currently subset (query for) specifications by passing a metadata term dictionary to the {{Jobs.specs.subset()}} method. This kind of query was intended to be permissive and just match any specification that _could_ apply given a Job's metadata. This meant that if the Job metadata had an extra term that the Specification does not filter by, that specification would still be applicable to the job.    For DM-12253, [~<USER> needs to subset specifications by an exact match to the input metadata query terms. This means that if the queried metadata has terms not present in a Specification's metadata, that specification does not match.    This ticket is to implement that alternative query pattern."
Answer: 957.0

User story: "[~<USER> determined that in order to properly disable MKL the following needs to be done on separate lines by the deploy script:    {{conda install nomkl}}  {{conda remove mkl mkl-service}}    Make these changes."
Answer: 381260.0

User story: "[~<USER> determined that in order to properly disable MKL the following needs to be done on separate lines by the deploy script:    {{conda install nomkl}}  {{conda remove mkl mkl-service}}    Make these changes."
Answer: 381261.0

User story: "Switching to Anaconda 5.0 requires either disabling or fixing {{healpy}} which currently gives the mysterious error:    {{c++: error: unrecognized command line option ‘-R’; did you mean ‘-R’?}}.    I tried the new 1.11.0 upstream version, but it has the same problem."
Answer: 381266.0

User story: "Implementation ticket for RFC-400."
Answer: 1542.0

User story: "As per RFC-395 we'll add display_matplotlib to the stack.  Part of the review of this ticket will be that the docs and tests are acceptable."
Answer: 122490.0

User story: As we are now quasi-reliably producing nightly/weekly eups distrib tarball binaries and a docker image, it should be possible to refactor the {{validate_drp}} jenkins job to utilize said docker image.    This would provide several benefits:    * a possible reduction of the wall-clock run-time and resource consumption for running {{validate_drp}}.  * allow for simple reproduction of the {{validate_drp}} execution environment for debugging and/or addition verification.  * provide a more comprehensive means for validating a build than the "stack demo"; as the nightly/weekly docker image is used as the basis for the jupyterlabdemo images, this would be providing improved validation of binaries that will be used directly by end-users.    It might also sever as a model for producing and validating a binary distribution for "production" usage.    Implementing this would likely involve:    * refactoring the jenkins {{validate_drp}} job to be docker based  * removing the existing jenkins "cron" trigger for {{validate_drp}} and adding it as a stage in the nightly/weekly release pipelines  * possibly modification of how {{post-qa}} collects software versions (essentially, provenience)
Answer: 150052.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: "In the current processing model, tract is the processing unit, each tract is processed independently, and we don't assume there is disk space to save all products of one tract for other tracts to use. SFM of one visit/ccd would be done once for each overlapping tract; therefore tract ID is needed in filename patterns to ensure a unique filename.      In DESDM wcl, add tract ID and camera symbol to the filenames of the SFM products.     "
Answer: 1394.0

User story: "The pipeilne failed running {{run-rebuild}} with this exception error string:    {code:java}  java.io.IOException: No space left on device  {code}  "
Answer: 1889.0

User story: "Let {{ap_verify}} call the association step in {{ap_pipe}} and verify that the code runs to completion on the standard {{ap_pipe}} dataset ({{verify_ap_hits2015}}, {{visit=410985 ccdnum=25}})."
Answer: 12954.0

User story: "Let {{ap_pipe}} call {{AssociationTask}} and verify that the code runs to completion on the standard {{ap_pipe}} dataset ({{verify_ap_hits2015}}, {{visit=410985 ccdnum=25}})."
Answer: 9863.0

User story: It appears that a groovy {{null}} may be getting stringified as the string "null".  {code:java}                treecorr:  ok (0.3 sec).            ci_ctio0m9:  ok (62.5 sec).  Traceback (most recent call last):    File "/home/jenkins-slave/workspace/science-pipelines/lsst_distrib/centos-6.py3/lsstsw/lsst_build/bin/lsst-build", line 51, in <module>      args.func(args)    File "/home/jenkins-slave/workspace/science-pipelines/lsst_distrib/centos-6.py3/lsstsw/lsst_build/python/lsst/ci/prepare.py", line 785, in run      manifest = p.construct(args.products)    File "/home/jenkins-slave/workspace/science-pipelines/lsst_distrib/centos-6.py3/lsstsw/lsst_build/python/lsst/ci/prepare.py", line 749, in construct      self.product_fetcher.validate_refs()    File "/home/jenkins-slave/workspace/science-pipelines/lsst_distrib/centos-6.py3/lsstsw/lsst_build/python/lsst/ci/prepare.py", line 373, in validate_refs      " {}".format(",".join(missed)))  RuntimeError: Did not checkout any products with the following refs: null  Failed during rebuild of DM stack.    {code}  
Answer: 2944.0

User story: "Jointcal currently defaults to using {{LoadAstrometryNetObjectsTask}} for its {{refObjLoader}}. This can be dangerous in that if one doesn't retarget in the config, loading the skyCircle will fail and getting to that point can take a long time with lots of files.    We also plan to phase out A.Net catalogs over time, so this is a good idea long term as well. It does require some reconfiguration of the unittests however."
Answer: 4414.0

User story: "Port the {{validate_drp}} package to use the more current {{lsst.verify}} classes and persistence.  This is corresponding with the updating of the {{jointcal}} package to use {{lsst.verify}}."
Answer: 43418.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: "In the 10/3/17 QA meeting at which we looked at the results of DM-10859, it was determined that a necessary drill-down tool would be the ability to see the outlines of visits on top of the sky plots.   Implement this ability in a non-crowded way.  "
Answer: 608219.0

User story: "Most of the QA metrics that we are most interested in visualizing require catalog matching.  Implement catalog matching within the interactive QA system so it can easily compute differences and (other statistics) of desired quantities among multiple catalogs.    Two specific (and related) use cases that must be enabled are (a) calculating the differences between measurements calculated on two different catalogs and (b) calculating repeatability of various measurements between multiple catalogs."
Answer: 135573.0

User story: from Xiuqin comment at https://github.com/Caltech-IPAC/firefly/pull/474    Here are the suggestions after discussing with Trey:    Change the slide-down menu associated with gear icon to the dialog associated with clicking on "Charts".    Modify the dialog with the following:  - Following the image dialog, give options "new chart", "add to existing chart" (it will be like adding a data series). When it comes up first without existing chart, "New chart" should be the only option.  - Change button label "ADD" to "OK" to cover both options.  - For "add to existing chart", the trace field could be filled with the default label as "add series" currently does.  - Use the same color schema as Image and Catalog dialogs, adding ? for help.    Other suggestions:  - If we can add a trace we need to be able to remove it.  - Would be nice to have a warning dialog with there are two traces and the user attempts to filter the non-active trace. This will result in a "no data found" and probably not what the user wants.  - Image overlay should clear when a filter with no data found (this is probably not your problem)        
Answer: 29114.0

User story: "{{despyastro}} is one of the packages DESDM framework consist of. The goal is to port it to Python 3."
Answer: 64788.0

User story: "{{despyDMdb}} is one of the packages DESDM framework consist of. The goal is to port it to Python 3."
Answer: 64842.0

User story: "{{despfitsutils}} is one of the packages DESDM framework consist of. The goal is to port it to Python 3."
Answer: 64846.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: In [HSC-1424|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1424], Mineo-san reports:  {quote}  Matsuoka-san wants to find drop-out objects by such a search condition as "the object was not detected in this band though there were two or more input images there." It is not feasible in hscPipe 5.4 since inputCount_value is zero if inputCount_flag_badCentroid is true, no matter how many inputs there actually were. This problem did not exist in hscPipe 4 because inputCount was measured also in forced measurement. In 5.4, inputCount is measured only in unforced measurement, and inputCount_flag_badCentroid can be true even if it is not in other bands. Please measure inputCount in forced measurement. ("Setting inputCount_value to a valid value no matter how bad the centroid is" may suffice  though.)  {quote}
Answer: 31864.0

User story: "See how it was done in the AWS deployment of squash:    [https://github.com/lsst-sqre/sandbox-jenkins-demo/blob/d74212c23f69670a0cb03c8c7bb5e657817e4e3c/jenkins_demo/templates/squash/production.py.epp]"
Answer: 679916.0

User story: "After the migration to the microservices architecture DM-10742 the {{squash-dash}} microservice cannot query {{squash-db}} directly and the stats we presented in the initial page must be moved to the REST API.   "
Answer: 30116.0

User story: "Right now, if we restart the hub, spawned labs lose the ability to talk to it.  That's not ideal."
Answer: 370.0

User story: "{{despymisc}} is one of the packages DESDM framework consist of. The goal is to port it to Python 3."
Answer: 66223.0

User story: "{{depydb}} is one of the packages DESDM framework consist of. The goal is to port it to Python 3."
Answer: 66226.0

User story: "The current interface for the deblender takes constraints and components as arguments but doesn't utilize that information when building the constraints for each object (for example having default constraints for different component types). It also doesn't pass those parameters to the main NMF algorithm without being explicitly given as function arguments, so improving this interface would make constraints and components easier to use and more robust against inconsistencies (for example this weekend I had forgotten to pass the constraints to the function to build the monotonicity operator, causing half of the components to not have monotonicity applied)."
Answer: 136958.0

User story: "The LSST-DESC blending group has asked Peter and I to give a presentation on the new deblender. Most of the talk was already created for LSST-2017, however some work is needed to update it with the latest results using multiple components and the current status."
Answer: 216.0

User story: "Implement a testbed for GraphQL using django-graphene and implement a  proof of concept GraphQL Schema to query the Metrics/Measurements"
Answer: 11024.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: "Mapping.applyForward and Mapping.applyInverse fail on empty arrays: it triggers an AST error.    This showed up as a mysterious error in DM-10765 in afw test_footprint1.py    The fix is trivial: have Mapping._tran skip the call to astTranN if the input array has 0 points."
Answer: 5351.0

User story: "Monitor the following URLs:    - https://squash.lsst.codes  - https://squash-bokeh.lsst.codes  - https://squash-api.lsst.codes    "
Answer: 18802.0

User story: "Our developer guide currently says to enable devtoolset-3 on lsst-dev:    https://developer.lsst.io/services/lsst-dev.html#select-appropriate-developer-tools    This is no longer correct and should be updated. The whole section probably needs a rewrite (i.e., we don't want people loading devtoolset in their startup!).    We may also need to revise the next section, once we've purged the existing stacks following RFC-334:    https://developer.lsst.io/services/lsst-dev.html#select-appropriate-developer-tools"
Answer: 126652.0

User story: "Document filesystem policy in appropriate project location(s)."
Answer: 551547.0

User story: "Create proposal based on as-is organization and policy considering reviewers comments."
Answer: 551549.0

User story: "Review with internal science users."
Answer: 27442.0

User story: "Create matrix of as-is (and perhaps anticipated) use type and organization of GPFS file system logical partitions."
Answer: 10.0

User story: "{{despyServiceAccess}} is one of the packages DESDM framework consist of. The goal is to port it to Python 3."
Answer: 70358.0

User story: "This is to attend my AURA-approved trip to Santiago, Chile for both ADASS and IVOA meetings at the same hotel conference venue. Agendas for both contiguous events will benefit my software development work for LSST as part of the DM group.    ADASS 2017:  http://www.adass.cl/    ChiVO - VOA Interoperability Meeting:   https://chivo.cl/news/11/  "
Answer: 29053.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 story and associated points recorded here are due to the following explanation:    Critical DM/Pathfinder Nebula instances began failing on Friday, Oct. 16.  DM personel spent the weekend attempting to retrieve data and fashion workarounds for stalled Nebula instances.  Note: This is NOT an example of "No Backup Snapshot in place". ALL of DMs Pathfinder activity components are built as storage backed instances, so if a running instance is compromised, a QCOW3 image of the instance is available on storage with the very latest state/storage changes on a volume that is bootable. On this occasion. the iSCSI connections to the Nebula store were compromised.  In addition, on Monday the barely running cluster began experiencing sporadic failure...case in point: Our Pathfindergroup was able to run through our sequence scripts on Monday and Tuesday. Retrieving Pathfinder EFD data after the group ran our new sequence code was nearly impossible. The solution we devised was to copy the QCOW image - a procedure that took +19 hours+ for an 11GB file - and then jump through the hoops necessary to convert the image, rebuild its file and partition table, and finally loop mount the image on a laptop so that we could access the RFD data.  <USER>accomplished this work, and his knowledge and actions were invaluable.    NCSA escalated this issues causing and surrounding this failure event in a Top Level Staff Meeting on Friday, Oct. 13
Answer: 1.0

User story: "When the DM OCS Bridge sends a Next Visit event, or an event published within the exposure sequence, the DMCS must catch this message and react accordingly. This behavior is only started in this story; one event is wired into DM Component code permanently, but the other exposure events are, for now, being caught and logged for the Pathfinder activity."
Answer: 18.0

User story: "Need to listen to new events from camera, scheduler and TCS as visit sequence/sequence-with-filter-change, then convert them into the DM internal messaging system."
Answer: 23.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: "Perform the upgrade to Miniconda 4.3.27.1 (patch version needed) from RFC-398.    This requires patching {{sconsUtils}} to disable LTO (either that, or wait for {{devtoolset-7}}), which is done on {{u/<USER>no_lto}}. It also involves fixing {{lsstsw}} {{./bin/deploy}} to not install {{mkl}} (install {{nomkl}} and remove {{mkl}} libraries) which is somehow broken."
Answer: 389769.0

User story: "The system python is really just for spawning JL itself."
Answer: 20156.0

User story: "Reprocess the HSC RC dataset, as defined in [DMTR-31 Sect. 4.1 |https://docushare.lsst.org/docushare/dsweb/Get/DMTR-31], using Stack w_2017_42.  Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}} (DM-10129/DM-11020)."
Answer: 18463.0

User story: "Destroy the AWS resources that were being use by squash including the 'squash' EC2 and RDS instances.  The pupppet + terraform configuration can also be removed."
Answer: 1723.0

User story: "Stars of certain colors (e.g., the upper branch in the gri diagram) are not suitable for use in measuring the photometric zeropoint. We know the color of stars in the reference catalog, so we can exclude them using that.    This involves putting in a suitable {{Config}} entry to select the appropriate stars, and implement the selection within photocal."
Answer: 37447.0

User story: "Currently the clusters at Princeton only have the python 2 version of the stack updated every week. It would be convenient to have the Python 3 version as well."
Answer: 103479.0

User story: External package treecorr fails to build on Linux gcc python3 due to its {{setup.py}} not encoding the "determine C++ compiler" test code before writing it.    We can fix this with a patch ourselves and then push it upstream later. Who would be responsible for pushing the fix upstream?
Answer: 7126.0

User story: When czar crashes while queries are running QMeta information for those queries is stuck in "EXECUTING"/non-complete state. This causes all of them to show up in SHOW PROCESSLIST output which grows over time. It would be nice to do some cleanup of QMeta when czar restarts after crash. In the future when/if we implement czar restart that will have to be handled differently.
Answer: 12924.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: {{pipe_base}} is failing to {{eups distrib install}} due to what appears to be an eups failure creating a cache dir.  This might (?) be a sign of file-system trouble (full  or unwritable) or some sort of eups cache corruption.  Either way, the {{.eups}} dir should not be under {{~}} to prevent cross contamination between jobs and to ensure it gets cleaned up.    {code:java}  [build]     ***** error: from /build/stack/miniconda2-4.3.21-10a4fa6/EupsBuildDir/Linux64/pipe_base-13.0-14-g8b3bf66+32/build.log:      self._setProductStack_fromCache(dataDir, [self.flavor])    File "/build/eups/2.1.4/python/eups/Eups.py", line 1488, in _setProductStack_fromCache      userCacheDir = self._makeUserCacheDir(dataDir)    File "/build/eups/2.1.4/python/eups/Eups.py", line 516, in _makeUserCacheDir      os.makedirs(cachedir)    File "/build/python/miniconda2-4.3.21/lib/python2.7/os.py", line 157, in makedirs      mkdir(name, mode)  OSError: [Errno 17] File exists: '/home/jenkins-slave/.eups/_caches_/home/jenkins-slave/.eups'  CameraMapper INFO: Loading exposure registry from /build/stack/miniconda2-4.3.21-10a4fa6/Linux64/obs_test/13.0-14-g7685640+2/data/input/registry.sqlite3  root INFO: Running: lsst.pipe.base.cmdLineTask.ExampleTask.parseAndRun(u'/build/stack/miniconda2-4.3.21-10a4fa6/Linux64/obs_test/13.0-14-g7685640+2/data/input', '--output', '/tmp/tmpOHmFFP', '--id', 'visit=3', 'filter=r', '--config', 'floatField=-99.9', '--clobber-config')  ===================== 2 failed, 50 passed in 10.15 seconds =====================  Global pytest run: failed  {code}  
Answer: 13246.0

User story: The most recently merged PR is https://github.com/lsst/jointcal/pull/45    {{jointcal}} from master is not buiding via {{eups distrib install}}.  I suspect this is because unit tests we introduced that are dependent on the {{setupOptiona}} {{testdata_jointcall}} product.  Test that rely on optional packages should bail out gracefully without failing.    {code:java}    [build]         lsst.afw.image.utils.resetFilters()                # Load or fake the necessary metadata for each CcdImage (using ccd=12)  >       data_dir = lsst.utils.getPackageDir('testdata_jointcal')  E       lsst.pex.exceptions.wrappers.NotFoundError:   E         File "src/Utils.cc", line 42, in std::string lsst::utils::getPackageDir(const string&)  E           Package testdata_jointcal not found {0}  E       lsst::pex::exceptions::NotFoundError: 'Package testdata_jointcal not found'    tests/test_photometryModel.py:26: NotFoundError  =============== 4 failed, 37 passed, 19 skipped in 6.84 seconds ================  Global pytest run: failed  {code}  
Answer: 111.0

User story: "The latest nightly release is in the process of failing (it is still retrying some tarball builds) due to the unit tests for {{jointcal}} failing when the optional {{testdata_jointcal}} is absent and what appears to be some sort of [{.eups}} caching corruption on some nodes.  A separate issue for {{jointcal}} will be opened."
Answer: 13260.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: "Investigate the memory usage of one multiBandDriver job. "
Answer: 50636.0

User story: "Add the the new squash api url [https://squash-api.lsst.codes] to validate_drp job, the idea is to have both production deployments up for some time before switching over."
Answer: 3589.0

User story: "It would be useful for users to share the same view of SQuaSH through and URL like this [https://squash-dash-demo.lsst.codes/dash/monitor/?metric=AM1&ci_dataset=hsc]   perhaps including also the same add x and y limits."
Answer: 688357.0

User story: "SQuaSH QC Tier 0 database must be generic to allow measurements from different {{lsst.verify}} packages such as {{jointcal}}. The work related to reimplement the SQuaSH API is covered in a separate epic DM-12787"
Answer: 115359.0

User story: "The original implementation of the SQuaSH REST API used Django REST Framework. We decided to reimplement in Flask to be aligned with the technology stack being used in DAX and other projects in SQuaRE.    For the Flask implementation these are the main resources I am using:    * REST APIs with Flask and Python: [https://www.safaribooksonline.com/library/view/rest-apis-with/9781788621526/]    * Developing RESTful APIs with Python and Flask: [https://auth0.com/blog/developing-restful-apis-with-python-and-flask/]    * Building RESTful Python Web Services: [https://www.safaribooksonline.com/library/view/building-restful-python/9781786462251/ch06s06.html]    Still Keep here the Django references in case they are useful in the future/for anyone:    * Building RESTful Python Web Services with Django: [https://www.safaribooksonline.com/library/view/building-restful-python/9781788620154/]    * Django Projects: E-Learning Portal: [https://www.safaribooksonline.com/library/view/django-projects-e-learning/9781788395175/video4_1.html]    * Mastering Django Web Development: [https://www.safaribooksonline.com/library/view/mastering-django-web/9781783989805/]"
Answer: 68866.0

User story: "We need to constraint the query that loads the measurenents in the monitor, right now we are reading all measurements and it is slow, the ideia is to add a filter called {{window}} and a select widget place right above the plot showing:    *  Last 3 months  *  Last 6 months  *  Last year  *  All"
Answer: 33143.0

User story: "Issues found during the end-to-end test of the {{squash-deployment}}  "
Answer: 1087.0