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: "Draft Operations planning w.b.s.  Create additional activity Diagrams,  Draft DPPD Operations processing talk."
Answer: 3.0

User story: "* Set up new lsst-dev7 as CentOS 7 server  * Continuing to set up IPMI on new test servers (working with Dell on issue with iDRAC license upgrade)"
Answer: 2108.0

User story: "Original URL is https://confluence.lsstcorp.org/display/DM/How+to+document+a+Task    This page may be most appropriate for the LSST Science Pipelines documentation."
Answer: 2074633.0

User story: "Port https://confluence.lsstcorp.org/display/DM/Orchestration"
Answer: 614519.0

User story: "Following DM-5013, it was requested to provide introductory documentation on EUPS for LSST developers."
Answer: 81339.0

User story: "I see this as being an overview of what methods DM uses to communicate, and what method should be chosen for any circumstance.    See the page https://confluence.lsstcorp.org/display/DM/Communication+and+Links in the DM Confluence space"
Answer: 2476482.0

User story: "There is a significant design issue when refactoring a piece of this importance.  Carry out a design study to implement in DM-4692."
Answer: 2.0

User story: "-ISR needs the following correction algorithms: fringe, crosstalk, overscan (with discontinuity), and non-linearity.  Several of these are implemented in HSC and have been ported, but may need some work.-    As noted below this will now only be the crosstalk portion of the ISR upgrades."
Answer: 834766.0

User story: "The stack can do many of the corrections needed.  Assess the status of the current algorithms and identify any deficiencies."
Answer: 10.0

User story: "Create a list of ISR requirements and have it RFCd."
Answer: 1.0

User story: "This is to assess the priority of a major approximation and interpolation refactor."
Answer: 1.0

User story: "We need a simple way to hold index files that will be easy to use and simple to set up."
Answer: 2.0

User story: "Prevent force-push to master for lsst repos using protective branches. See RFC-121 for full details"
Answer: 694173.0

User story: "{{SingleFrameVariancePlugin}} takes the median variance of the entire image, rather than within an aperture around the source of interest.  A {{Footprint}} is constructed with the aperture, but it is unused.    This means that this plugin takes an excessive amount of run time (255/400 sec in a recent run of processCcd on HSC {{visit=1248 ccd=49}} with DM-4692)."
Answer: 138.0

User story: "[~<USER> is looking for nebula images newer than {{w_2015_45}} (from the exploratory work in DM-4326) and [~<USER> is interested in images with a complete {{lsst_distrib}} install for orchestration testing.  New builds should incorporate the pending change to {{newinstall.sh}} that converts from {{anaconda}} to {{miniconda}}."
Answer: 11690.0

User story: "{{lsstsw}} needs to be able to use python 3.    It may be that DM-3129 leads to this by default."
Answer: 171393.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: "{{newinstall.sh}} needs to be able to generate a system configured to use Python 3. This may require some special conda environment selection and other subtleties."
Answer: 171399.0

User story: It would be useful to provide a "preflight" sanity check script for end users that verifies (the extent that is reasonably possible) that their system has all of the necessary stack prerequisites.
Answer: 1572758.0

User story: "The Confluence page mentions an Emacs configuration repo for use by lsst devs: https://confluence.lsstcorp.org/display/LDMDG/Emacs+Support+for+LSST+Development    The repo link, git://git.lsstcorp.org/LSST/DMS/devenv/build.git, does not resolve.    Does this repo still exist somewhere? Is it relevant? Should be document/suggest Emacs configuration in some other way?"
Answer: 1762950.0

User story: * Document spatial indexing  * Document database ingest  * Refresh "Stored Procedures and Function" in LDM-135
Answer: 960578.0

User story: "Document secondary index"
Answer: 78525.0

User story: "* Document webserv/imgserv/metaserv/dbserv"
Answer: 301941.0

User story: "* Improve butler documentation"
Answer: 168491.0

User story: "* Document db and table metadata  * Document async queries  * Document data loader"
Answer: 78449.0

User story: "* Refresh shared scans design documentation (in LDM-135)  * Add info about query cancellation (in LDM-135)"
Answer: 126797.0

User story: "* Document Data Distribution  * Create structure for DAX doc  * Bring over Provenance documentation from prov_prototype  * Update LDM-135 to reflect the updates to the storage/IO model  * Update LDM-152  * Fix LDM-135: 3.3.6.4 and 3.3.6.5 should be 3rd level, so 3.3.7 and 3.3.8  "
Answer: 960586.0

User story: "It would be very helpful to have an elliptical Guassian PSF available. One place I would use it is in {{InsertGaussianPsfTask}}, to insert an elliptical Gaussian PSF model at the beginning of each iteration of detect/measure/fit PSF in CharacterizeImageTask.    Two things to consider:  - Does it make sense to modify {{lsst::meas::algorithms::SingleGaussianPsf}} to be elliptical (e.g. add another constructor), rather than adding a new class?  - Do we want an elliptical double Gaussian PSF? I have no immediate need, but it does seem a logical thing to have. Again, if one is wanted, would it make more sense to provide a new class or expand {{DoubleGaussianPsf}}?"
Answer: 1783404.0

User story: "We need to switch existing code to a more permissive license (MIT or Apache) as we  want to accept patches from the community only under more permissive licenses.      We should develop a policy explaining to people who’d like to contribute exactly what  to do and what are boundary conditions.     "
Answer: 2305610.0

