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: Based on hipchat discussion it is not entire obvious, so we should clarify/document it. The relevant pieces of discussion :    * the person assigned to RFC should deal with their RFCs. If that is not working well, then their TCAM should step in. If that is not working, then system architect should. If that is not working either, PM will  * It just seemed intuitive that _adopting_ RFCs is an architecture/TCT/BDFL issue (though it is delegated to the crowd for things that are non-controversial) but _implementing_ them is a work-planning-and-monitoring issue. People in management positions have to be able to ask and answer the question "are adopted RFCs being implemented?" on a regular basis - to avoid the accumulation of technical debt, etc.  * "When consensus is established the Assignee should create a set of tickets that specify the implementation work, and then mark the RFC as Adopted in JIRA." i.e., you cannot move to Adopted without creating the implementation ticket. As Jim pointed out, that didn't get done retroactively for older RFCs. (quotation from the [RFC process document|https://developer.lsst.io/processes/decision_process.html#request-for-comments-rfc-process])
Answer: 7345.0

User story: "As per RFC-25, increase the Mask plane bit count from 16 to 32, which should *hopefully* just be (but probably won't be) a matter of modifying a typedef."
Answer: 453423.0

User story: "{{log}} is configurable at runtime using a log4cxx configuration file. Currently the configuration is hard-coded in {{utils.tests.init()}}.  Moving it out to a configuration file will give more flexibility. "
Answer: 72430.0

