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: "firefly_client needs to support https.   firelfy_client contains a bug that does not parse an https url correctly.  Needs to be fixed."
Answer: 18616.0

User story: "Add Firefly to cluster."
Answer: 7250.0

User story: "When the active trace is changed then move it to the top. This changes the order of the trace and replots,    This might needs to be discuss with [~<USER> and [~<USER> before the work begins."
Answer: 66491.0

User story: "Write a generic/wrapper search processor to do column experssion"
Answer: 48619.0

User story: Details:    * tbl_id in data  * syntax- "table::column" or "table::expression"
Answer: 47144.0

User story: "Work on API     * api function: showChart,  * do work on dispatchers to take a content object  * both data and layout will have a firefly object    * change api to consistent showChart  * firefly object in data and options  * firefly chart type: fireflyHistogram, fireflyHeatmap, fireflyScatter"
Answer: 63314.0

User story: "Run new cluster.  Then destroy it."
Answer: 7315.0

User story: "Last step in getting rid of SWIG dependency is to replace our SWIG-generated LUA wrapper for proxy with hand-crafted one. The interface is not too complicated, there are just four methods in C++ API that need wrapping."
Answer: 1511.0

User story: "We have less snowflake stuff than we used to.  Bertrand is right that the docs are confusing."
Answer: 7373.0

User story: "This ticket is to add {{lsst.verify}} to the new https://pipelines.lsst.io integrated documentation:    - Add boilerplate structure.  - Get docstrings to build."
Answer: 17916.0

User story: qserv seems to be the only thing left that uses SWIG for generating python wrappers. Time to switch to pybind11 to reduce dependencies. First step for that is to replace python wrappers with pytbind11. We also use SWIG for LUA wrappers, will replace that with hand-"generated" code in separate ticket.
Answer: 2890.0

User story: "The current documentation for {{ap_verify}} consists of a readme file and some unpublished API documentation. The readme has basic usage instructions, but assumes the user will run {{ap_verify -h}} to learn the details of each command line argument.    We should move documentation out of the readme and into well-organized user-facing documents. This work may need to wait until [~<USER>'s documentation upgrades roll out."
Answer: 174527.0

User story: "[~<USER> requests:  {quote}  Please just remove it from the build; it should already be optional as far as ndarray (not EUPS) is concerned.  {quote}"
Answer: 3065.0

User story: "Per nagios:      {code:java}  community/TLS cert expiration is CRITICAL:  CheckHttpCert CRITICAL: TLS/SSL certificate expires on 2017-10-14 15:42:17 UTC - 59 days left.  {code}  "
Answer: 78100.0

User story: "An el6 backlog was observed this morning.  Per request on #dm-square, additional bulid agents are being provisioned that will need to be torn down at the end of the week. "
Answer: 6070.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 changes merged in DM-8914 split up the qserv docker image build into two jobs.  The {{weekly-release}} job needs to be updated to trigger one or both of the new jobs."
Answer: 358640.0

User story: "The jenkins {{build-jupyterlabdemo}} job failed with package dependency errors."
Answer: 11850.0

User story: "Got input from Don got LDM-572 to start describing Chilean DAC"
Answer: 171484.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: "It would be nice if the images spawned by the JupyterLab environment had a set of Python configs that would make using the interpreter nice.  This is likely just a `.pythonrc` file in the home directory with at least tab completion (it's possible this comes for free when using ipython instead of python, but I haven't checked)."
Answer: 14409.0

User story: "We support {{image\[0:10, 4:10]}} and {{image\[bbox]}} but there's no way to specify whether you want {{afwImage.PARENT}} or {{afwImage.LOCAL}} (so we always default to the latter);  users accordingly have to write e.g. {{image.Factory(image, bbox, afwImage.PARENT}} (or, even more ugly, construct the BBox in the first example).    Please add an optional argument, {{LOCAL}} or {{PARENT}} with the former remaining the default;  <USER>or I will file an RFC to switch to {{PARENT}} at some point.  "
Answer: 99394.0

User story: "Many of jointcal's classes have a {{public:protected:private:}} ordering that doesn't match our standard. It'd be good to clean this up, as a separate single commit."
Answer: 94921.0

User story: "{code:java}  [vagrant@<USER>skc-f25 ~]$ which python  /usr/bin/which: no python in (/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/opt/puppetlabs/bin:/home/vagrant/.local/bin:/home/vagrant/bin)  [vagrant@<USER>skc-f25 ~]$ /opt/lsst/software/stack/newinstall.sh -b    LSST Software Stack Builder  =======================================================================    ######################################################################## 100.0%  Detected git version 2.9.4. OK.    /opt/lsst/software/stack/newinstall.sh: line 569: python: command not found    {code}  "
Answer: 29017.0

User story: "Work on DM-11371 illustrated some minor incompatibilities between the directory structure expected for datasets living in {{/datasets}} and our packaging scheme defined in DM-11116.  This ticket is to harmonize the {{ap_verify}} packaging as much as possible with the common datasets format."
Answer: 25933.0