User story: "Working with Ron to create a RFP for the acquisition of network equipment for the summit and base. "
Answer: 71909.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: "[SQuaRE suggests|http://developer.lsst.io/en/latest/tools/git_lfs.html#creating-a-new-git-lfs-enabled-repository] that Git LFS repositories should provide both {{.gitconfig}} and {{.lfsconfig}} files with identical contents. Please make it so."
Answer: 19.0

User story: "I split DM-4497 into two part so I can demonstrate code reviews. This part has paging controller & layout cleaned up.  This tickets is messy because it involves a lot of refactoring of the reducers.  Therefore I am going to end it and move the rest of the UI work to DM-5088."
Answer: 7107.0

User story: "As discussion on DM-4692 and in various HipChat rooms, it's too easy for camera-level config override files to contain many options that don't actually change anything, because they simply override the defaults with the same default values.  To aid in tracking these down and removing them, we should have an option in which {{CmdLineTask}} s (delegating to {{pex_config}}) refuse or warn about overrides that have no effect.    We should probably not make failing on do-nothing overrides the default behavior, but we could consider making warning the default behavior.  Mostly, I think it's important just to be able to find such options when wanted."
Answer: 2134562.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: "Finished out all necessary fields in the first cut at the WBS.  Split project into work phases,   Began drilling down into the milestones for each phase, with accurate estimation the goal.  Provided miscellaneous diagrams to capture expected functionality for various state transitions throughout the system."
Answer: 57129.0

User story: "A test plan draft was written and some short meetings were held regarding the use of the WAN Emulator. The manuals for the Apposite Netropy 40G emulator were retrieved and read. The test plan draft for three test projects is attached."
Answer: 72278.0

User story: The upgrade to pyfits 3.4 appears to have broken the defect list construction, which is part of the obs_subaru build:  {code}  bin.src/genDefectFits.py:56: PyfitsDeprecationWarning: The new_table function is deprecated as of version 3.3 and may be removed in a future version.            Use :meth:`BinTableHDU.from_columns` for new BINARY tables or :meth:`TableHDU.from_columns` for new ASCII tables instead.    table = pyfits.new_table(cols)  Traceback (most recent call last):    File "bin.src/genDefectFits.py", line 86, in <module>      genDefectFits(args.cameraName, args.defectsFile, args.targetDir)    File "bin.src/genDefectFits.py", line 58, in genDefectFits      table.header.update('NAME', ccd)    File "/tigress/pprice/lsstsw/stack/Linux64/pyfits/3.4.0/lib/python/pyfits-3.4-py2.7-linux-x86_64.egg/pyfits/header.py", line 1017, in update      'value, and comment string.' % idx)  ValueError: Header update sequence item #0 is invalid; the item must either be a 2-tuple containing a keyword and value, or a 3-tuple containing a keyword, value, and comment string.  scons: *** [hsc/defects/2013-01-31/defects.dat-fits] Error 1  scons: building terminated because of errors.  {code}    When I hack the environment to use pyfits 3.3, it works fine.
Answer: 831.0

User story: "When the test fails and the output directory is written but not populated, subsequent test executions fail every time until the output directory is deleted or REUSE_DATAREPO is set to False. This is misleading for users who don't know about this hidden feature.    Furthermore, the REUSE_DATAREPO=False feature is broken; setting it False causes NameError: global name 'DATAREPO_ROOT' is not defined.    It would be better if the test cleaned up after itself (deleted all outputs) every time. If it's really important to reuse the outputs then the dir should be cleaned up in the case of failed writes and/or corruption.    "
Answer: 53002.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: validate_drp will test more of our code if it uses default config parameters wherever possible. To that effect I would like to ask you to eliminate all config overrides that are not essential and document the reasons for the remaining overrides.    For DECam there are no overrides that are different than the defaults, so the file can simply be emptied (for now).    For CFHT there are many overrides that are different, and an important question is whether the overrides in this package are better for CFHT data than the overrides in obs_cfht; if so, please move them to obs_cfht.    As a heads up: the default star selector is changing from "secondMoment" to "objectSize" in DM-4692 and I hope to allow that in validate_drp, since it works better and is better supported.    Sorry for the incorrect component, but validate_drp is not yet a supported component in JIRA (see DM-5004)
Answer: 29976.0

User story: "Please add the following Components to JIRA:    - validate_drp  - validation_data_cfht  - validation_data_decam  "
Answer: 410.0

