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: "The region serializer in: firefly/src/firefly/java/edu/caltech/ipac/util  * RegionFactory.java    Region container data structures files in : firefly/src/firefly/java/edu/caltech/ipac/util/dd    * ContainsOptions.java  * Global.java  * RegionFileElement.java  * RegParseException.java  * Region.java  * RegionAnnulus.java  * RegionBox.java  * RegionBoxAnnulus.java  * RegionCsys.java  * RegionDimension.java  * RegionEllipse.java  * RegionEllipseAnnulus.java  * RegionFont.java  * RegionLines.java  * RegionOptions.java  * RegionPoint.java  * RegionText.java  * RegionValue.java      Note - do not port CoordException, there are other ways to do this."
Answer: 18959.0

User story: "The {{lsst-dev}} shared stack provided in DM-5435 breaks the link between Buildbot and the shared stack. This means it's no longer possible to request a build of a particular branch from the CI system and have that declared into the shared stack for testing.    That's a useful feature: please reinstate it."
Answer: 434063.0

User story: "The shared stack on {{lsst-dev}} provided in DM-5435 does not contain the {{obs_cfht}} or {{obs_decam}} camera packages. Please add them."
Answer: 413366.0

User story: "Part 2 includes: * 3 color * clean up on plot fail * clean up image in general * better row highlighting * other types of data layout (a FC type view) * artifacts (maybe part 3) * When image is small, like zoom it down 1/16x, behavior of selecting an image is not consistent. Clicking on an edge will select one, but will not work on another."
Answer: 12974.0

User story: "Assist [~schandra] with an initial implementation of his workflow using Luigi."
Answer: 12.0

User story: "The Configurable concept (a callable that takes a config as an argument) is a fairly important one in pex_config as the guts behind RegistryField and ConfigurableField, and it's mentioned several times in pex_config's documentation, but it doesn't seem to be directly documented itself."
Answer: 2033897.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 an outside container is resizable (using css properties: resize: 'both', overflow: 'auto'...), in order for the child inside the container to be resizable, the child has to specify its height and width properties using percentage format (height: 90%, width:100%).   When the TabPanel is used, the table is put on TabPanel.  The table needs to access the size information of the outside container, ie,, the grandparent's width and height. The TabPanel has to pass the height and width to its child component.  Without specifying the height and width in the TabPanel, by default, the auto is used.  When the width (height) is auto, it allows to use the child's width (height).  However, the child replies on the parent to provide such information.  When this circular relations occur, the default size of the child is used.  That is why the table component forever has 75px when it was put in the TabPanel.  To be able to resize with the outside (root) contains all the ancestors of the component have to specify the width and height explicitly. "
Answer: 1449.0

User story: "We need a plan for  all the Firefly APIs development in the new React/Redux based JS framework, including JS API and Python API.    - Backward compatibility  - Syntax format for JS API  - Syntax format for Python API  - Schedule     - convert the existing API first     - list of new ones to be added, when    "
Answer: 71542.0

User story: "DM-46921 and DM-5348 changed ProcessCcd to the point where past config files are no longer valid as stuff has moved a lot (see https://community.lsst.org/t/backward-incompatible-changes-to-processccdtask-and-subtasks/581)    This ticket is to go through past configs and create a new config file to reproduce the reductions done, or at least make something sensible come out the end of processCcd"
Answer: 22900.0

User story: "Whilst looking at an individual spot from the CBP on DECam I noticed a weird feature, and upon further investigation, several more, though these were very hard to see.    This ticket is to investigate what image processing techniques will make these hard-to-see features pop out so that they can be examined more closely."
Answer: 608612.0

User story: "Write some snippets to aide in the processing and visualisation of the CBP data/analysis.    Essentially, write some helper functions that you can throw sections of images at to help look at the shape of the CBP spots, as ds9 isn't great ideal this.    Some nice features would be:    A function that takes a list of images or arrays, and plots them side-by-side, which provides some intelligent options for the stretches, and optionally stretches each image as is best for it, or ties them all to be the same. This would be as 2D colour plots.    A function that takes part of an image and displays it as a colour-graded surface.    A function that takes part of an image and displays it as a 3D bar-chart (as in ROOT, but without using ROOT because there is already enough evil in the world)"
Answer: 71731.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: "Identify sets of DECam exposures from the CBP run and feed them to the coaddition script created in DM-5767.    This will need to be redone each time a reprocessing is done as the script will run on calexps. I will do it once now, and then again after DM-5465 is completed to satisfactory levels."
Answer: 284821.0

User story: "Create script to do the following:  * Takes a list of DECam exposure numbers  * for each CCD, loads the corresponding calexps  * creates a naive pixel-by-pixel coadd of the underlying images  * Possibly either ANDs or ORs the masks (though perhaps not necessary)  * Either sums the expusure time info from the headers, or averages them, depending on whether the images were normalised to exposure times or not  * write the corresponding images out as coadded fits"
Answer: 292501.0