User story: "DM-10729 added incomplete support for using meas_mosaic (and soon, jointcal) results in to calibrate the catalogs used by validate_drp.  This feature has only been tested in a one-off sense, because we currently don't have any CI processing of a dataset large enough to run meas_mosaic/jointcal.  Once that's addressed, we should finish making it possible to utilize jointcal results in the main driver scripts used by SQuaSH and enable these tests in CI.    If anyone knows of a ticket for adding larger datasets to CI, please add it as a blocker."
Answer: 176228.0

User story: "The new {{PhotometryModel}} design in jointcal is gaining (in DM-9195) a number of new C++ features, is safer with pointers and references, and uses {{unordered_maps}} for the Constrained ccdImage map with {{CcdImageKey}}, instead of raw pointers. We should update the {{AstrometryModel}}, Fit and Mappings to use this cleaned up design."
Answer: 686418.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: "scatter3d bugs:   - 2d axes should not show  - options should be basic (not scatter) and should not include options for 2d XY  - drag mode buttons should be those that are supported for 3d  - selection button should not show unless chart supports selection  - zoom to original should work"
Answer: 1262.0

User story: Short lived tags (daily, etc.) should be automatically cleaned up once they have "expired". This should include eupspkg and tarball repos.
Answer: 378748.0

User story: "Per request from project management, make a Test Report from the HSC full reprocessing analysis. "
Answer: 25727.0

User story: "Initial effort to bring {{pex_config}} to the Sphinx-based documentation system.    This involves:    - Adding Sphinx documentation infrastructure for packages.  - Convert docstrings in {{lsst.pex.config}} to Numpydoc format to generate an API reference.  - Port existing user guide content from {{pex_config}} to reStructuredText (though fully converting this content into topic-based documentation is not in this scope).    This is related to DM-11253 for {{pipe_base}}."
Answer: 751783.0

User story: "Create tutorial cluster/etc."
Answer: 15970.0

User story: "Update the chart content of ffapi-slate-test2.html to be in sync with the change of the relevant sample in firefly_client.     The content for each chart on WISE search is updated as follows,   2D scatter: w1-w2 and w2-w3 for x and y  heatmap: 3 sets, w1 vs. w2, w1 vs. w3, and w1 vs. w34.  histogram: 2 sets, w1, w2.  3D scatter: w1, w2, w3 for x, y, z.    "
Answer: 1532.0

User story: "After all the contributors have added their section, check for sanity/consistency/etc, and write a summary."
Answer: 9132.0

User story: "Our Block-SDMM algorithm has always had certain blends that never met the convergence criteria even when a model appeared to quickly converge to a solution. Further investigation revealed that this behavior occurs because the traditional check for convergence in an ADMM-like algorithm breaks down when the dual variable (_Z_) is a projection onto zero. In this case, which is true of the symmetry operator L, the residual is R^2 = (LX-Z)^2 (where X is the matrix we are solving for), which is compared to the primal error e^2=e_rel^2 * max(Z_k+1 - Z_k, LX^2)=e_rel^2 * LX^2 = e_rel**2 * R^2, where e_rel is the maximum relative error allowed.    The convergence criteria is R^2<= e^2, which is never true in the case where Z_k is a projection onto a single value (in this case zero). The current algorithm just checks that R^2<=e_rel**2, which does not scale properly with the number of objects and size of the image, causing the issues we are seeing with convergence in certain blends.    This ticket is to devise a mathematically sound and accurate check that the algorithm has converged, even in cases where the constraint _cannot_ be met (for example the solution is not symmetric), including a flag to note that a particular peak (or blend) failed to meet the constraint."
Answer: 343121.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 storage docstring  {code}  class Storage:      """Base class for storages"""  {code}  is wrong. It's a factory & helper for StorageInterfaces. It needs to be fixed.
Answer: 51605.0

User story: "Qserv has small bunch of Python scrips and modules which have not been migrated to python3 yet. Check and migrate what is necessary and make sure it works with both py2/py3."
Answer: 27048.0

User story: There are frequently breakages / regressions that occur in the normal course of development between runs of {{weekly-release}}, which for various reason only turn up during the weekly release cycle, and these problems are preventing its on time production.  As the "weekly" is now on the critical path for many developers, this results in unplanned / reactive ops works nearly every week.    In hopes of beating down the rate of failure, a more limited per day or "nightly" release is proposed.  At least initially, this would treated as a shake down or quasi-canary build and not considered as an "official" product.    The "nightly" would differ from the weekly in the following ways:    * no git tag (initially) -- a moving "nightly" tag might be useful at some point while avoiding having to eventually prune git tags  * only a single eups distrib tag would be created  * tarballs limited to py3 (reducing runtime / cpu consumption by half)  * no docker images (initially -- this will also reduce resource consumption)  * eups distrib tag format would be {{d_<year>_<mon>_<day>}}. Where the {{d}} prefix is for "day" and year/mon/day would be the Gregorian calendar date in project standard time.
Answer: 1421.0

