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: "Interactions and conversions between e.g. Point2I and Point2D have always been hard to get right, so it's worth an extra check to make sure they're working as well under pybind11 as they did in Swig.  Most important check is to make sure unit test coverage was good; if it was, the pybind11 interface is almost certainly fine.    There may also be some opportunities to enable some interoperability that weren't there before, because I could never get Swig's implicit conversion typemaps working properly."
Answer: 67657.0

User story: "DM-8913 changed {{DarkCombineTask}} to use {{VisitInfo}}, but this assumed that the {{combined}} variable is an {{Exposure}}, but it's actually a {{DecoratedImage}}.  That means we need to use a different means of getting the metadata in."
Answer: 212.0

User story: "Some very useful comments were made to the CLO posting announcing DMTN-030:    https://community.lsst.org/t/dmtn-030-science-pipelines-documentation-design-technote/1520    But several of us were unclear on some of the details of what was being asked for.  [~<USER> said he would specifically look into following up on these."
Answer: 25366.0

User story: "As an exercise, run the single frame processing code (as-in from pipe_drivers) with the HSC COSMOS dataset on the Verification Cluster.  If appropriate, develop scripts to facilitate the process. "
Answer: 77564.0

User story: "As of 2017-01-19T17:02:34-05:00, https://lsst-web.ncsa.illinois.edu/doxygen/ is giving me a 404.    Maybe related to the home directory migration on lsst-dev earlier today?"
Answer: 1479.0

User story: "The IP addresses of the OSX build slaves have changed since they were destroyed/created.  The configuration should be changed to use the DNS entries that have been created."
Answer: 37431.0

User story: "The PSF modeling tasks conveniently create and set flags indicating which sources were used to determine the PSF model.  The single-frame astrometric and photometric calibration tasks should do the same, indicating at least (for each procedure):   - Which sources were selected for potential matching.   - Which sources were actually matched.   - Which sources were actually used for calibration.    As we have done in PSF modeling, it would also be good to have the ability to reserve a set of candidate sources for validation purposes.    [~<USER> and/or [~<USER> may have opinions on how this interacts with the new source selection stuff they've been working on."
Answer: 158864.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: "meas_modelfit contains a lot of code that was used for FDR-era prototyping of modelfitting and has not been used since.  Some of this is worth keeping and reviving, because it's hard-won algorithmic code we may want to use in the future, while some of it should be removed.  In many cases, the unwanted code is being kept around because it's the only way the code we want is still tested; in other cases a small, easy-to-replace fraction of it is used by the bitrotted code we want to keep or code in active use (i.e. CModel).    This ticket is for cleaning up that mess.  Roughly, that means:   - Remove the custom table/record/catalog classes.   - Remove the custom CmdLineTasks.   - Remove the Sampler and Interpreter classes.    Some of this work may be best spawned done on other tickets, which should be linked here."
Answer: 52084.0

User story: "Tools for to allow quick displays of CModel fit results have generally bitrotted, but the most important ones - simple displays of the model image and residuals - seem to have disappeared entirely.  Given that the low-level code still exists, CModel has been restructured a bit since the HSC port, and I'm not sure at what point these were operational at all on the HSC side, I'm just going to reimplement the high-level part."
Answer: 50670.0

User story: "Currently each RepoData in a Butler is built entirely, one at a time, during Butler.__init__. This makes managing dependencies between Repositories (in RepoDatas) difficult.    For this ticket, rewrite the Butler init sequence so that RepoDatas are built a piece at a time."
Answer: 49124.0

User story: "A set of PSF-matched temp exps and coadds are needed for DM-8290 (Warped Image Comparison) and DM-8140 to test a deblender that incorporates color information.     This ticket will produce a data set for testing purposes with the following parameters:  * 3-patches   * filter=HSC-G, HSC-R, HSC-I    * field=SSP_UDEEP_COSMOS  * 2 types: Deep (matched to fwhm=13pix),  goodSeeing (matched to fwhm=7pix)    Deliverables will be:  1) a link to the repository (processed to mergeCoaddDetections)  2) cookbook for reproducing"
Answer: 17772.0

User story: "DM-7043 changes the SQuaSH database and REST API to make it possible to store datasets produced by validate_drp jobs, measurements metadata and metrics definitions.    Post-qa must be updated to send this information to SQuaSH API"
Answer: 31395.0

User story: "# Investigate installing ESXi 6.5. It's not yet supported for Mac Pro. See: http://www.virtuallyghetto.com/2017/01/esxi-6-5-support-for-apple-mac-pro-61.html  # Thin using this command: {{vmkfstools -K <vmdk>}}  # Install MacOS and Mac OS X upgrades on all VMs.  # Update brew on Sierra  # Enable autostart. See: https://communities.vmware.com/thread/160137?tstart=0  # Rename each VM appropriately and register with Route 53.  # Rename VMs on guest system so they are more easily identifiable when on the machine."
Answer: 31703.0

User story: "Create MacOS Sierra VMs for CI and related use cases for SQRE."
Answer: 12994.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: "Install and configure ESXi on lsst-dm-mac-2.lsst.org similar to lsst-dm-mac.lsst.org."
Answer: 31739.0