User story: "Once DM-3472 lands, it will be possible to write an image selection task that uses the SQLite 3 database produced by {{IndexExposureTask}} (from [daf_ingest|https://github.com/lsst/daf_ingest]) to search for exposures overlapping a region (in particular, the spatial extent of a coadd patch). The {{_rtree_search}} method in {{test_index_exposure.py}} (also from daf_ingest) has an example of how to perform spatial queries quickly.    I was originally scheduled to do something in this space, but Paul mentioned that he had plans to refactor the image selection tasks already, and is much more familiar with the pipeline side of things than I am. Therefore, I'm handing off the implementation of the pipeline task mentioned in DM-3472 to him."
Answer: 1128622.0

User story: "At the moment we display data as scatter plot, when the number of points does not exceed decimation limit, and as density plot when the number of points does exceed this limit.    Scatter plot and density plot should be separate charts. These are the reasons:  - User should be able to create density plot with any number of points  - Chart type and display might be different for density plot in the future  - Scatter plot look should not change when the number of points exceeds decimation limit  - Scatter plot should support errors in the future"
Answer: 560755.0

User story: "User needs to be able to control number of bins and bin size."
Answer: 97004.0

User story: "There are should be a way to display all the information about table columns in a table and allow user to choose a column using this table."
Answer: 127050.0

User story: "Make XYPlot expandable"
Answer: 11451.0

User story: "The TabPanel and CollapsiblePanel loses its state when it is re-rendered.  It is going to have to have a way keeps it state. Therefore it needs an option to take an ID and keep it state in the store.      Use case- tabs of tables then the image plot goes to expanded mode.  The table tabs gets reset to the first one.    "
Answer: 12981.0

User story: "DM-4494 has merged to the dev.  However, there are still two issues remained:  * Resize the popup with tabs does not work  * Sorting is depending on the BasicTable's sorting"
Answer: 4500.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: "NOTE: This ticket will be done by Oualid Achbal, trainee at LPC/IN2P3, but will be merged with [~<USER> account for convenience.    Oualid has identified several error in install documentation (quick start and quick-start for developpers). He will fix it here."
Answer: 30167.0

User story: The last few days exposed that we need a new field in JIRA for epics, something like "original cycle". The problem is that if some epics are late (like the 29 W16 epics that are now assigned to X16 or F16): https://jira.lsstcorp.org/issues/?filter=14212    We had to manually track them down, just look at the filter:    {code}  project = DM AND   issuetype = Epic AND   key in (DM-1109, DM-1111, DM-1117, DM-1123, DM-1233, DM-1955,           DM-1956, DM-1988, DM-2089, DM-2208, DM-2586, DM-3500,           DM-3559, DM-3578, DM-3581, DM-3594, DM-3602, DM-3622,           DM-3647, DM-3832, DM-3838, DM-3841, DM-3842, DM-3875,           DM-3876, DM-3878, DM-3887, DM-3906, DM-3909)   ORDER BY cf[10202] DESC, cf[10502] DESC, Cycle, WBS, Key  {code}    So, as much as I hate to ask for another field, it will really help.    And we can always do a swipe through all epics when we are starting a new cycle and set these if they are not set, so hopefully it won't be much burden on anyone.    I don't feel strongly about the name, if someone has better suggestion than my "original cycle", let's call it something else!
Answer: 2245354.0

User story: "I might have misinterpreted this in the documentation I read, so if this is completely incorrect, please ignore this.    LDM-141 says the images are 16-bits per pixel.  LCR-131 says this info is now 18-bits per pixel.  The Confluence pagehttps://confluence.lsstcorp.org/display/LKB/LSST+Key+Numbers  says that the images are 16-bits per pixel.  The Key numbers page http://lsst.org/scientists/keynumbers says Dynamic Range is 18 bits.    Some of the documentation says we're handling 16-bits per pixel, and some says we're dealing with 18-bits per pixel.  Now, I believe that it's settled on 18-bits.    A lot of calculations in LDM-141 use 16-bits per pixel, which cascades throughout the rest of the spreadsheet.  (examples otherInput!H10, otherInput!H12)."
Answer: 1408530.0

User story: "The welcome message should point a user to community.lsst.org rather than the mailing lists."
Answer: 80417.0

User story: "SQUASH dashboard prototype design is described here    http://sqr-009.lsst.io/en/latest/"
Answer: 70577.0

User story: "The result of DM-4899 was a simulation tool called StarFast that can quickly make simulated images with realistic Differential Chromatic Refraction. This ticket is to build an equivalent simulator using GalSim to check the accuracy of results and benchmark speed and memory usage. "
Answer: 1902901.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 initial database model was implemented in DM-5728 and outputs of the QA analysis code are being produced by the work described in http://dmtn-008.lsst.io/en/latest/    In this ticket we plan to implement and API for listing and creating jobs, metrics and measurements so that a job or the QA analysis code can register this information in the dashboard app."
Answer: 25989.0

User story: "Build packer automation to create machine images to use for the ELK system."
Answer: 79214.0

User story: "Create roles and deploy to Ansible Galaxy.    Create a role to combine all the individual projects together."
Answer: 79216.0

User story: "Create a Vagrant configuration and Ansible role to configure and combine Elasticsearch, Logstash and Kibana (ELK)."
Answer: 79229.0