User story: "The text for membership of the DM SysEng and DM CCB groups is inconsistent. Make them identical."
Answer: 2988.0

User story: "Work out all the issues in deploying a Firefly server in lss-dev or Nebula environment. "
Answer: 32776.0

User story: "Work out all the issues in deploying a Firefly server in lss-dev or Nebula environment. "
Answer: 1538.0

User story: Given the quality of the data expected/required for LSST (and already present for HSC), provide an option to plot and print statistics for certain metrics in "milli" units.  This includes all magnitude differences (milli-magnitude denoted as *mmag*), astrometric indicators (milliarcsecond denoted as *mas*), and ellipticity e1 & e2 residuals (unitless denoted as *milli*).  This will be provided as a config parameter *toMilli* that will default to *True*.
Answer: 61984.0

User story: "Write sections 1 (Introduction) and 6 (Interconnectedness) for LDM-542 (Science Platform Design)"
Answer: 2.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: "These scripts were being developed on an old version of matplotlib (which was being provided by the shared stack on {{tiger}} at Princeton -- this has recently been updated).  The shared stacks on {{lsst-dev}} and {{tiger}} (at Princeton) provide a newer version which results in deprecation warnings and badly formatted plots (to the point where axis labels fall off the side of the figures).  This makes several tweaks to adapt to the currently supplied shared stack versions:  {code}  Current on lsst-dev is matplotlib.__version__ '2.0.0'  Current on tiger at Princeton is: matplotlib.__version__ '2.0.2'  {code}"
Answer: 61988.0

User story: "The {{lsst.verify}} package uses flake8 pytest configurations meaning that by default {{verify}} fails when DM-11514 is active because the flake8 plugin is not installed. Add this package as a dependency of sconsUtils. We may have to install flake8 as well, although that might be in the conda installations already."
Answer: 235.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: "These small fixes address some warns that I have encountered in more recent gcc and clang releases, and some things flagged by the eclipse c++ code analyzer "
Answer: 236.0

User story: "The squash deployment tool will clone the repositories for the individual squash microservices, set the appropriate namespace for the deployment, create the secrets, and deploy the microservices in the right order.  "
Answer: 24444.0

User story: "Provide inputs to the DM-11535 spreadsheet."
Answer: 38629.0

User story: "Before we can switch to the replan schedule, we must ensure that all F17 milestones are complete or are mapped to post-replan milestones.    Work with the T/CAMs to achieve this."
Answer: 38630.0

User story: "For each of the 29 slipped milestones presented at the DM review, we should be able to:    - State with confidence that it will be addressed during F17, or  - Describe which post-replan milestone will capture the work.    Work with the other T/CAMs to capture this information."
Answer: 3931.0

User story: "[~<USER> has updated the master milestone list with new descriptions of DAX milestones. Pull these into LDM-564."
Answer: 5.0

User story: "Adapt Jim's notebook and dataset for the stack tutorial. "
Answer: 76215.0

User story: "Tasks from cancelled user queries are left on worker schedulers until they would be run. This may result in the query taking a very long time cancel, but testing needs to be done if this is the case.  If so, the code should be changed to run the cancelled tasks right away to clear the user query. When run, cancelled tasks realize they are cancelled quickly and use few resources. "
Answer: 2804.0

User story: "Invalid rows from cancelled attempts at a job are currently deleted when the next attempt of the job is started.  With large results this takes too much time, so the invalid row removal will be moved to a single query when all jobs have run. It will also be run if the query is too large, too make sure that the size problem is not caused by invalid rows.   There are markers in the code (TODO:DM-11524) where some changes need to be made."
Answer: 30193.0

User story: "SuperTask design is being documented in DMTN-055 prior to being integrated with (also rewritten) Butler design text in LDM-152.    This issue captures [~<USER>'s contribution to that tech note."
Answer: 134083.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 process of getting processCcd, jointcal, and multiband to work with obs_mosaic data, we found several cases where a default task configuration for some process did not work with our data. And we found in some cases that a default setting only worked with one camera (probably the one for which the config setting had been developed).    Other cameras seem to work around these kinds of problems by having their config settings in obs_*/config.  While this works, it would be better I think to have default setting which works with most cameras.  It would certainly be more friendly to new pipeline developers.    I will start by creating an RFC to create discussion on this issue, then let the result of the RFC decide what if any work needs to be done."
Answer: 62496.0

User story: "jointcal.py uses the visit identifier from its dataRef to group exposures which belong to the same visit.  However, in obs_mosaic, there is no visitId, just a set of five keys which together uniquely identify a visit.    I made a private alternation to jointcal.py to allow the option to create such a unique identifier from a set of dataId keys, and would like to propose that this be incorporated into the main code line.    John would like to examine the code before he commits one way or the other, so the purpose of this ticket is to allow me to create a branch with my changes which he can easily examine.  If he agrees with the concept, we can put this ticket through the normal review process."
Answer: 72113.0

