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: "Logical design and work breakdown of service software for all Level 1 services, Batch Production services, file-based portion of Data Backbone services, and IT security services, including network-based security and Authentication & Authorization. Breakdown to level sufficient to provide Basis of Estimate. Incorporate into replan layered architecture WBS.    Consider goals of deploying batch production service facade in spring 2017, early pathfinder integration activities, commissioning, and pre-operations as basis for defining phased service deployment.  "
Answer: 86714.0

User story: "Report on how to modify the current infrastructure to make use of a container cluster manager."
Answer: 108633.0

User story: "The code written for DM-7901 will produce covariance matrices for full visits. Modify the coaddition pipeline to coadd the covariance matrices from multiple visits."
Answer: 201793.0

User story: "The code produced for DM-7129 computes the covariance matrix for individual exposures in a visit. Modify the code in copyGoodPixels.cc to copy the covariance matrices from individual exposures into a covariance matrix for the full visit. "
Answer: 178368.0

User story: "It can be desirable to run ctrl_pool enabled commands (such as constructBias.py from pipe_drivers) without any batch system.    Please add an option  bq. --batch-type None  that simply runs the job in the current process.  "
Answer: 12724.0

User story: The new indexed reference catalogs (for photometric and astrometric calibration) are stored under the dataset "cal_ref_cat". This dataset was only added to obs_lsstSim and obs_test, and did not make it to the rest of the cameras. Since this is independent of camera it makes the most sense to move this into the common datasets in daf_butlerUtils. (The other required datatype, "IngestIndexedReferenceTask_config", is already in daf_butlerUtils).    This is currently blocking usage of the new Gaia reference catalogs, so it would be very useful to have this implemented soon instead of waiting for the various dataset RFCs to close. Giving this to [~<USER> per his suggestion.    
Answer: 28602.0

User story: "Implement slack build notifications equivalent to (and in parallel with) the existing hipchat notifications.  "
Answer: 10331.0

User story: "The new upstream pybind11 now has support for multiple inheritance.  In implementing this, the way bases are specified has changed. The {{py::base}} template has been deprecated in favour of listing the bases directly.  This ticket aims to modify our code accordingly."
Answer: 11697.0

User story: "Please add at least a README file providing a short summary of its functionality and some bare-bones documentation on how to enable and use it."
Answer: 14531.0

User story: "The call to xpa.set() is being passed a unicode string, which doesn't work.  The fix (as <USER>suggested) is to convert to bytes()  "
Answer: 19830.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 {{queryMetadata}} methods in both Mapper and Butler are very badly documented. Their docs both claim to accept a "key" parameter, but the methods don't take "key" (and Butler's version attempts to use one if "format" is not specified), while the "format" parameter (which appears non-optional from the code itself) doesn't have any docstring in Mapper. Looks like these docs rotted badly.
Answer: 364081.0

User story: "We have just merged the functionality of the HSC afterburner (DM-6784, DM-6785).  We need to add configuration options in obs_subaru to activate the features in the coadds."
Answer: 109622.0

User story: "Create an ordered container of {{Point2D}} objects.    The container must interoperate easily with C code. It is recommended, but not required, that it have a view as an array of floating-point coordinates. If a view is not implemented, a fast copy into such a format should be available."
Answer: 201739.0

User story: "Create an ordered container of {{SphPoint}} objects.    The container must interoperate easily with C code. It is recommended, but not required, that it be viewable as an array of floating-point angular coordinates. (If such a view is not implemented, a fast copy into such a format should be available)."
Answer: 201743.0

User story: "We currently use {{pyfits}} in multiple packages: afw, coadd_chisquared, obs_base, meas_astrom, meas_deblender, meas_extensions_psfex, meas_mosaic, obs_cfht, obs_lsstSim, obs_sdss, obs_subaru and obs_test.    Strangely, we only have explicit dependencies on {{pyfits}} listed for afw, obs_base, galsim, healpy and obs_subaru.    galsim can use astropy.io.fits or pyfits. healpy really does seem to not work with astropy.io.fits -- is there a newer version that does?    Please replace {{pyfits}} with {{astropy.io.fits}} where appropriate and update the table files to correctly express the dependency (and removing {{pyfits}} where inappropriate).  "
Answer: 928907.0

User story: "Implementation for what is decided by RFC-231.    Make differencing and coadd datasets consistent wherever possible.  Move common datasets to daf_butlerUtils.  Write a guide of changes for each camera."
Answer: 37510.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: "Systems Engineering and Chilean ITC Tiger Team (September work):  *  Addressed concerns relating to quick-look capabilities on the Summit and operational needs during disconnected operations  * IT Security, definition of SCADA enclave boundary  * Interface of DPP services to other logical components in Chile  "
Answer: 1.0