User story: Attempting to build MariaDB 10.1.10 (current LSST master) fails on my system as follows:    {code}  [2016-02-02T21:53:56.215123Z] [ 86%] Building CXX object storage/spider/CMakeFiles/spider.dir/spd_copy_tables.cc.o  [2016-02-02T21:53:56.418704Z] [ 86%] Building CXX object storage/connect/CMakeFiles/connect.dir/json.cpp.o  [2016-02-02T21:53:56.542279Z] /Users/jds/Projects/Astronomy/LSST/lsstsw/build/mariadb/storage/connect/json.cpp:597:7: error: assigning to 'PSZ' (aka 'char *') from incompatible type 'const char *'  [2016-02-02T21:53:56.542351Z]                 str = (err) ? NULL : "Ok";  [2016-02-02T21:53:56.542392Z]                     ^ ~~~~~~~~~~~~~~~~~~~  [2016-02-02T21:53:56.551663Z] 1 error generated.  [2016-02-02T21:53:56.554608Z] make[2]: *** [storage/connect/CMakeFiles/connect.dir/json.cpp.o] Error 1  [2016-02-02T21:53:56.554664Z] make[2]: *** Waiting for unfinished jobs....  {code}    My system is:    {code}  [jds@magpie ~]$ sw_vers && c++ --version  ProductName: Mac OS X  ProductVersion: 10.11.3  BuildVersion: 15D21  Apple LLVM version 7.0.2 (clang-700.1.81)  Target: x86_64-apple-darwin15.3.0  Thread model: posix  {code}    This is upstream [MDEV-9322|https://mariadb.atlassian.net/browse/MDEV-9322]; it's fixed in 10.1.11 or can be trivially patched.
Answer: 2670.0

User story: "if ci_hsc fails for any reason, (or is cancelled) it must start from the beginning of processing again. This is because of the use of functools.partial to generate dynamic function. These differ enough in their byte code that scons thinks each build has a new function definition passed to the env.command function. Using lambda would suffer from the same problem. This ticket should change how the function signature is calculated such that scons can be resumed.    This work does not prevent this from being used as a ci tool, as the .scons directory can be deleted which will force the whole SConstruct file to run again."
Answer: 11109.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: "Design plans for reimplementation of diffim task - separate point source measurement from dipole measurement.    Again, not sure if this belongs in this epic or the refactor diffim epic."
Answer: 2127875.0

User story: "Add robustness – add functionality to test for # of dipoles and abort dipole fitting if above config threshold. Also flag saturated stars/ bad pixels prior to fitting.      Coordinate with DM-3515. Not sure if this one belongs in this epic or that one."
Answer: 2078113.0

User story: "Implement new dipole fitting algorithm as SimpleAlgorithm -- implement measure, fail methods, define flags"
Answer: 124141.0

User story: "Benchmark dipole measurement (dipole fitting), compare speed directly to psf-fit (and/or galaxy measurement) task. Runtime should be comparable (~factor of two?) - if not understand why. Evaluate new implementation vs. current impl. Accuracy?"
Answer: 44752.0

User story: "validate_drp does not work on El Capitan due to SIP (System Integrity Protection) stripping DYLD_LIBRARY_PATH from shell scripts. The simple fix is to add  {code}  export DYLD_LIBRARY_PATH=${LSST_LIBRARY_PATH}  {code}  near the top of the scripts."
Answer: 1392.0

User story: "Extend the [API|https://confluence.lsstcorp.org/display/DM/AP] to pass security tokens."
Answer: 1224876.0

User story: "Outline a design of the authentication system (based on components provided by NCSA) that will support single sign-on. Current thinking involves two tokens: application token to certify the app is legitimate and to determine which users it can represent, and user token"
Answer: 1224881.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: We need to periodically review the status of the third party software packages that Firefly depends on. Making a plan to do upgrade if needed.   package.json lists out the dependencies Firefly has on the third party software. The attached file was last modified 2016-02-09.    package.json_version lists the current version of the third party packages, major changes were indicated by (M). The attached file was created on 2016-02-29.     bq.      "babel"     : "5.8.34",                           6.5.2 (M)      "history"   : "1.17.0",                           2.0.0 (M)      "icepick"   : "0.2.0",                            1.1.0 (M)                "react-highcharts": "5.0.6",                      7.0.0 (M)      "react-redux": "3.1.2",                           4.4.0 (M)      "react-split-pane": "0.1.22",                     2.0.1 (M)      "redux-thunk": "0.1.0",                           1.0.3 (M)      "redux-logger": "1.0.9",                          2.6.1 (M)      "validator" : "4.5.0",                            5.1.0 (M)      "chai": "^2.3.0",                                 3.5.0 (M)      "esprima-fb": "^14001.1.0-dev-harmony-fb",        15001.1001.0-dev-harmony-fb (M)      "babel-eslint"      : "^4.1.3",                   5.0.0 (M)      "babel-loader"      : "^5.3.2",                   6.2.4 (M)      "babel-plugin-react-transform": "^1.1.0",         2.0.0 (M)      "babel-runtime"     : "^5.8.20",                  6.6.0 (M)      "eslint"            : "^1.10.3",                  2.2.0 (M)      "eslint-config-airbnb": "0.1.0",                  6.0.2 (M) works with eslint 2.2.0      "eslint-plugin-react": "^3.5.1",                  4.1.0 (M)  works with eslint 2.2.0      "extract-text-webpack-plugin": "^0.8.0",          1.0.1 (M)      "html-webpack-plugin": "^1.6.1",                  2.9.0 (M)      "karma-sinon-chai": "^0.3.0",                     1.2.0 (M)      "redux-devtools"    : "^2.1.2",                   3.3.1 (M)      "webpack": "^1.8.2"                               1.12.14, 2.1.0 beta4 (M)          
Answer: 40449.0

User story: "Generate a description document of work flow that a scientist would go through in order to do time series research, visualize the light curve."
Answer: 40370.0

User story: Prepare for JTM session with a working title of “How Authentication/Authorization technology can be used to implement and enforce data access rights and operational processes for LSST".  Prepare a final title and agenda for the session. Tuesday from 3:30pm - 5:00pm.
Answer: 43124.0

User story: "Automate running the lsst stack demo on conda packages before they are published to a public conda channel."
Answer: 1252771.0

User story: "Create a jenkins job to build and publish a complete channel of conda packages.  It should be possible for this job to be scheduled to automatically build packages from the latest master bxxxx build."
Answer: 1252779.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: Build a "production" conda channel server based on the existing prototype work: https://github.com/lsst-sqre/sandbox-pkg    In particular, a backup mechanism is required.
Answer: 174481.0

User story: We need a programmatic means of determining the latest build id for that "master" branch that encompasses all top level products we want to product conda packages of.  Ideally, this would be the latest "master" build that completed successfully but that may be non-trivial to determine with the current CI sestup.
Answer: 1252785.0

User story: "Where ever possible, missing dep information and patches from conda-lsst should be upstreamed.  The patches have already been observed to cause builds to fail due to upstream changes."
Answer: 54905.0

User story: Check to see which, if any, eups package for "third party" software can be replaced with existing conda packages.
Answer: 1252789.0

User story: "The usage of LFS is growing across DM's repos.  The git-lfs client should be added to the conda-lsst build env and support for dealing with the helper cache added to conda-lsst."
Answer: 174484.0

User story: In order to ensure that "historical" builds can be reproduced, {{repos.yaml}} support should be added to {{conda-lsst}}.  Perhaps automatically fetching the lastest version from the github raw blob url.
Answer: 1019538.0

User story: Due to concerns about conda not correctly comparing some lsst product versions, conda channels should only publish a single version of each package (which at this point, should probably all be built together).  We need some simple plumbing to allow "atomic" channel updates.  Such as putting new builds into a new directory and changing a symlink
Answer: 1252796.0

User story: "At present, conda-lsst completely masks out the build of {{afwdata}}.  This prevents many of the unit tests from running when building a package.  At a minimum, we should make an afwdata conda package available for end users to install for boot strapping a development env.  Ideally, we could make it a build time dep only for the eups products which need it for unit tests."
Answer: 1252806.0

User story: "At least the conda-build package has a version that will break conda-lsst.  In the interest of making the package build as reproducible as is reasonably possible, I'd like to add a conda package spec or environment file to pin the versions of critical packages."
Answer: 1252809.0

User story: "* allow sudo to be run by the 'conda' user (easiset to allow any user)  * modify as needed to be used as a dynamically launched jenkins build slave  * attempt to trim down the installed set of system packages that duplicate deps fulfilled by conda packages"
Answer: 1252815.0

User story: "It would be convenient for end users to have the git-lfs client available as a conda package. There does not appear to be an existing recipe. "
Answer: 41571.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 technologies and architectures to use with panopticon, our logging system. Perform preliminary research and evaluations into ELK (Elasticsearch, Logstash and Kibana), extensions to ELK and other alternatives."
Answer: 64146.0

User story: "When lsst switched to using SafeClipAssembleCoaddTask, the camera mapper for hsc was not updated accordingly. This causes ci_hsc to fail when it attempts to verify the config class type for the deep_coadd. Camera mapper should be updated accordingly"
Answer: 2474.0

User story: "In order to determine the cause of the output differences between single frame processing runs of the same data using the LSST vs. HSC stacks (see figures attached to DM-4730), a detailed look at some of the image characterization steps is required.  This ticket involves a detailed investigation of the initial PSF estimation including:  {panel: title=LSST vs. HSC stack runs:}  - a comparison of the initial object detection (will likely involve looking at the initial background estimate as well as the specific assignment of footprints)  - which objects are selected as PSF candidates  - the initial PSF model (as a function of position)  {panel}"
Answer: 124909.0

User story: "The {{ci_hsc}} package executes a number of command line tasks directly from SCons based on {{Command}} directives in a {{SConstruct}} file. On an OSX 10.11 system with SIP enabled, there are two distinct problems which prevent the necessary environment being propagated to the tasks:  * -The {{scons}} executable starts with a {{#!/usr/bin/env python}}. Running through {{/usr/bin/env}} strips {{DYLD_LIBRARY_PATH}} from the environment.- (duplicates DM-4954)  * SCons executes command using the [{{sh}} shell on posix systems|https://bitbucket.org/scons/scons/src/09e1f0326b7678d1248dab88b28b456fd7d6fb54/src/engine/SCons/Platform/posix.py?at=default&fileviewer=file-view-default#posix.py-105]. By default, that means {{/bin/sh}} on a Mac, which, again, will strip {{DYLD_LIBRARY_PATH}}.    Please make it possible to run {{ci_hsc}} on such a system."
Answer: 18481.0

User story: "This ticket will only do the region saving.    The scope has change somewhat since region saving will talk a little longer and making the png requires some server side work. DM-6139"
Answer: 167082.0

User story: "Generate JSON output from validate_drp for inclusion in a test harness.    Generate a file that summarizes the key metrics calculated by `validate_drp`.      Develop naming conventions that will make it easy to plug into the eventual harness being developed as part of DM-2050."
Answer: 24474.0

User story: "Adapt the SRD-based specifications for calculation of astrometric performance.  Follow the examples for AM1, AM2 as presented at    https://confluence.lsstcorp.org/pages/viewpage.action?pageId=41785659    and detailed in DM-3057, DM-3064"
Answer: 20414.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 final version of {{pyfits}} has just been released. This ticket covers updating to that version. This will be helpful in determining whether the migration to {{astropy.io.fits}} will be straightforward or complicated."
Answer: 5605.0

User story: "Because the scons file in ci_hsc mixes lsst code with build code, simply typing scons to build the package on a system with sip will fail. The work around is to not let scons find the python version, but to specify it manually. The workaround is trivial, anyone on os x with sip can simply type:  {code:bash}  `which python` `which scons`  {code}  on the command line to build the package"
Answer: 10502.0

User story: "On a Mac with OSX 10.11 and SIP enabled, every time I run {{scons}} on an LSST package I get the message:    {code}  $ scons  scons: Reading SConscript files ...  Could not import lsstcppimport; please ensure the base package has been built (not just setup).    EUPS integration: enabled  [etc]  {code}    It's not fatal, and is not indicative of a fundamental problem. But it is alarming, especially for new users who will assume this means something has broken when they first hit this message. (I did.)"
Answer: 793404.0

User story: Command-line argument parsing of data IDs for {{CmdLineTask}} s is currently defined at the class level, which means that we cannot make data ID definitions dependent on task configuration.  That in turn requires custom {{processCcd}} scripts for cameras that start processing at a level other than "raw" (SDSS, DECam with community pipeline ISR, possibly CFHT).    Instead, we should let {{CmdLineTask}} *instances* setup command-line parsing; after a {{CmdLineTask}} is constructed, it will have access to its final configuration tree, and can better choose how to parse its ID arguments.    I've assigned this to Process Middleware for now, since that's where it lives in the codebase, but it may make more sense to give this to [~<USER>, [~price], or [~<USER>, just because we've already got enough familiarity with the code in question that we could do it quickly.  I'll leave that up to [~<USER>, [~<USER>, and [~<USER> to decide.
Answer: 58109.0

User story: "An **authenticated** user should be able to provision (and likewise, delete) an entire published software documentation project via ltd-keeper’s RESTful API. This includes creating an S3 bucket in SQuaRE’s AWS account and setting up Route 53 DNS. The user should also be able to delete a project. This ticket will add AWS affordances to ltd-keeper. DM-4950 will be responsible for hooking this functionality into the methods that service API calls."
Answer: 30594.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "This ticket is to create an MVP of the ltd-keeper web app (RESTful API) that tracks versions of LSST the Docs’ published software documentation. Specifically this ticket will implement the RESTful endpoints needed by ltd-mason. See [SQR-006|http://sqr-006.lsst.io] for design information.    [SQR-006|http://sqr-006.lsst.io] will be updated in this ticket as the design is clarified in implementation."
Answer: 57969.0

User story: "While working on DM-4629 (overhauling {{ProcessCcdTask}}) [~<USER> stumbled over {{TransformTask}}, which he wasn't previously familiar with. Existing Doxygen documentation covers what this task does, but lacks context as to why it's useful. Please provide a high-level overview of what the intention is here."
Answer: 1234956.0

User story: "Upon running buildbot on branch DM-4692, which built successfully on Jenkins, I have twice received failures in afw. One of the cases is:    {code}  :::::  [2016-01-28T23:38:27.571221Z] Failed test output:  :::::  [2016-01-28T23:38:27.577021Z] tests/convolve.py  :::::  [2016-01-28T23:38:27.577036Z]   :::::  [2016-01-28T23:38:27.577062Z] OpenBLAS: pthread_creat error in blas_thread_init function. Error code:11  :::::  [2016-01-28T23:38:27.577254Z] The following tests failed:  :::::  [2016-01-28T23:38:27.579376Z] /nfs/home/lsstsw/build/afw/tests/.tests/convolve.py.failed  :::::  [2016-01-28T23:38:27.579479Z] 1 tests failed  :::::  [2016-01-28T23:38:27.580101Z] scons: *** [checkTestStatus] Error 1  :::::  [2016-01-28T23:38:27.584614Z] scons: building terminated because of errors.  {code}    The other failure occurred in a different test but still with pthread_creat involved. [~<USER> believes that this is related to a similar problem that he saw on a UW machine involving process limits being exceeded. He can describe the issue better than I can.    The full output is available at http://lsst-buildx.ncsa.illinois.edu:8010/builders/DM_stack/builds/9320/steps/shell/logs/stdio. "
Answer: 16861.0

User story: "A probable bug in WCSLIB is causing {{wcscopy}} to create copies of {{Wcs}} objects which are not the same as the object that was copied. In some cases when this object is passed to {{wcsset}} it fails, as the {{Wcs}} object contains impossible values.    This has behaviour is non-deterministic (failure is only seen occasionally). The error has only been observed on OSX, but we do not believe it to be operating system dependent (except insofar as different systems and compilers produce different memory layouts and hence different failure modes). This reliably causes {{ci_hsc}} to fail when running on a Mac.    Relevant lines in {{afw}} are {{image/Wcs.cc:140}} and the {{Wcs}} copy constructor in {{image/Wcs.cc:468}}    Additionally a bug has been found in {{image/Wcs.cc}} on line 485 where the flag property should be set on an element, and not on the object itself, ie {{_wcsInfo[i]->flag = -1;}}."
Answer: 6986.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "This ticket is to capture preliminary design work we are doing for storage of QA system information, which we are working with the Database team on.     As well as prior experience, Jacek has made us aware of the sdqa tables in the schema:    https://lsst-web.ncsa.illinois.edu/schema/index.php?sVer=baseline    and also plan on mining pipeQA for quantities of interest.     Once we have a draft, there will be an RFD for soliciting further input. "
Answer: 171396.0

User story: "see the conversation on c.l.o. at [https://community.lsst.org/t/how-does-the-butler-support-compression/502].    The summary is, when the mapper returns e.g. a non compressed file name e.g. {{foo.fits}}, that file may be compressed and the filename may reflect this e.g. in reality it might be named {{foo.fits.gz}}. On a posix system some component of the butler framework should discover this and transform the filename to the correct filename and pass that to the deserializer.    TBD if the list of allowed extensions is hard coded someplace (in a mapper subclass?) or specified another way, perhaps by the policy (could be for dataset type or globally)."
Answer: 442234.0

User story: "First iteration of worker scheduler uses a skeleton of the memory manager that doesn't actually look at any of the tables, files, or memory. The scheduler needs to be switched to MemManReal. "
Answer: 41867.0

User story: The centroid slot is currently not being filled when processing difference images. The NaiveDipoleCentroid plugin centroids the positive and negative lobes of the dipole, but does not define an "overall" centroid. This change adds a new "center" key that will be filled by the midpoint of the positive and negative lobes if both are present, or if only one lobe is present, then it uses that centroid.
Answer: 1462.0

User story: "IRSA is contributing to Firefly development. We need to mentor the new developers."
Answer: 45203.0

User story: "IRSA is contributing to the Firefly package development.  we need to put in time to mentor the developers. "
Answer: 42177.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 order to update MariaDB to v10.1.10 {{scisql}} needs to also be updated to deal with the hard-coded version checking. For the current version we get this error with the latest MariaDB:  {code}  :::::  [2016-01-28T16:51:40.539306Z]     user_function(self)  :::::  [2016-01-28T16:51:40.539334Z]   File "/home/build0/lsstsw/build/scisql/wscript", line 63, in configure  :::::  [2016-01-28T16:51:40.539346Z]     ctx.check_mysql()  :::::  [2016-01-28T16:51:40.539392Z]   File "/home/build0/lsstsw/build/scisql/.waf-1.6.11-30618c54883417962c38f5d395f83584/waflib/Configure.py", line 221, in fun  :::::  [2016-01-28T16:51:40.539410Z]     return f(*k,**kw)  :::::  [2016-01-28T16:51:40.539432Z]   File "tools/mysql_waf.py", line 85, in check_mysql  :::::  [2016-01-28T16:51:40.539451Z]     (ok, msg) = mysqlversion.check(version)  :::::  [2016-01-28T16:51:40.539473Z]   File "tools/mysqlversion.py", line 74, in check  :::::  [2016-01-28T16:51:40.539514Z]     if not comparison_op(version_nums, constraint_nums):  :::::  [2016-01-28T16:51:40.539547Z] UnboundLocalError: local variable 'constraint_nums' referenced before assignment  Failed during rebuild of DM stack.  {code}
Answer: 913.0

User story: "{{python/lsst/ci/hsc/validate.py}} in {{ci_hsc}} [says|https://github.com/lsst/ci_hsc/blob/69c7a62f675b8fb4164065d2c8c1621e296e40ad/python/lsst/ci/hsc/validate.py#L78]:  {code:python}      def validateMatches(self, dataId):          # XXX lsst.meas.astrom.readMatches is gone!          return  {code}  {{readMatches}} (or its successor) should be back in place as of DM-3633. Please enable this test."
Answer: 101087.0

User story: Over time, it has become apparent that mixing RFD (request for discussion) requests with RFCs is causing confusion, and the custom RFC template and workflow are not as appropriate for RFDs.    Creating a separate RFD project will disentangle these.  The RFD workflow might look like "Proposed", "Scheduled", "Done".  There should be a clear field for the proposed time slot.
Answer: 545440.0

User story: "Attend the weekly meeting and answer questions as needed"
Answer: 1522.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 would like to calculate a correct average and RMS for a set of RA, Dec positions.    Neither [~<USER> nor [~price] knew of an easy, simple function to do that that existed in the stack.  [~price] suggested:    {code}  mean = sum(afwGeom.Extent3D(coord.toVector()) for coord in coordList, afwGeom.Point3D(0, 0, 0))  mean /= len(coordList)  mean = afwCoord.IcrsCoord(mean)  {code}    That makes sense, but it's a bit unobvious (it's obvious how it works, but would likely never occur to someone that they should do it that way in the stack).    Pedantically it's also not the best way to do a mean while preserving precision, but I don't anticipate that to be an issue in practice.    Creating a function that did this would provide clarity.  I don't know where that function should live.    Note: I know how to do this in Astropy.  I'm intentionally not using astropy here.  But part of the astropy dependency discussion is likely "how much are we otherwise rewriting in the LSST stack".
Answer: 3007.0

User story: The line that caused the kernel panic is in modules/mysql/MySqlConnection.cc line 151.  Currently the line is fine and is:          std::string const killSql = "KILL QUERY " + std::to_string(threadId);    This version of the line will occasionally cause the kernel panic (note the missing %1% that should be after KILL QUERY).          std::string killSql = boost::str(bo  ost::format("KILL QUERY ") % threadId);  
Answer: 131010.0

User story: "James needs to test network communication methodologies in an environment that mimics the expected real-world conditions. In order to minimize the complications with debugging, using bare metal machines in the first phase is preferred.    We can use 4 of the machines bought off the 2015 purchase or purchase new machines just for this purpose."
Answer: 51992.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 I run {{scons}} in {{ci_hsc}}, it fails as follows:  {code}  partial([".scons/sfm-903334-16"], ["DATA/registry.sqlite3", "DATA/CALIB", ".scons/sfm"])  : Validating dataset processCcd_config for {'ccd': 16, 'visit': 903334}  CameraMapper: Loading registry registry from /raid/<USER>src/ci_hsc/DATA/registry.sqlite3  CameraMapper: Loading calibRegistry registry from /raid/<USER>src/ci_hsc/DATA/CALIB/calibRegistry.sqlite3  : processCcd_config exists: PASS  : processCcd_config readable (<class 'lsst.pipe.tasks.processCcd.ProcessCcdConfig'>): PASS  : Validating dataset processCcd_metadata for {'ccd': 16, 'visit': 903334}  : processCcd_metadata exists: PASS  scons: *** [.scons/sfm-903334-16] Exception : input stream error  Traceback (most recent call last):    File "/nfs/home/lsstsw/stack/Linux64/scons/2.3.0+1/lib/scons/SCons/Action.py", line 1062, in execute      result = self.execfunction(target=target, source=rsources, env=env)    File "/raid/<USER>src/ci_hsc/python/lsst/ci/hsc/validate.py", line 116, in scons      return self.run(*args, **kwargs)    File "/raid/<USER>src/ci_hsc/python/lsst/ci/hsc/validate.py", line 92, in run      self.validateDataset(dataId, ds)    File "/raid/<USER>src/ci_hsc/python/lsst/ci/hsc/validate.py", line 67, in validateDataset      print(data.__class__)    File "/home/lsstsw/stack/Linux64/daf_persistence/2015_10.0-6-g5a5f333+5/python/lsst/daf/persistence/readProxy.py", line 41, in __getattribute__      subject = oga(self, '__subject__')    File "/home/lsstsw/stack/Linux64/daf_persistence/2015_10.0-6-g5a5f333+5/python/lsst/daf/persistence/readProxy.py", line 136, in __subject__      set_cache(self, get_callback(self)())    File "/home/lsstsw/stack/Linux64/daf_persistence/2015_10.0-6-g5a5f333+5/python/lsst/daf/persistence/butler.py", line 279, in <lambda>      callback = lambda: self._read(pythonType, location)    File "/home/lsstsw/stack/Linux64/daf_persistence/2015_10.0-6-g5a5f333+5/python/lsst/daf/persistence/butler.py", line 452, in _read      location.getCppType(), storageList, additionalData)    File "/home/lsstsw/stack/Linux64/daf_persistence/2015_10.0-6-g5a5f333+5/python/lsst/daf/persistence/persistenceLib.py", line 1430, in unsafeRetrieve      return _persistenceLib.Persistence_unsafeRetrieve(self, *args)  Exception: input stream error  scons: building terminated because of errors.  {code}
Answer: 1361922.0

User story: "In DM-4882, we observed a number of centroids measured while running the {{lsst_dm_stack_demo}} routines fall outside their associated {{Footprints}}. This was seen with both the {{NaiveCentroid}} and the {{SdssCentroid}} centroiders.    For the purposes of DM-4882 we quieted the warnings arising from this, but we should investigate why this is happening and, if necessary, weed out small {{Footprints}} entirely."
Answer: 278942.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 {{meas_base}} framework includes {{SafeCentroidExtractor}}, a convenience routine for extracting a centroid from a source record, setting a consistent set of flags if that's not possible or if the centroid is in some way compromised. This consistent flag handling is made possible by the use of the {{FlagHandler}} class.    Unfortunately, {{FlagHandler}} is not meaningfully usable from Python, not least because it's impossible to define flags:  {code:python}  >>> import lsst.meas.base as measBase  >>> measBase.FlagDefinition("flag", "doc")  [...]  TypeError: __init__() takes exactly 1 argument (3 given)  >>> fd = measBase.FlagDefinition()  >>> fd.name = "flag"  [...]  AttributeError: You cannot add attributes to <lsst.meas.base.baseLib.FlagDefinition; proxy of <Swig Object of type 'lsst::meas::base::FlagDefinition *' at 0x10a82b900> >  {code}    Looking further, even were we able to create {{FlagDefinitions}}, the {{FlagHandler}} is initialized with pointers to the beginning/end of a container of them, which seems like a stretch for Python code.    Please add Python support for these routines.
Answer: 5867.0

User story: "The minimum python 2.7.x version, I believe, is essentially unknown. I propose that we document 2.7.10 as the minimum supported version.    We also need to articulate what we expect to be present in the python env.  At this point, I think that is essentially {{setuptools}} and the python header files (python.h)."
Answer: 1903799.0

User story: "Because of OS X SIP, {{obs_subaru}} fails to build on os x 10.11. In the {{hsc/SConscript}} file, the library environment variables need properly set, and scripts need to be delayed until the shebang rewriting occurs. "
Answer: 4120.0

User story: "add toolbar: next, prev arrow buttons, title when multi image fits has image specific titles or title would be cube number.    Make sure the store will support multi images, add next, prev actions, etc"
Answer: 135414.0

User story: "We are planning to vertically partition some tables (for example Object). We should make sure such joins across say 5, 10 or 20 tables are not a problem for mysql from performance standpoint. The testing involves creating a wide table (say 200 columns) and testing a speed of full scan, then slicing that table vertically into different number of columns and using join to assemble the pieces together."
Answer: 50616.0

User story: "After DM-2993 is completed, the anaconda package should be renamed as {{legacy-}} to discourage any future use."
Answer: 2813.0

User story: "When download an image,  the proper name needs to be resolved based on the URL and   the information about the image.  In Java code, it has the following three methods:  {code}   encodeUrl  makeFileName  makeTitleFileName  {code}    These method should be ported to javascript.  Thus, the javascript version of the FitsDownloadDialog will save the file in the same manner. "
Answer: 1445.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 DECam-specific bugs only reveal in or affect the processed data. For example the bug of DM-4859 reveals in the {{postISRCCD}} products.  If the bugs are DECam-specific, some changes in {{obs_decam}} are likely needed.  It would be useful to have a more convenient way to test those changes. In this ticket I modify {{testdata_decam}} so that those data can be processed, and then allow wider options in the {{obs_decam}} unit tests.    I add {{testProcessCcd.py}} in {{obs_decam}} that runs {{processCcd.py}} with raw and calibration data in {{testdata_decam}}.  Besides a short sanity check, I add a test (testWcsPostIsr) that tests DM-4859. {{testWcsPostIsr}} fails without the DM-4859 fix, and passes with it.  "
Answer: 14328.0

User story: For some object names resolved by NED, the position is not right. In this situation, it would be better to get the position from Simbad. Currently, Firefly offers two options: first NED, then Simbad; first Simbad, then NED. The third option to be added would be "the best position according to the object type".     It should check the object type returned by NED, making a decision whether to get position from Simbad instead; and vice versa. 
Answer: 2270941.0

User story: "Meeting between NCSA CSD group, NCSA LSST DM group, and other LSST groups."
Answer: 14028.0

User story: "Security planning/meeting with PO."
Answer: 14032.0

User story: "Security meeting/planning with LSST DM team at NCSA."
Answer: 14032.0

User story: "Continuing work on cyber sec. plan renewal.  DM moving along, PO slated next."
Answer: 14030.0

User story: "Documenting cyber security operational requirements by LSST, particularly at the obs. site."
Answer: 14031.0

User story: "This ticket includes efforts to troubleshoot and improve processing DECam raw data in Jan 2016.   Investigations of the warnings from solving astrometry led to DM-4805, DM-4859. This ticket also includes partial efforts in DM-4859.         For validation, I ran {{processCcd.py}} with two visits of raw Stripe 82 DECam data with and without the changes in DM-4859 (using the first camera geometry fix, which is different from the final fix).  The script {{validateDecam}} in {{validate_drp}} is used to check astrometric scatter of the sources between the two visits.  Output plots are in the attachments.  By fixing DM-4859, the median astrometric scatter (mag < 21) decreases from 31.3 mas to 26.1 mas.  The number of matches between two visits increases from 56768 to 71265.  Also attached are the ra/dec patches plots, using the {{showVisitSkyMap.py}} script from DM-4095. The two colors represent the two visits of calexp wcs.  Southern CCDs had bad astrometric solutions before DM-4859.  The validation results are consistent with the patches visualization.   "
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: "Expand button hide/show, delete button hide/show, display title options,  support pv.hideTitleDetail to control showing zoom level and rotation info (used by planck)  support external title bar (planck as well)  support checkbox on title bar (planck)  "
Answer: 5687.0

User story: "Currently there is {{validateCfht.py}} and {{validateDecam.py}} as code.  These differ in just having {{defaultData}} functions that specify the dataIds to consider and the dataIds to use as a reference for comparison.    Storing the information necessary to create these sets of dataIds in separate data files, to be stored as YAML would  1. Improve the separation of code and data  2. Clarify the usage and necessary information to run on a new or different set of data  3. Make it easier to run different subsets easily by specifying a different input file    The proposals is that {{validateCfht.py}} and {{validateDecam.py}} would disappear from {{bin}} and be replaced by just {{validate_drp.py}}.  The examples in {{examples/runCfhtTest.sh}} and {{examples/runDecamTest.sh}} will be updated to show the new usage.  The README will also be updated."
Answer: 31916.0

User story: "We’re using [Breathe|http://breathe.readthedocs.org/en/latest/] to bridge C++ API references built with Doxygen in to the Sphinx documentation site builder. Breathe uses Doxygen’s XML output. This is a trivial modification to the existing scons documentation build target."
Answer: 38828.0

User story: "Implement a suite of simulations tools for testing the image differencing techniques, specifically with an eye toward dealing with DCR."
Answer: 76469.0

User story: "Having got the CBP/DECam data loaded into the stack, explore the parameter space and understand data.    This should result in a series of stories describing more detailed analysis with quantitative results."
Answer: 76656.0

User story: "Add PyYAML EUPS packages."
Answer: 156.0

User story: "Determine if existing bad pixel masks, flats, etc are adequate for analysing the DM-4893 DECam data, and, if not, provide alternatives."
Answer: 67849.0

User story: "[~<USER> will ingest the data taken in DM-4892 into the LSST stack. Initial experiments indicate problems with:    * Bias subtraction  * Flat fielding  * Bad pixel masks    These may already be remedied by work on {{obs_decam}}; if not, he will file stories and fix them."
Answer: 76681.0

User story: "[~<USER> recently figured out how to set up his system to run a remote IPython kernel on {{lsst-dev}} and interact with it from his laptop, including streaming image display from the remote system to a local instance of {{ds9}}.    He will write all this up so that others in the community can easily do the same."
Answer: 69286.0