User story: "This ticket is for the work of migrating the DB tests such that they run with the py.test test runner."
Answer: 974.0

User story: The current LDM-564 draft (on {{tickets/DM-11468}}) uses short names ("DRP-MS-IMCHAR-6", etc) for SciPi milestones. Turn them into something readable.
Answer: 1227.0

User story: "This ticket is for modifying sconsUtils such that it uses pytest for test execution rather than python.  This is part of improving the test execution environment such that we can capture output from tests in a JUnit format compatible with Jenkins, and so that we can report on skipped tests as well as test execution times."
Answer: 24742.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: "With [DMTN-030|https://dmtn-030.lsst.io] we have a conceptual design for Science Pipelines package documentation design. I've realized part of that concept in {{pipe_base}} documentation (DM-1253). The next step is to document these content patterns and the Git repository layout more precisely so that the {{pipe_base}} documentation effort can be replicated by anyone in any other package.    I think we want to continue to use the [lsst/templates|https://github.com/lsst/templates] repository for this type of package documentation. Two key issues with [lsst/templates|https://github.com/lsst/templates] are:    # It's filled with non-essential content (like a pybind11 example)  # It's hard in that example format to document libraries of repeatable content snippets, like Task documentation pages, for example, that aren't essential parts of a package, but _are_ nontheless standardized.    This ticket is intended to prototype a new organization of the [lsst/templates|https://github.com/lsst/templates] repository that allows more effective documentation of both package structure and documentation templates.    Some design goals are:    - Eventual compatibility with [cookiecutter|http://cookiecutter.readthedocs.io].  - Ability to document repeating content fragments in a way where an original source of truth is clear, and that templated information is propagated throughout the template project.  - Ability to have template documentation alongside the template itself.    On a practical level, [~<USER> notes that [obs_test|https://github.com/lsst/obs_test] is probably a more up-to-date example of a package than the [lsst/templates|https://github.com/lsst/templates] repository is."
Answer: 31721.0

User story: "Create an EUPS package for pytest PyPI distribution."
Answer: 4309.0

User story: "This is an old action from DMLT. But it is still relevant. We need Test Specifications and Test reports which tie NCSA work to requirements for verification. There are probably some missing requirements documents also."
Answer: 1341085.0

User story: "Our coadd catalogs still contain objects for which we can't compute a valid coadd PSF, which is strange, because we should have a coadd PSF anywhere we have pixel data and we should be restricting centroid errors to keep them from flying off the edges of images (at least mostly).    We should look at some coadd catalogs - especially in edge patches - and investigate the objects for which this is the case."
Answer: 2969.0

User story: "ssllabs is giving many (most) of our TLS fronted properties an F rating for being vulnerable to CVE-2016-2107.  Presumably, this will be resolved by an openssl updated."
Answer: 1649.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: "Prepare new system diagram for DM system architect."
Answer: 33117.0