User story: "As per discussion on DM-8533, this processing run is needed for comparison with the LSST stack run of the same HSC RC dataset of DM-6818.  Given the issue discovered on DM-8533, this should also include another pass comparing the current config settings of both stacks in order to catch an other divergences."
Answer: 103613.0

User story: "Amend the Developer Guide to require that test modules be prefixed with {{test_}} to enable automatic pytest discovery:    {code}  tests/test_example.py  {code}    See RFC-229."
Answer: 170055.0

User story: "Generate static HTML pages for each LTD product that list available editions and builds.    Edition dashboards are available from {{product.lsst.io/v}} and build dashboards are available from {{product.lsst.io/build}}."
Answer: 52895.0

User story: "Create a Flask app, deployed as a Kubernetes microservice, that creates static HTML version and build dashboards for LSST the Docs products. This service will use LTD Keeper as both a trigger (DM-9021 will de facto design API endpoints that trigger dashboard builds), and as a data source (use Keeper API to discover editions and builds for a product).    This ticket will establish the basic structure of LTD Dasher. A second ticket will then implement an MVP of the dashboards themselves."
Answer: 18704.0

User story: "LTD Dasher is a service to create static version and build dashboards for LSST the Docs products. The dashboards are regenerated with each new build upload and edition update.    - Add POST calls to a LTD Dasher microservice in the Kubernetes cluster from the build upload and edition update API endpoints.  - Add a new Keeper API endpoint to manually trigger dashboard uploads for one or more products.  - Add configuration to LTD Keeper so that it can discover the IP for the dasher microservice."
Answer: 48152.0

User story: "LTD Mason and LTD Keeper both have code that uploads, moves, and deletes collections of objects from an S3 bucket with metadata needed by Fastly. Soon we'll have another microservice, LTD Dasher, that will upload dashboards to S3 and be served by Fastly. This ticket is to refactor S3-related code from Mason and Keeper into a Python package that can be used by all LTD services.    Product: LTD Conveyor. Docs at https://ltd-conveyor.lsst.io"
Answer: 11393.0

User story: "- Enable use of dataset located on host  - Optimized xrrotd behaviour when pod crashes."
Answer: 82727.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: "pybind11 usually casts base-class references or pointers to the most-derived wrapped type, using RTTI and dynamic casts.  This does not seem to work for Table and Record objects, where we instead have to wrap derived-class accessors that return the appropriate type.    I suspect this is because the true types are defined in anonymous namespaces in C++ files, so the most-derived types are not actually accessible to pybind11, and it's doing some sort of dict lookup on {{std::type_info}} rather than a tree of {{dynamic_casts}} (what Boost.Python did).  If that's the case, a invisible change to how these classes are implemented could clean up our pybind11 wrappers.  I imagine we wouldn't want to try to fix this upstream, as pybind11's approach is almost certainly faster than Boost.Python's and works as well in the vast majority of cases."
Answer: 63533.0

User story: "{{singleFrameDriver.py}} (and likely other pipe_drivers scripts) echos a bunch of eups commands and their output on startup. Those commands aren't part of the standard logging system and it should be possible to turn them on/off with an argument. I suggest either:     * {{--verbose-eups-dump}} to turn them on  or   * {{--quiet-eups-dump}} to turn them off.    I'm not sure whether on or off is the better default, and I'd be happy with either.    One can turn them off currently via {{--batch-type none}}, but that changes the actual type of processing, which is not desired."
Answer: 8595.0

User story: "Use of MKL/OpenBLAS was disabled (in commit {{6fe95ec}}) while adapting meas_mosaic to work with the LSST pipeline. It needs to be re-enabled so we're not limited to the slow matrix inversion using Eigen.    Reverting that single commit is sufficient to get the threaded matrix inversion:  {code}    PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND             24920 pprice    32  12 14.7g  13g  45m R 717.0 14.3 506:09.03 python              {code}"
Answer: 205.0

User story: "We have 2 FileData classes and 1 FileInfo class which are all how information about a file.  Refactor these into one class - FileInfo."
Answer: 1586.0