User story: "Framework for replan WBS (BCR #1):  * Provide framework for delivering the rebaselined construction plan  * Adopted service-oriented framework as structure for WBS  * Pass 1 on developing work breakdown that considers phased business goals and incremental integration of services  * Began rendering logical design of services in EA. This functional architectural model will be the basis for a detailed work breakdown structure, as well as an application mapping needed to set up the high-level components of the CMDB  "
Answer: 3.0

User story: "Operations Planning Workshop, plus lead-up and follow-on:  *  Reviewed DPP WBS and FTEs with operational partners  * Wrote first draft of DPP chapter in concept of operations, with focus on DPP interface to other operations groups, description of DPP-external-facing services for project and users, and listed known high-level software components that will be maintained and evolved in DPP during operations. Contributed to Change Control chapter.  * Discussed ITC provisioning and administration Chile, cadence of changes and deployments, availability of tape support  * Estimating non-labor costing from sizing model  * Prepared 5 change requests for CCB related to Observatory-DPP interface  "
Answer: 5.0

User story: "* Defined commissioning timeline and business goals  * First iteration of defining integration timeline for DPP L1 services needed to support commissioning, based on timeline and goals  * Addressed concerns, especially related to DM-T&S / DPP-Observatory Ops interface, including: the need for Summit data services, the Commissioning Cluster, OCS-driven data processing and data access services, proposed baseline change to EFD replication, catalog of known databases, disaster recovery of EFD, services needed for Auxiliary Telescope, telemetry gateway mechanism (push vs. pull)  "
Answer: 6.0

User story: "Bucket for emergent L1 System work for November. Repurpose this story to represent one or more actual tasks in November."
Answer: 83612.0

User story: "Completed the micro-planning for DM - OCS interaction components. Chose language approach to the OCS Bridge component and implemented a rough but working prototype."
Answer: 39967.0

User story: "Bucket for emergent middleware work for November"
Answer: 89089.0

User story: "Monthly bucket for emergent work."
Answer: 44766.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: "Machines should wake up and be told their intended personality with a +very+ minimal amount of information; just enough so that the newly sentient instance can request registration from a foreman component. After registration, and the list of necessary checks to perform to insure security matters as well as operational integrity, the new machine is added to the Foreman's shape-up list and is ready to receive work.    This initial story in the registration development area is to build a prototype system and propose necessary message content."
Answer: 1.0

User story: "Please create a team in JIRA that we can use for tracking work which is being carried out under the aegis of Project Science. This would apply to e.g. DM-6567.    (This request comes following discussion with [~<USER>. We imagine that [~<USER> would manage the work carried out by this team.)"
Answer: 90.0

User story: "Evaluate InfluxDB for storing system snapshots in a DB keyed to times. Mechanism for saving snapshots and delivering them. Also, consideration on when to take the snapshots with the end goal being a detailed after action playback of the system allowing for the quick ability to track down flaws despite the complexity of the system."
Answer: 3.0

User story: "This work is in preparation for using new DMCS and OCS Bridge components in end-to-end testing with SAL. This corrects issues in both component messaging schema and dictionary as well as implementation flaws."
Answer: 1.0

User story: "Run packaged scripts to test SAL installation and become familiar with its behavior, and then compose an initial interface definition for a new component."
Answer: 84834.0

User story: "When running in verbose mode the virtualDevice assumes that it can access {{self.display.frame}}; this isn't always true.  "
Answer: 19947.0

User story: "Describe the current orchestration software architecture, and post it to the Orchestration confluence page."
Answer: 1809.0

User story: "The Concept of Operations for the LSST _Batch Production Services_ identifies two key components required to satisfy needs of the production system: a workload management system and an orchestration system. The goal of the review is to evaluate if [DIRAC|http://diracgrid.org/], a software framework for distributed computing used by LHCb experiment, could be used as any (or both) of those components.     Final report will be delivered as a DM technote."
Answer: 302377.0

User story: "Per discussion at the 2016-10-03 T/CAM meeting, we need a bug bucket *per WBS* per cycle to enable effort for bug to be correctly accounted for across the WBS structure. Please update DMTN-020 to make this clear."
Answer: 80398.0

User story: "Attend the ADASS XXVI and IVOA meeting in Trieste and write up report."
Answer: 34500.0

User story: "Poster paper to be presented at ADASS XXVI conference. Poster version of the proceedings paper discussed in DM-7863."
Answer: 11599.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 proceedings paper for the ADASS XXVI conference to be held in Italy in mid October. The paper must be submitted to the publication board. The paper covers our approach and experience from doing the Python 3 port."
Answer: 34505.0

User story: "A few components and functions of the StarFast simulator have fallen behind the needs of DM-6245. In particular, the exposures created by the simulator are missing needed metadata. This ticket is to clean up the interface to better support the current uses, and to supply the missing metadata."
Answer: 1550.0

User story: "Take another pass through the plan developed in DM-7846, checking for sanity/correctness/missing information/etc."
Answer: 62043.0