User story: "This ticket might be well be {{invalid}} but...    Why does the template package contain {{daf.fmt.mysql}}? e.g. in {{templates/python/lsst/}} and other places there is {{lsst.daf.fmt.mysql}}, which seems to have been added deliberately, but it's not clear, from idiot-inspection and the README, why this needs to be there.     Moreover, its existence in {{templates/ups/}} means that once one follows the instructions to replace all the {{TMPL}} instances with the new package name, doing a {{setup -j -r .}} from the package dir results in an error:    {noformat}  I can't guess which product you want; directory /Users/merlin/lsst/ip_cpp/ups contains: daf_fmt_mysql ip_cpp  {noformat}    Is this the desired functionality? Can this be safely removed? (It seems that it can, but then why is it there?)  "
Answer: 3043.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: "  {code:java}  ERROR: Execution failed  java.lang.UnsupportedOperationException: Undefined symbol ‘choiceParam’   at org.jenkinsci.plugins.structs.describable.DescribableModel.resolveClass(DescribableModel.java:438)   at org.jenkinsci.plugins.structs.describable.UninstantiatedDescribable.instantiate(UninstantiatedDescribable.java:174)   at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:364)   at org.jenkinsci.plugins.structs.describable.DescribableModel.coerceList(DescribableModel.java:453)   at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:357)   at org.jenkinsci.plugins.structs.describable.DescribableModel.injectSetters(DescribableModel.java:333)   at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:259)   at org.jenkinsci.plugins.workflow.steps.StepDescriptor.newInstance(StepDescriptor.java:194)   at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:181)   at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:126)   at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108)   at groovy.lang.GroovyObject$invokeMethod$19.call(Unknown Source)   at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)   at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)   at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:151)   at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:21)   at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:115)   at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149)   at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146)   at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123)   at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123)   at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:16)   at WorkflowScript.run(WorkflowScript:135)   at ___cps.transform___(Native Method)   at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57)   at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109)   at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82)   at sun.reflect.GeneratedMethodAccessor251.invoke(Unknown Source)   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)   at java.lang.reflect.Method.invoke(Method.java:498)   at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)   at   {code}  "
Answer: 11704.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 {{w_2017_31}} weekly release failed building master due to what appears to be a repeatable git-lfs error, possibly triggered by DM-11095.    {code:java}     testdata_jointcal: Traceback (most recent call last):    File "/home/lsstsw/jenkins/release/lsstsw/lsst_build/bin/lsst-build", line 51, in <module>      args.func(args)    File "/home/lsstsw/jenkins/release/lsstsw/lsst_build/python/lsst/ci/prepare.py", line 762, in run      manifest = p.construct(args.products)    File "/home/lsstsw/jenkins/release/lsstsw/lsst_build/python/lsst/ci/prepare.py", line 725, in construct      self._add_product_tree(products, name)    File "/home/lsstsw/jenkins/release/lsstsw/lsst_build/python/lsst/ci/prepare.py", line 713, in _add_product_tree      dependencies.append(self._add_product_tree(products, dprod.name))    File "/home/lsstsw/jenkins/release/lsstsw/lsst_build/python/lsst/ci/prepare.py", line 713, in _add_product_tree      dependencies.append(self._add_product_tree(products, dprod.name))    File "/home/lsstsw/jenkins/release/lsstsw/lsst_build/python/lsst/ci/prepare.py", line 696, in _add_product_tree      ref, sha1 = self.product_fetcher.fetch(product_name)    File "/home/lsstsw/jenkins/release/lsstsw/lsst_build/python/lsst/ci/prepare.py", line 333, in fetch      git.checkout("--force", ref)    File "/home/lsstsw/jenkins/release/lsstsw/lsst_build/python/lsst/ci/git.py", line 49, in checkout      return self('checkout', *args, **kwargs)    File "/home/lsstsw/jenkins/release/lsstsw/lsst_build/python/lsst/ci/git.py", line 44, in __call__      raise GitError(retcode, cmd, stdout, stderr)  lsst.ci.git.GitError: Command '['git', 'checkout', '--force', 'master']' returned non-zero exit status 128.  stdout:    stderr:  Downloading cfht_minimal/src/06AL01/D3/2006-05-20/r/SRC-849375-12.fits (75.94 KB)  Error downloading object: cfht_minimal/src/06AL01/D3/2006-05-20/r/SRC-849375-12.fits (5071e4548d33b407c0438b3b7fcbf4fab390674f30ccfd5f7492e21b689e6653)    Errors logged to /home/lsstsw/jenkins/release/lsstsw/build/testdata_jointcal/.git/lfs/objects/logs/20170805T020850.70624876.log  Use `git lfs logs last` to view the log.  error: external filter git-lfs smudge %f failed 2  error: external filter git-lfs smudge %f failed  fatal: cfht_minimal/src/06AL01/D3/2006-05-20/r/SRC-849375-12.fits: smudge filter lfs failed  {code}  
Answer: 1476.0

User story: "Qhttp unit test fails frequently under OSX.  Investigate and fix."
Answer: 5861.0

User story: "  If DNS needs to be managed external to k8s, here is an example:   https://github.com/lsst-sqre/deploy-eups-redirect/blob/master/terraform/dns/main.tf"
Answer: 66198.0