User story: "simpleShape can be verbose due to throwing {{pex::exceptions::RuntimeError}}.  Throwing {{meas::base::MeasurementError}} would make it quieter."
Answer: 46.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 newly added package [lsst-dm/pegasus_workflow|https://github.com/lsst-dm/pegasus_workflow]   uses Pegasus APIs directly in the Python script.  Investigate whether it will become necessary to add Pegasus as an external package / third part package and make it installable like the stack following [the policy|https://developer.lsst.io/build-ci/third_party.html]. Or do we install it on supported systems like HTCondor?     Some questions to think about may include:  - Running Pegasus requires a working HTCondor.  Does Pegasus use HTCondor APIs directly?   - Would HTCondor still be needed if one only runs the DAX-grnerating script, which uses the Pegasus.DAX3 Python APIs, but not tools like pegasus-run, pegasus-plan, etc?  "
Answer: 63465.0

User story: "In RFC-252 the TCT has given feedback on LDM-493. This ticket will implement that feedback.    In addition to technical changes,  LDM-493 needs to be de-scoped:    - Project documentation (LDM) will be described in the DM charter (LDM-294). It's no longer SQuaRE's responsibility to design, maintain, and document how LDM documentation works. Consequently, an overall documentation taxonomy is also no longer in the scope of LDM-493.  - Discussion about who writes the docs (the existence of a documentation engineering role, and participation of engineers in documentation) is also not in the scope of an LDM document, and instead will be managed by T/CAMs.    The scope that remains for LDM-493 is software documentation: technical notes and user guides."
Answer: 99235.0

User story: "Add the proposal for C\+\+ construction syntax from RFC-242 to the developer guide."
Answer: 54975.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: I tried to do my first lsstsw-based installation on a new macOS Sierra computer and got this error during the afwdata build:    {code}               afwdata: Traceback (most recent call last):    File "/Users/<USER>lsst/qa-system/lsstsw/lsst_build/bin/lsst-build", line 51,in <module>      args.func(args)    File "/Users/<USER>lsst/qa-system/lsstsw/lsst_build/python/lsst/ci/prepare.py", line 762, in run      manifest = p.construct(args.products)    File "/Users/<USER>lsst/qa-system/lsstsw/lsst_build/python/lsst/ci/prepare.py", line 725, in construct      self._add_product_tree(products, name)    File "/Users/<USER>lsst/qa-system/lsstsw/lsst_build/python/lsst/ci/prepare.py", line 713, in _add_product_tree      dependencies.append(self._add_product_tree(products, dprod.name))    File "/Users/<USER>lsst/qa-system/lsstsw/lsst_build/python/lsst/ci/prepare.py", line 713, in _add_product_tree      dependencies.append(self._add_product_tree(products, dprod.name))    File "/Users/<USER>lsst/qa-system/lsstsw/lsst_build/python/lsst/ci/prepare.py", line 713, in _add_product_tree      dependencies.append(self._add_product_tree(products, dprod.name))    File "/Users/<USER>lsst/qa-system/lsstsw/lsst_build/python/lsst/ci/prepare.py", line 713, in _add_product_tree      dependencies.append(self._add_product_tree(products, dprod.name))    File "/Users/<USER>lsst/qa-system/lsstsw/lsst_build/python/lsst/ci/prepare.py", line 696, in _add_product_tree      ref, sha1 = self.product_fetcher.fetch(product_name)    File "/Users/<USER>lsst/qa-system/lsstsw/lsst_build/python/lsst/ci/prepare.py", line 333, in fetch      git.checkout("--force", ref)    File "/Users/<USER>lsst/qa-system/lsstsw/lsst_build/python/lsst/ci/git.py", line 49, in checkout      return self('checkout', *args, **kwargs)    File "/Users/<USER>lsst/qa-system/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:  Error: unknown command "filter-process" for "git-lfs"  Run 'git-lfs --help' for usage.  fatal: The remote end hung up unexpectedly  {code}      Details:    - This is a Python 3 lsstsw installation but I also replicated the same issue with a Python 2.7 lsstsw.  - The git-lfs version I see in lsstsw is {{git-lfs/1.2.0 (GitHub; darwin amd64; go 1.6.1; git 9bd3b8e)}}.  - My computer also has a git-lfs 1.5.4 from Homebrew and I've been able to successfully clone {{afwdata}} with this git-lfs (no configuration issues).  - I've also manually cloned {{afwdata}} using the lsstsw-provided git-lfs 1.2.0 (no problem with that git-lfs in my environment).    *This leads me to think that there's some issue with how git/git-lfs is being controlled by {{lsst_build}} on macOS Sierra.*
Answer: 14333.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: lsst-dev01 shared stack builds are having exactly the same problem with w_2017_2 & _3 as recorded for w_2017_1 in DM-8803:    {code}  ***** error: from /software/lsstsw/stack/EupsBuildDir/Linux64/meas_algorithms-12.1-15-g09aec8f/build.log:  tests/testPsfCaching.cc(32): last checkpoint    *** 1 failure is detected in the test module "PsfCaching"  tests/testWarpedPsf    Running 2 test cases...  unknown location(0): fatal error: in "warpedPsf": signal: SIGSEGV, si_code: 0 (memory access violation at address: 0x00000080)  tests/testWarpedPsf.cc(260): last checkpoint: "warpedPsf" entry.    *** 1 failure is detected in the test module "DISTORTION"  The following tests failed:  /software/lsstsw/stack/EupsBuildDir/Linux64/meas_algorithms-12.1-15-g09aec8f/meas_algorithms-12.1-15-g09aec8f/tests/.tests/testExecutables.py.failed  /software/lsstsw/stack/EupsBuildDir/Linux64/meas_algorithms-12.1-15-g09aec8f/meas_algorithms-12.1-15-g09aec8f/tests/.tests/testImagePsf.failed  /software/lsstsw/stack/EupsBuildDir/Linux64/meas_algorithms-12.1-15-g09aec8f/meas_algorithms-12.1-15-g09aec8f/tests/.tests/testPsfAttributes.failed  /software/lsstsw/stack/EupsBuildDir/Linux64/meas_algorithms-12.1-15-g09aec8f/meas_algorithms-12.1-15-g09aec8f/tests/.tests/testPsfCaching.failed  /software/lsstsw/stack/EupsBuildDir/Linux64/meas_algorithms-12.1-15-g09aec8f/meas_algorithms-12.1-15-g09aec8f/tests/.tests/testWarpedPsf.failed  5 tests failed  scons: *** [checkTestStatus] Error 1  scons: building terminated because of errors.  + exit -4  eups distrib: Failed to build meas_algorithms-12.1-15-g09aec8f.eupspkg: Command:          source /software/lsstsw/stack/eups/bin/setups.sh; export EUPS_PATH=/software/lsstsw/stack; (/software/lsstsw/stack/EupsBuildDir/Linux64/meas_algorithms-12.1-15-g09aec8f/build.sh) >> /software/lsstsw/stack/EupsBuildDir/Linux64/meas_algorithms-12.1-15-g09aec8f/build.log 2>&1 4>/software/lsstsw/stack/EupsBuildDir/Linux64/meas_algorithms-12.1-15-g09aec8f/build.msg  exited with code 252  {code}
Answer: 429.0

User story: "The darktime can be {{NaN}} if not set explicitly in the obs package's {{makeRawVisitInfo}}.  Any scaling of an exposure by the darktime can therefore result in a useless image full of {{NaN}} values.  We therefore need to catch the case {{isnan(darktime)}} wherever we use it: pipe_drivers for construction of the dark, and ip_isr for application of the dark."
Answer: 167.0

User story: "The member function {{::clone()}} needs to be wrapped for all derived {{afw::table}} classes."
Answer: 5827.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 DM-9001, we tracked down José Garmilla's S/G separation code and archived it for future use.    On this ticket:    - Get the code working, making minor fixes as necessary;  - Ensure that it is adequately documented (in terms of README files, general explanations, etc), so that future developers can pick it up and understand how to use it.    At the end of this ticket, it should be possible to run the code and understand the outputs, but it's not necessary to perform any sort of integration with the LSST stack, or update it to match LSST coding standards, except insofar as that's necessary to get the basic functionality working."
Answer: 45959.0

User story: "As part of his PhD thesis work on HSC, José Garmilla produced a star-galaxy classifier and associated supporting code. He has now left the field: we should ensure that his code is not abandoned.    On this ticket, please:    - Track down José's code and any associated documentation;  - Make it available in a repository in the lsst-dm organization.    No changes to the code are required."
Answer: 13140.0

User story: "The password credentials for the jenkins swarm client is being set via a {{-password}} cli arg that is visible in the process table (eg, {{ps}}).  This has resulted in the slave credentials appear in the jenkins {{support-core}} plugin logs as well."
Answer: 7110.0

User story: "Write an api.lsst.codes microservice to front-end bootstrapping cookiecutter-created items.    First target: technote.    Stretch goal: microservice."
Answer: 17188.0

User story: "This is the implementation ticket for RFC-265. {{f}} variants of all the log output methods are to be created that will accept format strings in the Python {{str.format}} syntax."
Answer: 9999.0

User story: "The TCT as specified in RFC-206 (and later amended to be chaired by the System Engineer) needs to be inserted into LDM-294."
Answer: 207664.0

User story: "plotAMx currently displays the measured quantity as the design specification, but just at a different precision.  It should instead display the requirement spec."
Answer: 9237.0

User story: "{{ctrl_provenance}} is (almost?) the last product we have that uses {{pex_logging}}. It needs to be converted to use {{log}}."
Answer: 1338411.0

User story: "Minor changes to use the standard pytest boiler plate."
Answer: 240.0

User story: "This is a long-term project to bring in relevant content on the LSST SWUG into the PLI pages.      It's not critical to do right away, but there is a lot of useful info on the pages that will take thought about what needs to be kept and/or modified before inserting into PLI, so will be done longer term.    (The first temporary thing we likely want to do sooner than the full transfer is just put a note at the top of each SWUG page redirecting users who find the pages by Google searches to PLI or CLO for current info and abilities to ask q's that can get answered.) "
Answer: 1779840.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 the implemented version of matcherSourceSelector is purely a copy of the old SourceInfo from matchOptimsticB.py in meas_astrom. This may not be adequate as the matcherSS does not makes use of BaseSourceSelector's isBad flags for bad pixels or cosmics(for instance). This ticket will test and implement which isBad flags are appropriate for the matcher step in matchoOptimistB."
Answer: 1781820.0

User story: "Mask and artifacts needs to be handle in a better fashion. They should be made known to the application by the server any time an image is loaded. The various FileRetrievers that know about the data should include how to load a mask, image overlays, or artifacts.    The system should also try to investigate a multi extension fits file and see it is has related mask or image overlays.    On the client side Mask and artifacts should be added to the drawing layers automatically (turned off but on the list).    When showing tables of images such as wise or LSST images then the mask and artifacts should update as the image changes (this is the way the WISE applications works now)."
Answer: 30020.0

User story: "The Crop.java and CropTest.java are deprecated now.  They will be in repository for now and then they will be deleted when approperiate. "
Answer: 1249180.0

User story: "The ordinates for the overscan spline interpolation can violate the requirement of monotonic increasing in the presence of masked rows, causing GSL to reject it and we end up raising an exception.  For example (notice the third element):    {code}  #1  0x00002aaadf6ccae4 in lsst::afw::math::InterpolateGsl::InterpolateGsl (      this=0x6f4ef0, x=std::vector of length 30, capacity 32 = {...},       y=std::vector of length 30, capacity 32 = {...},       style=lsst::afw::math::Interpolate::AKIMA_SPLINE)      at src/math/Interpolate.cc:211  211         int const status = ::gsl_interp_init(_interp, &x[0], &y[0], _y.size());  (gdb) p x  $19 = std::vector of length 30, capacity 32 = {-4.6668978729026289,     -1.0006934865900383, -2.2712418300653598, -0.76676245210727956,     -0.70019157088122619, -0.63362068965517238, -0.5668103448275863, -0.5,     -0.43342911877394619, -0.36685823754789276, -0.30028735632183906,     -0.23371647509578544, -0.1669061302681992, -0.10009578544061301,     -0.033524904214559385, 0.033045977011494247, 0.099616858237547928,     0.16618773946360157, 0.23299808429118776, 0.29980842911877403,     0.36637931034482762, 0.43295019157088127, 0.49952107279693497,     0.56609195402298851, 0.6329022988505747, 0.69971264367816088,     0.7662835249042147, 0.83285440613026807, 0.89942528735632199,     0.96623563218390807}  {code}    This is because the code to generate these ordinates (binning the overscan data vector) is incorrect."
Answer: 483.0

User story: "This ticket will implement RFC-107, which states that all Python docstrings and comments must have a maximum line length of 79 characters.  "
Answer: 767659.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> noticed that jointcal is now very slow to write its output. This is at least in part due to the way I rewrote the output code to work with decam, which does not have "ccd" in its dataRefs. I think new slowdown is coming from the repeated calls to {{get("calexp").getDetector().getId()}}.    [~price] suggested making a dictionary to map visit and ccd name to each dataRef:    {code}  visit_ccd_to_dataRef = {(dataRef.dataId['visit'], dataRef.get('calexp').getDetector.getId()): dataRef for dataRef in dataRefs}  {code}    and then replacing the for loop and if statement with a lookup in the dict.    Note to Butler people: this problem is related to the problem of having no standard set identifiers in the dataIds: if we can guarantee that "visit" and "ccd" are always there (and, I'd argue, some other things), this code would be quite a bit simpler.
Answer: 2910.0

User story: "After DM-7043 the SQUASH API support the data blobs produced by validate_drp, to implement the drill down capability the bokeh apps must consume the data blobs associated to each measurement."
Answer: 69090.0

User story: "Repeat of DM-8950 to test probable fixes on current eups master branch."
Answer: 57520.0

User story: "Wrap the new Footprints class with pybind11. A success criteria for this is successfully porting and updating the Footprints python unit test to successfully run."
Answer: 12964.0

User story: "obs_cfht.table includes:  {code}  envAppend(DYLD_LIBRARY_PATH, ${PRODUCT_DIR}/lib)  envAppend(PYTHONPATH, ${PRODUCT_DIR}/python)  envAppend(PATH, ${PRODUCT_DIR}/bin)  {code}    These {{envAppend}} calls should be {{envPrepend}}."
Answer: 7246.0

User story: "Once DM-8968 is completed the developer guide needs to be updated with the new procedure for deprecating a feature. From RFC-213, this should be a decorator that creates a deprecation warning in the next 6-month release and removal in the following release."
Answer: 1072547.0

User story: "Create a decorator to mark features for deprecation, which includes the version of the stack that will no longer include the feature. The decorator will be used to both warn users of deprecation and to keep track of all features set for removal in a certain version. It will autogenerate note in the sphinx documentation to mark the feature as deprecated.    Once this is completed an update should be made to the developer docs."
Answer: 1072552.0

User story: After a discussion in Slack (a while ago in Dec 2016) we agreed that we're getting too many emails during code reviews when a developer replies "Done" to each line comment. A way around this is to use GitHub's emoji reactions: the dev can check off a comment, but an email is not sent out.    This ticket documents that process in the [Developer Workflow page|https://developer.lsst.io/processes/workflow.html] of developer.lsst.io.
Answer: 14597.0

User story: "Run my AP prototype on ccqserv150 with databases storage on SSD/NVMe and add performance figures here."
Answer: 6467.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "I want to try to improve indexing in the DiaObject table to make both search and insertion faster."
Answer: 19970.0

User story: "The signature of {{ProcessCcdTask.\_\_init\_\_}} has changed (in DM-8232 to support distinct reference catalogs).  {{SingleFrameDriverTask.\_\_init\_\_}} needs to be changed to match."
Answer: 459.0

User story: To reproduce the problem:    # Start the IRSA viewer in the browser (/ocalhost:8080/firefly/)  # Select "Create a New Plot 3-color"  # Select Red panel and Wise data  # Enter "m31"  # Click "Search"  # Click the file save icon in the toolbar  # Click "Download"   # But nothing happens after clicking download    NOTE: If the type of file is PNG, it works.  
Answer: 62116.0

User story: "{{lsst.afw.image.makeRawVisitInfo}} does not set the darktime. At the least, it should default to the exposure time."
Answer: 8599.0

User story: "Calling {{@sqrbot ltdstatus <product>}} with a non-existent product name currently only says the product is not published. Let's add another return type to distinguish between an actually broken product and bad input from the user (or a product that hasn't been registered yet)."
Answer: 284.0

User story: "DM-8621, which will re-organize the deblender tasks, requires some sort of multi-color deblender. The best candidate so far is using non-negative matrix factorization to ensure that templates have the same footprint in each band.    This ticket involves writing and testing an NMF plugin for the deblender and comparing its performance to the current deblender. NMF may be robust enough to replace the current SDSS deblender or it might just be another step in the deblending process."
Answer: 89250.0

User story: Sometimes in the irsa tri-view, the images don't match the table and the xy-plot.    For example:  In http://localhost:8080/firefly/lsst-pdac-triview.html;a=layout.showDropDown,  select "Images" and "Science Ccd Exposure",  target: ra = 9.6, dec = -1.1;    Then in the tri-view, five images have been downloaded (one of the scienceCcdExposureId is 1755410440). Now click any row which never downloaded images (for example, with the scienceCcdExposureId=4203410469), now this new set of images start to be downloaded. BEFORE (!) the downloading is finished, click back the very first row (1755410440) and wait for the downloading to finish. When the downloading is done, you will see the inconsistent tri-view:  The first row is selected in the table, the dot of the first row in the xy-plot is highlighted, but the images are the new set. If user keeps clicking on the first row, the tri-view won't change and the inconsistency stays. Only when the user clicks any other row, the inconsistency will be gone.    Bug?
Answer: 12792.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: "Once we have eupspkg and the developer docs updated to reflect the new {{_build/}} directory structure, we need to audit out current packages and update them to reflect this new structure. This would require at minimum updating their .gitignore files, but it may require tweaks to eups files as well.    Part 3 of the implementation ticket for RFC-111."
Answer: 1776956.0

User story: "In order to make the use of {{_build/}} directories viable, we need to update eupspkg to untar into those directories and look in that directory for the built products. This may require some work deep inside eupspkg.    Part 2 of the implementation ticket for RFC-111, and should probably be done at the same time as DM-8954, so that the build tools are ready at the same time as the documentation."
Answer: 1342146.0

User story: "Plan Epic DM-8290 (Implement prototype warped image comparison per LDM-151 8.3.5):  * Investigate problem  * Gather requirements  * Research previous solutions (what other projects, applications do)  * Plan work    The deliverable will be the creation of a series of tickets that will constitute this epic.      LDM 151 8.3.5 says:  {quote}Additional artifacts will be detected in DRP by comparing multiple visits that have already been resampled to the same coordinate system. This is similar conceptually to Snap Subtraction, but will operate quite differently in practice, in that we do not expect to combine this stage with the morphological detection stages; instead we assume that everything we can detect morphologically will have already been detected.  Instead, this stage will examine the full 3-d data cube (two spatial dimensions as well as the epoch dimension) for outliers in the epoch dimension that are contiguous in the spatial dimensions. This is an extension of traditional coadd outlier-rejection, which can cause spurious rejections of single pixels (or small groups of pixels) due to noise and differing PSFs. This can obviously detect astrophysical transients as well as image artifacts, and this is usually desirable; this stage is responsible for determing which pixels should con- tribute to our definition of the static sky, and we want to reject astrophysical transients from that as well.  The largest challenge for this algorithm is probably handling highly variable astrophysical sources that are the nevertheless present in most epochs. For these, defining the static sky is more subjective, and we may need to modify our criteria for rejecting a region on a visit as an outlier.  {quote}"
Answer: 72279.0

User story: "Work with [~<USER> on data product inputs/outputs; use JointCal as an example use case of composite datasets; summarize in a data flow diagram. "
Answer: 15527.0

User story: "In Summer 2015, <USER>wrote code to calculate the residual ellipticity KPM: TE1 and TE2    https://jira.lsstcorp.org/browse/DM-3040    Add this code to add TE1 and TE2 to the KPMs calculated in {{validate_drp}}"
Answer: 348489.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: "One option for binary distribution of packages (at least for Linux) is to use the {{eups distrib}} ability to distribute tarballs of built packages. This ticket is for investigating the feasibility of this option."
Answer: 2816.0

User story: "An issue in DM-8948 brought up a problem in how the time are calculated within ctrl_stats.  It made an assumption and used a files creation date as the year to start with;  this worked throughout the year, but failed if the files were pulled in one year, and run in the next year. (time stamps of 2016 vs the year being 2017).   This assumption was fixed in DM-8948.    There is still a problem that exists in year to year calculations, for jobs that start in one year and end in the next.  There will be negatives times calculated.   This ticket will address this issue."
Answer: 11328.0

User story: "Remove the dependency on CAT databases (this functionality has been deprecated and hasn't been in use for a long time).  Also make database setup optional."
Answer: 71903.0

User story: "The production jenkins master instance has become more unstable over time.  It is now often restarting several times a day.  After implementing DM-8378, it is clear that the master process is being sigkill'd rather than segfaulting.  It isn't yet clear if the kernel OOM is being invoked without making dmesg entries, if this is some how caused by the systemd cgroup management, or if it is something being caused by internally by the jvm (heap exhaustion?)."
Answer: 40611.0

User story: "There appears to be ~9 plugins in the production jenkins instance that are un-managed (manually installed) and not in usage.  The support plugin has been manually installed and it pulls in 3 deps. Additionally, the reverse of the {{credentials}} plugin is not version pinned."
Answer: 3013.0

User story: "Migrate the production RDS instance from MariaDB 10.0 -> 10.1 in preparation for the next squash release."
Answer: 435.0

User story: "We need to add a piston to the orientation objects.  This could be done by storing a {{Point3D}} instead of a {{Point2D}} in the {{Orientation}} object, or by adding a piston attribute.  The former is likely cleaner than the latter."
Answer: 4047.0

User story: "* Completed preliminary costing of all aspects of construction and service deployment and assigned tasks functionally to construction, commissioning, an early operations.  * Tied schedule of service deployment to commissioning, early operations, and other project-level milestones.  * Reviewed WBS service-oriented framework with incoming DM project manager.   * Prepared and presented status of NCSA's portion of the DM replan at the DMLT meeting.  * Organized the operational work of the ITC layer according to enclave."
Answer: 40226.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: "Refinements to Commissioning Plan, including consistency-checking with construction replan.  Commissioning Plan Review, plus prep, dry runs, and response.   * <USER>continued contributing to the Commissioning Plan and dry-runs, and traveled to SLAC to participate in the Review.  * Incorporated portions of the DM-wide replan that pertain to operating services for commissioning into the commissioning schedule and cost."
Answer: 40200.0

User story: "Refinement of plan, facility visits, updates to budget etc..  * Prepared for and traveled to Fermilab to present the DPP Ops plan and discuss areas of mutual technical interest and potential DOE staffing areas."
Answer: 40211.0

User story: "* Participation by <USER>on commissioning planning team.  * Contribution to Commissioning Plan document sections about DM and DPP services."
Answer: 4.0

User story: "* Development of NCSA DM WBS based on service-oriented WBS we developed for DPP operations. Resulted in ~1800 lines.  * Breakdown of work at the services layers. Steps are configuration, instantiation, verification, early life support, and operation/maintenance for the construction and commissioning activities. For DPP Services for Observatory Operations, linked service deployment steps to project milestones concerning the arrival of instruments, based on the business goals previously defined by Chuck/commissioning planning.   * Breakdown of design and work to construct the software for DPP services, including Observatory-facing (Level 1), Batch Production (Level 2), Data Backbone (including Base NCSA replication, disaster recovery, and data access support for users and sites), and IT security services. For each package in the software layer wrote a statement of work describing the software construction work as well as the work done at the service layers to support the software development and testing.  * Breakdown of work in ITC layer, organized by fiscal year. Includes development of annual acquisition strategy plans, procurement, installation, and configuration of equipment at both the Base Center and NCSA.  * First attempt at top-down estimation across the WBS, based on engineering judgement. BOE narratives provided as WBS notes, especially in areas where definition of requirements and/or design need improvement.  * Also developed a schema for managing the integration of components in the facility, based on known project goals and milestones. Factors project goals into sub-goals for each level of our WBS. This will serve as a basis for scheduling the WBS once it is complete and sufficiently estimated."
Answer: 1.0

User story: "As shown in DM-8890 MariaDB 10.1+ does not have native JSON support, as an alternative to use  MariaDB in production this ticket captures the work required to change SQuaSH to store JSON as a BLOB/TEXT in MariaDB 10.1+"
Answer: 35738.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: Fix formatting in validateDrp.py --help message    The "description" currently reads as    {code}  Calculate and plot validation Key Project Metrics from the LSST SRD.  http://ls.st/LPM-17\n Produces results to: STDOUT Summary of key metrics  REPONAME*.png Plots of key metrics. Generated in current working directory.  REPONAME*.json JSON serialization of each KPM. where REPONAME is based on the  repository name but with path separators replaced with underscores. E.g.,  "Cfht/output" -> "Cfht_output_"  {code}    But it should read (as written in the string):    {code}      description = """      Calculate and plot validation Key Project Metrics from the LSST SRD.      http://ls.st/LPM-17        Produces results to:      STDOUT          Summary of key metrics      REPONAME*.png          Plots of key metrics.  Generated in current working directory.      REPONAME*.json          JSON serialization of each KPM.        where REPONAME is based on the repository name but with path separators      replaced with underscores.  E.g., "Cfht/output" -> "Cfht_output_"      """  {code}    * I think this is just a matter of passing {{formatter_class=argparse.RawDescriptionHelpFormatter}} to {{argparse.ArgumentParser}}
Answer: 19305.0

User story: "Process refinement and improvement: based on monitoring of in-place processes; improving performance and tuning as needed."
Answer: 119407.0

User story: "Monitor Globus transfer tasks. Refine processes as needed to ensure reliable and robust backup/restore, as well as proper reporting of failures."
Answer: 99501.0

User story: "Build transfer mechanism into DR tool."
Answer: 37267.0

User story: "Install services to support backup and restore operations, e.g., globusonline, gridftp."
Answer: 12.0

User story: "Reconcile internal (low-level) service architecture with high-level services. Will lead to a map of dependencies and other artifacts in the service catalog, and ultimately help populate the configuration management database. Will need to be refined in future work."
Answer: 171491.0

User story: "Incorporate information security plan into service catalog: Work with ISO security representative to uderstand and fold security and risk information into the service catalog. "
Answer: 10.0

User story: "Incorporate additional services into the prototype service catalog: LSST core services (confluence, etc.) and services at NCSA (dev cluster monitoring, etc.) into the service catalog. Communicate with service owners at the appropriate institutions and process responses."
Answer: 80587.0

User story: "Configure and test performance thresholds and incorporate them into the prototype dashboard."
Answer: 171524.0

User story: "The slack migration appears to be a success and HC is essentially unused.  Hipchat notifications from jenkins jobs should be safe to remove at this point and it is an opportunity to prune another plugin."
Answer: 5935.0

User story: "Prototype LSST system monitoring dashboard."
Answer: 55.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: "Install and configure monitoring platform and client based on investigation of various solutions."
Answer: 53.0

User story: "Evaluate time series enterprise monitoring platforms. These include Graphite, TICK/InfluxDB, and Prometheus."
Answer: 53.0

User story: We need JUNIT test for the server side of IPAC table reading.     The testing should include:  * reading 2 or 3 examples of ipac table   * checking that the meta data that is produced    Work with Loi and tatiana for detail that they think need to be tested.      Test Cases Design:    Test One.    Make an IPAC table containing all required and optional fields, like the attributes with key-value key words and comments; the header with column names, unit, data type, and null string; at least one row of data.    Use the table above to test all the constructors in IpacTableReader.java and test all kinds of input parameters.    Allowed Data Types:  int  long  float  double  real - interpret as "float", unless all floating-points are "double"  char  date    Test Two.    Make IPAC tables to test   * missing optional fields, say comments.  * missing required fields, say column names.  * header fields (like the column name) or data are under "|"  * a comment without the space, like "\comment".  * key word without "="      Test if Firefly can handle the tables correctly.    
Answer: 49166.0

User story: "We have been experiencing java segvs on the el6 build slaves since the java update a couple of days ago.    This has been reported upsteam:    https://issues.jenkins-ci.org/browse/JENKINS-40842    This problem has not been (noticed) on test instances so the suspicion is that load/usage has something to do with triggering the issue.  It is also possible the that ongoing stability issues with the jenkins master are a trigger. "
Answer: 99447.0

User story: "Build script is here:  https://github.com/lsst-sqre/jenkins-dm-jobs/blob/master/pipelines/qserv/docker/build.groovy#L25-L26    dev containers should be created at each build, whereas release should only be created once a month."
Answer: 351169.0

User story: "A year has gone by since our last calibs were taken, and so we need to create more to support data obtained in 2016."
Answer: 17979.0

User story: "Write up a technote about how you create a microservice."
Answer: 9872.0

User story: "During deployment of SQuaSH we realized that JSONField() as implemented in DM-8414 works only with MySQL and that the corresponding field type for MariaDB is the DynamicField()    This ticket is to make sure we can use MariaDB features and stick with it in production."
Answer: 1215.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: "Pybind11 version 2, with it's latest bugfix update (2.0.1), is out.  This is a big release with some API incompatibilities (most of which we already depend on). But we have been using pybind11 {{master}} so far so we won't have to change much.  Nevertheless this is slightly more work than normal (normally about 0.1 SP) because {{py::metaclass()}} is now a required attribute for all classes that use {{.def_static}} which requires a lot of (trivial) changes. And of course there may be other hidden problems.    Now that a major fraction of the porting work is done, and we have the upstream features we need merged into the release version, the intention is to stick to fixed releases from now on if possible (instead of tracking master)."
Answer: 79221.0

User story: "May not have any work associated with it, but is an {{lsst_distrib}} dependency. Investigate and update SP."
Answer: 21494.0

User story: "May not have any work associated with it, but is an {{lsst_distrib}} dependency. Investigate and update SP."
Answer: 60102.0

User story: "May not have any work associated with it, but is an {{lsst_distrib}} dependency. Investigate and update SP."
Answer: 42069.0

User story: "May not have any work associated with it, but is an {{lsst_distrib}} dependency. Investigate and update SP."
Answer: 60103.0

User story: "[~price] points out that we can (and likely should) disable EUPS locking globally by adding    {code}  hooks.config.site.lockDirectoryBase = None  {code}    to the EUPS configuration."
Answer: 160890.0

User story: "May not have any work associated with it, but is an {{lsst_distrib}} dependency. Investigate and update SP."
Answer: 60109.0

User story: "May not have any work associated with it, but is an {{lsst_distrib}} dependency. Investigate and update SP."
Answer: 60109.0

User story: "May not have any work associated with it, but is an {{lsst_distrib}} dependency. Investigate and update SP."
Answer: 60109.0

User story: "May not have any work associated with it, but is an {{lsst_distrib}} dependency. Investigate and update SP."
Answer: 72285.0

User story: "May not have any work associated with it, but is an {{lsst_distrib}} dependency. Investigate and update SP."
Answer: 77577.0

User story: "May not have any work associated with it, but is an {{lsst_distrib}} dependency. Investigate and update SP."
Answer: 60117.0

User story: "First set of discussions with K-T to help discover what aspects need to have further information gathered.   * LSST DB 1/2 day meeting with K-T, Fritz, Don, Margaret, Amy  * Individual meeting with K-T to discuss files in more details to start understanding what is required for file catalog, metadata and provenance  * Prep for meetings (understanding how DES does these, discussions with NCSA LSST folks, etc)"
Answer: 28944.0