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: There are several region issues I have found when comparing old and new API:  (1, 2, 3, 7, 8 are implemented in DM-7147, 4, 5, 6 are implemented in DM-7190)    1. The default coordinate system when "pure numbers" are used should be pixel positions on the original image.     The [spec](http://ds9.si.edu/doc/ref/region.html) says the following:   "...the default system is implicitly assumed to be PHYSICAL. In practice this means that for IMAGE and PHYSICAL systems, pure numbers are pixels."  'If no coordinate system is specified, PHYSICAL is assumed.'    More explanation can be found [here](http://hea-www.harvard.edu/RD/funtools/regcoords.html)    2. PHYSICAL coordinate system does not mean screen pixels. The question is whether we can always use image pixels.    _If wcs is "physical", WCS is the pixel coordinate system of the original image, which may be different from the pixel coordinate system of the current image, if the current image is the result of an imcopy or other geometric transformation operation. In the "physical" coordinate system the ltv, ltm and the axis attribute parameters wtype, axtype, units, label, and format may be edited, but the FITS parameters crval, crpix, and cd cannot_. [reference](http://stsdas.stsci.edu/cgi-bin/gethelp.cgi?wcsedit)    3. When used in API, the actions are dispatched one after another. For example, dispatchCreateRegionLayer might be issued before image plot has finished loading. Can we make regionCreateLayerActionCreator wait for image with plotId to finish loading?     More details: If I create a region layer with a few regions in image coordinates right after firefly.showImage, two errors are loaded to console:   doOnAppReady: uncaught TypeError: Cannot read property 'getImageCoords' of null(…),   RegionFactory:602: Uncaught (in promise) TypeError: Cannot read property 'getImageCoords' of null(…)    4. When a region is selected, yellow dashed line appears around it. On zoom the line does not change color.    5. Can not add empty region. Line 124 of the test script.    6. Can not add or delete regions after the first one. (Load test script, click Show Regions, then Add Region, line 121 of the test script) When there is one region in the layer and you are adding another region with a different position but everything else the same, the added region is perceived to be the same.    7. It's possible to select regions only in in the first region layer added. In the other layer, you can sometimes see the selection blinking, but it does not stay.    8. If region format is wrong, for example  'image; box 40 400 72 72 # color=blue' instead of  'image; box 40 400 72 72 0 # color=blue',   the region is silently ignored, no warning or error is logged to console.    9. We need region selection action to support callbacks on region selection. (Currently the selected region is "calculated internally based on the distance between the region and  mouse readout.)
Answer: 52227.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: "Sahand progress on installing and deploying a cluster automatically with Kubernetes. After this is completed we will use a user case example of running in cluster managed by Kubernetes/Spark"
Answer: 34646.0

User story: "Di progress on understanding the possibility of using websocket locally to communicate with JS9 instances on local server. In this case we wouldn't need an external server and communication can be bi-directional. Now is only in one direction (mostly) when running Js9 locally "
Answer: 34635.0

User story: "Di progress on adding extra features to JS9, including load and saving regions in the local notebook server, same with files. "
Answer: 34637.0

User story: "DM-6312 might imply that the python being used to run SCons is not the same as the python we want to use when running the code. Update the EUPS cfg file to use python from the PATH rather than SCons python."
Answer: 11773.0

User story: "The aim is to package an experimental Jupyter widget with limited functionality so that it can be installed like other Jupyter widgets. Only a small set of Python and Javascript code will need to be packaged -- the widget will connect to a Firefly server. The [Jupyter widget cookiecutter|https://github.com/jupyter/widget-cookiecutter] provides a template.  "
Answer: 52194.0

User story: "{{pex_exceptions}} needs to be updated to support Python 3."
Answer: 13514.0

User story: "Modify the existing Firefly-Standalone build in Jenkins to use IPAC's github.  Make sure github auto-releases still works."
Answer: 2539.0

User story: "We need to support regular Firefly distribution builds (with bundled tomcat server),  similar to the builds we did in lsst firefly repository before the conversion.    This is to get Camera team started with new API."
Answer: 11233.0

User story: "Convert API documentation and code examples to get Camera team started with the converted Firefly FITS viewer. "
Answer: 13201.0

User story: "This is a problem with uploads, large image loads, and Atlas.   When a big image is loading the user does  not get feedback.  The problem is the the UI is not creating the ImageViewer soon enough."
Answer: 10344.0

User story: "Analyze the bug described in DM-6462"
Answer: 4.0

User story: "The visualization system is not update the memory accounting for the caching system."
Answer: 4221.0

User story: "Assign first thoughts responsibilities to all software primitives and algorithmic components.  This is my take.  John will have his own take."
Answer: 144065.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: By default, our builds are not optimised ({{-O0}}), which requires everyone who doesn't want to wait until the heat death of the universe to set {{SCONSFLAGS="opt=3"}}, but other packages that are built with scons may not recognise this.  This default is also contrary to the standard practise for open-source software, which is that by default builds are optimised.  I will change the default optimisation level to {{opt=3}} from the current {{opt=0}}.  I will also add support for {{-Og}}.    This change was approved in RFC-202.
Answer: 814.0

User story: "We may want to disable boost.python in the build. There are hints that there are problems with python3.5."
Answer: 17116.0

User story: "Look at databases located at *NCSA* so far to assess if they cover the full survey. The databases to be evaluated are mentioned in [DM-6905].    According to [S13 Testing Plan|https://dev.lsstcorp.org/trac/wiki/Summer2013/ConfigAndStackTestingPlans/Instructions] the S13 DRP dataset was split into two regions with an overalp used for cross-site verification:  * *NCSA*: -40< R.A. < +10  * *IN2P3*: +5 < R.A. < +55    Hence a goal of this task is to identify which previously located candidate databases and files correspond to either or both of these ranges."
Answer: 6103.0

User story: "Bokeh 0.12 was just released and some issues are being fixed, before updating the bokeh version used in SQUASH we propose to wait for 0.12.1 release.  "
Answer: 16386.0

User story: "Motivated by the deviation seen from build 156 to 157 in  https://squash.lsst.codes/AM1 (caused by a commit in meas_algorithms package), and other deviations seen later as well, we want to show the list of packages that changed in the current build with respect to the previous build and link to the the git commit URLs to easily identify what caused that deviation."
Answer: 153699.0

User story: "Calculate the ellipticity, and the residual ellipticity (moments - PSF).    Add to calculated SRD statistics.    This will involve thinking about things on an image-by-image basis, which is the natural and largely SRD-specified way for considering ellipticity."
Answer: 983781.0

User story: "Add the capability to match across filters.    1. Create color-color diagrams  2. Analyze performance metrics as a function of color."
Answer: 1862890.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: "Issues with coverage:     * Toolbar icon not showing up  * If only one point that is no coverage image (or one table with many records but has the same ra,dec values)  * CAN’T REPEAT: In expanded mode, magnifier fails when image fills the visible space entirely (seems to affect 'Coverage' image only)  * Missing feature: before migration, in expanded mode, the toolbar had an 'added image' button which was bringing an image search panel to add images to the current view. => _move to:_ DM-7068  * CAN’T REPEAT: if marker/footprint overlay is clicked, that doesn't activate the image viewer and doesn't update the layer dialog either.  * in laptop screen size, the toolbar is not fully visible, scrolling from left to right only move the background but not the expanded panel.  * CAN”T REPEAT:in expand mode and zoom 'fill the visible space' clicked, the magnifier image doesn't show anything from the coverage image, can be reproduced in http://localhost:8080/firefly/demo/ffapi-highlevel-test.html (BTW, it happens in finderchart in OPS on any image in expanded mode ( ? ) )  * Readout is sometimes off the screen  * Expanded then return to normal: zoom is not adjusted correctly    If we find a way to repeat the items marked 'CAN'T REPEAT' they should go into another ticket.  Maybe in DM-7068 if it is still opened.  "
Answer: 12933.0

User story: "Remove pex_logging dependency on pipe_tasks."
Answer: 178680.0

User story: "Per RFC-203, switch Task's logs from using pex.logging to lsst.log in pipe_base and pipe_tasks (stage 2)  This implements the main idea of RFC-203 and migrate the logging framework used in the task framework."
Answer: 61114.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: {{MemoryTestCase}} (or a derivative thereof) must be run as the last of all tests in a module in order to properly catch leaks.    [Our documentation|https://developer.lsst.io/coding/python_testing.html#memory-and-file-descriptor-leak-testing] implies, and [SQR-012 states|https://sqr-012.lsst.io/#memory-test], that this can be achieved by listing it as the last test case in the file.    This works for py.test, but not when using plain old unittest: the latter does not, so far as I can see, guarantee any sort of ordering as a matter of principle, and, in practice, it sorts things lexicographically (it uses whatever order it gets from running {{dir()}} on the test module, and I don't *think* that's guaranteed to be anything in particular).    For example, consider [{{testAstrometrySourceSelector.py}}|https://github.com/lsst/meas_algorithms/blob/master/tests/testAstrometrySourceSelector.py]. I made the following change to introduce a memory leak:    {code}  --- a/tests/testAstrometrySourceSelector.py  +++ b/tests/testAstrometrySourceSelector.py  @@ -70,8 +70,9 @@ class TestAstrometrySourceSelector(lsst.utils.tests.TestCase):           self.sourceSelector = sourceSelector.sourceSelectorRegistry['astrometry']()         def tearDown(self):  -        del self.src  -        del self.sourceSelector  +        pass  +        #del self.src  +        #del self.sourceSelector         def testSelectSources_good(self):           for i in range(5):  {code}    Py.test catches it:  {code}  $ py.test-2.7 testAstrometrySourceSelector.py  [...]  testAstrometrySourceSelector.py .........F  [...]  {code}    But simply running the test suite does not:  {code}  $ python testAstrometrySourceSelector.py  ..........  ----------------------------------------------------------------------  Ran 10 tests in 0.105s  {code}    Rename the test case:  {code}  @@ -144,7 +145,7 @@ def setup_module(module):       lsst.utils.tests.init()      -class MyMemoryTestCase(lsst.utils.tests.MemoryTestCase):  +class xMyMemoryTestCase(lsst.utils.tests.MemoryTestCase):       pass     if __name__ == "__main__":  {code}    And boom:  {code}  $ python testAstrometrySourceSelector.py  .........  54 Objects leaked:  {code}    Based on a very quick check, I think [sconsUtils runs tests by simply invoking {{python}}|https://github.com/lsst/sconsUtils/blob/f9763768d999cefa4c26b9f3418c28394dfb38df/python/lsst/sconsUtils/tests.py#L133], and I'm pretty sure that this is hard-wired into the muscle memory of many developers. In these cases, memory tests written following current guidelines won't be being properly executed.    
Answer: 7275.0

User story: "After combing through the current SUIT requirements, we feel that we need to re-organize and re-write the SUIT requirements to be in-line with SUIT vision document.    This story will be producing the first draft of the rewrite. "
Answer: 178155.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 scanned parts of ldm-151 (draft branch) and ended up making few minor fixes, see branch u/<USER>201607-fixes, feel free to accept them or ignore :). Also, I noticed few other things that I haven't fixed:    * consider refreshing author list, eg I know Frossie spent  time contributing  * SUI --> SUIT?  * break figure 1 into two and turn 90 degrees?  * figure 2 turn 90 degrees?  * "The data products produced by Alert production are given in table ." -  missing table number. This is on page 21  * "this would likely only be able to sample the selection function over a subset"  this sentence seems unfinished  * "A catalog of Sources with measured features (as described in ??)."  Maybe you want to refer to LDM-153 (db schema)?  * OCS introduced on page 17, no need to reintroduce on page 23?  * page 24: "Source detection to the 5σ limit of" something is broken here
Answer: 419175.0

User story: "The current {{matchOptimisticB}} algorithm uses a sophisticated search to initially solve for the mapping between the source catalog and the reference catalog using only the brightest ~hundred stars, but then verifies this solution by matching the entire contents of the source and reference catalogs by a brute-force search. This search is repeated several times as the fit converges. In crowded fields these catalogs can be very large, and matching overall can take ~30 minutes per CCD.    Replacing this brute force search with a KD tree should provide a functionally identical result at greatly reduced computational cost. "
Answer: 142480.0

User story: "Currently SQuaSH dashboard works only with a fixed dataset. We want to ingest measurements of metrics computed by validate_drp for multiple test data e.g CFHT, DECam and HSC. In order to handle multiple datasets, we need a new model in SQuaSH  and extended the job API to ingest the measurements for different datasets. The user must be able to selected in the interface the dataset to be displayed."
Answer: 31865.0

User story: "(Actual assignee: Samuel Piehl)     Have a script to show what visits are in what tracts/patches. This is especially useful for running coadd making and processing (e.g. makeCoaddTempExp, assembleCoadd) with runOrca and HTCondor, as the dataId of the jobs need to be specified. So this script's output will be in the format of a runOrca input file.     "
Answer: 25768.0

User story: "This ticket captures some testing practices from https://ep2013.europython.eu/media/conference/slides/obey-the-testing-goat-rigorous-tdd-for-web-development-with-django-and-selenium.pdf  that we intend to use in the SQuaSH prototype.     - Use selenium to test user interactions  (functional tests)  - Use unittest module for unit tests   - Include some documentation about testing in sqr-009 "
Answer: 374377.0

User story: "Review the composite dataset description document with [~<USER> and [~<USER>, and any others who may be interested (e.g. post on community or do an RFD)"
Answer: 60560.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: "Write a description of composite datasets as I understand them based on the email KT sent on May 20 (attached), and on conversation I had with KT and Fritz on July 20."
Answer: 20019.0

User story: "With the transition of Tasks' logs from lsst.pex.logging to lsst.log (DM-6999), suggest changesets using lsst::log instead of pex::logging in meas packages that has dependency on Tasks' logging framework. "
Answer: 62410.0

User story: "Suggest a changeset with lsst::log instead of pex::logging in afw"
Answer: 82418.0

User story: "Use lsst::log instead of pex::logging in daf_persistence and daf_butlerUtils"
Answer: 74956.0

User story: Following [~<USER>'s [recent changes to the Butler|https://community.lsst.org/t/im-checking-in-butler-changes-related-to-rfc-184/959], ci_hsc is failing as follows:    {code}  [2016-07-20T07:57:31.954576Z] Traceback (most recent call last):  [2016-07-20T07:57:31.954643Z]   File "/home/jenkins-slave/workspace/stack-os-matrix/compiler/gcc/label/centos-7/python/py2/lsstsw/build/ci_hsc/bin/validate.py", line 3, in <module>  [2016-07-20T07:57:31.954664Z]     main()  [2016-07-20T07:57:31.954732Z]   File "/home/jenkins-slave/workspace/stack-os-matrix/compiler/gcc/label/centos-7/python/py2/lsstsw/build/ci_hsc/python/lsst/ci/hsc/validate.py", line 53, in main  [2016-07-20T07:57:31.954756Z]     validator.run(dataId)  [2016-07-20T07:57:31.954825Z]   File "/home/jenkins-slave/workspace/stack-os-matrix/compiler/gcc/label/centos-7/python/py2/lsstsw/build/ci_hsc/python/lsst/ci/hsc/validate.py", line 155, in run  [2016-07-20T07:57:31.954851Z]     self.validateDataset(dataId, ds)  [2016-07-20T07:57:31.954923Z]   File "/home/jenkins-slave/workspace/stack-os-matrix/compiler/gcc/label/centos-7/python/py2/lsstsw/build/ci_hsc/python/lsst/ci/hsc/validate.py", line 117, in validateDataset  [2016-07-20T07:57:31.954956Z]     mappers = self.butler.repository.mappers()  [2016-07-20T07:57:31.954991Z] AttributeError: 'Butler' object has no attribute 'repository'  [2016-07-20T07:57:32.023212Z] scons: *** [.scons/ingestValidation-903342-100] Error 1  {code}    See e.g. https://ci.lsst.codes/job/stack-os-matrix/13274/compiler=gcc,label=centos-7,python=py2/console.    Please fix it. 
Answer: 74.0

User story: The current settings in psfex will only turn on oversampling only if the seeing is < 0.5", even if you have configured it do oversampling. This needs to be changed so that everything is determined by the config parameters.    We have also seen on HSC data that oversampling in general does not work well in psfex.  We need to change the current configuration which does 2x oversampling to just use the native pixel scale.
Answer: 9144.0

User story: "It should be possible to set Flag columns with bool arrays or scalar values.    This should just be a matter of adding a {{set}} overload or two around line 100 of {{specializations.i}}."
Answer: 2027366.0

User story: "Markers don't show up in PNG download"
Answer: 90612.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "DM-6521 improved Log class interface by replacing some static methods with non-static. Qserv is currently using couple of static methods which were retained in Log class for the duration of this migration. Once updated log package is released update qserv code to use new non-static methods and remove static methods from Log class after that."
Answer: 125854.0

User story: "There is an issue in the density plot for displaying the legends. Highcharts does not support the setting of the symbol size in the legends. So when the symbol size is too small or too large, the legends are not displayed.     We don't want to do too much workaround currently. This ticket is to watch for the Highcharts update. "
Answer: 357565.0

User story: "Please add a note to DMTN-020 describing the changes to release milestones discussed at the [DMLT meeting of 2016-07-18|https://confluence.lsstcorp.org/display/DM/DM+Leadership+Team+Meeting+2016-07-18]."
Answer: 3829.0

User story: "These docs are currently borken in CI -- just need to have the dates reformatted in their metadata.yaml"
Answer: 113.0

User story: "Update qserv install docs per new info at https://pipelines.lsst.io/install/newinstall.html"
Answer: 24426.0

User story: "- Update release notes  - Publish docs and bump version numbers"
Answer: 63834.0

User story: "[~<USER> has discovered that we don't have test coverage for converting less-common Eigen types to Python.  This is not urgent, but it should be fixed."
Answer: 1855376.0

User story: "Bug fixes for using the new {{LoadIndexedReferenceObjectTask}} and its associated components."
Answer: 8514.0

User story: It is well known that building, setting up a stack, and interactive devel work with those operations on NFS has performance issues.  Hence the official shared stack on lsstdev uses /ssd .    However,  a shared stack on NFS is useful and adequate for one important  use case --   users need a stack that can be used for small productions on the local condor pool currently available  on lsstdev.   For this use case multiple "source"/"setups" on a node/against the file system  can be avoidable by using a script to directly declare the environment.  run_orca /ctrl_orca supports this feature.       While GPFS is coming soon, there is expected to be a transition period of 2-3 months and so the NFS file system and a stack on it can serve users for an interim period.   If building a shared stack on NFS is not a heavy labor, we think it is worth the effort for this interim period, and as such make this request for a shared stack on NFS. 
Answer: 23135.0

User story: "Jim has put together a fairly complete software primitives section.  This task is to read it over from the perspective of Alert Production and expand/refine where necessary."
Answer: 1518.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 variance rescaling we're doing on the coadds (to try to account for missing covariance) is currently causing the HSC weak lensing team a lot of problems, because they affect every uncertainty value we produce and they're hard to include in simulations that otherwise look a lot like the data.  I think we need to disable this - and probably take it out of the codebase entirely, just to be safe - before the next major HSC release, even if we don't have anything to replace it.  I think it's doing more harm than good.  That will require changing coadd detection thresholds to compensate, I think."
Answer: 685678.0

User story: "Formalize the prototypical implementation of health checks and associated policy into 'what to do' actions"
Answer: 66387.0

User story: "Document policy regarding action to take when various components are found to be unhealthy. This can vary depending when 1 component type (Forwarder) is offline versus 21 Forwarders offline. In addition, plans must be formulated for addressing the point in the exposure cycle when the health failure occurs."
Answer: 66390.0

User story: "Build testing mechanism to inject faults into into health framework and stub code to address health check failures"
Answer: 36192.0

User story: "Implement and overlay health check mechanism on existing messaging control code. Prototype and gather timing information to determine optimal frequency of checks and the location in the exposure cycle when these checks should occur."
Answer: 36195.0

User story: "Consider creating a dictionary of code objects to represent messages. Currently message bodys are built on the fly - evaluate pros and cons of switching to a message factory pattern. Message types are not a very extensive list, but switching to object implementation could increase maintainability of code."
Answer: 36212.0

User story: "Add new ACK message types to existing Dictionary documentation."
Answer: 36215.0

User story: "New entries in message dictionary must be added and tested with the existing messaging code base."
Answer: 44738.0

User story: "Enumerate ACK messages for all primary message types. Prototype both blocking and non-blocking acknowledgement aggregator that works via timeout, behavioral change, etc. This is related to DM-6411"
Answer: 36220.0

User story: "Audit format of existing messaging and adjust according to 'wants' not task 'needs'...that is, msg body format that exists now is sufficient to fulfill tasks, but destination components must receive a broader description of overall system state. This will allow all components to log a more comprehensive snapshot of current state and is needed for troubleshooting. These additions to the message dictionary will be configurable like a logging priority levels function, and additions to message payload can be turned off for typical nightly operation."
Answer: 36243.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "While [~<USER> has commented that the outlines are probably good enough for planning work (and I thnk that's broadly true), the lack of text in the algorithmic components section did occasionally lead to some misunderstandings in [~<USER>'s first review pass, so I think I should flesh that out with text sooner rather than later.    In this issue, I'll stick to sections that no one else has added text for, but eventually I'll also need to work with [~<USER> and perhaps others to ensure that section has a consistent level of detail and focus."
Answer: 117954.0

User story: "It's recently become apparent that we need to at least consider using different background estimation techniques for different kinds of measurements.  This is will require some thought to work into our current processing plans."
Answer: 71663.0

User story: "Study the Jupyter notebook and understand the concept of Jupyter widget. Try to make a simple Jupyter widget that works with Firefly visualization."
Answer: 28789.0

User story: "Will address comments from [~<USER>, [~<USER>, and probably [~<USER>."
Answer: 330.0

User story: "This is -expected to be- a document specifying the final Startup scaffolding disposition. If specification is not final, it will assess which requirements for this epic were not reached.    Document available at:  https://confluence.lsstcorp.org/display/JP/L1+Cold+Start+Procedure"
Answer: 61917.0

User story: "If Kubernetes is the answer for startup provisioning which it is hoped to be, apply it to NCSA L1 machine startup requirements."
Answer: 37782.0

User story: "After Kubernetes is running as a simulated base site start up and provisioning tool, begin evaluation with fault injection such as the need for hot swap machine failover, sudden changes to Network topology and name server entries, etc."
Answer: 37788.0

User story: "Implement a Kubernetes instance running on the Nebula cluster and begin configuration for testing Base site Startup behavior."
Answer: 37791.0

User story: "Kubernetes is a machine provisioning application that has potential to assist LSST Startup scaffolding such as Just In Time personality assignment, persisting config settings, etc."
Answer: 37793.0

User story: "List all dependencies for specific processes that must be previously up an running. Establish the settings for 'time zero' on the startup timeline, such as purging queues, clearing specific data stores, arranging file system for startup, etc."
Answer: 37802.0

User story: "Plan Base machine needs for Startup, including those processes that must run together on the same physical host (such as databases resident in memory needed by other processes)."
Answer: 37806.0

User story: "This is a Prototype DAC (PDAC) and the access to it is limited. We need to draft a access policy. "
Answer: 44331.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 DPDD does not currently list any measurements that result from measurements on individual snaps or differences between snaps.  However, I have heard plenty of informal discussion about such quantities.  We need to clarify what we will measure on snaps (if anything), and codify this in the DPDD.  "
Answer: 1183629.0

User story: "Support circular selection by choosing a point and dragging the mouse across the image. The callbacks and functions supported for rectangular selection should be also supported for circular selection.    (Circular region selection is a part of Paul O'Connor's visualization wish list and is a long promised feature.)         Copied from GitHub(XW 1/18/18)    This development includes,   * adding circular selection support for area selection.   * change select area icon on the tool bar from on/off button to a on/off button with dropdown selection at off state. The dropdown list supports the selection for 'rectangular selection', 'elliptical section' (circular area).   * add stats calculation for circular area selection on both rotated and non-rotated images.   * fix stats calculation for rectangular area selection on rotated image case.   * update 'select catalog' and 'filter catalog' functions for circular area selection.    Test:   - Do image selection:   1. Click 'select area' icon (on 'off' state)  to get selection dropdown list,   2. Select either 'rectangular selection' or 'elliptical selection' (this will move the 'select area' icon into 'on' state)  and draw a selected area by choosing a point over the image and dragging the mouse across the image.              3. Click  'select  area' icon to move it back to 'off' state to remove the selected area.             4. Select one of the extension buttons for 'crop', 'stats', 'zoom', or 'recenter' while either 'rectangular  selection' or 'elliptical selection' is selected.   - Repeat the steps by rotating the image first.     - Do catalog selection next:   repeat the 'select area' steps done as image selection, and select one of the extension buttons for 'crop', 'stats', 'select mark data', 'filter', 'zoom' or 'recenter' while either 'rectangular selection' or 'elliptical selection' is selected."
Answer: 799647.0

User story: "This is effectively a port of [HSC-110|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-110] though, due to the considerable differences in bookkeeping for the SdssShape code, this will be more of a reimplementation.  "
Answer: 13982.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 turning on CModel a more robust extendedness classifier relieved that many of the stars being used as PSF candidates were being classified as extended as shown in the attached plot. This plot was generated from the output of ci_hsc. Work should be done to determine why these stars are mistakenly being selected and fix the bad behavior. Additionally the [temporary work around in ci_hsc|https://github.com/lsst/ci_hsc/commit/6daf43ca41b6d192b6e1dbedb60cde0bec90b615], where the success criteria for validate sources in validate.py should be reverted from 85% to 95%."
Answer: 125759.0

User story: "While investigating DM-6529 I found that LSST generally finds fewer reference objects than HSC when doing astrometry.  For the CCDs on the edge of the focal plane the number of stars was typically very low causing frequent failures.  I found that in the HSC code, there is a distortion being applied that shifts the exposure bounding box when getting objects from the reference catalog.  This distortion is not being applied in the LSST code."
Answer: 16306.0

User story: In DM-4887 we introduced a new measurement post-processing system which we called "afterburners".    The term "afterburner" is overloaded and applied in multiple contexts. To save confusion, please rename this system to something less ambiguous. Best if we can do this soon, before this usage spreads.
Answer: 76321.0

User story: "To understand better the load on L1 database I need a more or less adequate set of queries running against the databases. AP-generated queries should be a good start so a simple script that simulates what AP does will be very helpful. Sure I don't need any actual image processing or alert production, only the parts which read/write data to the database on per-visit basis."
Answer: 27416.0

User story: "DM-6629 provided a new API for consistently specifying metrics, their specification, and reporting results of measurements.    This API can, and should, be used beyond validate_drp for any code that wants to submit metadata to SQUASH. This ticket will provide user documentation on the API base classes to help other developers write new metrics and measurements."
Answer: 33102.0

User story: "If {{last_revised}} and {{version}} are not present in metadata.yaml, then the Git commit date and branch name should be used while building metadata instead.    Also updates lsst-technote-bootstrap to take advantage of automated metadata for new projects."
Answer: 1355.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 try to read in FITS tile compressed calexps (created with either cfitsio's fpack or astropy.io.fits), the files appear to be read correctly, but something from the headers appears to be mangled. I have not tracked down the problem in detail, but running jointcal on a butler repo containing the tile compressed calexps results in bad fits, while running it on the uncompressed files works fine.    The problem likely lies in how we are extracting header information that may be modified as part of the tile compression process (compressed HDUs are actually binary tables, not images).    This ticket came out of a [discussion on community|https://community.lsst.org/t/fits-tile-compression-support-in-the-stack/909]."
Answer: 676654.0

User story: "There are several issues with tab titles:  - Sometimes we don't want them to be resized at all (like in Images panel since the tabs are all fixed at begining)  - When titles are resized, their size is proportional to the length of the title, use fixed-size tab length instead to make sure no tab is too long.    Please add other tab panel issues here."
Answer: 51955.0

User story: When a table is filtered from the expanded mode, the layout is changed back to unexpanded.    It looks like the issue is more general: table actions trigger layout changes, which are not always right. For example, TABLE_REMOVE action while in a dropdown makes the  dropdown to get closed. I've traced it to FireflyLayoutManager.js:layoutManager generator function.    Test sequence in firefly:   - When a table is loaded, open "Charts" dropdown, select Col link for X, then select Col link for Y. (At this point the previous table is removed).  - TABLE_REMOVE action on the second click triggers dropdown to go away.   
Answer: 19757.0

User story: "Need to add filter editor to the chart toolbar. Filter editor should be without selectable rows."
Answer: 22904.0

User story: "http://maia.usno.navy.mil/ser7/tai-utc.dat has already been updated."
Answer: 1872174.0

User story: "Locate and evaluate a dataset of SDSS Stripe82 which is going to be used for testing the prototype DAC."
Answer: 23316.0

User story: "Several visualization tools will be very helpful to fully understand the effect of DCR correction algorithms and their failure modes.   * A function that generates difference images with the sources used for calibration and/or psf fitting marked.  * A visualization that indicates the spectral type of each source in an image. This could be a mask overlay where the color corresponds to the spectral type.  * A visualization of the coarse spectral resolution model built for DCR correction"
Answer: 607568.0

User story: "(actual assignee: Samuel Piehl)     Sometimes it is useful to know where the CCDs are on the plot. Add an option to label the CCD numbers. "
Answer: 11665.0

User story: "Connect all of the parts together."
Answer: 30573.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: "Use some type of known data (image) to load and test into the buttler. Data types might include DECam MEF images of single-plain image files from simulations."
Answer: 3291.0

User story: "Get data stream (module?) from Jim into a fits file than can be loaded subsequently to the butler."
Answer: 19180.0

User story: "ButlerFactory is vestigial and should be removed (per KT).   There are maybe a dozen packages that still use it and these should be changed to use the Butler initializer directly - either 'new' style Butler(outputs=...) or 'old' style Butler(root=..., mapper=...., etc)"
Answer: 1873575.0

User story: "Our colleagues on HSC have reported a non-deterministic astrometric solution being generated by the stack. That's clearly a bug, and will have to be fixed (and it might be HSC specific). However, it's notable that this varies with the number of cores being used to execute the stack. That's hard for developers to spot when running tests on their own systems, but it would be easy to catch by varying the (virtualized?) hardware environment when running automatic regression tests."
Answer: 1873606.0

User story: "Some issues came up during DM-6300 which indicated that a more controlled set of tests would be required than the random Great3Sims tests to understand the behavior of NGMIX LMSimpleShape.      LMSimpleShape appears to fail computing moments on low SNR objects.  It also shows pretty wide variation in shear bias which did not show up with CModel.    The needed tests with would include controlled profiles (Gauss, Dev, and Exp), controlled SNR, and controlled q, theta, and flux.  This should separate out the causes of failure and shear variation which we have seen."
Answer: 18837.0

User story: "Secure access to machine(s) with the LSST stack. This includes installation on local desktop/laptop."
Answer: 4268.0

User story: "Update certificate in LTD Keeper’s Kubernetes deployment with new lsst.codes cert."
Answer: 47.0

User story: "Split the memory mapping function from the memory locking function to allow the scheduler to initiate locking without blocking. Add additional memory tracking improvements in line with current thinking. Reduce lock contention. Add logging."
Answer: 54619.0

User story: "Address TBD additional emergent concerns "
Answer: 225596.0

User story: "Incorporate concerns, solutions and agreements into ConOps and any draft design notes."
Answer: 225596.0

User story: "Submit proposed operational design to Change Control for consideration. See LCR 780.  "
Answer: 225598.0

User story: "Work needed to support acceptance of change request, including addressing concerns with target side (SLAC) and specifying design to satisfy disaster recovery requirements.    Examples is understanding permissions and protections that would be in the reformatted EFD that otherwise would not have been, should we proceed with the proposed change."
Answer: 483303.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: Work with <USER>and others to understand architecture and use of "source" EFD. The goal is to understand the amount of volume of data that would be in reformatted EFD that otherwise would not have been, should we proceed with the proposed change.
Answer: 225597.0

User story: "Ongoing work on the pybind11 trial (see DM-6168) should eventually lead to nice and consistent wrapping of C++ code. This includes conventions on file / module / variable (for things like class objects) naming, import conventions, etc.  In addition we need some place to keep track of pybind11 gotchas.  This ticket aims to setup a template for such a document (as a technote) which is to be continuously updated as the epic progresses.  Reviewers of epic tickets can check against conventions set in this document to help ensure consistency."
Answer: 6705.0

User story: "On DM-6631, [~<USER> asserts:  {quote}  Command-line tasks are encouraged to be in the package that makes most sense for them, so IsrTask belongs in ip_isr. pipe_tasks is intended for tasks (command-line and otherwise) that need so many packages that they don't make sense being in a lower-level package.  {quote}    I certainly don't disagree – seems perfectly reasonable – but I've not seen it written down before. Please capture this in the developer documentation."
Answer: 2041878.0

User story: "Design and implement critical processes defined in the RACI document, coordinated with impending hire."
Answer: 88952.0

User story: "Run through process of detailing activities down to story size requested by the LSST EVM system.     Do detailed estimation of conops development and a sample of technical areas, and extrapolated based on number of epics, size of staff, and complexity of mission. Total = 100 hours for 3 months of activities for current staff size."
Answer: 1.0

User story: "Turn criteria into tabular comparison chart and respect test implementation constraints."
Answer: 24179.0

User story: "Review evaluation criteria with Fabio during his visit from CC-IN2P3 to NCSA.   https://drive.google.com/open?id=1Xhj6kaFEnNhCyRPskB6BCXYxgfs_9-cl3BRX9wCh1sE"
Answer: 1.0

User story: "Run planning process with local staff to appreciate amount of effort needed."
Answer: 16.0

User story: "DM-5695 created a functional implementation of a simple DCR correction algorithm. While it appears to successfully create template images with airmass and DCR matched to science images, it is computationally inefficient and appears to introduce new artifacts to the template image. This ticket is to enhance the simple algorithm in several ways:  * Convert to sparse matrices where possible  * use variance weighting of the images  * propagate masked pixels correctly  * Refine the algorithm to mitigate the new artifacts"
Answer: 38935.0

User story: "Given directions from interim project management, participation consisted of direct conversations with Kevin and Jacek plus background work talking to staff related to assembling a plan."
Answer: 75.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: "[~price] [recommends|https://community.lsst.org/t/centrally-defined-butler-datasets/841] a new way to define datasets common to all cameras in daf_butlerUtils, but modifying these yaml files require explicit lists of datasets to be modified in tests/cameraMapper.py.    If these tests are still useful, they need to depend on a minimal set of dataset definitions instead of the real ones."
Answer: 88094.0

User story: "After updating some latest changes, need to update documentation to explain the extend of this supertask and activator initial implementation."
Answer: 39169.0

User story: "Setup up one master node and one worker node."
Answer: 46030.0

User story: "Interact with qserv developers supporting deployment and NCSA's service provisioning environment. Learn and investigate aspects of qserv administration present in test deployment but not previously covered."
Answer: 89289.0

User story: "Review and gain administrative insight using the processes encoded in test scripts and other relevant features based on investigations in the prototype installations. For example, we may observe steps in test scripts to gain understanding of capabilities behind the scripts.    Provide comments on documentation where deemed helpful."
Answer: 89301.0

User story: "Di progress in writing a wrapper to interact between JS9 within Jupyter"
Answer: 36168.0

User story: "Di progress in getting JS9 to work in Jupyter notebook"
Answer: 36167.0

User story: "Di progress on Communication technologies for the web"
Answer: 36167.0

User story: "Di progress on learning these web technologies"
Answer: 16.0

User story: "Sahand progress on storage objects to be used in OpenStack"
Answer: 70851.0

User story: "Sahand progress on learning about automatic deploy and scalability of Docker containers using Kubernetes "
Answer: 36204.0

User story: "Sahand progress on getting Spark installed "
Answer: 36204.0

User story: "Sahand progress on learning Docker containers and potential automatic deploy in OpenStack"
Answer: 6.0

User story: "Sahand progress on getting familiar with Spark and use of the interface to  create a small Spark cluster in OpenStack"
Answer: 10.0

User story: "Sahand progress on getting the interface to access the Openstack interface using Nova Client"
Answer: 18.0

User story: "Sahand progress on learning about Openstack"
Answer: 19.0

User story: "Write a report on my visit to the SPIE conference in Edinburgh."
Answer: 16340.0

User story: "Split off from DM-6302."
Answer: 47201.0

User story: "Split off from DM-6302."
Answer: 8677.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "In the process of comparing HSC vs. LSST stack single-frame processing runs, we have been running with the Brighter-Fatter correction (BFC) turned off.  The reason for this to begin with was that is was not yet available on the LSST stack when we started these comparisons.  We also want to isolate as many features as possible in order to confidently assess their individual effects  The functionality was ported on DM-4837 with a default of *doBrighterFatter=False*.  This issue is to continue the single-visit run comparisons (see e.g. DM-5301, DM-6490, DM-6491) with BFC turned on on both stacks.    In particular, we are finding that slight differences in the reference stars selected for a given CCD can result in significantly different psf models.  Also, it was noted in DM-4960 that LSST seems to select reference stars to a brighter cutoff than HSC.  If a given field has a larger fraction of bright stars considered in the psf modeling, it is conceivable that it will be more significantly influenced by the BF effect, thus causing the large CCD-to-CCD variations seen in, e.g. DM-6490 (https://jira.lsstcorp.org/secure/attachment/28213/compareVisit-v1322-diff_base_PsfFlux-skyZp.png)."
Answer: 26012.0

User story: Contribute to Concept of Operations sections about Chilean, NCSA, and CC-IN2P3 facilities. Describing the "nuts and bolts" basics and summarize each facility's role in the LSST operational system.
Answer: 17113.0

User story: "For each diagram covering a key use case, provide a narrative interpretation of the key concepts being conveyed, including significant operational implications from the concepts being presented.    Fill in the table for the assigned use case areas.    Key use cases/concepts include: L1 production, L2 production, ITC incident response, ITC problem management."
Answer: 17122.0

User story: "Over recent months, the Camera subsystem has required substantial input from the DM team in using our codebase to process data from their “Monocam” instrument. It seems likely that requests for support from other subsystems within LSST will continue throughout construction. Who is responsible for handling and resourcing these?"
Answer: 141649.0