User story: "[~<USER> manually invoked a {{build-publish-tag}} build with a git tag of {{qserv-dev}}, which was transliterated by the build into the eups distrb tag of {{qserv_dev}}.    https://ci.lsst.codes/job/release/job/build-publish-tag/169/parameters/    Per discussion on #dm-square, [~<USER> has ruled that {{-}}s are OK in distrib tag names."
Answer: 145.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: Switched to using the {{lsstsw}} miniconda set of Python.  This triggered a test failure in plotting:    1. Diagnose the incomptible syntax  2. Develop and implement a workaround.    {code}  [2017-08-04T19:31:15.808465Z] ======================================================================  [2017-08-04T19:31:15.808497Z] ERROR: testPlotMetricsFromJsonJob (__main__.ParseJsonJob)  [2017-08-04T19:31:15.808532Z] Does plotting the metrics run and produce the correct filenames?  [2017-08-04T19:31:15.808569Z] ----------------------------------------------------------------------  [2017-08-04T19:31:15.808590Z] Traceback (most recent call last):  [2017-08-04T19:31:15.808629Z]   File "tests/test_load_json.py", line 96, in testPlotMetricsFromJsonJob  [2017-08-04T19:31:15.808649Z]     plot_metrics(job, filterName)  [2017-08-04T19:31:15.808704Z]   File "/Users/wmwv/lsstsw/build/validate_drp/python/lsst/validate/drp/validate.py", line 319, in plot_metrics  [2017-08-04T19:31:15.808724Z]     outputPrefix=outputPrefix)  [2017-08-04T19:31:15.808781Z]   File "/Users/wmwv/lsstsw/build/validate_drp/python/lsst/validate/drp/plot.py", line 483, in plotAMx  [2017-08-04T19:31:15.808807Z]     fig = plt.figure(figsize=(10, 6))  [2017-08-04T19:31:15.808861Z]   File "/Users/wmwv/lsstsw/miniconda/lib/python2.7/site-packages/matplotlib/pyplot.py", line 527, in figure  [2017-08-04T19:31:15.808920Z]     **kwargs)  [2017-08-04T19:31:15.808989Z]   File "/Users/wmwv/lsstsw/miniconda/lib/python2.7/site-packages/matplotlib/backends/backend_qt5agg.py", line 43, in new_figure_manager  [2017-08-04T19:31:15.809026Z]     return new_figure_manager_given_figure(num, thisFig)  [2017-08-04T19:31:15.809099Z]   File "/Users/wmwv/lsstsw/miniconda/lib/python2.7/site-packages/matplotlib/backends/backend_qt5agg.py", line 50, in new_figure_manager_given_figure  [2017-08-04T19:31:15.809125Z]     canvas = FigureCanvasQTAgg(figure)  [2017-08-04T19:31:15.809188Z]   File "/Users/wmwv/lsstsw/miniconda/lib/python2.7/site-packages/matplotlib/backends/backend_qt5agg.py", line 216, in __init__  [2017-08-04T19:31:15.809224Z]     super(FigureCanvasQTAgg, self).__init__(figure=figure)  [2017-08-04T19:31:15.809287Z]   File "/Users/wmwv/lsstsw/miniconda/lib/python2.7/site-packages/matplotlib/backends/backend_qt5agg.py", line 65, in __init__  [2017-08-04T19:31:15.809322Z]     super(FigureCanvasQTAggBase, self).__init__(figure=figure)  [2017-08-04T19:31:15.809384Z]   File "/Users/wmwv/lsstsw/miniconda/lib/python2.7/site-packages/matplotlib/backends/backend_qt5.py", line 239, in __init__  [2017-08-04T19:31:15.809418Z]     super(FigureCanvasQT, self).__init__(figure=figure)  [2017-08-04T19:31:15.809448Z] TypeError: 'figure' is an unknown keyword argument  [2017-08-04T19:31:15.809454Z]  [2017-08-04T19:31:15.809491Z] ----------------------------------------------------------------------  {code}
Answer: 10.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: "Now that ip_cpp exists on Github, could you do whatever JIRA magic is required so that it appears on the drop-down menu so I can file tickets that relate to it please?"
Answer: 172.0

