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: "Seeking out developer use cases of incoming data sets. Need to determine if datasets will be accessed for verification only or by developers and QA in general. Determine access methods. "
Answer: 6635.0

User story: "https://confluence.lsstcorp.org/display/~<USER>Data+Access+Center"
Answer: 17605.0

User story: "When {{sconsUtils}} is migrated to use {{nose}} or {{py.test}} some test scripts will need to be modified because test discovery will be slightly different and the namespace of test execution will change.    Two things to consider:  * People would still like the option of running a test as {{python tests/testMe.py}}.  * We have to work out how to run the memory test case.  "
Answer: 221314.0

User story: "I was asked for a revision of [DM-2983] which is part of the Backport HSC parallelization code"
Answer: 20005.0

User story: "Should produce the numeric values required (or an explanation of why they aren't available) together with a description of the process for generating them (incl. the data processed, scripts used for plotting, etc)."
Answer: 11360.0

User story: " Should produce the numeric values required (or an explanation of why they aren't available) together with a description of the process for generating them (incl. the data processed, scripts used for plotting, etc)."
Answer: 11363.0

User story: "Should produce the numeric values required (or an explanation of why they aren't available) together with a description of the process for generating them (incl. the data processed, scripts used for plotting, etc)."
Answer: 11364.0

User story: "Should produce the numeric values required (or an explanation of why they aren't available) together with a description of the process for generating them (incl. the data processed, scripts used for plotting, etc)."
Answer: 11372.0

User story: "The previous prototype provided confidence that a DHT overlay could work for routing and placement at the scales and time constants needed for chunk distribution.  The next prototype will need actual data transport and storage management facilities layered on the node/key management provided by the DHT layer.  Explore existing works at this level to a greater depth pick from among proven approaches."
Answer: 10359.0

User story: "Do a comprehensive read-through of the previous released version of LSE-78.  Look for self-consistency and for consistency with the rest of the DM and overall system design.  Report issues to appropriate people."
Answer: 269109.0

User story: "Prepare for CCB action on LCR-323.  Ensure that DAQ integration is included (it's not in the original LCR proposal)."
Answer: 269111.0

User story: "Addition of [https://confluence.lsstcorp.org/display/~<USER>Products+of+Image+Ingest+and+Processing] to understand more of the requirements necessary for the functional design  "
Answer: 1521.0

User story: "Gather feedback on initial designs for FY16 purchase plans."
Answer: 8639.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: In the one unit test, DM-3462 introduced an implicit dependence on TESTDATA_DECAM_DIR.    {code}  +        datadir = os.getenv("TESTDATA_DECAM_DIR")  +        assert datadir, "testdata_decam is not setup"  {code}    If someone git clones this repository and builds it, this test will fail unless they've explicitly downloaded the test dataset and setup it up.  This is not the behavior we want.  We want it to check for the test data and skip the test if not set up.
Answer: 1695.0

User story: "This ticket will add any missing data products required for coaddition to the obs_decam mapper. (And make any updates should problems arise) "
Answer: 760097.0

User story: "I have seen enough anomalies that I have had to go back a bit and do some basic tests of CModel and its ellipticity bias.  This involves running the same pipeline as before, but with controlled galaxy profiles, ellipticities, and angles.  These are zero-shear, zero-seeing tests which I probably should have run first thing.    It I understand everything I see in these tests, I will be confident that the results I am seeing for CModel with varying footprint size, varying nInitialRadii, and varying stamp size are correct."
Answer: 260718.0