User story: "Using the    * Understanding developed in DM-7560;  * Dependency map developed in DM-7558;  * Responsibility assignments developed in DM-7031;  * Rough resource requirements developed in DM-7032, DM-7034;  * Tooling decided in DM-7559;    develop an outline of a plan for Calibration Products Production."
Answer: 49946.0

User story: "Develop planning packages suitable for loading into PMCS which reflect the DRP plan."
Answer: 9705.0

User story: "There is no LBaaS plugin currently in openstack for load balancing. Need to look at thar"
Answer: 84871.0

User story: "Certification files are used but need to add authentication groups so when connecting remotely user and password credentials can be used"
Answer: 46017.0

User story: "Develop a new WBS describing work to be undertaken in 02C.04."
Answer: 39822.0

User story: "Kubernetes installation has some trouble setting a DNS server for the internal network to resolve names especially when connecting remotely. Might need to create a separate DNS server for it"
Answer: 30244.0

User story: "Before testing in other environments (bare metal) we will try to install Kubernetes directly on top of Nebula OpenStack using current infrastructure and Openstack plugins."
Answer: 11.0

User story: "A initial investigation on using Kubernetes as resource manager "
Answer: 10.0

User story: "Upgrade LSSTdev Puppet to version 4.x  to prepare for GPFS migration."
Answer: 2.0

User story: "Please implement the changes proposed in the RFC"
Answer: 21382.0

User story: "Take another pass through the plan developed in DM-7563, checking for sanity/correctness/missing information/etc."
Answer: 51450.0

User story: The project office requests the following changes to community.lsst.org, needed for wider roll-out (DM-7663):    - Add a prominent disclaimer: "Any opinions, statements (including statements about LSST and what it will deliver), or recommendations expressed on this forum are those of the author(s) and do not necessarily reflect the views of the LSST Project.”    - Add LSST’s new code of conduct to https://community.lsst.org/faq (see attachment)
Answer: 6298.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 a command-line task is executed it would be very helpful to have the command logged. This helps diagnose issues with packages such as {{ci_hsc}} and {{validate_drp}}.    This is trivial when the task is executed from the command line, e.g. add the following to {{ArgumentParser}}:  {code}  log.info("Running: {}".format(" ".join(sys.arvg)))  {code}  It is a bit trickier if the command is executed by code that calls {{CmdLineTask.parseAndRun}} directly; the arguments are readily available but determining the task will require introspection.
Answer: 3112.0

User story: "The preconvolution step for A&L in combination with the decorrelation afterburner was studied and implemented in a test bed in DM-7657; here we are going to translate this into the LSST stack and test it (a bit) on real DECam images."
Answer: 34191.0

User story: "Right now, the LC viewer knows how to fetch the single exposure by hard-coding a WebPlot request (plus some column to use) which is specific to WISE and has a particular image set that doesn't necessarily correspond to the time of the observation (see problem describe in DM-7784.    The single exposure to be displayed should come from and contained by the table itself. The LC viewer shouldn't be aware about the mission, image set or any other specific logic.     Change the way to fetch the single exposure by reading out the URL from the table (a column for each time identified by the flux as a prefix of the column name will be present in the table) and build a WebPlotRequest based on a URL fetch instead.    This method is generic for any data-set such as PTF, WISE, IRTF, etc. The generator of the table is responsible for giving the unique way to fetch the single exposure for a particular time and band.    For example, in case of WISE MEP table, it will contain 4 columns, each of them will have a name such as 'w1_url', 'w2_url', etc. When the user select the flux column to be used by the periodogram/xy-plot, for example 'w1mpro_ep', the image URL request to be used will come from the column which prefix name matches the user selected flux column, in the example, it will be 'w1_url'. The url will be an IBE call to WISE like:    http://irsa.ipac.caltech.edu/ibe/data/wise/allsky/4band_p1bm_frm/7b/00717b/102/00717b102-w2-int-1b.fits      "
Answer: 211558.0

User story: "Some examples in meas_astrom and meas_deblender are very outdated and do not run. For example, meas_astrom/examples/queryReferenceCatalog.py uses {{createSolver}} which has been [removed|https://github.com/lsst/meas_astrom/commit/f0102ac22a9de2f9144dff86151de2d1649171ab], meas_deblender/examples/drivers/tractorPreprocess.py and tractorDeblend.py  use {{lsst.pipette}} which no longer exists.  Please fix them or remove them. "
Answer: 1799099.0

User story: "Produce a scorecard document cataloging features and concerns."
Answer: 45861.0

User story: "Evaluate capabilities and gaps with respect to operational needs (fault tolerance, ability to monitor service and state, etc.)"
Answer: 45862.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Investigate and deploy optimizations to size and build speed for the installation."
Answer: 2.0