User story: "Include {{processFile}} in {{lsst_ci}} to ensure that {{processFile}} is kept up-to-date.    # Move {{processFile}} from {{github.com/lsst-dm}} to {{github.com/lsst}}.  This step is optional.  It technically would work fine to keep it in {{lsst-dm}}.  It's more of a symbolic statement.  #  Add {{processFile}} repo to {{lsstsw/etc/repos.yaml}}  # Add {{processFile}} as a required dependency of {{lsst_ci}}"
Answer: 1811435.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: [~<USER> reports a numerical issue in the afw test suite:  {code}  ======================================================================  FAIL: testEvaluate (__main__.ChebyshevBoundedFieldTestCase)  Test the single-point evaluate method against explicitly-defined 1-d Chebyshevs  ----------------------------------------------------------------------  Traceback (most recent call last):    File "tests/testChebyshevBoundedField.py", line 110, in testEvaluate      self.assertFloatsAlmostEqual(z1, z2, rtol=1E-13)    File "/Users/timj/work/lsstsw3/stack/DarwinX86/utils/12.0-9-gf85c792/python/lsst/utils/tests.py", line 641, in assertFloatsAlmostEqual      testCase.assertFalse(failed, msg="\n".join(errMsg))  AssertionError: True is not false : 1/50 elements differ with rtol=1e-13, atol=2.220446049250313e-16  0.00367933486006 != 0.00367933486006 (diff=4.4408920985e-16/0.00367933486006=1.20698231268e-13)     ----------------------------------------------------------------------  {code}
Answer: 1982.0

User story: "Do 8 points worth of work implementing what is described on the [Swift Butler Storage Trial Confluence Page |https://confluence.lsstcorp.org/display/DM/Swift+Butler+Storage+Trial]"
Answer: 392991.0

User story: "finish going thru examples on https://confluence.lsstcorp.org/display/DM/Use+Cases+for+Butler+Composite+Datasets    as needed, create requirements on   https://confluence.lsstcorp.org/display/DM/Requirements+and+Design+for+Composite+Datasets+in+Butler    * In examples, indicate what requirements satisfy them and why.  * Sort out any questions about the use cases and their implications on requirements."
Answer: 27307.0

User story: When linking items in DPDD to requirements and design documents, we need to provide anchor links that can be referenced outside of DPDD and which are guaranteed not to change. Section numbers and "item 5 in list on page 3" are not acceptable anchors. Explicit numbers will be assigned as margin notes to requirements-like items in DPDD.
Answer: 129272.0

User story: "After a discussion between [~<USER>, [~<USER> and [~<USER>, there is a strong rationale for separating the FireflyClient API into its own repository (not combined with widgets):  * FireflyClient has very few dependencies, while {{firefly_widgets}} already depends on Astropy and more dependencies may be added.  * FireflyClient is pure Python, while {{firefly_widgets}} includes both Javascript and Python.    The proposal is to move FireflyClient out of the {{firefly}} repository and into its own repository {{firefly_client}}. -Within this repository, FireflyClient needs to be packaged to be pip-installable via {{pip install firefly_client}}.-    -To conform to Python module naming conventions, the module needs to be all lower-case, so that the users will import the class with something like {{from firefly_client import FireflyClient}} after it has been installed.-    Examples of using the Python API could be included in an {{examples}} subdirectory in this repository."
Answer: 110871.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: September X-SWAP goals:    1. Finish integration of queryID into analysis pipeline  2. Quantify "Query Throughput"  3. Profile system parameters against Query Throughput  4. Run new test configuration/test docker resource limiting
Answer: 51798.0

User story: "Create action for region selection and the region selection can be done by calling from command line or by mouse click from the UI. The work includes,   - Create region selection dispatch function which accepts region string as the region identity for the selection.   - Update state to record which region(s) are selected from either command line or mouse click.   - Provide utility function to get the selected region of the specified region layer - one region per region layer.   - Add region highlight mode as the parameters for dispatch functions which create region layer and add region data, the highlight mode set the highlight style and color on the selected region.   "
Answer: 20064.0

User story: "Running a fresh build of afw master on os x fails on two unit tests. One is in testExecutables.py and is related to not finding AFWData. On my system AFWData is not installed and the test should be skipped, but is still run. The other is DM-7474."
Answer: 1441.0

User story: "Unlike {{pex.logging}}, {{log}} backed by log4cxx is configurable at runtime using a configuration file. For running CmdLineTasks, DM-6999 sets some defaults inside {{pipe_base}} and provides an {{-- longlog}} option to output in a more verbose format, including data, time, and data IDs.  I think it would be useful to let users supply their own log4cxx configuration file easily through the command line task interface, giving users more control over their logs. "
Answer: 70619.0

User story: "Use Docker compose or something similar to easily scale up from one Kafka alert consumer to N consumers."
Answer: 231889.0

User story: "Figure out how to use Docker compose or something similar to easily scale up from one producer to 189 producers, one per CCD."
Answer: 224267.0

User story: "Write code that will simulate one Kafka consumer: reads each alert, prints alert, sleeps for some amount of time (simulating slow consumer), and logs latency from timestamps.  "
Answer: 90357.0

User story: "Write code that will simulate the alerts (content and size) expected for one visit for one CCD as a producer within Kafka."
Answer: 90359.0

User story: "Extend sample alert to include a simulated postage stamp cutout of the pixels that caused the alert.  This is for size estimate and to test feasibility.  For now, still not using any specific alert format."
Answer: 132115.0

User story: "Sample alert includes all the expected fields, just to get a good approximate size estimate of the alert (minus postage stamp).  For now, not worrying about having the alerts in any specific format."
Answer: 129637.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Following the discussion at RFC-215, we need to update the developer guide to reflect that python tests should not be executable, nor have a shabang at the top. This is probably a few sentences to the python [testing portion|https://developer.lsst.io/coding/python_testing.html] part of the dev. guide, possibly in a new subsection at the end."
Answer: 1533853.0

User story: "Galsim building with conda-lsst requires that the eups dependency on python_future is explicit. Without the declaration it errors out."
Answer: 2882.0

User story: "The DCR template generation code has been developed and tested using simulated data. It would be informative to try running it on real data to identify new issues and see if it works."
Answer: 133844.0

User story: "Once the DCR algorithm bakeoff is complete, a tech note should be written describing the approaches that were tried and the results. Highlights should include:  * Edge cases found in DM-5699      * In particular, an example using data with varying seeing  * Plots of the DCR severity metric (DM-5920) to highlight which technique to use under different conditions.  * Example spectra recovered from the images, compared with the input (simulated) spectra. An estimate on the accuracy of recovering spectra or at least differentiating between different types of objects (e.g. between stars and quasars) would be great.  * If possible, provide an example using real data. "
Answer: 607501.0

User story: "The current DCR template generation code takes approximately 30s per pixel on a single core to run. This code needs to be optimized to run much faster."
Answer: 130028.0

User story: While working on the jointcal quiver plots, etc. I made all the plots with the default, interactive, backend. Now that I need to use larger datasets on lsst-dev, interactive mode won't work, but would be useful to keep as an option. I had started to convert to using Agg during the All Hands Meeting, but got stuck on some strange interactions with quiver.    This story is to capture the work I started on it, and to finish cleaning up that code. It might even be worth lifting the plotting code out of the tests, now that they're becoming more complicated. It would be useful to be able to generate these plots during non-testing jointcal runs.    This might be a good opportunity to develop the "unified plotting abstraction layer" described in DM-5790.
Answer: 160626.0

User story: "DM-5697 and DM-6249 created code that generates DCR-matched template images for image subtraction. These functions should have unit tests."
Answer: 80724.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 idea of composing SQuaSH as several individual bokeh apps is atractive, one way to do that is running independent bokeh servers (on different ports) and comunicate among the apps through user interactions in the client side. This ticket capture testing this scenario, understanding implications for deployment and also investigating alternatives.     See for instance example in bokeh mailing list that runs a Bokeh Server by creating a Tornado io_loop, send that loop to bokeh.server.server.Server and embeds two bokeh apps in a Flask app."
Answer: 129785.0

User story: "LTD Keeper current has a special case for make /v/DM-NNNN edition routes for tickets/DM-NNNN branches. A small regex change can allow the same pattern to be used by other types of JIRA tickets, e.g. tickets/LCR-758"
Answer: 90.0

User story: "Jenkins return status is not captured correctly and this information should be displayed at the dashboard as well (right now a missing measurement means the jenkins job failed)"
Answer: 315681.0

User story: "Remove obsolete files and directories and update documentation.  See:  - admin/tools/cluster/  - admin/tools/*"
Answer: 112780.0

User story: {{GetCoaddAsTemplateTask}} does not specify a filter when asking the butler for the correct coadd; this prevents the butler from finding the coadd for Decam data (I think because the filter is not included in difference image template?). The science exposure's filter should be included in the query to the butler.    The task also looks for a coadd with the dataset name "deepCoadd" (e.g.), but this should apparently be "deepCoadd_calexp". 
Answer: 1602695.0

User story: "Currently {{assembleCoadd.py}} supports mean and sigma-clipped mean statistics; adding support for median is simple. The main use case is generating templates for image differencing."
Answer: 303209.0

User story: "Add a testing suite to {{processFile}}.  Specifically create a simple test case that verifies that {{processFile.py}} runs on a known set of test data.    Optionally create simple additional tests if any occur.    Implementation Plan  1. This test data will be from {{afwdata}}, as this adds minimal dependencies.  See https://community.lsst.org/t/should-i-take-example-test-files-from-afwdata-or-obs-test-to-write-a-test-case-for-processfile/1101/2 for a bit of discussion.  2. The dependency on {{afwdata}} will be {{setupOptional}}.  A user shouldn't have to download {{afwdata}} just to run {{processfile}}, but we will want to run this test as part of our regular Jenkins builds and CI efforts to make sure things don't get broken.    Tests of performance against a known standard will be deferred to the {{lsst_ci}} package.    "
Answer: 3658.0

User story: "Sort out any questions needing answers for prototyping alert distribution with Kafka."
Answer: 44265.0

User story: "Review existing VOEvent-based alert systems, tools, and shortcomings and write this up."
Answer: 20173.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: "Make sure I can do these things- Get Kafka quickstart running.  Get Kafka running with Colin's demo.  Get Kafka quickstart running with Docker.  Get Colin's Kafka alert demo running with Docker."
Answer: 3.0

User story: "The treatment will be a static HTML landing page, similar to ldm-151.lsst.io"
Answer: 1166.0

User story: "Following the merger of DM-6919, pipe_tasks is failing on {{master}}:  {code}  *** last few lines:  :::::  [2016-08-29T23:08:10.039201Z]   :::::  [2016-08-29T23:08:10.039219Z] ----------------------------------------------------------------------  :::::  [2016-08-29T23:08:10.039228Z] Ran 8 tests in 2.413s  :::::  [2016-08-29T23:08:10.039233Z]   :::::  [2016-08-29T23:08:10.039241Z] FAILED (errors=1)  :::::  [2016-08-29T23:08:10.039252Z] The following tests failed:  :::::  [2016-08-29T23:08:10.040404Z] /home/jenkins-slave/workspace/stack-os-matrix/label/centos-7/python/py2/lsstsw/build/pipe_tasks/tests/.tests/testTransform.py.failed  :::::  [2016-08-29T23:08:10.040486Z] 1 tests failed  :::::  [2016-08-29T23:08:10.040883Z] scons: *** [checkTestStatus] Error 1  :::::  [2016-08-29T23:08:10.042462Z] scons: building terminated because of errors.  Failed during rebuild of DM stack.  {code}"
Answer: 10.0

User story: "Some improvements on the display  of the threshold lines in the bokeh app   1) we want lines that extend to infinity independently of the zoom, pan   2) we dont want the hover tool on threshold lines   3) we want to turn them on/off  to not hide subtle changes in the measurements (the y-axis range is automatically set to the threshold values if they are on)   4) we want to indicate regions below/above the thresholds"
Answer: 21687.0

User story: "Work for porting {{pipe_supertask}} to Python 3."
Answer: 21682.0

User story: "The current text in LDM-151 for joint calibration (by [~pyoachim]) mostly concerns global calibration, but references to it in the DRP pipelines section assume we'll use Gaia for global calibration.    I'll try to resolve that discrepancy with minimal modification on this issue, and then ask [~<USER> and [~<USER> to review.  "
Answer: 5601.0

User story: "Write up notes on shortlist of candidates and pick one to prototype."
Answer: 106.0

User story: "Background research on what technologies exist and may be used for the alert distribution system and also a first pass on what requirements may be necessary for the LSST use case."
Answer: 38.0

User story: "Augment the SuperTask version of ProcessCcdTask and its subtasks according to the proposal of DM-6274"
Answer: 74895.0

User story: "Work related to porting {{dax_webservcommon}} to Python 3."
Answer: 579317.0

User story: "Work related to porting {{dax_webserv}} to Python 3."
Answer: 477130.0

User story: "Work related to porting {{dax_metaserv}} to Python 3."
Answer: 440719.0

User story: "Work related to porting {{dax_imgserv}} to Python 3."
Answer: 413612.0

User story: "Work related to porting {{dax_dbserv}} to Python 3."
Answer: 466979.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: "Prepare for and participate in the meeting."
Answer: 4099.0

User story: "Prepare for and participate in the meeting"
Answer: 4100.0

User story: "Prepare for and participate in the meeting."
Answer: 4101.0

User story: "Prepare for and participate in the meeting."
Answer: 4101.0

User story: "In order to use the validation_data repositories for subsequent analysis and testing (e.g. jointcal), it is very useful to have pre-generated skymaps available. These files are quite small, and should be produced by those who know the most about each particular data set."
Answer: 1323349.0

User story: "Create a skeleton Light curve app with basic components laid out.    This ticket covers:  - introduce template into firefly entry point.  - create light curve as a template.  - create viewer, controller, and results component for light curve.    - these components are place holders and are not fully implemented.  - create upload form for use during development.  "
Answer: 5781.0

User story: "Uploading a votable result from simple cone search is not currently supported.    We should provide VOTable xml file as part of the format supported by table upload.    Make sure that it handle also VOTable with BINARY2 encoding (attached sample from Gaia DR1)."
Answer: 421928.0

User story: "Realistic quasar SEDs are needed in simulations to test the DCR algorithms.  This ticket will add point-like objects with quasar spectra, appropriate fluxes, and a range of redshifts."
Answer: 1271390.0

User story: "Create a suite of test images that exercise different parts of subtraction and diaSrc detection and characterization.  These will likely be a mix of real images and simulated images.    Having such a suite of tests will help provide feedback when investigating individual tricky cases to make sure that the default algorithms and configurations still do reasonable jobs for other types of objects and subtractions.    I list a few cases here, but part of this ticket will be coming up with a more exhaustive list    1. Isolated transient point source against sky background.    - This should be trivial, should always be captured correctly, and should be a useful exploration of recovery as a function of counts relative to sky noise.  2. Varying isolated point source.    - In principle should be easy.  Compare forced photometry light curve on difference images to the photometry from the science images.  3. Transient point source on top of extended source.    - Classic SN+galaxy case.  Tests noise background decorrelation, object identification, merging, de-blending.  4. Transient point source overlapping with footprint of isolated point source.  (a) bright static source; (b) faint static source    - Tests ability to separate, sensitivity to detecting sources near potential dipoles, reliability of photometry.    * There could be additional levels of spatial PSF variation, spatial background level variation, spatial noise level variation."
Answer: 1985057.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: "Attend LSST2016 commissioning workshop and hold followup discussions to gather use cases and requirements and timeline for integration of services."
Answer: 3.0

User story: "First pass through all services possessing Concepts of Operations to identify main components"
Answer: 11472.0

User story: "Implement changes identified in walking through the Algorithmic Components and Software Primitives sections with [~<USER> and [~<USER>."
Answer: 72.0

User story: "While it is important to use random seeds to prevent a strange random value from causing a test to fail, a handful of tests seem to depend to heavily on the specific seed they are given. This ticket should act as both a log for tests that may be too sensitive to the seed value and eventually corrections to those tests."
Answer: 1863128.0

User story: "Migrate the {{obs_decam}} tests to support py.test"
Answer: 20479.0

User story: "Ticket DM-7377 exists to find a long term solution to an infinite recursion problem in afw catalog python bindings. This is a ticket to introduce a temporary hack until a more concrete solution is found."
Answer: 59.0

User story: This line in meas_algorithms fails under python 3:  https://github.com/lsst/meas_algorithms/blob/3f92e4c18e582ae77eba88b0ee4b522d1298dff7/python/lsst/meas/algorithms/readFitsCatalogTask.py#L115    with the error:  {code}  Traceback (most recent call last):    File "tests/testReadFitsCatalog.py", line 150, in testBadColumnName      task.run(FitsPath)    File "/Users/nate/repos_lsst/meas_algorithms/python/lsst/meas/algorithms/readFitsCatalogTask.py", line 115, in run      table = Table(hdu.data, copy=False)    File "/Users/nate/lsstsw/python3/lsstsw/miniconda/lib/python3.5/site-packages/astropy/table/table.py", line 360, in __init__      init_func(data, names, dtype, n_cols, copy)    File "/Users/nate/lsstsw/python3/lsstsw/miniconda/lib/python3.5/site-packages/astropy/table/table.py", line 643, in _init_from_ndarray      newdata = data.view(dtype).ravel()    File "/Users/nate/lsstsw/python3/lsstsw/miniconda/lib/python3.5/site-packages/numpy/core/records.py", line 480, in __setattr__      raise exctype(value)  ValueError: new type not compatible with array.  {code}  as can be shown by running the readFitsCatalog unit test.    The problem can be worked around by copying, but in the future this should be reported upstream, to see if the copying is a hard requirement due to type limitations or if it can be fixed so we can again create a table without copying.
Answer: 1814619.0

User story: "The conda-lsst code doesn't follow pep8. Run autopep8 on the repository."
Answer: 957492.0

User story: "When running on the cluster, identical queries may return varying numbers of rows. This needs to be investigated and fixed."
Answer: 53268.0

User story: "This ticket is for the work of migrating the obs_subaru tests such that they run with the py.test test runner."
Answer: 1451.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: "Per discussion on Hipchat, it would be useful to record in DMTN-020 that time taken for onboarding of new recruits can be charged to the relevant 00 WBS element.    {quote}  <USER>   @<USER>since I didn't think about it before, is it worth mentioning in the T/CAM DMTN that onboarding activities can be planned and resourced under 02C.*.00?  {quote}"
Answer: 434875.0

User story: "Per [this discussion of LDM-472|https://github.com/lsst/LDM-472/commit/5ad5f731463cb0b17f8919c6d6016e63441b0a2e#commitcomment-18628148], please add material to DMTN-020 about relationships between milestones."
Answer: 138745.0

User story: "The [LDM-132|http://ls.st/LDM-132*] is obsolete, but it is still showing up in Collection-2511. We should move it to an obsolete area, and add a new version that contains redirection to [LPM-44|http://ls.st/LPM-44*] (template can be found here https://docushare.lsstcorp.org/docushare/dsweb/Services/Document-12321)"
Answer: 9319.0

User story: "go through the stack & find all the paf Butler Policies. load them as daf.persistence.Policy and write them out to yaml. in git, remove the paf file, add the yaml file. "
Answer: 405409.0

User story: "This ticket is for the work of migrating the meas_modelfit tests such that they run with the py.test test runner."
Answer: 944.0

User story: "Some of the test code in meas_deblender (e.g. testEdges.py, testFitPsf.py etc...) can generate and save figures if the test file is edited to set a plotting flag to True. Decide how this should be handled in a py.test evironment."
Answer: 1823936.0

User story: There are a number of {{if not self.defDataDir: print("skipping"); return}} blocks in the ip_diffim tests that should be converted to {{@unittest.skipIf}} decorators. Otherwise, those tests may silently not be run, which is bad.
Answer: 10310.0

User story: The short summary for X16 that we created: https://confluence.lsstcorp.org/display/DM/X16  was very well received, many developers liked it. We didn't create similar F16 summary 3 months ago, but let's fix it now. I created a framework for that, see:    https://confluence.lsstcorp.org/display/DM/F16    TCAM's, please add your narratives and link them similarly to how we did that on X16 page. Let's cover all 6 months of F16. When you are done, please remove your name from "reviewers" list.
Answer: 607872.0

User story: "This ticket is for the work of migrating the meas_deblender tests such that they run with the py.test test runner."
Answer: 204.0

User story: "This ticket is for the work of migrating the obs_sdss tests such that they run with the py.test test runner."
Answer: 14331.0

User story: "Implement RFC-214 by modifying the developer guide to recommend numpydoc/reStructuredText markup for Python docstrings instead of Doxygen."
Answer: 10398.0

User story: "This ticket is for the work of migrating the meas_extensions_shapeHSM tests such that they run with the py.test test runner."
Answer: 316.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "This ticket is for the work of migrating the meas_extensions_psfex tests such that they run with the py.test test runner.  "
Answer: 324.0

User story: "The {{testExecutables.py}} script that allows py.test to run executable unittests requires lsst.utils.tests. Several packages such as sphgeom explicitly avoid making lsst.utils a dependency. Hence {{testExecutables.py}} is unable to reside inside the {{sphgeom}} package and {{py.test}} is unable to run the executable unittests for now. Figure out which is better:    # Make sphgeom depend on lsst.utils  # Remove the lsst.utils dependency from testExecutables.py"
Answer: 2024829.0

User story: "The lsst-mariadbclient auto-generated recipe does not work. The build.sh and meta.yaml need to be changed."
Answer: 115060.0

User story: "Port the skymap repository to pytest."
Answer: 12.0

User story: "This ticket is for the work of migrating the meas_extensions_simpleShape tests such that they run with the py.test test runner.  "
Answer: 1527.0

User story: "This ticket is for the work of migrating the meas_extensions_photometryKron tests such that they run with the py.test test runner."
Answer: 1556.0

User story: "This ports {{validate_drp}} to Python 2+3 compatibility.    (Note that the work is still against the {{u/sqre/measurement-api}} integration branch until we can coordinate the coordinate the deployment with SQUASH.)"
Answer: 162899.0

User story: "Check that {{ngmix}} works on python 3."
Answer: 24511.0

User story: "The stack is being adapted to work with Python 3 as well as Python 2. Following the guide from LSST2016 for porting packages to Python 3, adapt the FireflyClient API. This will allow afw.display to work with Firefly in a Python 3 stack."
Answer: 23222.0

User story: "Work associated with adding support for Python 3 to {{meas_extensions_ngmix}}."
Answer: 25611.0

User story: "Work associated with ensuring that {{ci_hsc}} works with Python 3."
Answer: 493986.0

User story: "The Python API for Firefly has changed, due to the Firefly rewrite, and to renaming of methods to be more compatible with PEP8. This ticket updates the existing display_firefly plugin for these changes and also to ensure compatibility with Python 3.    The targeted functionality follows the {{testDisplay.py}} test in the {{afw}} package:  * Display an Exposure or MaskedImage with image and mask overlaid  * Set a specific mask plane color.  * Turn off a specific mask plane.  * Erase a display.  * Zoom to a user-specified zoom level.  * Pan to a particular pixel position.  * Display a symbol at a specific pixel position.  * Change the stretch / scale.  * Display a line with specified vertices.  * -Interact with the display to return a pixel coordinate that a user has clicked on.- Deferred to DM-8173."
Answer: 131460.0

User story: "This ticket is for the work of migrating the ip_diffim tests such that they run with the py.test test runner."
Answer: 1987.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "This ticket is for the work of migrating the daf_persistence tests such that they run with the py.test test runner."
Answer: 11.0

User story: "We can now use astropy in daf_butlerUtils. Looks like it's only a couple of lines of editing to replace the dependency."
Answer: 1428747.0

User story: "Make the unit tests in the sphgeom package compatible with pytest."
Answer: 4549.0

User story: A Python 3 Jenkins build failed with a very unusual log full of "#" and no clear idea of what went wrong.    https://ci.lsst.codes/job/stack-os-matrix/label=centos-7,python=py3/14730//consoleFull
Answer: 57765.0

User story: Several Jenkins runs today, including 14725, 14726 and 14727, have reported success in less than a minute, and it appears that nothing was actually done.    When this occurs the Jenkins message "stack-os-matrix/label=..." is never shown.
Answer: 17747.0

User story: "This ticket covers the work required to get obs_cfht working with Python 3."
Answer: 116550.0

User story: "lmfit is meant to work with Python 3 but this needs to be checked. Some code in the tree does not work with Python 3 but it is possible that this code is not used by LSST."
Answer: 46018.0

User story: "The current release of astrometry.net does not support Python 3. Upstream needs to be fixed."
Answer: 38765.0

User story: "Wrap up the work done in the summer by writing small notes and moving repos to lsst-dm for visibility. "
Answer: 18714.0

User story: DM-7271: table enhancements    * do not apply default data format  * introduce optional display format  * add "AUTO" and "NONE" as format keywords.  * for fits table, set display format to "%.9g" for double type.  * add support for TDISPn fits table header  * remove condition so temp files will not get written into source directory    When reading fits table, set display format to "%.9g" for double if TDISPn is not given.
Answer: 8820.0

User story: "Although most of the tests in the utils package have been updated for py.test, there are a few cleanups left to do in it."
Answer: 18130.0

User story: "Because of sizing considerations, I believe we will need to drop some DIA sources on the floor.  These will be DIAsources we are very certain are artifacts in the image: e.g. glints, airplanes.  I do not believe this is written down anywhere.  This issue is to document this someplace.  Perhaps it should go in the DPDD."
Answer: 379150.0

User story: "LSST2016 DM hack session for updating LSST code to support python3.  Instructions: https://project.lsst.org/meetings/lsst2016/sites/lsst.org.meetings.lsst2016/files/201608-LSST2016-py3.pdf  "
Answer: 1435.0

User story: " I'm seeing some odd behavior with /asynchPeople/ only listing a small number of the actual users.  The list keeps refreshing itself with a different partial list.  Possibly related, /user/<userid> isn't listing all builds for a users, in some cases, it lists no builds at all for users which should have 100s"
Answer: 21727.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: "For example, the drawing layers doesn't allow the text to be copied. Need to be able to copy the labels and the coordinates information. Same for readout, or mission labels, overlays,etc.    In Firefly, the style of key components (i.e., InputFieldLabel) have the user-select value set to 'none'. Change it to default or true.    Steps:  * identify all places allow user to copy  * identify all input area allow user to paste  * make a plan of implementation  * systematically make the change   "
Answer: 1995253.0

User story: Per KT:  {quote}  When loading the Policy, we need to replicate the behavior of pex_policy's {{GetDefaultPolicy}}.    we need to load default policy from certain locations, and then override parameters with more local policies. Order, highest to lowest priority is:    * User  * repository  * obs_*  * butlerUtils    For the in-code ones, it should only need something like: {{os.path.join(utils.getPackageDir(packageName), "policy", policyFilename)}}    We may need a default policy somewhere else (e.g. a tests subdirectory). It could be done with an optional {{dirName="policy"}} argument. That would just be a helper method to find in-code policies.    Also need a {{loadOverride()}} method that takes a YAML file and merges it on top of an existing policy, with what is read in overriding what was there before.    We don't think we need inclusion semantics.  (inclusion semantics is one of the features of pex_policy was that you could put strings starting with "{{@}}" in a paf file and have it include a sub-policy from another file.)  {quote}
Answer: 17505.0

User story: "LSST2016 DM hack session for updating LSST code to support python3.    Instructions: https://project.lsst.org/meetings/lsst2016/sites/lsst.org.meetings.lsst2016/files/201608-LSST2016-py3.pdf"
Answer: 176.0

User story: "The stack is switching to use pytest, as per this page:    https://developer.lsst.io/coding/python_testing.html    The changes in this ticket are updating the tests so they run as standalone tests, and so they also work with py.test"
Answer: 8700.0

User story: AWS does not provide a mechanism to restrict IAM accounts on a per region basis.  However, it is possible to add "conditionals" to most API endpoints to restrict the region.  It will be fairly tedious to determine all endpoints which may be restricted in this manner.    See: https://serverfault.com/questions/589150/is-it-possible-to-restrict-aws-users-accounts-to-a-specific-region
Answer: 1581651.0

User story: "Follow the steps in the [LSST 2016 presentation|https://project.lsst.org/meetings/lsst2016/sites/lsst.org.meetings.lsst2016/files/201608-LSST2016-py3.pdf] by [~<USER> to update the Python code in the {{display_ds9}} package. This will be a learning exercise to prepare for updating {{display_firefly}} for SUIT."
Answer: 4151.0

User story: "This ticket is for the work of migrating the meas_algorithms tests such that they run with the py.test test runner."
Answer: 7206.0

User story: "Port skymap to Python 3."
Answer: 39947.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: It's an oft-stated wish ([e.g.|https://community.lsst.org/t/running-processfile-with-lsst-stack-v12-0/904/1]) that end users should be able to quickly and easily process a FITS file through the LSST stack as, at a minimum, a "SExtractor workalike". This is frequently regarded as being essential for engaging the external community in working with the stack.    This goal is at least partially — and independently — addressed by obs_file and processFile. However, maintaining and enhancing these packages is not clearly in scope for any part of the DM construction WBS. Experience suggests that, when somebody needs them, they generally turn out to be bit-rotted and, at best, semi-functonal. That's a pretty poor new-user experience for collaborators from outside DM who are trying to get up to speed with our code.    Please clarify the long-term requirements (if any) for this work and establish its position within the construction project.
Answer: 33748.0

User story: "Convert unit tests in validate_drp to use pytest"
Answer: 150574.0

User story: "The python unit testing section provides no guidance on the use of specialized asserts. This needs to be fixed. In particular to indicate that {{assertTrue}} should only be used if no specialist equivalent exists and that {{assertRaises}} should be used with {{with}}."
Answer: 271632.0

User story: "Try to see whether cat package is still needed and can be removed (or reduced). There may be files that are still useful (sql directory) but Python code can probably disappear."
Answer: 384729.0

User story: "Boost is out of date. The stack currently uses 1.60.x and version 1.61.x is out. If this upgrade is trivial it will help the Conda builds.    More specifically conda-lsst can't use the upstream SWIG recipe unless we make this minor upgrade. This is because [SWIG 3.0.10 specifically references a dependency on boost 1.61|https://github.com/conda-forge/swig-feedstock/blob/master/recipe/meta.yaml#L25]. In the meantime this is worked around by having our own SWIG recipe (etc/recipes/swig) in conda-lsst.    It is my opinion that this dependency should be optional so I'll attempt to get that change made upstream with conda-forge/swig-feedstock."
Answer: 24481.0

User story: "This ticket is for the work of migrating the pipe_tasks tests such that they run with the py.test test runner.  "
Answer: 1708.0

User story: "Modernize unit tests in meas_astrom to be compatible with test.py"
Answer: 2.0

User story: "This ticket is for the work of migrating the ip_isr tests such that they run with the py.test test runner."
Answer: 1433.0

User story: "This ticket is for updating the tests to use pytest."
Answer: 2681.0

User story: "This ticket is for the work of migrating the cat tests such that they run with the py.test test runner."
Answer: 321.0

User story: "This ticket is for the work of migrating the meas_base tests such that they run with the py.test test runner."
Answer: 10073.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: "There is a PR to update the SWIG Conda recipe in conda-recipes. Once this is accepted it can be removed from conda-lsst (etc/recipes/swig)."
Answer: 211806.0

User story: "Develop a file upload function:  - upload FITS, VOtable, IPAC table, CSV file,  ...  - distinguish file type  - list multiple extensions of FITS, to know the type (image or table) of each extension  - display header information of each extension or the data accordingly  "
Answer: 503332.0

User story: "summarize the following:  - what tags to use in JS file for JSDoc to pick up  - steps to set up and run JSDoc  - lint rules   - certain pitfalls in writing doc in JS source code  "
Answer: 35602.0

User story: "Now we have the first set of Python API, we need to have documents for the functions. https://developer.lsst.io/docs/py_docs.html has some information regarding Python documents generation.   "
Answer: 23799.0

User story: "The current version of conda-build creates a file in the working directory and breaks eups. This creates an error about TaP packages.    The long term fix is to make our eups TaP packages use the new convention which is an environment variable (TAP_PACKAGE=1). This needs to be added to the eupspkg.cfg.sh in all LSST TaP packages.    The workaround until this has happened is to move to an older version of conda-build."
Answer: 47676.0

User story: "SWIG 3.0.10 is required for current builds. But the current version in Conda is 3.0.8. So we need our own recipe to install."
Answer: 47771.0

User story: "See https://community.lsst.org/t/swig-bindings-for-member-functions-returning-a-reference/1022    We should also audit our code for %returnCopy use to see if we can replace it by %returnReference.    This may be useful to do before DM-3549, where I happen to know we're using %returnCopy precisely for this reason.  On the other hand, if we do decide to switch to Pybind11, this obviously becomes a moot point."
Answer: 108350.0

User story: "Fix a few minor errors that were flagged by the Eclipse Neon C++ code analyzer."
Answer: 168.0

User story: "This ticket is for the work of migrating the AFW tests such that they run with the py.test test runner."
Answer: 27366.0

User story: "In early September, we should present to the project — by means of an RFC, RFD, clo posting, or some similar medium — the results of the attempt to port afw to pybind11, along with some commentary and recommendations as to where we should go from here. Prepare the materials needed to make such a presentation. This may include focusing on small pieces of the codebase rather than trying to complete the whole of afw."
Answer: 35683.0

User story: "August X-SWAP goals:    1. Re-configure monitoring statistics uniformly over time periods  2. Instrument collection of queryID from qserv logs into elasticsearch  3. Re-tool pipeline to integrate queryID information parsing and analysis  4. Add cpu-wait on I/O parameters to monitoring and perhaps analysis  "
Answer: 29463.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 package template, https://github.com/lsst/template should be discussed in the developer guide. See also DM-7140 for documentation of dependency tracking, specifically.    A related idea, which would make the docs easier to write, is to turn the template repo into a cookiecutter project (this would be technically straightforward)."
Answer: 1277377.0

User story: "We need a design schema document to identify and describe the core functions that will be commonly used by the Light-curve viewer as well as the inputs and outputs on:  - getting the single exposure image  - compute and getting a phase folded curve  - compute and getting periodogram  - getting the peaks table    Those functions will be used by the processors DM-7162, DM-7164, DM-7165 via one or several Firefly 'search' processor.  Would be also helpful to add the description on the expected table format and content that the (future) NexSci API will offer."
Answer: 72988.0

User story: "The LC viewer need an extra download button to get all the cutout from the light-curve table.  The output can be a tar/zip file, or it can be also the wget (curl) scripts to download them if too many images."
Answer: 262151.0

User story: "DM-5889 only refers to gcc, but we need to fix clang too.    The fix to DM-5889 is different from the way we fix all other compilers, but I'm not proposing fixing this here.  "
Answer: 14.0

User story: "This one is made to include some issues report in DM-7027 (issues 4, 5, 6):    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."
Answer: 19019.0

User story: "There is a problem installing {{protobuf}} on Python 3 triggered by modern EUPS quoting. This may be a generic issue found on bleeding edge EUPS that quote {{$PREFIX}} to allow for spaces in names. On modern EUPS the install target is {{eval}} -led and {{protobuf}} has code copied from the old implementation of the install target."
Answer: 110.0

User story: "As part of the Python 3 port of other packages {{log}} may be sent Python 2 {{unicode}} strings. Support for this must be enabled in the SWIG interface."
Answer: 253.0

User story: "There are few things that are not yet very well understood in the L1 database access from AP. I need to meet with pipeline people at LSST2016 and try to clarify all of them The list of questions will be added below."
Answer: 690293.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: Because one can use any version of phosim at any date, the validStart/validEnd dates are not useful for identifying the correct camera description--and thus the correct obs_lsstSim version. obs_lsstSim knows which phosim version the camera geometry was created from via {{description/phosim_version.txt}} and the {{description/camera/camera.py}} generated with that. To ensure that one is using the correct obs_lsstSim for a given set of phosim data, obs_lsstSim should compare its phosim version with the "branch" field in the phosim headers and either except, fail, or issue a warning when they do not match.
Answer: 1836146.0

User story: "Policy objects have been able to dump to yaml for a while now but the formatting of the yaml file is really bad. It needs to be usable, readable. Refer to pre-existing paf files for reference."
Answer: 28814.0

User story: "Create a technote and a community posting on the new Footprints class to both document the new api, and explain the differences with the old class."
Answer: 374718.0

User story: "Using new functionality exposed by SpanSets, design a new Footprints (and Footprint sets, heavy Footprints) class."
Answer: 151376.0

User story: "Reimplement the current footprints functionality using the new SpanSets class. This will serve as a good checkpoint in development."
Answer: 161443.0

User story: "Implement SpanSet topological operators intersection/difference"
Answer: 151385.0

User story: "Implement functionality to do spatial unions of SpanSets"
Answer: 151386.0

User story: "Implement testing for overlapping spans in SpanSets"
Answer: 151388.0

User story: "Write up a brief technote describing the new SpanSet interface, both things such as functions etc, and descriptions about how it is expected to be used in the future, and made available through python. This will give others a chance to express their needs opinions for span sets while the development is still ongoing"
Answer: 151390.0

User story: "Building off the work done in RFC-37, design a interface for a collection of sets to be called SpanSet. This should encompass most of what currently exists in afw footprints, but contain more topological set functionality."
Answer: 151421.0

User story: "LC viewer (DM-7159) could in principle be displaying 3 kind of LC:  - original LC (WISE mep for example)  - peridogram (power vs period) result from the nexsci API  - phase folded curve (flux vs. time/period)    For plotting chart based on the type of the table (power vs period, or LC or phase folded), we need a controller that will plot the different type described above:  - XY plot for periodogram should have period in log scale,   - XY plot for LC/phase folded should plot flux vs time by identifying the flux (w1mpro for WISE i.e.) and time ('mjd') by default."
Answer: 45732.0