User story: "Create roles and deploy to Ansible Galaxy."
Answer: 79232.0

User story: "Create roles and deploy to Ansible Galaxy.    These are common roles for cloud-init (and any other future cloud dependencies), java (openjdk-jdk) and an editors role."
Answer: 18604.0

User story: "The git-lfs server protocol needs to be upgrade to support the batch protocol. This is required to get support from the git-lfs core team and to keep up with the client which will deprecate v1 API in the near future.    See:    https://github.com/github/git-lfs/blob/master/docs/api/README.md?utm_source=gitlfs_site&utm_medium=api_spec_link&utm_campaign=gitlfs"
Answer: 449342.0

User story: "The git-lfs configuration is fragile. The git-lfs client doesn't support our most common use case."
Answer: 524433.0

User story: *  The testing data "table_data.tbl" in the testing tree was accidentally moved.  It should be added back so that IpactTableTest.java can run.    * The request in JsontableUtil was mistakenly moved out from the tableModel by the the line   * {code}  * if (request != null && request.getMeta().keySet().size()>1) {              tableModel.put("request", toJsonTableRequest(request));  }  {code}.  The meta can be null but the request is not null, the request should be put into the TableModel.     
Answer: 6756.0

User story: "This story captures the process of getting DM comments on the document draft and applying any changes required to bring it to final form. "
Answer: 82201.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: "- Canonical table of KPMs and the document reference they flowdown like (kind of like the ldm240 tab 2)  LSE-029     - For each KPM we specify:    * Verification Owner: the person or group that performs the tests     * Verification Technique: How the KPM will be tested conceptually    * Verification Code: What code will be used for this test [blank for CoDR]    * Verification Implementation: Which group is delivering  any code that has to be written specifically for this test specially [blank for CoDR]    * Verification Data: How can the KPM test be evaluted prior to real data being available (percursor data - maybe a hierarchy of preference HSC, DECAM etc - , simulated data)      - Process    * SQuaRE will compile the testing report as part 02C09    * An outline of process (obtain from MJ) on signing off on the report of this testing     "
Answer: 82210.0

User story: "This ticket captures the steps to create the django project for SQUASH, its configuration and the dashboard app http://sqr-009.lsst.io/en/latest/    The planned tasks are:        - Implement the ``Dataset``, ``Visit`` and ``Ccd`` tables in the django ORM layer, as a minimum set      of tables for the dashboard app      - Prototype home page and dashboard pages      "
Answer: 10997.0

User story: It'd be good to have a framework for documenting work done in each cycle (beyond "just" release notes).
Answer: 2238806.0

User story: "Tatiana will attend the weekly meeting. Xiuqin and Gregory also attends when needed. "
Answer: 72903.0

User story: "While Tatiana is the assignee of this ticket, Xiuqin and Gregory participate this weekly telecon semi-regularly to lend support. "
Answer: 34070.0

User story: "Test table to make sure it can be resized under a variety of layout."
Answer: 2729.0

User story: "Convert gwt's client-side sorting to javascript."
Answer: 9691.0

User story: "This tracks SPs spent on JIRA requests. "
Answer: 84521.0

User story: "Strategy design with pipeline and deployment teams. Discussions of service description and levels of support. Sufficient design to lead to procurement. Discussions with vendors. Quote selection. Budget tracking. Quote submission to finance. GCO follow up questions. OBFS follow up questions. Finance follow up questions. Overall tracking of purchase progression."
Answer: 41769.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 WCS fitter is too chatty:  {code}  processCcd.calibrate.astrometry.matcher: filterStars purged 0 reference stars, leaving 85 stars  processCcd.calibrate.astrometry.matcher: Purged 1314 unusable sources, leaving 40 usable sources  processCcd.calibrate.astrometry.matcher: Matched 23 sources  processCcd.calibrate.astrometry.wcsFitter: Updating centroids in refCat  processCcd.calibrate.astrometry.wcsFitter: Updating coords in sourceCat  processCcd.calibrate.astrometry.wcsFitter: Updating distance in match list  processCcd.calibrate.astrometry.matcher: filterStars purged 0 reference stars, leaving 85 stars  processCcd.calibrate.astrometry.matcher: Purged 1314 unusable sources, leaving 40 usable sources  processCcd.calibrate.astrometry.matcher: Matched 22 sources  processCcd.calibrate.astrometry.wcsFitter: Updating centroids in refCat  processCcd.calibrate.astrometry.wcsFitter: Updating coords in sourceCat  processCcd.calibrate.astrometry.wcsFitter: Updating distance in match list  processCcd.calibrate.astrometry.matcher: filterStars purged 0 reference stars, leaving 85 stars  processCcd.calibrate.astrometry.matcher: Purged 1314 unusable sources, leaving 40 usable sources  processCcd.calibrate.astrometry.matcher: Matched 21 sources  processCcd.calibrate.astrometry.wcsFitter: Updating centroids in refCat  processCcd.calibrate.astrometry.wcsFitter: Updating coords in sourceCat  processCcd.calibrate.astrometry.wcsFitter: Updating distance in match list  {code}    The "Updating" messages don't provide any useful information for the user, and only clutter the logs.
Answer: 307.0