User story: The current python version test logic in {{newinstall.sh}} returns a non-zero exit status when run under python 2.6.  This causes the script to exit with no information other than a python stack trace.  Additionally, this prevents {{newinstall.sh}} from functioning on a el6.    {code:java}  [master] ~ $ docker run -ti centos:6 bash  [root@32ae96127e92 /]# python --version  Python 2.6.6  [root@32ae96127e92 /]# PYVEROK=$(python -c 'import sys  > minver2=7  > minver3=5  > vmaj = sys.version_info.major  > vmin = sys.version_info.minor  > if (vmaj == 2 and vmin >= minver2) or (vmaj == 3 and vmin >= minver3):  >     print(1)  > else:  >     print(0)')  Traceback (most recent call last):    File "<string>", line 4, in <module>  AttributeError: 'tuple' object has no attribute 'major'  {code}    
Answer: 55.0

User story: "The search processor to handle the API periodogram is fake for now. It needs to be changed to the concrete API when available."
Answer: 150063.0

User story: "Please, add the same feature to the raw-table highlight as the phase folded table.    When the raw-table LC is loaded and a row is highlighted, display the image single exposure.    "
Answer: 54692.0

User story: "This story is about adjusting the option panel which control the periodogram API call.  Please adapt accordingly if needed when the API is available."
Answer: 150071.0

User story: "Setting of the colorbar in the ImageViewer widget from Python has been implemented as part of DM-7065. However, if the colorbar is updated using the graphical Settings, the Python model is not updated. Implement the synchronization so that the colorbar attribute in Python will update properly. "
Answer: 188914.0

User story: "We will need to package lsst data from any image metadata searches or when using the light curve tool.    This is done with a file group processor for determining what is to be package and retrieving the files."
Answer: 168548.0

User story: "Add zoom and pan functionality to the ImageViewer widget.    * Set zoom level from Python  * After user updates the zoom graphically, update the Python model with the new zoom level  * Set pan position from Python  * After user pans the image graphically, update the Python model with the new pan position  "
Answer: 349731.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: "MAJOR: imposing filters on the catalog makes the plot go away.   (1) Gator. Search in WISE. All WISE. M16. 30 arcmin  (2) In the data table, enable filters. Type “>10” in each of the w1snr, w2snr, w3snr, w4snr column filter boxes. do NOT tab across to get them; it messes up the column headings.  (3) the plot never comes back, the overlays never update on the image, and the “circular cyclical dots” indicating “I’m thinking” never stops. As in, I did this, reproduced this, typed this up, got distracted by a text, checked email in different accounts, came back to this, and still no updates.   Reproducibility:  restarted tool both platforms. WISE/AllWISE/M16/30 arcmin cone.  both come back with 17,816 sources.  impose filters.  plot vanishes as soon as first filter imposed. never returns from all four filters being imposed. Firefox is tilling me 695 sources are left (with the “circular cyclical dots” still spinning) and Chrome is telling me 979 sources are left  (with the “circular cyclical dots” still spinning).  another test:   restarted tool both platforms. WISE/AllWISE/M16/30 arcmin cone.  both come back with 17,816 sources.  impose JUST filter on w1snr. >10  Firefox: 3823 sources, plot vanishes, overlay doesn’t update, “circular cyclical dots” still spinning  Chrome: 3609 sources, plot vanishes, overlay doesn’t update, “circular cyclical dots” still spinning  So, this problem exists for one filter AND more than one filter.    *Copied from the pull request by Loi (9/30/2016)*  We were using cookies to pass websocket connection info to the server. This approach does not work in and embedded mode, ie. Gator.  I've converted to use custom http headers instead. This also affects python api. I've modified the code to reflect the changes.    This change fixed the above problem and should not have any regression issue"
Answer: 4634.0

User story: "When exposing Histogram React Component to API and writing the demo, I found the following bugs:    - log scale for y axis fails  - tooltip might be misaligned with bin boundaries   "
Answer: 305.0

User story: "Attend the weekly meeting, give advice and explanations of Firefly API,  gather issues back to team to resolve. "
Answer: 75095.0

User story: "An important part of the SDSS deblending algorithm was removing objects with similar templates.  Currently, when running multiBand each filter runs the deblender independently so we do not allow it to remove objects in order to keep the same number of objects.  We need to be able to consistently remove objects inside the deblender and have it be consistent across filters.    "
Answer: 95346.0

User story: "Participate in the 2-day discussion of 2D plotting package design,  functions supported, and strategy for introducing new 3rd party software packages,"
Answer: 1.0

User story: "Participate in the 2-day discussion of 2D plotting package design,  functions supported, and strategy for introducing new 3rd party software packages,"
Answer: 2.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Participate in the 2-day discussion of 2D plotting package design,  functions supported, and strategy for introducing new 3rd party software packages,"
Answer: 2.0

User story: "Participate in the 2-day discussion of 2D plotting package design,  functions supported, and strategy for introducing new 3rd party software packages,"
Answer: 3.0

User story: "Participate in the 2-day discussion of 2D plotting package design,  functions supported, and strategy for introducing new 3rd party software packages,"
Answer: 5.0

