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: ci_hsc fails is failing for me on Py2 OS X under Jenkins due to an import error.  I saw this on a ticket branch (DM-9045) but given the nature of the change and the fact that ci_hsc ran successfully under Jenkins on Linux, I'm pretty confident that's not the cause of the problem.    I don't particularly need this fixed soon, but if we don't expect this combination of build target and environment to work, it'd be nice to somehow make it clear that's the case.    Here's what looks like relevant part of [the log of the failed build|https://ci.lsst.codes/job/stack-os-matrix/21610/label=osx,python=py2/consoleFull]:  {code}  [2017-02-24T17:28:38.711336Z] ImportError: No module named _utilsLib:  [2017-02-24T17:28:38.711418Z]   File "/Users/square/jenkins/workspace/stack-os-matrix/label/osx/python/py2/lsstsw/build/ci_hsc/SConstruct", line 6:  [2017-02-24T17:28:38.711459Z]     from lsst.pipe.base import Struct  [2017-02-24T17:28:38.711544Z]   File "/Users/square/jenkins/workspace/stack-os-matrix/label/osx/python/py2/lsstsw/stack/DarwinX86/pipe_base/12.1-5-g06c326c+22/python/lsst/pipe/base/__init__.py", line 2:  [2017-02-24T17:28:38.711578Z]     from .argumentParser import *  [2017-02-24T17:28:38.711666Z]   File "/Users/square/jenkins/workspace/stack-os-matrix/label/osx/python/py2/lsstsw/stack/DarwinX86/pipe_base/12.1-5-g06c326c+22/python/lsst/pipe/base/argumentParser.py", line 40:  [2017-02-24T17:28:38.711691Z]     import lsst.utils  [2017-02-24T17:28:38.711773Z]   File "/Users/square/jenkins/workspace/stack-os-matrix/label/osx/python/py2/lsstsw/stack/DarwinX86/utils/12.1-5-g648ee80+3/python/lsst/utils/__init__.py", line 24:  [2017-02-24T17:28:38.711800Z]     from .utilsLib import *  [2017-02-24T17:28:38.711881Z]   File "/Users/square/jenkins/workspace/stack-os-matrix/label/osx/python/py2/lsstsw/stack/DarwinX86/utils/12.1-5-g648ee80+3/python/lsst/utils/utilsLib.py", line 27:  [2017-02-24T17:28:38.711907Z]     _utilsLib = swig_import_helper()  [2017-02-24T17:28:38.711987Z]   File "/Users/square/jenkins/workspace/stack-os-matrix/label/osx/python/py2/lsstsw/stack/DarwinX86/utils/12.1-5-g648ee80+3/python/lsst/utils/utilsLib.py", line 26:  [2017-02-24T17:28:38.712121Z]     return importlib.import_module('_utilsLib')  [2017-02-24T17:28:38.712199Z]   File "/Users/square/jenkins/workspace/stack-os-matrix/label/osx/python/py2/lsstsw/miniconda/lib/python2.7/importlib/__init__.py", line 37:  [2017-02-24T17:28:38.712222Z]     __import__(name)  {code}
Answer: 1356538.0

User story: "The measurement framework should probably log all exceptions at debug level, even the ones thrown via {{MeasurementError}} that will result in a specific flag being set. This is a bit tricky because it probably needs to be done in per-Plugin loggers that are children of the measurement task's logger, so logging can be configured differently for different plugins.  We should probably have the measurement framework create those loggers and pass them to Plugin constructors."
Answer: 84774.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: "Often when I run: {{python <some test script>.py}} on {{lsst-dev01}} from my home directory, the script can take upwards of 40 seconds before it begins to execute. This happens when I run a copy of the stack build with lsstsw in my home directory. Please address whatever issue is causing this. "
Answer: 1577396.0

User story: "In DM-8589, [~<USER> figured out all the information he needs to make the “donut pipeline” work. Make all this available through the standard cameraGeom interfaces."
Answer: 70702.0

User story: "HSC would like to base its next release on a stable version of the LSST codebase. How could this work in a way that benefits both projects? Draft some ideas and discuss with stakeholders."
Answer: 18913.0

User story: The qserv/docker/build jenkins job is very useful to the qserv team (thanks!) but would be even more awesome if it had an additional stage which ran the "4_build-configured-images.sh" script (which is co-located with the scripts used by the preceeding two stages of the job).    The desired sequence is indeed the monty-pythonesque "1, 2, 4..."  here -- script 3 is only used by devs when interposing local changes into their container builds, and is not applicable in the jenkins context.    Thanks much!
Answer: 1832112.0

User story: There are two tags used by the qserv team: "qserv_latest" and "qserv-dev".  The invariant of these tags should be:            qserv-dev >= qserv_latest    That is, qserv-dev should never be left behind when qserv_latest is moved/updated, else much mayhem may ensue.    To avoid mistakes/trouble, we should only retain the two jenkins jobs in qserv/release which:       1) advance both qserv-dev and qserv_latest simultaneously     2) advance qserv-dev on its own    Thanks much!          
Answer: 1832093.0

User story: "[~<USER> requests that I read through the risks in 02C.04 and flag any issues to him before lunchtime (timezone not specified) on Monday 27 Feb."
Answer: 1282.0