User story: "Solve fit-and-finish issues with the stock readthedocs.org Sphinx template when rendering DM design documents. Issues include:    * Sections need to be numbered and those numbers need to appear in TOC  * RTD's TOC does not properly collapse sub-topics  * Appropriate styling for document title and author list  * Wrapping the changelog table  * Adapt section references so that just the section number can be referenced, independently of the section number and title in combination  * Section labels given explicitly in the reST markup are different from the anchors that Sphinx gives to the {{<hN>}}tags; the former are simply divs inserted in the HTML.    The solutions may involve    # reconfiguring the Sphinx installation of individual documents  # forking the RTD HTML template, and/or  # developing extensions for Sphinx in {{sphinxkit}}."
Answer: 8926.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: During some multi-threaded builds {{meas_algorithms}} is sometimes failing when loading the matplotlib font cache. We think this is due to two tests simultaneous using matplotlib infrastructure and the second one sometimes attempts to load the font cache when the first is using it.    {code}     import matplotlib.colorbar    File "/home/vagrant/stack/Linux64/anaconda/2.2.0/lib/python2.7/site-packages/matplotlib/colorbar.py", line 34, in <module>      import matplotlib.collections as collections    File "/home/vagrant/stack/Linux64/anaconda/2.2.0/lib/python2.7/site-packages/matplotlib/collections.py", line 27, in <module>      import matplotlib.backend_bases as backend_bases    File "/home/vagrant/stack/Linux64/anaconda/2.2.0/lib/python2.7/site-packages/matplotlib/backend_bases.py", line 56, in <module>      import matplotlib.textpath as textpath    File "/home/vagrant/stack/Linux64/anaconda/2.2.0/lib/python2.7/site-packages/matplotlib/textpath.py", line 19, in <module>      import matplotlib.font_manager as font_manager    File "/home/vagrant/stack/Linux64/anaconda/2.2.0/lib/python2.7/site-packages/matplotlib/font_manager.py", line 1415, in <module>      _rebuild()    File "/home/vagrant/stack/Linux64/anaconda/2.2.0/lib/python2.7/site-packages/matplotlib/font_manager.py", line 1402, in _rebuild      pickle_dump(fontManager, _fmcache)    File "/home/vagrant/stack/Linux64/anaconda/2.2.0/lib/python2.7/site-packages/matplotlib/font_manager.py", line 952, in pickle_dump      with open(filename, 'wb') as fh:  IOError: [Errno 2] No such file or directory: u'/tmp/matplotlib-vagrant/fontList.cache'  {code}    Currently matplotlib import failures are trapped as follows:    {code:python}  try:      import matplotlib.pyplot as plt      import matplotlib.colors  except ImportError:      plt = None  {code}    but this only protects the case where matplotlib is not installed. It does not protect against a failure of an existing matplotlib to load.    The matplotlib project has come across this problem itself when using Travis ([https://github.com/matplotlib/matplotlib/commit/f0888de10e8740200c7cb8387a3733d4fe6af967]) and they disable the font cache when {{$TRAVIS}} is set.    To fix this we can therefore either fix every import to also trap an {{IOError}} or else modify {{sconsUtils}} to set the TRAVIS environment variable when it runs the tests.
Answer: 1473.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 using the grid overlay in galatic coordinate over an image that is around longitude = 0, the overlay doesn't work properly. In BOLOCAM, on fits image works but not the other one.    Reproducible:   Steps to Reproduce:   Go to Atlas search, and select BOLOCAM galactic plane survey (GPS).  Then enter single coordinate search on "0 0 gal" to find images taken around that.     See column "FITS filename" and search for the sharc-ii instrument images such as  images/sharc2/L000.15+0.00.fits [bad]   and   images/sharc2/L000.00+0.00.fits [good]     Then open it on irsaviewer by clicking on the icon link (first column).  On the image viewer, enable the grid overlay and click on the icon 'layer' on the toolbar.  Change the coordinate system to galactic to see the problem.     On the overlay for the associated Bolocam map there are three horizontal lines which exist only on the left hand side of the image. When the image coordinate system is set to "Gal", the reported GLON values range from -355.4 to -1.6 (from left to right), passing through -0.0 in the center.     Same problem can be seen for   images/v1/INNER_GALAXY/map/v1.0.2_super_gc_13pca_map50_crop.fits [bad]  
Answer: 41536.0

User story: "ctrl_pool (formerly hscPipeBase) is being ported with no unit tests - the only testing is an example script that can be run by hand to demonstrate a piece of the functionality.    Some functionality may simple not be amenable to tests (such as batch submission).  Other parts may be tricky to run via SCons because they're intrinsically parallel, and SCons naively wants to be able to run each test in a separate process.  Overcoming those problems is the reason this is challenging - there isn't really that much functionality to test."
Answer: 2319327.0

User story: "The new ctrl_pool package (port of hscPipeBase) has no tutorial-level documentation, making it hard to figure out how to start using the package.    Unfortunately, I think only [~price] is qualified to write it directly, though it may make sense to have someone unfamiliar write it while bugging Paul a lot, both to transfer the knowledge and target the documentation better."
Answer: 2129869.0

User story: "Redesign pipe_base to allow the creation of supertasks which will be more flexible for  different execution applications"
Answer: 23055.0

User story: "Convert LDM-129 from Word to restructuredText and deploy onto readthedocs.org"
Answer: 70736.0

User story: "Convert LDM-135 from Word to restructuredText and deploy on readthedocs.org"
Answer: 66604.0

User story: "Convert LDM-230 from Word to restructuredText and deploy on readthedocs.org"
Answer: 70893.0

User story: "Try to run processCcd.py with raw DECam data and see what are yet to be solved for it to run. "
Answer: 23281.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: "email to German about the all the L1 stuff and clarified that the L1 system were a  derive provided to the Telescopes site (important for fitting this into the proper place in the who is worrying about what hierarchy.  Also, revised SA to see fi the EPO changes discusses affected the IT roles in th model (not apparently)  lastly attitude the TOWC "
Answer: 1.0

User story: "added the image and engineering facility database.  and Observatory Operations Server."
Answer: 1.0

User story: "Trying a newer Eigen has exposed several issues in meas_astrom:  - tests/createWcsWithSip.py blindly uses sipWcs in the result returned by ANetBasicAstrometryTask.determineWcs2, but that attribute may be None  - ANetBasicAstrometryTask.determineWcs2 terminates iteration early if the # of matches goes down, even though the result may be improved. In the case in question the first fit iteration results in significantly better RMS error, but has one fewer matches, so the SIP fit is rejected, triggering the first bug mentioned."
Answer: 6104.0

User story: "NIST SP 800.82 investigation for a more cohesive SCADA enclave security plan."
Answer: 20625.0

User story: "Work for LSST Identity management and authentication."
Answer: 20623.0

User story: "Bi-weekly meeting with PO on cyber security."
Answer: 20625.0

User story: "Creation of configured master and worker image will be improved here, and a deploymen tool (like swarm, of hand-made) will be used to deploy images over in2p3 cluster."
Answer: 43412.0

User story: "When ccdnum is not given as part of the dataId, instead of iterating over it, an error like this happens    {code:java}    RuntimeError: No unique lookup for ['ccdnum'] from {'visit': 205344}: 61 matches  {code}    Likely a problem in policy/DecamMapper.paf"
Answer: 13458.0

User story: "Build a platform for DM design documents with requirements    * Each design document has it's own repo on GitHub  * Content of the design document is in reST with images as appropriate  * Documents are continuously built on commit and rendered via readthedocs.org    A predecessor to this work was DM-3546. This is a meta story to coordinate individual stories in this effort related to doc infrastructure and content conversion."
Answer: 125714.0

User story: "This is a port of the following HSC tickets:  [HSC-1072|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1072]  and  [HSC-1175|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1175]"
Answer: 40692.0

User story: "Setup the lsst_sphinx_kit package, including    * setup.py  * unit tests, tox and Travis CI  * README stub  * Sphinx stub and readthedocs"
Answer: 15776.0

User story: "Build a Python package (ideally Python 3.4+ compatible, but absolutely Python 2.7 compatible) containing Sphinx and docutils extensions to support the LSST Stack documentation. This package should be sufficiently generic that other open source projects can find & use it."
Answer: 66548.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: "To match the conversion of lsstsw from anaconda -> miniconda to reduce the disk footprint and improve install times."
Answer: 212744.0

User story: "In sfm.py on line 271, a comment indicates that some code is a temporary work around until the switch from meas_algorithms to meas_base is complete. This work is complete, so this temporary workaround should be removed, or if it is decided it should be kept, the comment should be removed. See https://github.com/lsst/meas_base/blob/tickets/DM-2915/python/lsst/meas/base/sfm.py#L271"
Answer: 764341.0

User story: "Enable SSL (https) for the Discourse site at community.lsst.org"
Answer: 7955.0

User story: "Now that SIM-1314 has been merged, we should be able to remove the    {code}   if [[ $(uname -s) = Darwin* ]]; then    #run install_name_tool on all of the libpythonX.X.dylib dynamic    #libraries in anaconda    for entry in $PREFIX/lib/libpython*.dylib    do     install_name_tool -id $entry $entry    done   fi  {code}    from eupspkg.cfg.sh in the EUPS anaconda package, and still have GalSim build correctly"
Answer: 2034085.0

User story: "Viz:    {code}  [<USER>lsst-dev ~]$ . /lsst/stack/loadLSST.sh  /lsst/stack/eups-1.5.9/bin/eups_setup: line 6: /home/lsstsw/anaconda/bin/python: No such file or directory  /lsst/stack/eups-1.5.9/bin/eups_setup: line 6: /home/lsstsw/anaconda/bin/python: No such file or directory  /lsst/stack/eups-1.5.9/bin/eups_setup: line 6: /home/lsstsw/anaconda/bin/python: No such file or directory  {code}    This was discussed on HipChat yesterday (9 Sept); it's still happening as of this morning.  Not clear if this is just a glitch related to the upcoming release or if there's something intentional going on."
Answer: 54.0

User story: "The David Keller kademlia implementation used in the earlier prototype has some bugs/limitations.  Try to find a better off-the-shelf DHT and integrate with prototype framework."
Answer: 20407.0

User story: "We have an action to allow people to pull obs_decam and a working stack without including obs_decam in lsst_distrib. And we want to CI it.     The strawman plan is to make a new TLP for decam. SQuaRE will discuss. "
Answer: 282177.0

User story: "The procedure for pulling/pushing xrootd changes from/to the upstream official xrootd repo is cumbersome, confusing, and error-prone.    Buildbot now has support for releasing packages from branches other than master.  Given this, we can now reasonably replace our lsst/xrootd repo with a fresh genuine fork (shared history) of upstream, then carry our lsst-specific work forward on a dev-branch.  This will make it much easier to track and contribute to the xrootd project moving forward.    Existing legacy branches and tags are to be migrated to the fresh fork, so historical builds will not be broken."
Answer: 4.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've been ignoring some accumulating warns in the qserv build for some time now.  Now that it is possible to develop qserv in eclipse, it would be useful to address warns and analyzer issues so that we can start to notice when new ones pop up."
Answer: 1324.0

User story: "Google protobufs 2.6.1 includes a few unnecessary semicolons in some of its supplied header files; these generate a lot of compiler warnings when compiling client packages.    Proposed fix is to add a patch to our eups t&p protobufs package to remove the offending semicolons."
Answer: 419.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: "Due to the 2 year gap between the original authoring date of LDM-144 and the recent update,  the 'costing only' update caused the document to be less self consistent than desired. This work is to do more than 'costing' updates such that the document is useful and on target to be more than a costing umbrella."
Answer: 8302.0

User story: "This is a port of the following HSC updates to how tracts and patches are found and listed given a set of coordinates.  These are all standalone commits (i.e. not associated with a ticket):  [Add findTract() and findTractPatchList() in ringsSkyMap.|https://github.com/HyperSuprime-Cam/skymap/commit/761e915dde25ce8ed5622c2d84b83793e9580fd7]  [move RingsSkyMap.findTractPatchList to BaseSkyMap.findClosestTractPatchlist|https://github.com/HyperSuprime-Cam/skymap/commit/56476142060bdb7d8c7fb59eacc383f0e0d5c85b]  [Small bug fix for RingsSkyMap.findTract().|https://github.com/HyperSuprime-Cam/skymap/commit/f202a7780ebb89166f03479d7447ace1555027c1]  [Add fast findTractPatchList() in RingsSkyMap.|https://github.com/HyperSuprime-Cam/skymap/commit/7e49c358501f95ce4c0e1aa8f48103a24391fc22]  [Fixed the problems regarding poles and RA wrap.|https://github.com/HyperSuprime-Cam/skymap/commit/841b0c9eda7462a7a4f182b7971d5e8e81478bfe]  [Add spaces around '+' and '-' to match LSST standard coding style.|https://github.com/HyperSuprime-Cam/skymap/commit/f7e2f036494afe382e653194c82bb15728c60fc3]"
Answer: 99368.0

User story: "A problem with the default ref in {{repos.yaml}} support implemented in DM-3679 was discovered last Friday, shortly after deploying this feature to the production CI systems.    The default ref for {{xrootd}} was changed/overridden in {{repos.yaml}} to {{legacy/master}}.  This worked as expected (and as was tested) when setting {{xrootd}} as the sole {{lsstswBuild.sh}} product or when running {{rebuild}} by hand.  However, when building any package that pulled in {{xrootd}} as a recursive dependency, the {{master}} branch was being used (this case had not been manually tested)."
Answer: 181.0

User story: "A RUNID needs to be added as an option to EventAppender to allow event logging selectors to receive only events for a particular run."
Answer: 14779.0

User story: "There are several issues need to be resolved for the system to work properly. "
Answer: 38559.0

User story: "Due to the changes of the database and tables, the system has to be rebuilt."
Answer: 5362.0

User story: "Collect the information for the tables populated for Bremerton end-to-end exercise. Use them in SUI/T so we can access them using the DAX API. "
Answer: 38571.0

User story: "In the last few days or so I've been getting 2-3 copies of every comment posted to any ticket I'm watching. Did JIRA change? Are my settings messed up? It's not a big deal, but it's rather annoying to have to wade through all the duplicates and avoid accidentally skipping messages I care about."
Answer: 56172.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: "Goals:  - Have something to ingest calibration data and create a calibration registry (calibRegistry.sqlite3)  - Add mapping class calibration into DecamMapper and make butler able to get bias/flat/fringe.  - Include calib in testdata_decam and add to the unit test retrieving calib data.    Summary:  - A new task {{ingestCalibs.py}} is added to {{pipe_tasks}} for parsing through calibration data and creating a calibration registry.  The DECam customized configuration is added in {{DecamCalibsParseTask}} in {{obs_decam}}.   {{pipe_tasks/ingest.py}} is modified slightly for more general use while its original behaviors are kept by default.   - The calibration data are DECam Community-Pipeline products, including nightly-MasterCal bias/flat downloadable from NOAO Science Archive, and fringe of the latest version 56876 from  http://www.ctio.noao.edu/noao/content/decam-calibration-files or also on /lsst8/decam/cal/DECamMasterCal_56876/  Note that files from the two sources have different formats (MEF one HDU for each detector, or one single-HDU fits for each detector).  - New Butler dataset types bias/flat/fringe are added along with functions to standardize them to Exposures in {{DecamMapper}}.  - Tests of retrieving bias/flat/fringe by Butler are added.    - testdata_decam used by the unit tests is at lsst-dev:/lsst8/testdata_decam/    Known caveats for future users  - The task could be a bit noisy when ingesting DECam calibration data products.  But given the variety of data products on hand I might rather have those reminders than letting all pass silently.      - I wouldn't be too surprised if future DECam Community-Pipeline products appear in different formats. Depending on how different they become, {{DecamCalibsParseTask}} might or might not need future modifications.   "
Answer: 40042.0

User story: "SUI team would find it useful to get counts of columns for a table, ideally, all counts of columns for all tables in a given database in one request. They'd also find it useful if we could send column description."
Answer: 1297701.0

User story: "The scons build system is unaware of extra flags which may be set in SCONSFLAGS environment variable, which are used from scons utils. This will cause the build to fail. The package needs to behave properly and build in the presence of these flags"
Answer: 7745.0

User story: "There are a couple references to EventLog in ctrl_orca, which is an object that no longer exists."
Answer: 21561.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "This issue is to modernize the diffim task.  Once it is running it should be refactored to use the new measurement tasks and reference loading wherever possible.  Also remove any one off code used in past reports.    Measurement should be split into its own task.    The resulting task should be general, but not so general as to make it hard to run.    This issue is being split into three issues:  * DM-3704: split monolithic task into:  ** ImageDifferenceTask - creates image difference  ** ProcessDiffim - perform detection and measurement on image differences (and calexps)  * DM-5294 Refactor/Clean up new ImageDifferenceTask  * DM-5295 Refactor/Clean up new processDiffimTask"
Answer: 2118798.0

User story: Pull HSC pixelFlags for suspect and suspect center over from {{meas_algorithms}} to {{meas_base}}. Additionally there are a few places in {{meas_base}} (& possibly in {{_algorithms}} as well) which set flags that have comments such as "Set suspect flag if it was available". Each of these places should be updated to use the ported bit. The relevant commit can be found at https://github.com/HyperSuprime-Cam/meas_algorithms/commit/21be65187c30302abb430d59fc5f67730ca7e0a1 and is discussed at https://dev.lsstcorp.org/trac/ticket/2838    It may also be necessary to add or update a unit test to make sure the flag is set appropriately.
Answer: 67800.0

User story: "Everything learned through the literature search and project wide meeting should be synthesized into a single readable report that details the expected effects of DCR on difference imaging as well as possible mitigation techniques.    This may involve some preliminary analysis work to measure effectiveness of various techniques.    Note that I expect this to be two weeks of work for two people, thus the 40 story points.  I don't know how to assign a story to two people."
Answer: 222151.0

User story: "Advertise and conduct a broadly advertised videocon on DCR in the context of diffim.  The result of this should be minutes.  Ideally we would come out of this meeting with a list of possible techniques for dealing with DCR (preferentially sorted by priority)."
Answer: 222152.0

User story: "Go through the literature to find relevant seminal papers on DCR.    The outcome will be a bibliography and executive summary.  This should be posted on Discourse."
Answer: 127066.0

User story: "Replace the --trace argument with an enhanced version of --loglevel that supports named values and numeric log levels (which are the negative of trace levels). This simplifies the interface for users and potentially reduces the log level/trace level confusion, though that won't fully happen until we finish replacing use of pex_logging Trace and Debug with Log.    This work was already done as part of DM-3532; it just needs to be copied with minor changes (since there are no named trace levels in pex_logging)."
Answer: 501.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: "Buildbot frequency is now down to two builds, one at 19:42 machine time (NCSA) and one at 1:42. This is to stop people needing buildbot runs to eups publish to have to wait before a CI build, since they are now done on[ https://ci.lsst.codes ]/ Jenkins.     "
Answer: 2.0

User story: "This is a port of the standalone changesets:  [calibrate: make astrometry failures non-fatal|https://github.com/HyperSuprime-Cam/pipe_tasks/commit/e9db5c0dcdca20e8f7ba71f24f8b797e71699352]  [fixup! calibrate: make astrometry failures non-fatal|https://github.com/HyperSuprime-Cam/pipe_tasks/commit/c2d89396923f9d589822c043ed8753647e70f3f6]  (the above is a fixup, so will likely be squashed)  [make failure to match sources non-fatal|https://github.com/HyperSuprime-Cam/pipe_tasks/commit/cf5724b852937cfcef1b71b7a372552011fda670]  [calibrate: restore original Wcs after initial astrometry solution|https://github.com/HyperSuprime-Cam/pipe_tasks/commit/ab6cb9e206d0456dc764c5ef78ac80ece937c610]  [move CalibrateTask from ProcessImageTask into ProcessCcdTask|https://github.com/HyperSuprime-Cam/pipe_tasks/commit/08a8ec029dd52ac55e47b707a6905df061a40506]  [processCoadd: set detection to use the declared variances|https://github.com/HyperSuprime-Cam/pipe_tasks/commit/9e8563fd8d630dad967786387b1f27b6bc7ee039]  [adapt to removal of CalibrateTask from ProcessImageTask in pipe_tasks|https://github.com/HyperSuprime-Cam/obs_subaru/commit/52733a7ab1731a15cbb93151851f57cec276f928]  and HSC tickets:  [HSC-1085: background not saved in processCcd|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1085] and  [HSC-1086: psf - catalog scatter is very large in some coadds|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1086]"
Answer: 79183.0

User story: "This is a port of the changesets from [HSC-966|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-966].    It provides the ability to reserve some fraction of PSF candidates from the PSF fitting in order to check for overfitting and do cross validation."
Answer: 120669.0

User story: "The CFHT-specific CalibrateTask tries to apply aperture correction once just after measuring it (which is too early) and again later, at the right time. The error probably has no effect on the final results, but it is confusing and needlessly divergent from the standard CalibrateTask. The required changes are small. I plan to test by running [~<USER>'s CFHT demo."
Answer: 8595.0

User story: "Setup a system to forward new post notifications from http://community.lsst.org categories to their appropriate legacy Mailman email list counterparts.    ||Discourse Source Category||Mailmain Forward List||  |DM Team||dm-staff|  |Announcements||dm-announce|  |DM Notifications||dm-devel|    Once this is implemented I will send a notice that all communications and replies should occur on discourse (these mailing lists should be read-only).    I will also send a notice that dm-users is deprecated.  "
Answer: 53881.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "It would be nice to have a hipchat channel with notifications of discourse activity.  As a power up, perhaps new topics under certain categories, I'm thinking specifically of DM Notifications, could generate posts to select general HC channels -- similar to how RFC notifications are currently handled.    A quick google search turns up this plugin for integration:    https://github.com/binaryage/discourse-hipchat-plugin"
Answer: 655133.0

User story: "We want to try out GitLFS and evaluate its suitability as a solution to storing binary data in repos for CI. We want to know how it compares in usability terms to git-annex, git-fat etc. "
Answer: 28557.0

User story: "I have been talking to the {{scons}} developers about supporting Python 3. They state that one of the impediments to supporting Python 3 is that they do not have any buildbot slaves currently using python 3.    Would it be possible for SQuaRE to set up a small system (say, running Fedora so that python 3 is native) that can be a buildbot slave for the {{scons}} project?    Instructions for activating the slave can be found at [https://bitbucket.org/scons/scons/wiki/InstallingBuildbotSlaves]"
Answer: 759054.0

User story: Support of xrootd within the stack is currently complicated by the fact that qserv depends on features that are not available on upstream master (only available on an upstream non-master branch).  Since we can currently only publish packages from master, this means that our lsst fork of xrootd cannot be a "pure" fork -- we end up merging/rebasing from an upstream branch, then force-pushing the downstream master.  Upstream and downstream xrootd repos thus have completely different branch topologies, labels, etc., and history of master in the lsst fork is being continually rewritten to carry local patches forward.  The processes of both adopting upstream changes into the lsst fork and the pushing lsst changes back upstream are cumbersome, confusing, and labor intensive.    It is proposed that we extend our tools to allow publishing components from branches other than master.  This would allow us to have xrootd for example be a "pure" fork of upstream -- we could then create our own branch based off any upstream branch, carry our downstream patches there, and release off of that.    This functionality could be used similarly for any of our current "t&p" components where it would be convenient to track the upstream repo directly and/or carry changes in git instead of in an agglomerated patch file (e.g. when we might want to update frequently and/or contribute general purpose changes back upstream regularly with pr's, etc.)
Answer: 1380.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 involves pulling over the following standalone (i.e. non-ticket) HSC commits:  [Updated star selection algorithm.|https://github.com/HyperSuprime-Cam/meas_algorithms/commit/071fcadc016908a10583c746f0a8e79df2a45ead]    [Appropriate config parameter for a unit test of testPsfDetermination.py.|https://github.com/HyperSuprime-Cam/meas_algorithms/commit/e73c5e447ac0b8a71926d3e78fec30aad4beee91]    [Remove HSC specific codes.|https://github.com/HyperSuprime-Cam/meas_algorithms/commit/15bb812578531766199e9a1ee41cc707fb3d9873]  (Note, the above reverts some unwanted camera-specific clauses added in the first commit.  May just squash them to only add the desired features)    [ObjectSizeStarSelector: push non-fatal errors to DEBUG level|https://github.com/HyperSuprime-Cam/meas_algorithms/commit/44f75bc60b41c5f77b323a8d9981048ef7e5f3c4]    [We don't use focal plane coordinates anywhere, and detector may be None|https://github.com/HyperSuprime-Cam/meas_algorithms/commit/4413db4610e4793727e591f395f5ad8cd0cb6030]    [Fixed axis labels|https://github.com/HyperSuprime-Cam/meas_algorithms/commit/67efacaccf8346fdfa1b450617aebabddb2b7ec0]    [Improved PSF debugging plots|https://github.com/HyperSuprime-Cam/meas_algorithms/commit/b1bc91ed1538607eb90e070881a82498fd551909]    [Worked on star selector|https://github.com/HyperSuprime-Cam/meas_algorithms/commit/6b36f4d757187d30142a7e026754a07ffeb8dea2]"
Answer: 30244.0

User story: "This is a port of the changesets from:  [HSC-756|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-756]  "
Answer: 75219.0

User story: "The {{log}} package does not depend on {{utils}} for anything other than some minor Swig includes."
Answer: 12.0

User story: "  Identify required resources for Verification runs and communicate them to NCSA.   "
Answer: 202693.0

User story: "  Present talk at AHM to seed Verification effort and seek feedback. "
Answer: 737.0

User story: "  Identify candidate Verification sets (in the first instance, datasets with extant processed data used in one-off reductions with lsst_apps to allow a preliminary assessment of current quality from a science QA perspective).     Identify people within the project with effort, expertise and interest available to contribute to this effort. "
Answer: 1.0

User story: When you added messages about "EUPS integration" you failed to make the message generation obey {{-Q}} (cf. DM-1565).  Please fix this.  
Answer: 5324.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: ingestImagesDecam.py no long builds registry.sqlite3 with some recent changes of the stack. Output messages:     {code:java}  ingestImagesDecam.py . --mode=link instcal/*fits.fz  : Loading config overrride file '/Users/<USER>decam/playground/obs_decam/config/ingest.py'  : Config override file does not exist: '/Users/<USER>decam/playground/obs_decam/config/decam/ingest.py'  : input=/Users/<USER>decam/dataTempInstcal/data2  : calib=None  : output=None  CameraMapper WARNING: Unable to locate registry registry in root: /Users/<USER>decam/dataTempInstcal/data2/registry.sqlite3  CameraMapper WARNING: Unable to locate registry registry in current dir: ./registry.sqlite3  CameraMapper WARNING: No registry loaded; proceeding without one  ingest.parse WARNING: Unable to find value for ccdnum (derived from CCDNUM)  ingest.parse WARNING: Error reading instcal/c4d_130922_234714_ooi_i_d1.fits.fz extensions set(['S7'])  /Users/<USER>decam/dataTempInstcal/data2/instcal/c4d_130922_234714_ooi_i_d1.fits.fz --<link>--> /Users/<USER>decam/dataTempInstcal/data2/0237628/instcal0237628.fits.fz  /Users/<USER>decam/dataTempInstcal/data2/dqmask/c4d_130922_234714_ood_i_d1.fits.fz --<link>--> /Users/<USER>decam/dataTempInstcal/data2/0237628/dqmask0237628.fits.fz  /Users/<USER>decam/dataTempInstcal/data2/wtmap/c4d_130922_234714_oow_i_d1.fits.fz --<link>--> /Users/<USER>decam/dataTempInstcal/data2/0237628/wtmap0237628.fits.fz  Traceback (most recent call last):    File "/Users/<USER>decam/playground/obs_decam/bin/ingestImagesDecam.py", line 3, in <module>      DecamIngestTask.parseAndRun()    File "/opt/lsst/DarwinX86/pipe_tasks/10.1-35-ga8dd78f+3/python/lsst/pipe/tasks/ingest.py", line 353, in parseAndRun      task.run(args)    File "/Users/<USER>decam/playground/obs_decam/python/lsst/obs/decam/ingest.py", line 67, in run      self.register.addRow(registry, info, dryrun=args.dryrun, create=args.create)    File "/opt/lsst/DarwinX86/pipe_tasks/10.1-35-ga8dd78f+3/python/lsst/pipe/tasks/ingest.py", line 311, in addRow      conn.execute(sql, values)  AttributeError: 'RegistryContext' object has no attribute 'execute'  {code}    
Answer: 45895.0

User story: "The CModel has a large number of failure modes, largely dealing with different kinds of problems in the inputs, and a correspondingly large number of flags.  It also has some fairly complex logic determining which flags can be set simultaneously.  All of these combinations need to be tested.    DM-1574 may be useful in capturing these conditions from runs on real data."
Answer: 1927370.0

User story: "We need to assemble the basis for an integration test using HSC data, to protect HSC processing and obs_subaru from upstream changes.    This includes the assembly of the required data, a basic mechanism to test the mechanics of data release production, sufficient for the SQuaRE team to take it and incorporate it into the Jenkins system.  Addition of any scientific validation is deferred for now."
Answer: 485.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 have to set up a new set of slots that will be used to execute the overlapping thread of execution for alert production.   Because of limited resources at this time, this means reconfiguring the worker nodes to provide additional slots, and to split the worker nodes into two sets.    "
Answer: 23349.0

User story: "This story is a catch-all for preliminary conversations about LSE-140 with the new Calibration Instrumentation Scientist, <USER>"
Answer: 4.0

User story: "Pursue interactions with Telescope and Site personnel regarding LSE-75, and in particular the issues surrounding calibration data products for the wavefront and guider data analysis pipelines.    Covers work through the end of August 2015."
Answer: 67.0

User story: "Create a change request for LSE-75, the TCS - to - DM ICD."
Answer: 1.0

User story: "With the arrival of new Telescope & Site personnel, especially the Telescope Scientist, [~<USER>, prepare a summary of the current state of LSE-75 and its open issues."
Answer: 3259.0

User story: "work with John Rector on SUIT design document outline"
Answer: 914352.0

User story: "Work with Gregory on the SUIT design document outline    1.  Requirements flow down, making sure that we design the system satisfying the current requirements.  2.  Use cases collection. at least one typical use case in each major science theme  3.  Levels of different users  ** novice: treat the web portal as a archive to get some information, don't know much about LSST  ** novice expert: has some ideas of what special functions they would like, has some knowledge of LSST data  ** domain expert: knows LSST data very well and want some special functions ready to use  ** savvy expert: knows LSST data very well and like to use API to their own programming    4. functions for all different levels of users  5 system design   ** system diagram  ** details of the different parts  *** Firefly server  *** Firefly client  *** Firefly server extension  *** Firefly JavaScript API  *** Firefly Python API  *** Firefly Python API, Jupyter notebook, and other Python applications  *** workspace and level3 data  *** SUI web portal sketch, workflow  ** dependency on other capabilities of other institutes    6. development and test plan,  timeline  7. deployment plan                "
Answer: 914312.0

User story: "Attend UIUC weekly meeting and give support as needed. "
Answer: 48666.0

User story: "SUI/T design document outline.  "
Answer: 914366.0

User story: "Work associated with Workshop IV in the series, held at NCSA July 8-10, 2015."
Answer: 13.0

User story: "Working with Loi on the design of Firefly core system based React and FLUX frameowork  "
Answer: 136460.0

User story: "Working with Loi on the design of Firefly core system based React and FLUX frameowrk"
Answer: 48706.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "install DM stack, get familiar with the current DM task concept.   This is for getting ready to use task with Firefly server side extension capability.  Here is the link to the tutorial.  https://confluence.lsstcorp.org/display/DM/Getting+started+with+stack+development"
Answer: 398867.0

User story: "Prepare for and attend an OCS-subsystems workshop at SLAC May 6-8, 2015."
Answer: 86.0

User story: "Prepare for and attend a half-day teleconference on OCS issues."
Answer: 8.0

User story: "Provide the first draft  of detailed content required for authorization and authentication system from SUIT point of view to NCSA. "
Answer: 1095599.0

User story: Re-synchronize with prior work after vacation.    Write up page both engineering and facility database ingest  and use, incorporate suggestion and comments from KT and GDF.    Clean up (better name entities, and move for better narrative flow) pages about the general thing that is called "level 1",  -- the context diagram and supporting prose for further descriptions,  Review internally with Jason, Steve and Margaret.    Create a revised  diagram that would change LDM-230 specifications. (all non crosstalk corrected data flow into a disk buffer, and and an new archive tasks empties it)  to make specifications consigned with the refined specifications on the page above.  Yet to write the prose....    These pages are in my personal pages in the LSST confluence area.        
Answer: 1.0

User story: "Propose a preliminary design for Firefly core using React and FLUX framework. "
Answer: 49001.0

User story: Recent changes to meas_astrom accidentally removed a function readMatches (copied below). Please restore it, preferably in its own module (though if someday we have more small python functions we may want a utils.py module).    Also please include a unit test.    {code}  def readMatches(butler, dataId, sourcesName='icSrc', matchesName='icMatch', config=MeasAstromConfig(), sourcesFlags=afwTable.SOURCE_IO_NO_FOOTPRINTS):      """Read matches, sources and catalogue; combine.      @param butler Data butler      @param dataId Data identifier for butler      @param sourcesName Name for sources from butler      @param matchesName Name for matches from butler      @param sourcesFlags Flags to pass for source retrieval      @returns Matches      """      sources = butler.get(sourcesName, dataId, flags=sourcesFlags)      packedMatches = butler.get(matchesName, dataId)      astrom = Astrometry(config)      return astrom.joinMatchListWithCatalog(packedMatches, sources)  {code}  
Answer: 161402.0

User story: "Spend about one hour per day to read up on JavaScript and React framework. Get ready to work on some of the JavaScript programming in Firefly"
Answer: 187118.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: "Implement RFC-62 by using {{config}} rather than {{root}} in config override files for the root of the config.    Note that I propose not modifying astrometry_net_data configs because those are numerous and hidden. They have their own special loader in LoadAstrometryNetObjectsTask._readIndexFiles which could easily be updated later. if desired. An obvious time to make such a transition would be when overhauling the way this data is unpersisted."
Answer: 7065.0

User story: DM-3359 demonstrated the feasibility of running jenkins builds in one-off docker containers but did not cover investigation of user creation of containers nor did it include a puppetized deployment.    Per build containers are desirable for a number of reasons but the largest motivation is allowing DM developers to define their own jobs without disrupting the "sanctity" of the lsstsw build slaves.
Answer: 398857.0

User story: "The question that is being raised is how much it would cost to keep more than the last two Data Releases on readily-accessible storage (i.e. spinning disk). This will require changing several numbers and formulas in LDM-141, the storage sizing  model, observing the results as they propagate through LDM-144, the cost model,  and checking to make sure that everything makes sense and nothing has been overlooked. It looks like an answer to this question will be needed somewhere between a month and three months from now."
Answer: 19922.0

User story: "Prepare for and attend the OCS-DAQ-CCS-DM workshop in February 2015. This is primarily intended to continue to make progress on LSE-70 (the definition of the OCS interface to the subsystems) and therefore prepare for updates to LSE-72 in time."
Answer: 17.0

User story: "Prepare for and attend the OCS-DAQ-CCS-DM workshop in November 2014.  This is primarily intended to review the status of LSE-70 (the definition of the OCS interface to the subsystems) and therefore prepare for updates to LSE-72 in time."
Answer: 40.0

User story: "Expose image XY readout at cursor point function in JavaScript API"
Answer: 50289.0

User story: "expose region overlay on image function through JavaScript API"
Answer: 38705.0

User story: "Provide option to reverse the axis for XY plot, one example is the magnitude value convention. "
Answer: 252260.0

User story: "Time series plot"
Answer: 630440.0

User story: "When there are error or uncertainty for a data point, there should be option to plot the error bars in the XY plot.     The 'hat' for error bar is not plotted in most cases, only visible when there are less than 20 data points.   User can reduce the points to plot by applying filters in table, or use rubber-band in plot. "
Answer: 687140.0

User story: "Use a session at the LSST 2015 all-hands meeting to prepare for LSE-68 work in the Winter 2016 cycle."
Answer: 21.0

User story: "Carry out the CCB review, respond to questions, support final implementation of updated document."
Answer: 2.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "SUIT needs certain specific information through DAX meta service when searching for meta data. For Example, what kind of table it is, does it have spatial index to search by position, which set of (ra, dec) columns is the primary one, etc?"
Answer: 400151.0

User story: "LCR-357 was an outline of work to be done, based on discussions with the Camera DAQ staff.  This task is to generate an actual proposed document change for the CCB."
Answer: 4.0

User story: "Collect changes and submit a change request to LSE-68 for a mid-phase-3 update to the document, covering clarifications on guider data and image identification, among others.    Includes preliminary work to prepare for change request."
Answer: 9.0

User story: "Backend is a class that connects to mysql and can cause the worker to terminate. It is buried in the Foreman and should be renamed and have the class defined in a header file so that it is more visible. The class should also be available to use for any other in memory tables. "
Answer: 600362.0

User story: "Existing butler unit tests should run without an sqlite database registry."
Answer: 93590.0

User story: "We need to include fields added by other tasks (e.g. the deblender) or the source minimal schema (e.g. parent) in transformed catalogs.  I believe it should be safe to assume any such fields can simply be copied (i.e. they do not require any actual transformation - they're mostly flags), but we do need to make the list of fields to be copied by this mechanism dynamic."
Answer: 2087157.0