User story: "Participate in the 2-day discussion of 2D plotting package design,  functions supported, and strategy for introducing new 3rd party software packages,"
Answer: 6.0

User story: "Participate in the 2-day discussion of 2D plotting package design,  functions supported, and strategy for introducing new 3rd party software packages,"
Answer: 7.0

User story: "Organize in the 2-day discussion of 2D plotting package design,  functions supported, and strategy for introducing new 3rd party software packages,"
Answer: 7.0

User story: "Participate in the 2-day discussion of 2D plotting package design,  functions supported, and strategy for introducing new 3rd party software packages,"
Answer: 10.0

User story: "participate discussion of WBS restructuring,  review and edit"
Answer: 882.0

User story: "participate in the discussion of WBS restructuring"
Answer: 885.0

User story: "Restructure SUIT WBS to prepare for the long term replan. We want a WBS structure to capture the work we are doing and going to do better. "
Answer: 887.0

User story: "To get the PDAC up and running several things need to happen:    * firefly apache and tomcat server need to be set up on  sui-proxy01,  sui-tomcat01, maybe sui-tomcat02 (if there is one)  *  we need a way to easily rebuild and redeploy, should be use Jenkins?    Loi will determine if Jenkins is necessary.  However we do it, we need to be able to pull, build, and deploy."
Answer: 55829.0

User story: There are a bunch of "extra" branches associated with this ticket as early, the thinking was to assembly the weekly containers out of conda packages.  It was decided that this was premature and to stick to the known working method of using {{newinstall.sh/eups distrib install}}.    Weekly docker containers builds were implemented as follows:    * The docker agent  was added to all jenkin's {{el7}} build slaves in order to facilitate builds.  * a collection of new jenkins jobs using {{lsst-sqre/packer-newinstall}} ({{packer}}) to construct the containers were added  * jenkins handles the push/pulling of docker images  * The {{weekly-release}} jenkins job was extended to construct a container after {{build-tag-publish}} is successful  
Answer: 76191.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: "As part of the LC viewer public release, 2D plotting features need to be added/changed for next December for PTF if available.   Ultimately it has to be ready for WISE Light-curve release in March 2017.    This ticket should collect the 2D plotting features required for that release:    - -Line Chart, connected data-points-  - -Error bars-  - Add axis intermediate tick marks, specially interesting for LOG scale (moved to DM-9575)"
Answer: 213003.0

User story: "When the tri-view have found an object is need to capability to launch the time series viewer.    Add time series viewing capability to the /suit app.    When suit detect that a table contains time series data, it should add a button to display the table in the time series viewer.  If a table contains object IDs that can be used to query time series data, it should add a button to display the time series data by querying of the highlighted object ID."
Answer: 228737.0

User story: "Make a LSST version of the time series viewer prototype.    The work should include the following:    * LSST search processor doing object and flux id search  * Make the abstraction infrastructure to be mission specific  * Experiment to understand where we need to abstract  * loading the correct images based on the data source (using the abstraction layer)      This is the first part of changes to support LSST time series: (done)    * Refactored LSSTCataLogSearch - separated LSSTQuery - with the common code to do DAX queries  * Added LSSTLightCurveQuery - to get raw lightcurve table for a given objectId  * Refactored LC code to abstract WISE specific code into a LCMissionConverter object  * Supports either WISE or LSST raw table (from LSSTLightCurveQuery processor)    Limitations of LSST Light Curve app that will be addressed in another ticket  - The table should be filtered manually (by applying a filter to filterName column), UI for switching the bands is not ready  - images are not cutouts, centered on the object ra and decl, but a full image containing ra and decl (cutouts are being implemented by DAX)  "
Answer: 190257.0

User story: "The generated wrappers will live parallel to the Swig wrappers. This ticket only covers the C++ wrappers themselves, not the Python layer on top (which will continue to use the old wrappers) all work will stay on a separate branch and will not be merged to master until DM-6168 is complete.    The tests included in this ticket are:  # testDetector.py  # testMakePixelToTanPixel.py  # testExposure.py  # testCamGeomFitsUtils.py  # testCameraGeom.py  # testDistortedTanWcs.py  # testCameraTransformMap.py  # testColor.py  # testOrientation.py  # testCameraSys.py  # testWarper.py (moved to DM-8619)"
Answer: 107731.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 the search processors related to accessing the lsst DAX.    * Work with <USER>for a common design of the search processor.  * implement all the searches discovered by DM-7762.  Use DAX calls designed by DM-7762.  * the should be one search processor to return image data and 1 or more for various types of table data.    This ticket is divided into two tickets.  This one is for the work of processing the data and saving to a IpacTable/DataGroup.  This work includes writing two search processors, one for MetaData and the other for TableData itself.  The TableData processor has to call the MetaData processor so that the proper data types are defined.     The ticket DM-8010 is to write the data access part of the processors and image search processor.  The data access is depending on the URI and the search string etc.  "
Answer: 27519.0