User story: "Incorporate various external python scripts that find and fit out-of-focus donut images into a DM stack command line task (and potentially subtasks).  I've got a hacky-but-functional version of this on branch u/jemeyers/donutPipeline.  Items remaining:    * Pull out relevant pieces of characterizeImage into donutFit, so that I don't have to forcibly ignore many of its subtasks.  This includes reducing the schema to what's actually important.  * Add quarter rotations.  * Move obscuration code into afw.cameraGeom and/or obs_* packages.  * Make maximum Zernike coefficient a list so that complicated fits can be developed progressively (first fit Z4-Z11, then Z4-Z15 using previous results as starting point, then Z4-Z21... etc.)  * Add debugging.  Should display donut, model, and residual.  * Extract ZFit code from donutFit task."
Answer: 122321.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: "Sometimes, we don't want users to change the filters applied to the table. (For example, when user selects a band in the LSST time series viewer, we want user to see the table filtered by band, but no choice to remove band filter.     One way to do it is to wrap the requests with the filters we don't want user to see into another request."
Answer: 5669.0

User story: "DM-8088 changed makeCoaddTempExp so that the user no longer has to specify the pixel dimensions of the model PSF to match to. The model Psf dimensions are updated at runtime to match those of the warped calexp PSFs (which have dimensions impossible for a user to know ahead of time).     AssembleCoadd currently attaches the PSF corresponding to the *user-specified model PSF* dimensions rather than the updated PSF-dimensions.  This is bad because the user-specified dimensions could be way off and it's incongruous to tell users that they don't have to pay attention to this in makeCoaddTempExp, but they do in assembleCoadd.     This ticket will ensure that the modelPsf dimension information flows down from the coaddTempExps to the assembled deeepCoadd in a sensible way. Most likely using the maximum dimensions of the input coaddTempExps.    "
Answer: 52536.0

User story: "With RFC-286 the butler now defaults to not return proxy objects. This was done pending solution of DM-9112. Now that this has been solved, reenable lazy loading and check (with {{ci_hsc}}) for which types {{T}} a proxy convertor (implicit conversion {{ReadProxy -> T}}) needs to be registered with {{daf::base::python::register_proxy<T>();}} (in the appropriate pybind11 wrapper files)."
Answer: 1873747.0

User story: "Evaluate IT service management platforms, finalize tool selection."
Answer: 11513.0

User story: "Preliminary testing of the NMF deblender shows that the radial monotonicity operator as designed does not work as expected. [~<USER> and I have verified that the monotonicity operator itself is built properly based on our earlier design, which uses a single reference pixel (the one that lies closest to a radial line from the peak to the current pixel) for each pixel.    Based on a pixels position from the peak, it lies in one of 8 octants that determines which pixel it will use as a reference, but it appears that the transition between reference pixel positions is causing the monotonicity operator to generate weird streaks in the deblended objects that are unphysical.    We are redesigning the monotonicity operator to use the weight of all three neighboring pixels that are closer to the peak as a reference, which we hope will fix this issue."
Answer: 26016.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 spreadsheet I use for planning a cycle provides:    - Number of hours devoted to LOE work per individual;  - Number of hours devoted to story points per individual;  - Number of SPs per epic per individual;  - WBS for each epic.    Given these, and some estimate of rates, it should be possible to extend the sheet to provide a predicted cost breakdown per month per WBS element. This would make explaining variances much easier (see DM-9201, for e.g.)."
Answer: 151027.0

User story: "Similar to DM-9532, create a Python API for accessing specifications located in the {{validate_metrics}} package, producing {{lsst.validate.base.Specification}} objects. This work may introduce a {{SpecificationSet}} class as well.    The loader implementation is driven by the specification YAML format designed in DM-9350. This includes implementing the lightweight specification inheritance system."
Answer: 68807.0

User story: Prototype improved "gray" corrections with aperture corrections in FGCM.  Streamline and vectorize, and make sure that results are consistent with old version at the mmag level.
Answer: 17151.0

User story: "DM-6817 revealed a difference in the trace radii for PSF model stars between the LSST vs. HSC stack runs (DM-6816 and DM-9028).  DM-9535 uncovered that this is due to differences in the implementations of the Brighter-Fatter correction between the stacks (namely in how the second derivatives are computed).     To make a fair comparison between the LSST and HSC stacks, we should be using the same algorithm for the Brighter-Fatter correction.  While an assessment of the optimal algorithm awaits DM-9553, we concluded in DM-9535 that the HSC version seems to be doing a slightly better job, so we will adopt that on the LSST stack for this run.    In addition, I will set {{processCcd.charImage.measurePsf.reserveFraction=0.0}} for this run (instead of the default of 0.2 for {{obs_subaru}}) and do the same in another run of the the RC dataset through the HSC 4.0.5 stack in order to minimize differences in calibrations due to PSF model star selection differences.    While the differences due to the BBox setting for adoptive moments were small (DM-9411) I will also use consistent settings for both runs (here I will adopt the HSC stack to use LSST's setting)."
Answer: 56089.0

User story: "As noted in DM-9535, the method used to compute second derivatives in the Brighter-Fatter correction implementation can lead to significant (up to 1%, which is particularly significant for weak lensing considerations) differences in the trace radii of sources, with the differences becoming larger with brighter magnitudes (see figures in DM-9535).  This ticket is to investigate the optimal algorithm to use for the Brighter-Fatter correction."
Answer: 38792.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 utils.py script in the LSST-DM package sgs-fsbutler calls the function "makeMapperInfo" from the utils.py script in the LSST analysis package. Move "makeMapperInfo" into the sgs-fsbutler utils.py script so that sgs-fsbutler no longer depends on analysis.
Answer: 11417.0