User story: "The result view architecture needs to be written.    * A meeting needs to happen with David, Gregory, Xiuqin, Trey, and Tatiana to discuss this.  * Trey, Loi, and Tatiana should have a design meeting.    It should support some or all of the following ideas:    * A search defining a new results view type  * A search adding to an existing result view  * A search replacing the results - any cleanup needs to happen.  * Some sort of controller that know which view should show and which view can be shown   * New search panels easily added. Maybe the html file defines which are visible"
Answer: 41664.0

User story: "There is a need to go though the entire ui and document inconsistencies with the old UI."
Answer: 1189622.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: "At various times in the past few months I've promised [~<USER>, [~<USER>, [~<USER>, and probably a few others a document describing the parallelization needs for DRP in greater detail.  My understanding of the plans for the eventual DRP probably good enough to do this well now, and is unlikely to improve further in the near future (as that will require algorithmic research).    This needs to be prioritized with my other responsibility for documents that describe the DRP system in other ways, most of which are oriented towards scientists and science pipelines developers.  The document on this ticket is essentially the description that would matter the most for the process control middleware team."
Answer: 81684.0

User story: "A local docker registry at CC-IN2P3 would improve performance when running Qserv from Docker, and would also prevent using Squid proxy for all nodes to access the internet.    A discussion between Square Team and CC-IN2P3 might be useful to clarify requirements before setting up registry, do we need:    1. A docker hub mirror registry which seems easy to set up and maintain, and might be enough:  [https://docs.docker.com/v1.6/articles/registry_mirror/]    Or:    2. a stand-alone registry with :   - full internet access   - authentication for Qserv team    Common requirement for both proposals would be:  - stand-alone virtual machine  - registry port reachable for all Qserv cluster  - 100 GB storage on a local device    "
Answer: 1939127.0

User story: "A local docker registry at CC-IN2P3 would improve performance when running Qserv from Docker, and would also prevent using Squid proxy for all nodes to access the internet.    A discussion between Square Team and CC-IN2P3 might be useful to clarify requirements before setting up registry, do we need:    1. a registry with :     - full internet access    - authentication for Qserv team    - 100 GB storage on a local device    2. A docker hub mirror registry seems easier to set up and maintain, and might be enough:  [https://docs.docker.com/v1.6/articles/registry_mirror/]"
Answer: 1868347.0

User story: "A local docker registry at CC-IN2P3 would improve performance when running Qserv from Docker, and would also prevent using Squid proxy for all nodes to access the internet.    A discussion between Square Team and CC-IN2P3 might be useful to clarify requirements before setting up registry, do we need:    1. a registry with :     - full internet access    - authentication for Qserv team    - 100 GB storage on a local device    2. A docker hub mirror registry seems easier to set up and maintain, and might be enough:  [https://docs.docker.com/v1.6/articles/registry_mirror/]"
Answer: 1858461.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: "A local docker registry at CC-IN2P3 would improve performance when running Qserv from Docker, and would also prevent using Squid proxy for all nodes to access the internet.    A discussion between Square Team and CC-IN2P3 might be useful to clarify requirements before setting up registry, do we need:    1. a registry with :     - full internet access    - authentication for Qserv team    - 100 GB storage on a local device    2. A docker hub mirror registry seems easier to set up and maintain, and might be enough:  [https://docs.docker.com/v1.6/articles/registry_mirror/]    "
Answer: 1858462.0

User story: "A local docker registry at CC-IN2P3 would improve performance when running Qserv from Docker, and would also prevent using Squid proxy for all nodes to access the internet.    A discussion between Square Team and CC-IN2P3 might be useful to clarify requirements before setting up registry, do we need:    1. a registry with :     - full internet access    - authentication for Qserv team    - 100 GB storage on a local device    2. A docker hub mirror registry seems easier to set up and maintain, and might be enough:  [https://docs.docker.com/v1.6/articles/registry_mirror/]    "
Answer: 1858462.0

User story: "Once we have a composite distortion model from DM-5701, evaluate the performance of AST and GWCS over a range of numbers of pixels, likely from ~100 through full-CCD (4k^2).    As part of this process, we will try to determine whether there is a way to efficiently warp images/postage stamps using python-only models in GWCS and whether bottlenecks could be worked around via optimizations in cython."
Answer: 18704.0

User story: "Using lessons learned from DM-5701, create a more complex distortion model that cannot be represented from the basic models in GWCS or AST. A good example for this might be a rapidly varying sinusoidal tree-ring-like function that is not well represented by the standard polynomial basis functions. This will test our ability to extend each framework with new models that have not yet been decided on.    Once completed, we could plug this back into the composite model in DM-5701."
Answer: 27498.0

User story: "To help us evaluate WCS options, we need to create a relatively complicated composite model in AST and GWCS, using a few models currently available within the existing packages. A minimal composite model to test these things would include:     * FITS linear transform   * ccd distortion   * optical model   * FITS TAN WCS    The middle steps do not need to be realistic models, just something that we can use to compare AST's and GWCS's respective interfaces and capabilities for creating the composite model, and test for differences in their results. We can then use this model to evaluate performance when run on different numbers of pixels."
Answer: 18719.0