User story: "The generated wrappers will live parallel to the Swig wrappers. This ticket only covers the C++ wrappers themselves, not the Python layer on top (which will continue to use the old wrappers) all work will stay on a separate branch and will not be merged to master until DM-8467 is complete.    The tests included in this ticket are:  # {color:#14892c}image.py{color}  # {color:#14892c}offsetImage.py{color}  # {color:#14892c}statistics.py{color}  # {color:#14892c}imagePca.py{color}  # {color:#14892c}maskedImageIO.py{color}  # {color:#14892c}wcs1.py{color}  # {color:#14892c}stacker.py{color}  # {color:#14892c}mask.py{color}  # {color:#14892c}polygon.py{color}  # {color:#14892c}approximate.py{color}  # {color:#14892c}display.py{color}  # {color:#14892c}warpExposure.py{color}  # {color:#14892c}convolve.py{color}  # {color:#14892c}test1079.py{color}  # {color:#14892c}imageIo1.py{color}  # {color:#14892c}maskedImage.py{color}  # {color:#14892c}background.py{color}"
Answer: 109471.0

User story: "Do the following:     * Add hooks so the time series tool to be able to be launched externally   * Gator or the triview (or something else) should be able to launch the LC with search parameters (see my comment below about initial values for IRSA)"
Answer: 190148.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 generated wrappers will live parallel to the Swig wrappers. This ticket only covers the C++ wrappers themselves, not the Python layer on top (which will continue to use the old wrappers) all work will stay on a separate branch and will not be merged to master until DM-6168 is complete.    The tests included in this ticket are:  # {color:#14892c}testFluxFromABMag.py{color}  # {color:#14892c}testWcs835.py{color}  # {color:#14892c}testHeader.py{color}  # {color:#14892c}testTableArchiveImport.py{color}  # {color:#14892c}testMaskedImagePersistence1.py{color}  # {color:#14892c}testImageIo2.py{color}  # {color:#14892c}testTicket2352.py{color}  # {color:#14892c}testTicket2905.py{color}  # {color:#14892c}testImagePersistence1.py{color}  # {color:#14892c}testScaledPlus.py{color}  # {color:#14892c}testRandom1.py{color}  # {color:#14892c}testImageTestUtils.py{color}  # {color:#14892c}testKernel.py{color}  # {color:#14892c}testWcsFitsTable.py{color}  # {color:#14892c}testTicket2162.py{color}  # {color:#14892c}testStatisticsOverloads.py{color}  # {color:#14892c}testMakeWcs.py{color}  # {color:#14892c}testStatisticsMasked.py{color}  # {color:#14892c}testKernelIo1.py{color}  # {color:#14892c}testEllipse.py{color}  # {color:#14892c}testRowColumnStats.py{color}  # {color:#14892c}testMethods.py{color}  # {color:#14892c}testKernelImagesForRegion.py{color}  # {color:#14892c}statBug1697.py{color}"
Answer: 90532.0

User story: "Evaluate the TICK stack considering monitoring system requirements and interface needs"
Answer: 11221.0

User story: "Initial review of the TICK stack for suitability.  A survey was carried out to look at the functions it provides and the ease of integration with our existing software under development."
Answer: 11222.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: Draft logical design of the monitoring system:  Requirements of the Enterprise Service Monitoring Software Needs:  -       Integrate ITC monitoring ­ how do we get info out of RRDBs sufficient for service monitoring?  -       Ability to mirror for disconnected operations -- how to run 2 copies and synchronize?  -       Ability to get info out ­ can data be exported to Pandas/R/similar analytical environment?  -       Python API for programs/applications to inject data  -       Ability to produce Go plugins ­ if monitoring agent that is not ITC  -       Generate displays for well-known customers using 1 of 2 display generators that database supports  -       Conquerer tool ­ generates events by monitoring scripts, back-end displays  o   Integrate with paging infrastructure, but paging should be separate  Ability to inflate independent test instances of monitoring infrastructure and bring in tools from production infrastructure to run tests and retaining test records.  Admin of databases itself:  -       State data retention policies  -       State data summaries and their own retention policies  -       Using namespace in the database ­ schema development and maintenance, how to use namespace so there is not chaos  It would look like we need something akin to a "Swiss Army Knife on the back-end which will be able to do the following   * integrate someone else¹s software   * communicate directly with software we write   * work with agent    One of the tools which seems to satisfy the aforementioned requirements was the TICK stack which includes a InfluxDB   
Answer: 11223.0