User story: "The Linux build for ctrl_stats succeeds, but the mac OS X build for ctrl_stats fails in the tests/testYearWrap.py.    Additionally, a change in Python 3.6:  {code}  Unknown escapes consisting of '/' and an ASCII letter in regular expressions will now cause an error.  {code}  now makes some code in terminated.py fail (and possibly in other places)."
Answer: 2900.0

User story: "When user upload a time series table that doesn't come from a known mission with images, the images shouldn't be displayed.  So the user can still use the periodogram and do phase folding.    For known mission with missing images or missing expected column for the plot request object,  should not display them or display a user-friendly message. (affect ALLWISE, NEOWISE)      The viewer shouldn't fail or freeze in a 'non-rescued' way."
Answer: 29989.0

User story: "In order to use jointcal's metric outputs with the new metrics system, we need to define what metrics we want to measure. Now that the  {{validation_metrics}} package exists and has some examples in it, we can add the jointcal metrics to it."
Answer: 33116.0

User story: To help prevent problems like DM-9412, obs_base tests should have a {{ButlerPutTests}} class that does a "put" and "get" for every dataset (or some reasonable subset thereof), and checks that what it "get"s matches what was "put". In addition to just testing "put" calls, this lets us test "get" on datasets that don't exist in all of the {{testdata}} repos.
Answer: 1478092.0

User story: "As noted in DM-6817 and highlighted/further explored in DM-9411, there is a trend of increasing difference in trace radii with increasing magnitude when directly comparing outputs from the HSC vs. LSST stacks.  A likely culprit is slight differences in the implementations of the Brighter-Fatter corrections between the stacks.  This ticket is to assess whether this is contributing to the trace radii differences."
Answer: 50472.0

User story: "Until we have butler metrics persistence system, we can use a dedicated logger to output each product's metrics. Since jointcal is the testbed for the new metrics system, we'll use it as an example for how to produce those logs."
Answer: 391874.0

User story: "[~<USER> has written up our sketch of a plan for the new metrics system. This needs to be turned into a technote to facilitate collaborative doc writing. Said technote will eventually become the guiding document for new developers writing new metrics and specifications."
Answer: 20562.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: "DM-9542 completed initial work on transforming metrics to the new YAML schema design in https://sqr-017.lsst.io. Meanwhile, DM-9559 has introduced a SpecificationSet API design that parses a metrics package and provides a collection of Specifications as a mapping.    This ticket is to update the {{MetricSet}} and {{Metric}} classes to match the {{SpecificationSet}} API design."
Answer: 74190.0

User story: "Compiling afw on modern clang results in this warning:  {code}  include/lsst/afw/geom/SpanSet.h:662:10: warning: 'isPersistable' overrides a member function but is not marked 'override' [-Winconsistent-missing-override]      bool isPersistable() const { return true; }           ^  {code}  Please fix by marking the method {{override}}"
Answer: 15410.0

User story: "We need to organize a repository to store validation metric definitions. To start with, pattern it on the [validate_base metrics yaml format|https://validate-base.lsst.io/metric-yaml.html].    As part of this, we should lift the units definition into the metric layer, instead of the specification layer (see DM-9312)."
Answer: 10348.0

User story: "Use the checklist from DM-9182 to clean up code in meas_deblender."
Answer: 11298.0

User story: "Produced tarballs are to copied to a versioned s3 bucket, which will serve as the canonical repository."
Answer: 41682.0

User story: "A method of mangling the shebangs on OSX to a valid path is needed."
Answer: 103648.0

User story: "Needed to pick up support for tarball distribution."
Answer: 11701.0

User story: "The next EUPS release needs to include through at least https://github.com/RobertLuptonTheGood/eups/commit/6eec86deac5da7450b159eb20f707631cea9410e to support tarball distribution."
Answer: 1479.0

User story: "This is triggered by RFC-290, and will be comprised of 2 parts: actually removing runIsrTask from the current ip_isr examples dir, and then editing the doxygen docs so that the example is not referred to any further on the doxygen pages."
Answer: 240.0

User story: "This is triggered by RFC-290, and will be comprised of 2 parts: actually removing calibrateTask from the current pipetasks examples dir, and then editing the doxygen docs so that the example is not referred to any further on the doxygen pages."
Answer: 10370.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: Following DM-3804, the meas_extensions_ngmix tests fail with:    {code}  Traceback (most recent call last):    File "tests/testLMSimpleShape.py", line 130, in testMaxFev      source, msf = self.runShape(config, self.algName, self.exposure, model='dev')    File "tests/testLMSimpleShape.py", line 103, in runShape      task.run(exposure, cat)    File "/ssd/<USER>lsstsw-py2/stack/Linux64/meas_base/12.1-11-g06625e2/python/lsst/meas/base/sfm.py", line 287, in run      assert measCat.getSchema().contains(self.schema)    File "/ssd/<USER>lsstsw-py2/stack/Linux64/afw/12.1-33-g072fda8/python/lsst/afw/image/imageLib.py", line 11600, in <lambda>      __getattr__ = lambda self, name: _swig_getattr(self, ExposureF, name)    File "/ssd/<USER>lsstsw-py2/stack/Linux64/afw/12.1-33-g072fda8/python/lsst/afw/image/imageLib.py", line 89, in _swig_getattr      raise AttributeError("'%s' object has no attribute '%s'" % (class_type.__name__, name))  AttributeError: 'ExposureF' object has no attribute 'getSchema'  {code}    And similar. Should be a simple order-of-arguments fix.
Answer: 117.0