User story: "Currently the image select panel is in a dialog.  It also needs to be able to work in a dropdown."
Answer: 5751.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Once a complete DCR correction prototype is finished, we will want to run many different sky simulations from StarFast with different densities of sources, noise properties, airmasses, and astrometric errors to find the limitations and edge cases where it fails. There are likely to be several thousand simulations needed which will take an as-yet undefined number of CPU hours, but this ticket is for the work in setting up and analyzing the results from the run."
Answer: 479629.0

User story: In DM-5695 a simple DCR correction was applied to simulated images in the case that the effect was purely along the pixel grid and could be reduced to 1D. This ticket extends that work to the general 2D case.  Possible approaches include resampling the "science" image to match the "template", or including neighboring pixels and computing their covariance. Ideally, multiple approaches will be implemented and tested.
Answer: 232077.0

User story: "We need to add blank image support."
Answer: 575164.0

User story: "<USER>wrote a simple DCR correction recipe that runs in 1D in an ipython notebook. This ticket is to re-write the notebook in python modules that can be run on StarFast simulated images prior to image differencing. For this ticket, the simulated images will be 2D, but DCR will be purely along the x or y pixel grid, allowing columns or rows of pixels to be treated separately in 1D."
Answer: 130025.0

User story: "Determine the metadata and dependencies needed to fully process two images simulated with StarFast through diffim. "
Answer: 57773.0

User story: "The simulated images generated by StarFast need to be able to be run through the LSST stack, to test and make use of the existing measurement, fitting, stacking, and image differencing capabilities.   This includes writing or updating a simulations obs package, and determining and supplying the required metadata."
Answer: 40766.0

User story: "{{dm_dev_guide:conf.py}} currently reads:  {code:python}  exclude_patterns = ['README.rst', '_build', 'development/docs/snippets']  {code}  There is no {{development}} directory. Suggest it should be:  {code:python}  exclude_patterns = ['README.rst', '_build', 'docs/snippets']  {code}    This causes a warning on build:  {code}  docs/snippets/figure.rst:None: WARNING: duplicate label fig-example-figure-label  {code}"
Answer: 81.0

User story: "When the data for a table is completely loaded fire another action such as TABLE_NEW_LOADED_DONE. This way the xyplots and the image overlays know to go fetch the data.    4/22/2026 from the pull request:  added new action TABLE_NEW_LOADED to table; fired when table is completely loaded.  added table error handling.  fix active table not updating after an active tab is removed."
Answer: 35601.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: "Table seems to perform poorly on Firefox. Firefox gets into the complete refresh state only when the table is visible with charts only, fits view only or fits view and chart it does not happen    Helpful article: http://benchling.engineering/performance-engineering-with-react/    changelog:  - added react performance tools, React.addons.Perf  - fix some performance issues:    - skip render of selection boxes when not needed.    - skip rendering of xyplot options when not needed.    - skip wasted render called for table cell and headers.    - will do a more in depth investigation in another ticket.  - refactor table code and it's state.    - move all table related states into table_space.    - create sub reducers for each data domain    - rename and move functions to better describe what it's doing   - added 'title' to table.  - show mask while loading    "
Answer: 26924.0

User story: The reference object loader in {{meas_algorithm}}'s *loadReferenceObjects.py* grows the bbox by the config parameter pixelMargin:  doc = "Padding to add to 4 all edges of the bounding box (pixels)" . This is set to 50 by default but is not reflected by the radius parameter set in the metadata, so some matches may reside outside the circle searched within this radius. This increase needs to be reflected in the radius set in the metadata fed into {{joinMatchListWithCatalog()}}.  
Answer: 19822.0

User story: "processCcd.py is failing on some u band CFHT data, as reported by [~<USER> on c.l.o: https://community.lsst.org/t/testing-dm-4692-the-new-processccdtask/507/24    See that posting for sample data to reproduce the problem."
Answer: 6874.0

User story: "In DM-5284, {{meas_extensions_simpleShape}} was added to the stack. However, not all of its dependencies were included in the table file. Full listing of dependencies is required following RFC-52. Please add them. ([~<USER> suggests this should include at least {{numpy}}, {{utils}}, {{pex_config}} and {{pex_exceptions}})."
Answer: 31362.0

User story: "In DM-5284 [~<USER> added a new {{meas_extensions_simpleShape}} algorithm. This should be part of the {{lsst_apps}} top-level package. Please make it so."
Answer: 31377.0

User story: "In DM-3368, we provided a means of running multiple processCcd tasks across an exposure, but without performing global calibration etc as provided by HSC's ProcessExposureTask.    Please augment this with whatever additional capability is required to enable HSC data release processing."
Answer: 42208.0

User story: "As per DM-5471, but using cffi."
Answer: 21208.0