User story: Discussions with the team to assess the current ITC service level monitoring that is being developed.  Puppet system provides a ITC monitoring agent that reports status back to the monitoring element. This can be tuned to suit our needs in terms of the frequency of the poll (which in this case is 1 hour). this will not meet the needs of the service that we need to monitor at the service level.  Based on the discussions "a trust but verify" relationship was developed to integrate this at the service level. Looking at the possible "push" / "pull" of the required information. It is generally good to get regular status information (periodically) as a pull (polling) and any faults / failures as an immediate push from the entity being monitored.  Discussions were also done with DPD team (Jim Parsons and Jason Alt) on the functionality that will be needed to be embedded in the L1 functions.  Also under discussion was the need for the monitoring the network functions and interfaces on the circuits from the summit to NCSA.  
Answer: 11224.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: "Definition of the Architecture of the devices, processes and services to be monitored. This includes looking at commercially available frameworks for monitoring like   *Open NMS  * Nagios XI  *  and other similar Open Source provisions.  This will need a definition of a dashboard for the ITSM service management functions.  It would require to be 24/7 a service. More consideration needs to be given as to the SLA (Service level Agreements) between the various participating entities."
Answer: 11224.0

User story: "when getting objects in butler, keep a weakref to objects so that if they are a component that is loaded a second time by another object the component does not get loaded into a second instance, but is instead shared between composites.    if feasible, the caching mechanism should be easy to change by configuration or by subclass or plugin.    notes:   weakref caching has certain implications; objects will not be kept if another (composite) object is destroyed; if the composite is destroyed and then another composite that uses the same component is loaded, the object will be reloaded. (this has plusses and minuses, depending on use case    Butler does not protect shared objects being changed and it's possible that one owner could change the shared object at a time or in a way that the other owner does not expect it. The question of how to address this remains open."
Answer: 60729.0

User story: "I added document {{doc/FITS headers for exposures.rst}} to afw and am asking him to move the document somewhere more suitable, as per [~<USER>'s request on github https://github.com/lsst/afw/pull/89"
Answer: 1893976.0

User story: "Move the setting in karam.conf.js into webpack.config.js to support js testing"
Answer: 8625.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: Jenkins sometimes fails to run the demo despite being asked to run it. I had a page, but it had "latest" in it, and I can't find it any more. The page showed the information below, but the build was 16475 and that appears to have failed, despite the page showing it has having completed. This may be more a problem of showing incorrect config and providing a latest link where a user is expecting a link to the job the user started.    Notice the following in the configuration (which matches what I requested, though I am surprised to find lsst_ci listed twice; I explicitly requested it and I guess Jenkins already included it because it was running the demo):  {code}  PRODUCT: lsst_sims lsst_distrib lsst_ci ci_hsc lsst_ci  REF_LIST: -r tickets/DM-5503  RUN_DEMO: yes  {code}    and the job ends with:  {code}  # BUILD b2748 completed.  The DM stack has been installed at /home/jenkins-slave/workspace/stack-os-matrix/label/centos-7/python/py2/lsstsw with tag: b2748.  ------------------------------------------------------------------------------    Skipping Documentation build.  Skipping Demo.  [PostBuildScript] - Execution post build scripts.  [py2] $ /bin/sh -xe /tmp/hudson7603861939452210171.sh  ++ lsof -d 200 -t  + Z=  + [[ ! -z '' ]]  + rm -rf /home/jenkins-slave/workspace/stack-os-matrix/label/centos-7/python/py2/lsstsw/stack/.lockDir  Finished: SUCCESS  {code}  
Answer: 371814.0

User story: "TO understand how regular command line tasks work and interact with the rest of the system I want to run a simple example task which takes some data from somewhere and produces more data."
Answer: 21831.0

User story: "The Histogram is used by FitsRead.  Therefore it is very important to have unit test added for Histogram."
Answer: 31679.0

User story: "Under the plot package, there are many classes which are making the image plot.  Crop is one of the such utility class.  Therefore, the unit test is a must."
Answer: 58759.0

User story: "The Zscale class is used by FitsRead.  Therefore, it is important to make sure it works correctly all the time.  The unit test is needed to identify any bugs introduced by changing this class."
Answer: 142565.0

User story: "The unit test should be added for FlipXY class."
Answer: 203058.0

User story: "The FitsRead class is one of an important class in Firefly.  It is necessary to have unit test so that any bugs introduced by changing FitsRead can be detected immediately."
Answer: 151080.0

User story: "Butler can look up policy in a repository, but right now it does not have any way to put policy into a repository. We need to define API for that and implement it.    When this is implemented, fix the hack workaround in daf_butlerUtils testComposite.py"
Answer: 70712.0

User story: "pex_config is one of the central pieces in task/supertask. Figure out its design and how it is used by tasks."
Answer: 1180.0

User story: "Define and procedure involving introducing a change that breaks existing code (e.g., such as changing heavily used API)"
Answer: 1492503.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 region text defined with  region object (not text region) is not shown on PNG.   "
Answer: 3259.0

User story: "This story involves understanding the data we need to access for the PDAC UI.     * Understand the two applications we want to make for the PDAC: general catalog search and light curve viewer  * Understand the data base searches we need to do.  * Analyze the tables and data we need for the two applications.  * Come up with example select statements for each search.  * Try to make the the related DAX URL for each search. (We might need to make a second ticket to really work this last issue)  * Get some example fits files and put the into firefly_test_data    The scope grew and more work in documenting the difference of qserv_* functions and scisql_* functions. "
Answer: 92645.0