User story: "With the move of ctrl_events to legacy status the activemqcpp and ctrl_activemq packages is no longer in use,      Moving lsst/activemqpp to lsst-dm/legacy-activemqcpp  (this is a move and a change in etc/repos.yaml)    and    Moving lsst/ctrl_activemq to lsst-dm/legacy-ctrl_activemq (this is just a move)"
Answer: 9.0

User story: "meas_algorithms contains several (e.g. [#1|https://github.com/lsst/meas_algorithms/blob/0bf8251ccb5c79be6e181817359729fdb2425311/python/lsst/meas/algorithms/objectSizeStarSelector.py#L43], [#2|https://github.com/lsst/meas_algorithms/blob/d421edbfcf2fc993cbad9211c1498767479d069a/python/lsst/meas/algorithms/pcaPsfDeterminer.py#L35], there are more) explicit uses of {{lsst.afw.display.ds9}}. These should be replaced by calls to the generic (backend-independent) {{lsst.afw.display}} system."
Answer: 1129350.0

User story: 1. autopep8 should not add blank line before docstring:  {code}  $ cat /etc/debian_version   8.6  $ autopep8 . --in-place --recursive     --ignore E133,E226,E228,E251,N802,N803 --max-line-length 110  ...  $ git diff  ...  +   class _UnreadableConfigError(_ToolError):  +       def __init__(self, config):           _ToolError.__init__(self, "Can't access the config file: " + str(config))        -####################################################################################  +#   class CommandParser(object):  +       """       Parse commands and calls appropriate function from qservAdmin.       """          requiredOpts = {  -        "createDb" : [ # Db opts  +        "createDb": [  # Db opts  ...  $ pydocstyle  bash: pydocstyle: command not found  {code}  
Answer: 62428.0

User story: "testdata-cfht and testdata-decam are required for some obs package tests.    obs-master requires both. obs-cfht requires testdata-cfht. obs-decam requires testdata-decam.        "
Answer: 699514.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: Jointcal has two distortion models implemented: SimplePolyModel and ConstrainedPolyModel. Until now, I've been using the former because it was the default when I started using jointcal. The choice of model should be a config parameter (they share an API), which will require bringing the Constrained model up to match other changes in the C++ code.    The CFHT or DECam files in testdata_jointcal should work as test datasets: Constrained wants a full mosaic. To fully exercise it, it would be best to use the latest validation_data_hsc for multiple full-focal plane visits.    Note also this note from [~<USER> about getting the Constrained model to work:    {quote}The problem with ConstrainedPolyModel is that  at line 72, a test reads :    if ((chipp == _chipMap.end()) && visit == refVisit )    which should just be:  if (chipp == _chipMap.end())    because the initilization should be done anyway, possibly with a warning  if the chip is found on a different visit. Maybe the initializer should be  im.Pix2CommonTangentPlane() rather than im.Pix2TangentPlane()  but it is not mandatory.    For this model, the first fitting steps we are using read:  astromFit.Minimize("DistortionsVisit"); // those are *not* initialized at all  astromFit.Minimize("Positions");  astromFit.Minimize("DistortionsChip");  {quote}
Answer: 135446.0

User story: "At one time the ndarray tutorial was part of the Doxygen documentation, but that is no longer the case. It really should be served somewhere -- preferably linked from the docs that are already on github."
Answer: 26121.0