User story: "Same as DM-5471 but using pybind11"
Answer: 36047.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 running ci_hsc after setting-up the meas_extensions_shapeHSM, meas_extensions_photometryKron and dependencies using setup -v -r . in the respective cloned folders, I get  {code}  Cannot enable shapeHSM (RegistryField 'calibrate.detectAndMeasure.measurement.plugins' failed validation: Unknown key 'ext_shapeHSM_HsmMoments' in Registry/ConfigChoiceField  For more information read the Field definition at:    File "/home/vish/code/lsst/lsstsw/stack/Linux64/pex_config/2016_01.0+3/python/lsst/pex/config/registry.py", line 179, in __init__      ConfigChoiceField.__init__(self, doc, types, default, optional, multi)  And the Config definition at:    File "/home/vish/code/lsst/lsstsw/stack/Linux64/meas_base/2016_01.0-13-g779ee14/python/lsst/meas/base/sfm.py", line 109, in <module>      class SingleFrameMeasurementConfig(BaseMeasurementConfig):  ): disabling HSM shape measurements  {code}  Find out why this is happening and find a fix  
Answer: 20.0

User story: At the scipi-wg meeting of 23 & 24 March 2017, [~<USER> presented an overview of his plans for L2 processing. The next step is to refine those plans and prepare a more detailed "deep-dive" discussion of the L2 plans.
Answer: 28865.0

User story: "Participate in HSC docs transfer hackathon."
Answer: 1039827.0

User story: "Participate in HSC docs transfer hackathon.  "
Answer: 1039828.0

User story: "Participate in HSC docs transfer hackathon.  "
Answer: 1039828.0

User story: "Participate in HSC docs transfer hackathon."
Answer: 1039829.0

User story: "Participate in HSC docs transfer hackathon."
Answer: 1039830.0

User story: "Participate in HSC docs transfer hackathon."
Answer: 861177.0

User story: "Participate in HSC docs transfer hackathon.  "
Answer: 1039831.0

User story: "Participate in HSC docs transfer hackathon."
Answer: 1039832.0

User story: "Liase with SQuaRE to determine the most effective way to transfer HSC docs to LSST. Organize a hackathon session for DRP developers at which we get this done. Bring doughnuts."
Answer: 1039834.0

User story: "The file {{config/psfex.py}} has no documentation and is bit rotting. If you feel it should be kept then please document it and add a simple unit test that loads it and runs data using it. If it is not needed, then please get rid of it."
Answer: 2198050.0

User story: "As of DM-5532 a few config files need updating to not refer to star selector config fields as registries (not ones run by our normal CI, which is how I missed this)."
Answer: 1313.0

User story: "Please add the {{lsst_ci}} top-level package to the system used to tag weeklies. This will make it possible to include it in the shared stack provided on development machines (DM-5435), which is an important user request ([1|https://community.lsst.org/t/shared-stack-on-lsst-development-machines/641/6], [2|https://community.lsst.org/t/shared-stack-on-lsst-development-machines/641/11])."
Answer: 480479.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 well-motivated theoretical fits to the astrometric and photometric performance measurements based on derivations from LSST Overview paper.  http://arxiv.org/pdf/0805.2366v4.pdf    Photometric errors described by  Eq. 5  sigma_rand^2 = (0.039 - gamma) * x + gamma * x^2  [mag^2]  where x = 10^(0.4*(m-m_5))    Eq. 4  sigma_1^2 = sigma_sys^2 + sigma_rand^2    Astrometric Errors   error = C * theta / SNR    Based on helpful comments from [~<USER>    {quote}  I think eq. 5 from the overview paper (with gamma = 0.039 and m5 = 24.35; the former I assumed and the latter I got from the value of your  analytic fit that gives err=0.2 mag) would be a much better fit than the adopted function for mag < 21 (and it is derived from first principles).  Actually, if you fit for the systematic term (eq. 4) and gamma and m5, it would be a nice check whether there is any “weird” behavior in  analyzed data (and you get the limiting depth, m5, even if you don’t go all the way to the faint end).     Similarly, for the astrometric random errors, we’d expect        error = C * theta / SNR,    where theta is the seeing (or a fit parameter), SNR is the photometric SNR (i.e. 1/err in mag), and C ~ 1 (empirically, and 0.6 for the idealized maximum likelihood solution and gaussian seeing).   {quote}"
Answer: 30811.0

User story: "When several dialogs are up together.  The most recently click one should be one top. When table are in the dialogs such a fits header view. The scroll bars will go over other dialogs. This needs some though and work.  Another thing- when a message dialog is show because of a dialog error. It should center on the dialog.  Update- I don't think I will do the error centering now.  I am going to leave that and see if it is a real problem."
Answer: 44180.0

User story: "This script is currently located in:   admin/tools/docker/deployment/in2p3/runQueries.py     Here's some improvments:    - use lsst/db instead of mysqlpython  - externalize queries and other parameters in a config file  - add an option to make script stop after a few queries (in order to have deterministic query results for Large Scale integration tests)  - any other minor improvments..."
Answer: 1865112.0

User story: "Both {{ObjectSizeStarSelector}} and {{SecondMomentStarSelector}} have logic to transform measured moments from pixel coordinates to TAN_PIXELS in order to remove optical distortion.  That's generically useful for any star selector that works on measured moments, and we shouldn't have to repeat it everywhere it is used."
Answer: 2228081.0

User story: "Implement RFC-167 for adding esutil to the stack.  This will be done in the same way as proposed to add scipy."
Answer: 2748.0

User story: "Writing down SUIT vision that the group has discussed and shaped in last year off and on.   SUIT will use it as guidance for system design."
Answer: 20047.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 initial MVP of ltd-keeper had all-or-nothing authentication; any user was effectively an admin user. It would be useful have fine grained roles that each API user could have (for example, one API user might be able to add a build, but not create an edition or product or add another user). The phases of this ticket at:    1. Design a set of roles that cover current functionality  2. Add these roles to the User DB model and user creation API  3. Authorize users against these roles in specific API calls"
Answer: 14078.0

User story: "In interfacing with AstroPy it'd be useful to easily convert PropertySet and PropertyList to nested dict and OrderedDict (respectively), converting elements with multiple values to lists in the process."
Answer: 58482.0

User story: "With DM-5641, we'll soon be able to get astropy.table views into afw.table objects.  That will be a bit more useful if astropy can understand the unit strings we give it, and since we currently don't use those strings as anything more than textual information for humans, we might as well standardize on the terms they've already selected."
Answer: 64487.0

User story: At an LSST/AstroPy summit hack session, we've put together a functional system for viewing afw.table objects as astropy.table objects on branch u/<USER>astropy-tables of afw and https://github.com/astropy/astropy/pull/4740.    Before merging, we should add support for "object" columns for subclasses to hold e.g. Footprints in SourceCatalog, and add some documentation.  We may also want to add a convenience method to return an astropy.table.Table directly.
Answer: 74194.0

User story: "Develop a lsst-autopep8 command in [sqre-codekit|https://github.com/lsst-sqre/sqre-codekit] that can run [autopep8|https://github.com/hhatto/autopep8] in an automated fashion across all of the LSST Stack repositories according to the PEP 8 exceptions determined in RFC-162."
Answer: 541194.0

User story: "Please add pipe_drivers to lsst_distrib.    Does this need an RFC?"
Answer: 66276.0

User story: "Add necessary data products and default config in order to run forcedPhotCcd, coaddDriverTask, and multiBandDriverTask with DECam data. "
Answer: 14257.0

User story: "Preparation work to learn about ctrl_pool and pipe_drivers packages.      - Install ctrl_pool and pipe_drivers packages on my OSX desktop (no slurm).   - Run the ctrl_pool mpiexec example to verify if the mpi is working.  - Obtain a HSC data repo from ci_hsc as sanity checks.   - Construct a small DECam data repo, using raw Stripe82 data consisting of two visits, one band, one patch.  - Run ctrlPoolDemo.py with the HSC data repo and then the DECam data repo.  - Run the pipe_drivers scripts {{coaddDriver}} and {{multiBandDriver}} with the HSC data repo and then the DECam data repo.  - All with the default batch system SMP to run on a single machine."
Answer: 11481.0

User story: "Please make it possible to build pipe_drivers as part of lsstsw."
Answer: 205.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "In DM-5590, we worked around a problem in which clang 3.8 refused to access protected members of a cousin class given a friend declaration in the base. To our best understanding at time of writing, the code is valid: it seems possible that this is a bug in clang.    Investigate what went wrong, produce a minimal test case, and (if appropriate) report this as an upstream bug."
Answer: 1951939.0

User story: "create way using repo of repos to get only the posix root in the returned cfg, update example/test code.  write an RFC, review with KT  post RFC & gather feedback.  incorporate feedback and/or create another design story if needed."
Answer: 1844499.0

User story: "per comments in DM-5593, an incorrect comparison operator was found, that used {{is}} instead of {{==}} in a string comparison (e.g. {{var is 'left'}} which is incorrect, it should be {{var == 'left'}}.  This needs to be corrected in {{Repository}} (see DM-5593 for details), and the rest of daf_persistence and daf_butlerUtils should be checked for correct use of is vs. ==."
Answer: 15726.0

User story: "Add Advisory Message receiving support.  This allows monitoring of consumer/producer activity by receiving messages on standard topics supported by the broker.    See:    http://activemq.apache.org/advisory-message.html    for more information.    Support will be added for consumed messages and consumer connectivity.   "
Answer: 464984.0

User story: "Internet-free install scripts are unused and should be removed with related documentation."
Answer: 1843947.0

User story: "Internet-free install procedure has never been used for real install and seems to be replace in practice by Docker procedure. So related scripts and documentation should be removed."
Answer: 1843953.0

User story: "Internet-free install procedure has never been used for real install and seems to be replace in practice by Docker procedure. So related scripts and documentation should be removed."
Answer: 1843953.0

User story: "Internet-free install procedure has never been used for real install and seems to be replace in practice by Docker procedure. So related scripts and documentation should be removed."
Answer: 1843953.0

User story: "Internet-free install procedure has never been used for real install and seems to be replace in practice by Docker procedure. So related scripts and documentation should be removed."
Answer: 1843953.0

User story: "Internet-free install procedure has never been used for real install and seems to be replace in practice by Docker procedure. So related scripts and documentation should be removed."
Answer: 1843953.0

User story: "Internet-free install procedure has never been used for real install and seems to be replace in practice by Docker procedure. So related scripts and documentation should be removed."
Answer: 1843952.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: "Backwards compatible behavior is that when butler returns a single item, it is NOT in a list. A recent change (when the Repository class was added) broke this behavior.     Change it back so that if an operation in repository would return a list with a  single item, it pulls it from the list.    Note this is only related to the case where a repository's parentJoin field is set to 'outer' and since no one is using this yet (they should not be, anyway) then the point is moot.     "
Answer: 223.0

User story: "The current implementation of the new {{DipoleFitTask}} for {{ip_diffim}} uses {{lmfit}} to perform parameter estimation (least-squares minimization). {{lmfit}} is essentially an API on top of {{scipy}}'s optimizer, adding functionality such as parameter boxing (constraints) and improved estimates of parameter uncertainties. It would be nice to include this small, pure-python package in the stack rather than investigating and re-implementing the optimization using {{scipy}} or {{minuit2}} (which are the two optimizers that I know of that are in the stack already)."
Answer: 14568.0

User story: "This is a clone of DM-5581 tracking [~<USER>'s SPs"
Answer: 1859.0

User story: "This  component will upload and validate the file as part of the input's validation process.  It will return a token generated by the server which will resolve to the uploaded file if the upload success.   "
Answer: 7127.0

User story: "Support getting LCR-385 against LSE-78 through the CCB."
Answer: 1.0

User story: "[SQR-011|http://sqr-011.lsst.io] documents the various communication and publishing platforms that SQuaRE operates on behalf of DM. This ticket will complete v1 of the document (DM-4721 created a time-boxed first draft) and also include work to present the document to LSST management."
Answer: 3321.0

User story: "Create a docgen from the LSE-140 content in Enterprise Architect."
Answer: 1.0

User story: "* Add working message when plot is loading, (downloading..., plotting..., etc)  * Add error message when plot fails  * for multi-viewer remove and failed plot cells  * work out if image select panel should become visible again.  * Any thing else the is plotting feedback related"
Answer: 59351.0

User story: "Write a short overview of the planned work of your team in X16 and add it to your page under: https://confluence.lsstcorp.org/display/DM/X16. Audience that you are writing it for: the DM team.  "
Answer: 7904.0

User story: "Write a short overview of the planned work of your team in X16 and add it to your page under: https://confluence.lsstcorp.org/display/DM/X16. Audience that you are writing it for: the DM team."
Answer: 3946.0

User story: "Write a short overview of the planned work of your team in X16 and add it to your page under: https://confluence.lsstcorp.org/display/DM/X16. Audience that you are writing it for: the DM team.  "
Answer: 487913.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 short overview of the planned work of your team in X16 and add it to your page under: https://confluence.lsstcorp.org/display/DM/X16. Audience that you are writing it for: the DM team.  "
Answer: 1302.0

User story: "Write a short overview of the planned work of your team in X16 and add it to your page under: https://confluence.lsstcorp.org/display/DM/X16. Audience that you are writing it for: the DM team."
Answer: 1571686.0

User story: "Write a short overview of the planned work of your team in X16 and add it to your page under: https://confluence.lsstcorp.org/display/DM/X16. Audience that you are writing it for: the DM team."
Answer: 94.0

User story: "Write a short overview of the planned work of your team in X16 and add it to your page under: https://confluence.lsstcorp.org/display/DM/X16. Audience that you are writing it for: the DM team."
Answer: 470577.0

User story: Review LCR-603, "LSE-74 document revision"
Answer: 6.0

User story: "Review the LSE-70 and LSE-209 drafts submitted with change requests LCR-567 and LCR-568 in January 2016."
Answer: 7.0

User story: "Prepare for, attend, and follow up on the OCS-subsystems teleconference on December 9, 2015. This story covers work related to LSE-74; LSE-70 and LSE-209 work was also done under a separate epic."
Answer: 4.0

User story: "Prepare for, attend, and follow up on the OCS-subsystems teleconference on December 9, 2015. This story covers work related to LSE-70 and LSE-209; LSE-74 work was also done under a separate epic."
Answer: 1.0

User story: "Prepare for, attend, and follow up on the OCS-subsystems teleconference on November 11, 2015.  This story covers work related to LSE-74; LSE-70 and LSE-209 work was also done under a separate epic."
Answer: 4.0

User story: "Prepare for, attend, and follow up on the OCS-subsystems teleconference on November 11, 2015.  This story covers work related to LSE-70 and LSE-209; LSE-74 work was also done under a separate epic."
Answer: 10.0

User story: "Following the investigatory work into switching our Python test files to be compliant with pytest, whilst still using {{unittest}}, a tech note needs to be written explaining the required changes."
Answer: 67549.0

User story: "Prepare for, attend, and follow up on the OCS-subsystems teleconference on October 8, 2015."
Answer: 5.0

User story: "Assist with tech note SQR-007 and document investigation of logging, monitoring and metrics technologies and architecture."
Answer: 1856404.0

User story: "TablePanel and BasicTable now accept optional renderers.  For each column, you can set a custom renderer for the header, cell, or both.  Also, created several commonly used renderer for images, links, and input field."
Answer: 7181.0