User story: "Build the LSST Catalog search form using the components form IRSA catalog search  form.      * Generalize the table selection component    * Make a simple search panel with target panel, table constrains, and table list."
Answer: 35057.0

User story: "DM-7753 (as fixed) leads to an exception in meas.algorithms.utils.showPsfMosaic (unfixed it's a SEGV).  Please fix this.  "
Answer: 35.0

User story: "The OCS Bridge will act as a translator for messages from and to the SAL. In order to do this, the OCS Bridhe will need to subscribe to the correct channels, interpret incoming XML, and XML encode outgoing ntelemetry messages from the DMCS."
Answer: 50188.0

User story: "Outline existing production pipeline tasks in the stack (e.g. those currently used in ci_hsc), summarize the main input and output data of each major pipeline, and note the level of data products it's operating on."
Answer: 30415.0

User story: "{{pipe_drivers}} needs to be converted to python 3."
Answer: 196354.0

User story: "This simple script:  {code}  import lsst.afw.image as afwImage    exp = afwImage.ExposureF(1, 1)  {code}    generates the error:  {quote}  log4cxx: No appender could be found for logger (afw.image.Mask).  log4cxx: Please initialize the log4cxx system properly.  {quote}    I'd expect to be able to use LSST primitives without explicitly setting up the logging.  "
Answer: 7284.0

User story: "Running the attached script generates a SEGV.  Please fix this, and check for similar errors elsewhere in meas_base.    {code}   Thread 0 Crashed:: Dispatch queue: com.apple.main-thread  0   libmeas_base.dylib             0x00000001150c83e0 lsst::meas::base::CentroidChecker::operator()(lsst::afw::table::SourceRecord&) const + 240  1   libmeas_base.dylib             0x00000001150cdd01 lsst::meas::base::GaussianCentroidAlgorithm::measure(lsst::afw::table::SourceRecord&, lsst::afw::image::Exposure<float, unsigned short, float> const&) const + 449  2   _baseLib.so                    0x0000000114d10fd6 _wrap_GaussianCentroidAlgorithm_measure(_object*, _object*) + 422  {code}"
Answer: 156.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: "If an exposure within a visit goes awry, this part of the DMCS will generate the appropriate telemetry response and hand it to the OCS Bridge to be sent."
Answer: 113983.0

User story: "This work phase captures initial archival logical interaction and movement."
Answer: 52187.0

User story: "This story tracks the first part of the necessary work adjusting the prototype OCS Bridge into a mature component that interacts with both the OCS SAL and the DMCS component."
Answer: 10222.0

User story: "After some improvements in the squash metrics plot it is ready to be deployed to production, this ticket captures that.    The current master is available in my test environment:    https://angelo-squash-squash.lsst.codes/ "
Answer: 3690.0

User story: "In discussing the PDAC schema and references from its tables to images today, it emerged that work remains to be done to make the coadded images from the 2013 Stripe82 processing available in PDACv1.  They will be an important part of making that processing available to users.  Most of the effort so far has been on calexps.    I was not able to find a ticket for that yet; epic DM-6223 doesn't mention coadds, and the stories in it seem to be about calexps only."
Answer: 15339.0

User story: The ZOGY algorithm can be performed without FFT-ing the images. This ticket will involve developing a test implementation of this procedure and comparing it with the simple FFT-based version for simulated images.     This will include computing the diffim PSF, correct variance plane, and proper likelihood image "S" as prescribed in Zackay, et al. (2016).
Answer: 34500.0

User story: "There's a call in constructCalibs.py that doesn't specify the dafBase.Timescale  "
Answer: 13.0

User story: "{{obs_decam}} README has outdated information, leading to confusion like [this|https://community.lsst.org/t/error-of-using-obs-decam/1181/1]. Remove the outdated instructions to avoid confusion. For example, {{processCcdDecam.py}} is no longer used since DM-4692 (https://community.lsst.org/t/backward-incompatible-changes-to-processccdtask-and-subtasks/581) "
Answer: 1492.0

User story: "Use the future package; see https://confluence.lsstcorp.org/display/DM/Python+3+Porting+progress    All of {{validate_base}}’s (few) dependencies are already Python 3 compatible."
Answer: 96560.0

User story: "This ticket is used to update Verification Cluster documentation, follow up to DM-6010.  "
Answer: 3390.0

User story: "obs_sdss has some tests in it: those should get lifted into obs_base and deleted (or just deleted, if there is already an equivalent test in obs_base), and {{test_obs_sdss.py}} should be created to inherit the obs_base testing framework.    Once the new tests are merged in, the other obs packages that depend on obs_base should have their test setUp updated to reflect the new tests."
Answer: 1695146.0