User story: [~<USER> points out that the lsst_py3 Jenkins build is currently failing and has been since [build #454|https://ci.lsst.codes/job/stack-os-matrix/label=centos-7,python=py3/21317/console] (regardless of the misleading red circles on Jenkins). Reported error is:    {code}  ======================================================================  FAIL: testLeaks (__main__.TestMemory)  !Check for memory leaks in the preceding tests  ----------------------------------------------------------------------  Traceback (most recent call last):    File "/home/jenkins-slave/workspace/stack-os-matrix/label/centos-7/python/py3/lsstsw/stack/Linux64/utils/12.1-5-g648ee80+2/python/lsst/utils/tests.py", line 161, in testLeaks      self.fail("Leaked %d block%s" % (nleak, plural))  AssertionError: Leaked 13 blocks    ----------------------------------------------------------------------  Ran 10 tests in 0.688s    FAILED (failures=1, skipped=2)       Number of calls to function has reached maxfev = 10.       Number of calls to function has reached maxfev = 10.       Number of calls to function has reached maxfev = 10.       Number of calls to function has reached maxfev = 10.  {code}
Answer: 5302.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: "Interface the forced photometry procedures developed in DM-9282 with Firefly as a server-side extension, on the PDAC v1 systems.    Develop a Jupyter notebook demonstrating how a forced photometry function can be added to the server as a callback when a point is selected in a deep coadded image. Demonstrate that a Firefly extension can be added to initiate the forced photometry call."
Answer: 59324.0

User story: "As pointed out in another review by [~<USER>, jointcal isn't following the {{#define LSST_BLAH}} standard for multiple inclusion prevention in its header files. Should fix this with a quick pass over the current headers. Might also be a good time to look over the existing headers and see if any can disappear or be merged elsewhere."
Answer: 117956.0

User story: "A work around exists which uses 1.20.0.    But conda-lsst has begun to fall behind the current stable {{conda-build}} version."
Answer: 703845.0

User story: "A work around exists which uses 4.1.    But {{conda-lsst}} has begun to fall behind the current stable Conda version."
Answer: 703853.0

User story: The Time Series viewer is about to support two missions WISE and LSST/SDSS. We need to be able add a generic table, specify the columns that matter (i.e. flux, time, url to get an image) as headers, then use this table for the viewer.    Todo:    * Read a table that has the flux,time, url metadata tags (we need to talk about the the metadata key names)  * Create a "unknown" data type  * make the UI work with this unknown data. In the mission specific area the UI should take the 3 columns as input.  * Note the the 3 columns can be specified in 2 ways, via metadata or change via UI input  
Answer: 19869.0

User story: "Do the following:  * make point selection work if extension is added before image * point selection is not always showing point * mask is not working when zoom is quickly changed before new mask is added * make table active row table extension * remotely turning on target match "
Answer: 6957.0

User story: "ImageHeader needs to re-organized to make it easy to understand the structure."
Answer: 1712376.0

User story: "Confused as to why I submit a build of lsst_distrib and yet xrootd is being pulled - or rather why qserv_distrib is being built (which is what pulls in xrootd).     "
Answer: 8.0

User story: "During training, the SGS classifier is provided with a list of the magnitude bins to use when learning how to separate stars from galaxies, ie. the classifier parameters are a function of magnitude bin. When classifying new data, the same list of bins has to be provided to the classifier because it forgets the original bin list used during training. Make the bin list used during training a classifier attribute so that it does not have to be provided when using a trained classifier. "
Answer: 1842361.0

User story: "Investigate the footprint of L1 Prompt processing in terms of files sizes for input and outputs."
Answer: 6.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Investigate mechanisms for gathering and storing meta-data header information for LSST images that can support the two basic scenarios: "Normal Observations" and "Catch-up mode"
Answer: 6.0

User story: "Add Data Management Policy page/doc to developer.io  documentation."
Answer: 15958.0

User story: "Identity and propose an initial Metadata (header) key-value pairs for LSST exposures  "
Answer: 57.0

User story: "Use Terraform to do a basic deployment for RabbitMQ.    1. Should be approximately three instances on Nebula.  2. Uses the Panopticon network.  3. Be capable of being part of a Shovel configuration."
Answer: 150086.0

User story: Logstash is failing to use a specific Cipher that is being used by filebeat.    {code}  [2017-02-16T17:19:59,480][ERROR][logstash.agent           ] Pipeline aborted due to error {:exception=>#<LogStash::ConfigurationError: Cipher `TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384` is not available>, :backtrace=>["/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-beats-3.1.12-java/lib/logstash/inputs/beats.rb:184:in `create_server'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-beats-3.1.12-java/lib/logstash/inputs/beats.rb:172:in `register'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:358:in `start_inputs'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:357:in `start_inputs'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:233:in `start_workers'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:188:in `run'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:302:in `start_pipeline'"]}  {code}
Answer: 4689.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: "Under the assumption that the RAW files will be created as {{Int18}} files, we need to mock the creation of {{Int18}} RAW files inside a {{Int32}} container. We need to test how well this mocked {{Int18}} files will compress."
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: "Update the data product diagram of top-level Pipelines on [~<USER>'s [Data Release Production Top-Level Overview page|https://confluence.lsstcorp.org/display/~<USER>Data+Release+Production+Top-Level+Overview] to reflect the new changes and follow the terminology in [LDM-151|https://ldm-151.lsst.io/v/draft/LDM-151.pdf]. "
Answer: 56297.0

User story: "TO reduce the confusion, the error input field should be removed"
Answer: 36033.0

User story: "Suggest to have a title for this portion to be more consistent with other portion in the window.  Title: Data Selection "
Answer: 1854035.0

User story: * label for column sorting information:      "Sorted by column: column name, ascending/descending"  * Period Finding:      "Find Period"  * Single image download dialog title change      "Fits" should be "FITS"  * Download Options dialog title change      "Image Download Option"  * Button "Find Periodigram"      "Calculate Periogigram"  * Button "Change Periodigram"      "Recalculate Periodogram"  * Upload dialog "search" button       "Upload"  * tab names change      "raw table"  = "Input Data"      "Phase folded" => "Phase Folded Data"  * Table name 'peaks_table' without '_'    * in the "Find Period" view, the folded light curve title should not have the units in parenthesis (that's appropriate for variables, not values). Also, there should be a space between the value and the unit.  * Labels 'time column' and 'flux column' changed to:  "Time column" and "Value column"  * In upload dialog:  ** "Raw Light Curves Table"-->"Time Series Table:". This needs a help link to describe the format and the current limitations. Basically, if it's a WISE file, you will see associated images. Otherwise, you will not.  ** In the "Mission" list, "wise"-->"WISE"
Answer: 20323.0

User story: "DMTN-024 is obsolete as soon as the pybind11 coding guidelines are in the dev-guide. Mark it as such."
Answer: 47061.0

User story: "The bug is FitsHeaderToJson which is a utility class for Projection's unit test.  It is under java/test.  It has nothing to do with java/src.    Bug description:    The objetArrayToJsonSring converts a 2-dimension or 1-dimension array to a Json string.  When it does the conversion, it shares a listObject and this object is cleared after each use.  How since this list is added to another 2-dimension list, the values added in the 2-dimension were accidentally reset to 0.0.    This bug was introduced when create unit test for Projection.  But this bug does not affect the Projection's unit test since the array values are not relevant to the Projection and were not used.    Analysis:  The FitsHeaderToJson was created to produce the testing files for Projection.  Since now there is util/ package under test.  This file should move to util/ directory."
Answer: 1423.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 current [clang-format docs|https://developer.lsst.io/tools/clang_format.html] link to setup instructions for vim and emacs, but not SublimeText. We should have a similar link on that page to how to integrate clang-format (including the best choice of Sublime package for it) with SublimeText."
Answer: 332643.0

User story: "Our final pybind11 coding conventions dictate that the wrapper library name should match the source code name. However, all of our existing pybind11 wrappers assume that the library name will always start with an underscore (whether the source file name does or not).    I will add a new flag {{addUnderscore=True}} to the {{pybind11}} function. New code should specify this flag as False. Old code will continue to work unchanged."
Answer: 1175.0

User story: "The ingress controller is insufficient.  It does not provide http->https redirects, and it has a fixed timeout of 30s, which is not enough for cookiecutter."
Answer: 17336.0

User story: "The ctrl_stats package can load information from dagman files into a database.  Integrate this functionality into ctrl_orca so we have it after a run completes."
Answer: 615953.0

User story: "There are a few assumptions that ctrl_stats makes about the format of the DAG it acts upon.  This package needs to be updated to not make those assumptions.  (The preJob, postJob, etc).    This will also require an update to require pegasus runs to add additional information into the dagman log files (specifically, the slot name), which it currently doesn't include.  This is (likely) an addition to the sites.xml.template file."
Answer: 61856.0

User story: "{{makeDocs}} needs some minor tweaks to make it work on Python 3."
Answer: 17312.0

User story: I'm seeing a test failure in meas_algorithms due to what looks like a failure of {{esutil}} compiled code to import the NumPy C API:  {code}  ======================================================================  ERROR: setUpClass (__main__.HtmIndexTestCase)  ----------------------------------------------------------------------  ImportError: numpy.core.multiarray failed to import    The above exception was the direct cause of the following exception:    Traceback (most recent call last):    File "tests/testHtmIndex.py", line 125, in setUpClass      cls.indexer = IndexerRegistry['HTM'](config)    File "/home/<USER>LSST/sw/build/meas_algorithms/python/lsst/meas/algorithms/indexerRegistry.py", line 44, in makeHtmIndexer      return HtmIndexer(depth=config.depth)    File "/home/<USER>LSST/sw/build/meas_algorithms/python/lsst/meas/algorithms/htmIndexer.py", line 34, in __init__      self.htm = esutil.htm.HTM(depth)    File "/home/<USER>LSST/sw/stack/Linux64/esutil/0.6.0+1/lib/python/esutil/htm/htmc.py", line 152, in __init__      this = _htmc.new_HTMC(depth)  SystemError: <built-in function new_HTMC> returned a result with an error set  {code}    This is Python 3.6 and Numpy 1.12, so it's likely I'm seeing the problem because I'm pushing to newer versions than anyone else.
Answer: 1336422.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: "While working on ImageHeaderTest, I found there are some methods can be utility methods.  To add those methods there, the FileLoader is no longer meaningful.  I rename it as UnitTestDataIO which contains all kind I/O including file, json file etc."
Answer: 1461.0

User story: "Implements RFC-292."
Answer: 187.0

User story: "The ctrl_pool framework builds a batch submission system around our existing tasks. It provides a series of arguments which can be used to control the resources allocated to each task. For example:    {code}  $ constructBias.py  --help    [...]    Batch submission options:    --queue QUEUE         Queue name    --job JOB             Job name    --nodes NODES         Number of nodes    --procs PROCS         Number of processors per node    --cores CORES         Number of cores (Slurm/SMP only)    --time TIME           Expected execution time per element (sec)  {code}    However, the wrapped task also has some similar sounding arguments. Following on from the above, we have:    {code}  *** Wrapped script:  usage: constructBias.py input [options]    [...]  optional arguments:  [...]    -j PROCESSES, --processes PROCESSES                          Number of processes to use    -t TIMEOUT, --timeout TIMEOUT                          Timeout for multiprocessing; maximum wall time (sec)  {code}    I can speculate about how these options interact (I guess that {{-j1 --procs 2}} means run two tasks at a time and give each access to one CPU core, while {{-j2 --procs 1}} means one task a time a time but let it use two cores), but I don't know, and I don't think I can unambiguously derive it from the documentation. Similar issues arise for timeouts, etc.    Please provide some instructions on how this is actually supposed to fit together so we can avoid confusion in the future (see e.g. DM-9415 for what happens when somebody encounters the current system for the first time).  "
Answer: 1822052.0

User story: "This ticket contains all the tickets which are for refactoring."
Answer: 1714126.0

User story: "The periodic builds of {{lsst_apps}}/etc. can end up competing with end-user submitted jobs for resources.  A simple solution is to shift these builds to run outside of regular business hours."
Answer: 283789.0

User story: "Using the prototype pybind11-based stack, process the HSC RC dataset. Work with [~<USER> to identify and resolve errors."
Answer: 13282.0

User story: "In DM-8796, it was found that the current implementation of calculating the ZOGY S_corr (corrected likelihood image) is underperforming. This appears to be a regression. Could also just be a detection issue (detection was changed to use pixel_stdev and positive only, but not changed for SZOGY)."
Answer: 1823047.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-8796, it was found, using simulated images, that the current test ZOGY implementation (both Fourier and image-based) has poorer performance than A&L when template is not noisy -- but only with measured PSFs -- leading to fewer detections, more false positives.    – TESTED - try with re-measuring science img PSF but not template PSF (no improvement)  "
Answer: 1823047.0

User story: "In DM-8796, it was found that:    ZOGY seems to have better performance than A&L(decorr) (better true-positive rate, similar rate false positives). Part of this may be the windowing issue (losing detections in convolution window around image edge) but I tried to prevent any transients from being placed near edges and still seeing this effect a little (~10% difference).  – Tested - could be misalignment of PSF. TRY: re-run with bigger matching radius (this is not the problem)  – Tested - could be issue with ALdecorr PSF. TRY: compare ALdecorr PSF with ZOGY psf (PSFs are slightly different)  – Tested - different PSFs are related to imperfect PSF matching. Tried other parameters for basis (e.g. make them somewhat smaller) which improved the AL result slightly.  – TODO: investigate basis function generation for A&L (and use comparison with ZOGY as a method for evaluation)."
Answer: 1823051.0

User story: "show_xyplot in Firefly python API is outdated. Implement it using chart actions.    To test, put the attached notebook into firefly/src/firefly/test/python directory and run it."
Answer: 2471.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: When a command-line task runs, it [writes the versions of packages currently set up to the repository|https://github.com/lsst/pipe_base/blob/54f122d8ff9696ff2b1de8f72d33eff08773e0a3/python/lsst/pipe/base/cmdLineTask.py#L285]. We're then [unable to run the same task again without matching versions|https://github.com/lsst/pipe_base/blob/54f122d8ff9696ff2b1de8f72d33eff08773e0a3/python/lsst/pipe/base/cmdLineTask.py#L614]. This helps with reproducibility.    However, when I repeatedly try to run the same task with exactly the same task with exactly the same packages set up, this version checking fails intermittently. The task exits, complaining:    {code}  Traceback (most recent call last):    File "/Users/jds/Projects/Astronomy/LSST/src/pipe_drivers/bin/constructBias.py", line 4, in <module>      BiasTask.parseAndSubmit()    File "/Users/jds/Projects/Astronomy/LSST/stack/DarwinX86/ctrl_pool/12.1-7-gb57f33e/python/lsst/ctrl/pool/parallel.py", line 422, in parseAndSubmit      if not cls.RunnerClass(cls, batchArgs.parent).precall(batchArgs.parent):  # Write config, schema    File "/Users/jds/Projects/Astronomy/LSST/stack/DarwinX86/pipe_base/12.1-5-g06c326c+6/python/lsst/pipe/base/cmdLineTask.py", line 303, in precall      self._precallImpl(task, parsedCmd)    File "/Users/jds/Projects/Astronomy/LSST/stack/DarwinX86/pipe_base/12.1-5-g06c326c+6/python/lsst/pipe/base/cmdLineTask.py", line 285, in _precallImpl      task.writePackageVersions(parsedCmd.butler, clobber=parsedCmd.clobberVersions)    File "/Users/jds/Projects/Astronomy/LSST/stack/DarwinX86/pipe_base/12.1-5-g06c326c+6/python/lsst/pipe/base/cmdLineTask.py", line 618, in writePackageVersions      "); consider using --clobber-versions or --no-versions")  lsst.pipe.base.task.TaskError: Version mismatch (meas_algorithms: 12.1-17-g13cfda1+6 with boost=1.60.lsst1+1 eigen=3.2.5.lsst2 vs 12.1-17-g13cfda1+6 with eigen=3.2.5.lsst2 boost=1.60.lsst1+1; coadd_utils: 12.1-1-g5961e7a+70 with boost=1.60.lsst1+1 eigen=3.2.5.lsst2 vs 12.1-1-g5961e7a+70 with eigen=3.2.5.lsst2 boost=1.60.lsst1+1; afw: 12.1-31-gb5bd9ab+1 with boost=1.60.lsst1+1 eigen=3.2.5.lsst2 vs 12.1-31-gb5bd9ab+1 with eigen=3.2.5.lsst2 boost=1.60.lsst1+1); consider using --clobber-versions or --no-versions  {code}    Note that the versions *are* the same, but are being reported in a different order ({{12.1-17-g13cfda1+6 with boost=1.60.lsst1+1 eigen=3.2.5.lsst2}} as compared to {{12.1-17-g13cfda1+6 with eigen=3.2.5.lsst2 boost=1.60.lsst1+1}}).    Please fix this so that version checking works reliably.
Answer: 4130.0

User story: "With the availability of PS1 and Gaia catalogs in the LSST format, we can remove our dependence on astrometry.net.  This involves changing configuration files to use the PS1 catalog in LSST format and disable the use of astrometry.net."
Answer: 50089.0

User story: "All jenkins jobs that use {{lsstsw}} consume couscous amounts of disk space and require periodic manual workspace purging.  This should either be moved to a jenkins plugin or an automated script."
Answer: 185765.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 cannot find any documents on what to use our current pex::exceptions for. Many of them are similar to the [std::c++ exceptions|http://en.cppreference.com/w/cpp/error/exception], but even having links to the "matching" C++ doc for each exception would be a start. Some of our exceptions have no {{std::}} counterpart. Either way, it's often unclear at the C++ layer what one should raise. Even a single sentence each would be a good start.    If this documentation does exist, I can't readily find it in our doxygen or source code.    Adding a large watcher list, since when I brought this up on slack, [~<USER> said    bq. ...first someone has to actually decide what those uses are, and the list of people who feel empowered to decide that is very small.
Answer: 617791.0

User story: "An error is occurring in testTimeFuncs.py:    {noformat}      Unable to execute query: CREATE DATABASE test_14871027723 - * Access denied for user 'srp'@'%' to database 'test_14871027723' {0}  lsst::pex::exceptions::RuntimeError: 'Unable to execute query: CREATE DATABASE test_14871027723 - * Access denied for user 'srp'@'%' to database 'test_14871027723  {noformat}    The error is occurring because users don't have database creation permissions to create   {noformat}test_%{noformat} databases.    This only occurs on machines in the ncsa.illinois.edu domain, because the test is skipped if not run on that domain."
Answer: 1046.0

User story: "In Python 2, we can use {{Exception.message}} to retrieve the message associated with a (wrapped, C++) exception. In Python 3 this no longer works. This breaks the obs_cfht [tests|https://github.com/lsst/obs_cfht/blob/master/tests/testButler.py#L114]; please fix them.    This was already fixed on the pybind11 port as part of DM-9276."
Answer: 235.0

User story: "Update lsst_dm_stack_demo for pybind11 and fix anything needed in the dependent packages"
Answer: 157.0

User story: "pex_exceptions contains a tutorial in Doxygen that includes Swig-specific instructions for making sure C++ exceptions are propagated correctly to C++.  This should be updated."
Answer: 19953.0

User story: "Add osx 10.11 and 10.12 (elcap / sierra) to the jenkins {{stack-os-matrix}} job."
Answer: 321.0

User story: "Our logging system needs a way to securely ship logs. Since this is a key feature that Elastic.co uses to monetize ELK through the X-Pack we need to find a different solution.    RabbitMQ can solve to potential problems. First, it can solve shipping our logs across different infrastructures. Second, it can handle spikes of logging messages.    This is common practice in ELK logging systems. See:    https://www.elastic.co/guide/en/logstash/5.2/deploying-and-scaling.html#deploying-message-queueing"
Answer: 152968.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: "Do the following related to the remote API    * Fix the point selection - should turn on automatically  * Make sure the simple image meta data table uploads work   * mouse click return table information to python client  * -some issues with mask not always overlaying correctly when sent from awfDisplay - need to reproduce- moved to DM-9490   * -Fix compass when image is smaller than screen than window- - moved to DM-9430    "
Answer: 3007.0

User story: "{{gfortran}} is required to build {{oorb}} on osx, which is a dep of {{lsst_sims}}.  Brew has removed the {{gfortran}} package and the front end is now provided by the brew {{gcc}} package/bottle.    This is a sims deps but I believe gfortran is technically also a pipelines dep."
Answer: 1866961.0

User story: "[HSC-1398|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1398] allows multiple filters to be used in the mosaic solution.  This is helpful because there are multiple r-band and i-band filters, and it's helpful to combine them.    I'll also update the {{MosaicTask}} to allow use of the new LSST format reference catalogs."
Answer: 3041.0

User story: "Re-work the SUIT demo code at https://github.com/stargaser/forced_phot into something more idiomatic from a pipelines point of view. This should include aggregating tables using {{afwTable}}, rather than dumping to disk and reloading using AstroPy. Discuss the results with [~<USER>, 2017-02-20."
Answer: 20517.0

User story: "https://lsst-web.ncsa.illinois.edu/doxygen/x_masterDoxyDoc/log.html has some useful documentation on using the {{lsst::log}} logging framework.    https://developer.lsst.io/coding/logging.html#logging also has some useful documentation on using the same.    Ultimately, these documents should be unified to provide one complete reference. As a stop-gap measure, they should refer to each other so that developers are getting the full picture."
Answer: 24360.0

User story: "Collect or estimate sizing information of L2 data products of DPDD. "
Answer: 21551.0

User story: "While converting to use lsst::log in DM-8547, I started cleaning up all of the dead read/write code for StarLists. Since we're using LSST catalogs and refcats now, we shouldn't need it for anything, and we'll eventually be able to interrogate those lists from python (once we deal with DM-4043), if such functionality is desired.    I'm filing this as a separate ticket so it doesn't clutter DM-8547 with a bunch of deleted lines."
Answer: 4525.0

User story: "Since RFC-114, possibly earlier, it seems that cmake is required to build the Stack on macOS. This is missing from https://pipelines.lsst.io/install/newinstall.html#mac-os-x"
Answer: 4165.0

User story: "Per RFC-291, libcurl (headers and link lib), soon to be required for unit tests within the qserv package, is to be -considered a platform prereq- provided as an eups package."
Answer: 72383.0