User story: Create ip_cpp from LSST package template.    Clone it, rebase out template stuff, create this branch to change template values to real values, merge (and optionally make that look like the birth if that's "the done thing").    To make sure that all the machinery works, also include the birth of its first task and subTask. The {{task}} will be the "run all" task, called {{cppTask}} which will be configurable in the usual way, and its first {{subTask}} will be the first worker task for this package, which will calculate the gains, amplifier by amplifier, using Fe55 data.
Answer: 191896.0

User story: "The {{squash-api}} will connect the {{squash-bokeh}} and {{squash-db}} microservices"
Answer: 31633.0

User story: "The plotly code needs to handle plot type that the firefly applications do not support.    The code should do the following.  # recognize each plotly plot type  # put the correct tool bar up for those groups.  This is mostly past through code to plot.ly.  It involves disabling the plotly toolbar and having a firefly like toolbar.  This might already be working.  # make sure plot show the basic options    Test the following:     - bar   - pie   - histogram  (is mostly done already)   - histogram2dcontour   - surface   - box "
Answer: 51830.0

User story: "see- ffapi-slate-test2.html, ApiViewer.showPlot    Add support for plot.ly, make a similar test as ffapi-slate-test-2.html (talk to Trey), add support for the reinitApp event (as implemented in ApiViewer.reinitViewer).    The content for each chart on WISE search is updated as follows,   2D scatter: w1-w2 and w2-w3 for x and y  heatmap: 3 sets, w1 vs. w2, w1 vs. w3, and w1 vs. w34.  histogram: 2 sets, w1, w2.  3D scatter: w1, w2, w3 for x, y, z.  "
Answer: 11574.0

User story: "continue working on the grid layout for firefly, access the plot.ly support, and make more demo/test code"
Answer: 1456.0

User story: "Per my mail to various luminaries of 2017-08-01, we have converged on having three requirements documents for the Science Pipelines: L1 (document ID TBD), L2 (TBD) and CPP (TBD), which will map through LDM-151 (Pipelines design) to three test specifications: L1 (TBD), L2 (LDM-534) and CPP (TBD).    Those requirements documents will capture all of the Pipelines requirements.    Update LDM-503 and the document tree figure to reflect this."
Answer: 703214.0

User story: "At the DM review we were asked to detail the release features. In NCSA at another meeting we agreed to document how releases would be passed to NCSA and delineate responsibility. LDM-564 will serve both puposes for now at least"
Answer: 22561.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 issue is to get us started on updating the descope options for all “subsystems” of DM (3rd level WBS elements), following the 2017 DM review. I have updated guidance after talking to the PST and Steve K.    To remind you, the recommendation says:    bq. #1 Ensure by the Progress Review that all subsystems have consistently derived de-scope options, and link them to their science impacts.    Our response will be an LCR to update the list of DM de-scopes. These are maintained in [Document-17914|http://ls.st/Doc-17914] (and summarized in [LPM-72|http://ls.st/LPM-72]). So you should be looking at Doc-17914 for the rows to update (or add), and LPM-72 for the overall instructions.    How do we start this:      a) Updating the list of descopes: For your respective WBS, we need at least one descope that the Product Owner would be likely to recommend if we had to de-scope. Much of this should be a matter of just reformatting the information from the review slides and entering it into the Doc-17914 format, here:    https://docs.google.com/spreadsheets/d/1xdBoyDbGBY3WIelCAb-14UvtsmalJ4yWzNcMoK34jdE/edit?usp=sharing    (the "DM de-scope" tab). [~<USER> & [~<USER>, could you do it for the pipelines; [~<USER>, can you identify at least one for calibration, [~<USER> for SQuaRE work, [~<USER> for Portal. [~<USER> & [~<USER>, could you do that for the data access services & networks, respectively. [~<USER>/[~<USER> and/or [~<USER>. — could you the same for the NCSA work package? (I hope that covers everyone..). Note: Do consider the proposal that the reviewers made in the close-out comments.      b) The science impact: when updating the science impact, it’s important to clearly mark anything that would violate the SRD, vs. reductions that wouldn’t (as Steve K. put it “that would just be in conflict with contemporary science practice”; say, distributing data over ftp). Those two have different (formal) levels of severity. You can just tag the downscope with “This option would violate REQ-SRD-xxx.”      c) While doing this, do scrub the spreadsheet for scope options that are out of date (and your top scope options may already be in there, just needing an update).      Everyone listed above obviously needs to work with their TCAM to understand the cost/schedule impacts of various options. I don’t think those estimates need to be exact by August 11th (or even September 6th); even a draft will do by then. For the status review, I think it will be sufficient to show we’ve started and will finalize the LCR quickly.    Let’s try to do as much as we can by Aug 11th; I’ll set a deadline of next Tuesday, 8/8; please add your rows by then. If you can’t make that deadline, or if anything’s unclear, let me know.    P.S.: I realize that looking at descopes at 3rd WBS level may miss some system-wide ones (e.g., 60-second latency), but let’s begin this way.
Answer: 42081.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 present, there isn't a mechanism for an end-user to update the `lsst_build` clone used by `lsstsw`.  This could be accomplished by adding additional logic to the `deploy` script or pulling in `lsst_build` as a git sub-tree."
Answer: 37685.0

User story: Early experience from creating {{pipe_base}} documentation has shown that we need a *user documentation content style guide* to help us effectively produce consistent and high-quality documentation for end-users.    This style guide becomes a place to:    - Discuss tone and voice for specific types of end-user documentation and share technical writing advice.  - List preferred spellings, especially for domain-specific words. For example, "subtask" or "sub-task" — I've seen both in existing documentation. We need to decide on one. We also need a place to remind use that it's spelled "GitHub."  - Discuss grammar and style issues beyond what is already in the [Project Publications Style Manual|https://ls.st/Document-13016].    The intent of the user documentation style guide is to respectfully build upon the [Project Publications Style Manual|https://ls.st/Document-13016]. The DM user documentation style guide's default stance should be to inherit the recommendations of the Project style guide. In rare occasions, we may need to override its advice to adopt best practices specific to end-user documentation writing. It's possible that the DM user documentation style guide's recommendations could eventually get moved to [Project Publications Style Manual|https://ls.st/Document-13016], but I think we will always need a style guide specifically for user documentation because of the unique requirements of user documentation compared to management documentation and scientific articles.    This ticket will seed the user documentation content style guide as a sub-section of the [DM Developer Guide|https://developer.lsst.io].
Answer: 826678.0

User story: "The {{ap.verify.dataset.Dataset}} class currently recognizes three types of input data: raw science images, calibration images, and templates. Depending on future policy decisions, up to two more data types -- reference catalogs and defects -- may have their own locations.    For forward compatibility (i.e., to avoid having to change hardwired assumptions about where these files are located) the {{Dataset}} class should have properties giving the location of these two data types. At present, they may be defined to be equal to or subdirectories of {{Dataset.calib_location}}."
Answer: 4037.0

User story: "Recent changes to the Butler have broken the DCR template generation code. This ticket is to update the DCR code to work with the latest version of the Butler."
Answer: 44476.0

User story: "I need to explicitly write down the photometric model that I'm going to implement for DM-9195. It should go in a new section of the jointcal.tex document, which might eventually be converted into a DMTN or actual paper."
Answer: 45862.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 datashader solution that allows the plotting of millions of datapoints (DM-11405) changes how linking the marginal histograms to the selection box must be implemented, and how dataIDs might be obtained from the figures.  That is, because it is now an image rather than a plot containing information about each points, the hover/select features that I had used for DM-10619 must be updated.  I propose to have a secondary "zoom-in" figure on the dashboard that *is* a bokeh scatter plot (thus allowing typical bokeh hover/selection), but would show the region selected in the primary datashader figure.  It will be capped at maybe ~5000 points, beyond which holoviews/bokeh will "decimate" the figure by random sampling.   The marginal histograms, though, should be able to remain the distributions of the full un-decimated dataset (or selection thereof).    In this ticket, implement the following alongside the datashader demo:  * Decimated bokeh plot corresponding to selection  * Marginal histogram figures computed from the full dataset (or selection thereupon), corresponding to what was done for DM-10619.  * Some way for *all* the dataIDs in a region selected on the datashader image to be returned, for use in a callback 
Answer: 111131.0

User story: "A standardized off-boarding process for DM should be documented. Primarily this process will reverse the _on-boarding_ procedure documented at https://developer.lsst.io/getting-started/onboarding.html, though there might be additional steps.    This documentation _could_ appear in the DM Developer Guide, but not necessarily. The presence of this documentation should be advertised to T/CAMs, management, the DM Admin, and anyone involved in the process (such as those who manage NCSA accounts or GitHub organization memberships)."
Answer: 345838.0

User story: "To date, the qa analysis scripts have only been run and tested on HSC data.  As such, it is almost certain some HSC-isms have been unwittingly been baked into the code.  This ticket involves running the scripts on DESC DS1 simulation output and making any adaptations required.  The testing will be done on the visit and coadd levels for the single band (r) of the DC1 run.  This will be a significant step towards generalizing the scripts to run on any LSST-stack processed dataset."
Answer: 146023.0

User story: "add metadata to the ability to put and get {{src}} datasets. this includes column, table, and group metadata, and serialization version info."
Answer: 158134.0

User story: "Use [~<USER>'s AFW database IO code to get a src dataset from a database table via Butler.    This excludes writing specific metadata information from the table (column, table, group descriptions); schema will be inferred.  "
Answer: 74517.0

User story: "Use [~<USER>'s AFW database IO code to get a {{src}} dataset from a database table via Butler.    This excludes getting specific metadata information from the table (column, table, group descriptions); schema will be inferred.  "
Answer: 61777.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> here is my attempt  in changing terraform configuration to allow external connections to SQuaSH DB RDS instance. It didn't work and I couldn't figure out what is missing.    For testing the {{squash-api}} in the kubernetes deployment I can run mysql on another container  and restore a copy of the current DB. It should be enough for now.    If we are going to deploy the SQuaSH DB on kubernetes this example seems to cover what we need:  https://kubernetes.io/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume/"
Answer: 5390.0

User story: "Test Robust Coaddition and answer the following questions:    1) How does it handle 3 input images? What behavior do we want on regions where there are 2 input images? What about the boundaries between regions with 2 and 3 input images.  2) Visually, what does it do with the scattered Y-band background?  3) Subtraction imperfections as a function of source magnitude.   4) Process full Cosmos field to find rare failures.   5) Split Cosmos UDEEP into 2 random subsets of visits and compare robust coadds."
Answer: 148607.0

User story: "{code}  $ bash newinstall.sh     LSST Software Stack Builder  =======================================================================    ######################################################################## 100.0%  Detected git version 2.13.3. OK.      In addition to Python 2 (>=2.7) or 3 (>=3.5), some LSST packages depend on  recent versions of numpy, matplotlib, and scipy.  If you do not have all of  these, the installation may fail.  Using the Miniconda Python distribution  will ensure all these are set up.    Miniconda Python installed by this installer will be managed by LSST\'s EUPS  package manager, and will not replace or modify your system python.    Would you like us to install the Miniconda Python distribution (if  unsure, say yes)? yes    Configured EUPS_PKGROOT: https://eups.lsst.codes/stack/src    ::: Deploying Miniconda2-4.2.12-MacOSX-x86_64.sh  mktemp: too few X's in template ‘XXXXXXXX.Miniconda2-4.2.12-MacOSX-x86_64.sh’  {code}  "
Answer: 14490.0

User story: "Fix {{make refresh-bib}} command in lsst-technote-bootstrap; {{\n\t\n}} were not being properly output in bash shells."
Answer: 9811.0

User story: "If afwData is not installed, afw has a test in test_ImageIo1.py which fails.    "
Answer: 48.0

User story: "Recent changes to {{newinstall.sh}} (e.g. on DM-9526, etc) have substantially changed the way it works so that it's no longer compatible with {{shared-stack.py}}. Update the latter.    In particular, we'll need to:    - Customize the environment so it aligns with that provided by {{newinstall.sh}};  - Rework the installation procedure so that it provides something equivalent to {{newinstall.sh}}."
Answer: 61558.0

User story: "Follow up to DM-10005 (Prototype). Implement Robust Coaddition task and merge into stack. "
Answer: 66221.0

User story: "The {{w_2017_30}} weekly release failed due to master being broken."
Answer: 6199.0