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: "This is a proof-of-concept for building the new Sphinx-based Science Pipelines documentation using Jenkins.    - https://github.com/lsst/pipelines_lsst_io is the core documentation repository  - https://github.com/lsst/validate_base is a package with prototype documentation that can be built with {{pipelines_lsst_io}}.  - ltd-mason is the tool that 1) copies package doc directories into {{pipelines_lsst_io}}, 2) runs {{sphinx-build}}, and 3) uploads to LSST the Docs."
Answer: 50679.0

User story: "change the LC results area to implement the new UI flow.    The development includes:    revamp result area including finder panel, chart, table and image areas  . finder panel includes entries which are mission related and non-related.  . synchronize among table highlight, image selection, chart highlight and entries changes.  . add 'Period finding' button in the finder panel to move to period area to find period and the phase folding table.  . Reorder the phase folding table by moving phase related columns to the left side of the table.  . add indication regarding table sort columns and sort order.  update period area according to the feedback to the flow and the layout of DM-8668  . show the time and flux field as read only data (as set in result area).  . put period min and max entries to the end of the period slider.  . highlight the period field.  . change the layout of phase folding chart, periodogram tables and charts.  . put 'revert to' button by 'period' field in the finder panel.  . put 'change periodogram' button into the priodogram table/chart area.  . update the validation functions for some fields in the finder panel,  - default: period min = 0.001, and period max = 365.  - period min >= 0.001, period max > period min, period >= period min and period <= period max  - extend period max or period min in case period is set beyond the min and max range.  - adjust period in case period min is set greater than period or period max is set less than period.  - zero point time >= 0.0.  . update the slider to work for any period range scale.  . make the look of phase folding chart consistent with those of periodogram table and charts.  . no slider and period related items changes until the periodogram popup is closed.  update Periodogram popup  . update field validation which allows period min, period max and step size fields to be blank"
Answer: 78102.0

User story: "Work with DM-8668 to design and how the LCManager should work"
Answer: 822493.0

User story: "Do the following:  * Implement the new Period Finder Panel portion of the Light Curve UI  * Revamp the LcManager to work with new flow  * Make change to LcResult for new UI  * Make any necessary store changes"
Answer: 56453.0

User story: "This work removes the following:    ctrl_platform_lsst  ctrl_platform_gordon    from etc/repos.yaml    adds:    ctrl_platform_lsstvc    to etc/repos.yaml    and moves the repos to    lsst-dm/legacy_ctrl_platform_lsst  lsst-dm/legacy_ctrl_platform_gordon  "
Answer: 505.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Use ADQL parser prototype to extract the columns and their associated tables from an arbitrary query, with the goal of looking up UCDs and other metadata."
Answer: 191406.0

User story: "To ensure the Firefly works correctly, the unit test for ImageData is needed."
Answer: 82256.0

User story: "The unit test is needed for Geom class. This class is used for making images.  Therefore it is important to make sure it works as it should.    Analysis by Lijun:  * Add unit test for its public method  * Add end to end test for its seven cases so that all methods can be run.  * Prepare different input and output data set to test different combinaitons"
Answer: 71945.0

User story: "On request.    Testing the integration via this ticket    "
Answer: 16.0

User story: "The O2b line is extracted from ∼140 spectra of HD14943 taken during run 3 and the equivalent width (EW) is measured (illustration figure 2). The result is presented on the first figure as a function of time and airmass. Each night is distinguished by a different color and the size of the EW is normalized by the mean value of the run, times .1 to scale the axis. The observation strategy has been to take three images in a raw each time a given star was observed. As a result, it can be estimated that there is a fast varying component of the EW measurement which can be as high as 20%. This need to be study in greater detail, and images from Rasicam would prove useful."
Answer: 138052.0

User story: "When images are displayed, a change of table/xy plot highlight will change the image currently active, the over way around is not true. If i click on an image, the table/xy plot doesn't change or follow the image selected.    This is also part of the story DM-7971.    "
Answer: 104603.0

User story: "Determine the users of binary distributions and determine a basic plan with proof of concept for how to proceed to meet those users' needs."
Answer: 74776.0

User story: "Wrap {{testDs9.py}} with pybind11.  This was left over from DM-7799 because it didn't really fit there."
Answer: 11814.0

User story: "Trying to use landscape.io,"
Answer: 101611.0

User story: "This documentation will be presented at ASTERISC demo."
Answer: 155983.0

User story: "{{AUTOBRIEF}} is turned off by default in our Doxygen configuration. The developers guide   https://developer.lsst.io/docs/cpp_docs.html suggests using @brief but the very first example after that omits it and much of our code omits it. I think it should be optional and certainly much of our code reflects that.    The proposed fix is set the following to {{YES}} in in `doc/base.inc`:  - {{JAVADOC_AUTOBRIEF}}  - {{QT_AUTOBRIEF}}    We mostly use javadoc style, but there is no harm in supporting both, and some of our code may already use QT style."
Answer: 23.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "To make display_firefly be installable via eups, and with the implementation of its dependencies in DM-8295 and DM-8296, some updates are needed:    * Add the firefly_client packages as a dependency in ups/display_firefly.table  * Remove the xpa, pex_exceptions and swig parts from ups/display_firefly.cfg  * Add the display_firefly repository to etc/repos.yaml in the lsstsw repository"
Answer: 3979.0

User story: "astrometrySourceSelector can not be used alone in matchOptimisticB as it tests for two different criteria depending on if it's matching objects(needs good centroid, is a parent object, has a minimum S/N, valid flux) or returning those objects to astrometry.py(all the previous plus is not saturated, is not interpolated, and is not edge). The new source selector matcherSourceSelector will make former selection, astrometrySourceSelector will make the second test. This ticket extends the work of DM-6824."
Answer: 53275.0

User story: "Figure out how to run enough of processCcd.py to detect and extract images of out-of-focus stars.  Doing this will likely require asserting something for the PSF.  First try just asserting some various widths for a GaussianPsf.  If that isn't satisfactory, then maybe a matched filter with a more realistic image of an out-of-focus donut will work."
Answer: 51797.0

User story: "Building on the example Sphinx site developed in DM-8641, install [numpydoc|https://pypi.python.org/pypi/numpydoc], modify your Python code to use numpydoc-formatted docstrings, and experiment with having them properly displayed on your Sphinx site."
Answer: 254926.0

User story: "Few random thoughts on quanta to keep record of my misunderstanding."
Answer: 166967.0

User story: "To learn how the sphinx framework works with the actual code, will make some simple examples of python code with docstrings, then in an rst file, place a directive to process that piece of code, and make a nice finally processed html page from it."
Answer: 31093.0

User story: "The current docstring for the deblender is missing descriptions for more than half of the parameters and an improved description."
Answer: 5708.0

User story: "Refine design for file portion of data backbone focusing on interactions with L1, L1 PP, and L2  current file requirements: (unique filename vs unique (path + filename)  current metadata service and future plans vs anticipated (DES-like)  current provenance service (and future plans) vs anticipated (DES-like)"
Answer: 808835.0

User story: "Initial design for file portion of data backbone focusing on interactions with L1, L1 PP, and L2  current file requirements: (unique filename vs unique (path + filename)  current metadata service and future plans vs anticipated (DES-like)  current provenance service (and future plans) vs anticipated (DES-like)"
Answer: 808836.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: "Initial gathering of requirements for file portion of data backbone focusing on interactions with L1, L1 PP, and L2      current file requirements: (unique filename vs unique (path + filename)      current metadata service and future plans vs anticipated (DES-like)      current provenance service (and future plans) vs anticipated (DES-like)  "
Answer: 73116.0

User story: "This is transcribing these templates from straight outline form into rst that sphinx can parse, making sure we all agree on the structure of them. "
Answer: 50526.0

User story: "Please add a configuration option to disable interpolation over saturated pixels.  I.e. an if block around  {code}  self.saturationInterpolation(ccdExposure)  {code}  in isrTask.py"
Answer: 315002.0

User story: "The goal is to generalized the prototype described in [DM-8633|https://jira.lsstcorp.org/browse/DM-8633] to allow it to handle arbitrarily complex workflows."
Answer: 115454.0

User story: "Pegasus' abstract workflows (DAXs) are specified in XML format and it provides a dedicated API for their generation. The goal is to write a prototype of a wrapper which will automate creating DAXs for multi-component, though sequential, workflows. As a starting point, a sequential workflow representing algorithmic components of {{processCcd}} will be used."
Answer: 114033.0

User story: "Pegasus provides a dedicated library to generate workflows in the XML format. To learn that API and Pegasus' core concepts, I will write a script allowing to run a single task, {{processCcd}} combined with {{Executor}}, using Pegasus.  "
Answer: 34596.0

User story: "One frequently occurring problem with pybind11 is segfaults happening when two classes in an inheritance hierarchy have different holder types (i.e. parent has {{unique_ptr}} holder type while derived class has {{shared_ptr}}).  This ticket aims to investigate and implement (if possible) a compile time (or import time) check for matching holder types.  While this check is not strictly necessary, it would make the pybind11 stack significantly more robust."
Answer: 85286.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: Last weekly available is {{w_2016_48}}. Judging by the logs, builds have been failing since 29 November. Error is:    {code}  ***** error: from /ssd/lsstsw/stack/EupsBuildDir/Linux64/daf_persistence-12.1-15-gaf6b168/build.log:  buildConfig(["doc/doxygen.conf"], ["doc/doxygen.conf.in"])  doxygen /ssd/lsstsw/stack/EupsBuildDir/Linux64/daf_persistence-12.1-15-gaf6b168/daf_persistence-12.1-15-gaf6b168/doc/doxygen.conf  /ssd/lsstsw/stack/EupsBuildDir/Linux64/daf_persistence-12.1-15-gaf6b168/daf_persistence-12.1-15-gaf6b168/src/DbStorageImpl.cc:192: warning: argument 'am' of command @param is not found in the argument list of lsst::daf::persistence::DbStorageImpl::startSession(std::string const &location)  DirectoryInstaller(["/ssd/lsstsw/stack/Linux64/daf_persistence/12.1-15-gaf6b168/tests"], ["tests"])  Install file: "ups/eupspkg" as "/ssd/lsstsw/stack/Linux64/daf_persistence/12.1-15-gaf6b168/ups/eupspkg"  Install file: "ups/daf_persistence.cfg" as "/ssd/lsstsw/stack/Linux64/daf_persistence/12.1-15-gaf6b168/ups/daf_persistence.cfg"  Install file: "ups/daf_persistence.build" as "/ssd/lsstsw/stack/Linux64/daf_persistence/12.1-15-gaf6b168/ups/daf_persistence.build"  DirectoryInstaller(["/ssd/lsstsw/stack/Linux64/daf_persistence/12.1-15-gaf6b168/include"], ["include"])  DirectoryInstaller(["/ssd/lsstsw/stack/Linux64/daf_persistence/12.1-15-gaf6b168/lib"], ["lib"])  DirectoryInstaller(["/ssd/lsstsw/stack/Linux64/daf_persistence/12.1-15-gaf6b168/policy"], ["policy"])DirectoryInstaller(["/ssd/lsstsw/stack/Linux64/daf_persistence/12.1-15-gaf6b168/python"], ["python"])Install file: "ups/daf_persistence.table" as "/ssd/lsstsw/stack/Linux64/daf_persistence/12.1-15-gaf6b168/ups/daf_persistence.table"  DirectoryInstaller(["/ssd/lsstsw/stack/Linux64/daf_persistence/12.1-15-gaf6b168/src"], ["src"])  eups expandbuild -i --version 12.1-15-gaf6b168 /ssd/lsstsw/stack/Linux64/daf_persistence/12.1-15-gaf6b168/ups/daf_persistence.build  DirectoryInstaller(["/ssd/lsstsw/stack/Linux64/daf_persistence/12.1-15-gaf6b168/doc"], ["doc"])  eups expandtable -i -W '^(?!LOCAL:)' /ssd/lsstsw/stack/Linux64/daf_persistence/12.1-15-gaf6b168/ups/daf_persistence.table  eups expandtable: Processing /ssd/lsstsw/stack/Linux64/daf_persistence/12.1-15-gaf6b168/ups/daf_persistence.table: Product miniconda2 is a dependency for log 12.1-4-gad3b865+2, but is not setup  scons: *** [table] Error 9  scons: building terminated because of errors.  + exit -5  eups distrib: Failed to build daf_persistence-12.1-15-gaf6b168.eupspkg: Command:          source /ssd/lsstsw/stack/eups/bin/setups.sh; export EUPS_PATH=/ssd/lsstsw/stack; (/ssd/lsstsw/stack/EupsBuildDir/Linux64/daf_persistence-12.1-15-gaf6b168/build.sh) >> /ssd/lsstsw/stack/EupsBuildDir/Linux64/daf_persistence-12.1-15-gaf6b168/build.log 2>&1 4>/ssd/lsstsw/stack/EupsBuildDir/Linux64/daf_persistence-12.1-15-gaf6b168/build.msg  exited with code 251  {code}
Answer: 12476.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: "On cc-in2p3 cluster (ccqserv123) next message appears in xrootd-console.log:  {code}  [2016-12-10T23:37:28.298+0100] [LWP:275] INFO  xrdssi.msgs (cmsd:0) - Meter: Insufficient space;  7GB available < 11GB high watermark  {code}  Maybe next lst.cf directive should be moved to global:  {code}      # Specify that no significant free space is required on servers      # Indeed current configuration doesn't expect to be dynamically      # written to, but export the space in R/W mode      cms.space 1k 2k  {code}"
Answer: 72664.0

User story: "This to prepare the RC for February of IRSAViewer with 2 added features:    - Histogram (simplest version: column/express, no binning method option)  - WCS target search [DM-8310]     once DM-8310 is done, make a RC out of dev and start with DM-8309."
Answer: 110557.0

User story: "Here is a list of issues that i can identify in the current LC implementation to be potentially improved/adjusted to load other LC than coming from WISE MEP dataset:    * Guess sorting table in time and probability (DM-7966): currently, `mjd` and `SDE` is used to sort the table by default but a UI feature to let the user decide between other column name like `bjd` for example might be needed in the future (PTF,etc.)  * XY-plot are also built based on assumptions about column name to start with, such as `w1mpro_ep` and `mjd`.    I will update the list if we find more similar implementation issues. "
Answer: 110627.0

User story: "In addition to testing the blender using observed fields, it would also be wise to create synthetic objects using galsim or SynPipe where we know what the underlying structures are and compare that to the results from running the deblender.    The goal of this ticket is to evaluate galsim and Synpipe to see if one or the other (or both) will be useful in debugging certain failure cases with the deblender."
Answer: 55965.0

User story: "In DM-7503 one possible solution to the deblender issues occurring at the center of galaxy clusters will be to allow the deblender to accept models generated from previous deblender execution. The goal of this ticket is to accept a model or template and evaluate it using the problem datasets described in  * DM-8059  * DM-8139  * DM-8266"
Answer: 198371.0

User story: "Eric Sheldon (DES) implemented a hierarchical deblend, beginning with the brightest objects, as opposed to simultaneously fitting multiple objects. The goal of this ticket would be to implement a hierarchical deblending scheme and evaluate it using the problem objects described in  * DM-8059  * DM-8139  * DM-8266"
Answer: 198379.0

User story: "The new deblender will require footprints in all bands to be simultaneously stored in memory. This is not possible with the current 4k x 4k patch sizes. We need to calculate the optimal new patch size to be able to fit all of the footprints in memory and re-run the HSC Coadd pipeline to generate smaller coadds."
Answer: 1912730.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: "So far, due to rapid prototyping, {{Exectuor}}'s code was kept outside of the LSST organization though in a publicly accessible repository.  Now the code is mature enough to be transferred where it belongs after cleaning up its commit history a bit."
Answer: 21.0

User story: "A calibrated SED (from Calspec and others) of the observed star is converted from Flam units to photons number and convolved with a fiducial model of the atmosphere at the CTIO site. Then, the spectrum is converted into electrons using the QE of the camera and its resolution is downgraded to match the nominal (~.7pix) seeing of the observations.     The converging beam adds an extra dispersion as the defocus increases at larger wavelength \footnote{Note on MonoCam tests, from S. Dagoret-Campagne \&al, LAL.}.  $$\delta(\lambda) = \frac{l}{f/D}\left( \frac{1}{\sqrt{1-(\lambda/a)^2}} -1\right)$$  This corrective term is added to the forward modeling (result illustrated in file attached).     "
Answer: 145102.0

User story: "Implementation of `db.utils.loadSqlScript()` runs mysql command and passes  password as command line argument which is not very secure. We want better way to pass credentials to mysql, special protected defaults file is probably the best choice."
Answer: 8407.0

User story: "There are several issues rising out of SUIT requirement and design discussions. Those issues affect SUIT but need DM management attention. This ticket is an attempt to make a list of those issues and ask DM management/architecture team to address them. "
Answer: 238135.0

User story: "In DM-8339, a Pegasus workflow following {{ci_hsc}} is made. As in {{ci_hsc}}, it includes only one patch.      In this story, make a more general workflow, similar to {{ci_hsc}} but considers multiple patches. Same as in DM-8339, ignore orchestration details and Executor.  "
Answer: 80784.0

User story: I noticed that when we try to show table panel in a PopupPanel it does not show up, moreover it’s causing the unmount of the popup panel.    The test steps:   * do a catalog search to bring a chart,   * go to "Chart" menu at the top, select "Scatter Plot" radio button, then click on the link“Cols” there.   * The popup disappears, when the link is clicked. (You can compare this behavior with the chart options, when not in a popup, which works fine.)    I traced it to renderTable in ColSelectView.jsx, which renders a TablePanel. If I replace it with some other div, it works fine. Also the same code works fine, when not invoked from a popup.
Answer: 51994.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: "Hot pixels or cosmics lying in the footprint are flagged using the Laplacian detection method published in van Dokkum (2001). The algorithm is based on the measurement of the seeing and the noise level of the image background to select cosmic-rays of arbitrary shapes by the sharpness of their edges.      The efficiency of the algorithm has been tested by measuring the number of cosmics in a dark image and a stellar field, then on the sum of both images. The ratio of the number of detections in both case being an assessment of its performance. The result is about 99% of common detections. In the 800 by 60 pixels rectangles of the footprints, the total number of flagged pixels is typically between 0 and 5."
Answer: 263426.0

User story: "Get a bot, capable of conversing in a channel, running reliably, and providing some useful (unauthenticated) service when queried."
Answer: 19546.0

User story: "Create a Pegasus-workflow repo in [GitHub lsst-dm|https://github.com/lsst-dm]. Move the ci_hsc workflow (DM-8339) there.  "
Answer: 978.0

User story: The pybind11 wrapper for {{CoaddInputs}} added in DM-8417 has a serious problem: any attempt to read the {{visits}} field causes a segfault: "pointer being freed was not allocated".    To see this run {{afw/tests/testExposureTable.py}} after enabling {{testCoaddInputs}} by commenting out the skip decorator.    The code uses {{def_readwrite}} to wrap these fields. However, I have also tried:  - Adding new getter and setter methods in {{CoaddInputs.h}} and wrapping those using {{def_property}} in {{coaddInputs.cc}}  - Specifying other return value policies such as {{reference_internal}} (the default, and desired policy) and {{reference}} (not very desirable, but emulates what SWIG did and if it worked then the unit test should have run correctly).    The final commit of DM-8417 includes some temporary extra code in {{CoaddInputs.h}} and {{coaddInputs.cc}} that helped me perform the above tests. You may find it useful for experimentation.
Answer: 8242.0

User story: "Attend the Camera visualization weekly meeting, act as the point of contact the UIUC team, bring back the requests and bug reports to Firefly team. "
Answer: 16085.0

User story: "AS we discussed with Gregory yesterday command line interface of cmdLineActivater needs some improvement:  - drop --extras option and use more natural syntax: {{cmdLineActivator --activator-options super.task --supertask-options}}  - should be possible to specify fully-qualified name of the task like {{lsst.validate.drp.task.ValidateSuperTask}}  "
Answer: 93755.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 material for the [2nd LSST Chile Workshop|http://www.sochias.cl/eventos/internacionales/317-second-lsst-chile-workshop] on community/communication tools:    bq. Hands-on session about “LSST Community Tools” (which should be c.l.o., Slack, anything else that we want the community to be using). This is what I’d expect Jonathan would cover (participating remotely). Jonathan, can you compile some bullet points on what would be useful to speak about here? Imagine talking to an audience who has heard about the LSST, but is still relatively new to it and wants to get involved. What should they know?"
Answer: 9916.0

User story: DM-8557 introduced a workaround for an issue seen in afw's multiMatch module where a numpy.int64 could not be used as an index by SWIG under Python 3. This ticket is to see if pybind11 has a similar issue under Python 3, and introduce a fix if so.    Suggested procedure to diagnose the numpy.int64 as index issue is:    # Revert commit in afw from DM-8557 called "Cast catalog indices to int as SWIG Py3 workaround"  # See if the afw test {{tests/testTableMultiMatch.py}} runs.
Answer: 1869462.0

User story: Remove dependency on the "cat" package in ctrl_stats
Answer: 19930.0

User story: "In order to use [CWFS|https://github.com/<USER>cwfs] or a forward modeling package (e.g., donutlib or galsim) for HSC images, we'll need a model for the instrument, including things like the focal length, pupil diameter, field-dependent obscuration (i.e., vignetting), and probably more.  This ticket is to figure out exactly what's needed and how to model it."
Answer: 162854.0

User story: "PUB-39 requires DOIs for DMTN-006 and DMTN-021. For now, these DOIs are prepared manually since we haven't engineering a technote release process yet."
Answer: 304.0

User story: "It's (fairly) well known that DM has a policy of making materials deriving from talks given, papers published, etc by DM members available on [Zenodo|https://zenodo.org/communities/lsst-dm]. But we need some documentation specifying at least:    - The details of the policy (what should be made available, who is responsible, etc);  - The mechanism (how does one upload to Zenodo, what collections should the upload be added to, etc);  - Requirements regarding licensing."
Answer: 15949.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 an interim solution to allow multiple developers the ability to maintain the production jenkins/squash deployments (possibly expanding to other deployments in the future), a simple instance should be created to host the currently active production {{sandbox-jenkins-demo}} deployment.  Due to a tight timebox, primitive access is to provided by injecting ssh keys from all active sqre developers injected into this instance.    In order to isolate this "control" instance from existing deployments, it shall be isolated into a new "production control" VPC.  In the future, it may make sense to add routes between various VPCs (note: private DNS would need to be setup), to add a VPN concatanator, and/or host auth/CA services within this VPC.  This implies that consideration should be given to the VPC prefix and subnet addressing.    Any state associated with the deployment of the deployment control should be hosted such that is accessible to all sqre devs and in a redundant manner. Eg., on {{s3}}
Answer: 1875092.0

User story: "The {{ansible-beat}} role does not support [metricbeat|https://www.elastic.co/guide/en/beats/metricbeat/current/index.html]. Also the repository for beats has changed since the last update six months ago."
Answer: 25.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: "Now that we have experience with https://developer.lsst.io, we can improve the usability of the top-level topic organization.    *The current organization is:*    # Getting Started  # Processes  # Coding Guides  # Writing Docs  # Build, Test, Release  # Developer Services    *Proposed new top-level organization:* _(work in progress)_    # Getting started  ## Account onboarding checklist  ## Where to find LSST/DM information  # Team  ## Team Culture and Conduct Standards  ## DM Organization (maybe not normative, but at least something useful)  # Communicating  ## Request for Comments (RFC)  ## Changing controlled documents with the TCT  ## Request for Discussion (RFD)  ## Meeting notes in confluence  ## Using the Community forum  ## Presenting at conferences.  ##* _slide templates_  ##* _link to information policy_  ##* _link to pub board procedure_  ##* _Zenodo deposition_  ##* _community.lsst.org conference report_  # Workflow  ## Overview of the DM workflow  ## Using JIRA  ## GitHub organizations  ## Git branching and merging  ## Code reviews  # Development guides  ## Overview  ## Python  ### Python style guide  ### Python unit testing  ### Using Astropy  ### Logging (or move to Pipelines documentation site)  ## C++  ### C++ style guide  ### C++ unit testing / Unit testing Private C++ functions  ### Using C++ templates  ### Using Boost  ### Using Eigen  ## EUPS packaging and Git repositories  ### EUPS tutorial  ### How to make a Stack repository  ### Adding Git LFS to a repository  ### Managing copyright and license info in repositories  ### Renaming an LSST Git repository  ### Moving code between packages  # Build and continuous integration infrastructure  ## Using Jenkins stack-os-matrix  ## _other Jenkins jobs_  ## lsstsw and lsst-build  # Development infrastructure  ## Using the lsst-dev server  ## Using the Verification Cluster  ## Using the NCSA bulk transfer server  ## NCSA Nebula OpenStack user guide  # Developer tools  ## Required Git configuration  ## Configuring the Git LFS client  ## Git practices  ## Atom configuration  ## Emacs configuration  ## Vim configuration  # Documentation style guide"
Answer: 640815.0

User story: "As part of tickets/DM-8417 I added a Python unit test of Citizen. [~<USER> would like me to add the same unit test to master."
Answer: 12.0

User story: "clean up including:    - moved some files our of server/visualize  - created a ...server.visaulize.imageretrieve package  - remove unused code  - clean up some caching to simplify  - removed aborting a plot  - cleaned up managing plot context  - moved the *Commands.java files to .../server/rpc  - general cleanup including some java 7 syntax updates and javadocs"
Answer: 5486.0

User story: In the image meta search triview, click "Restore to the defaults", a new image tab called "FITS Data" pops up. The tab is empty.    How to repeat:    Target = 9.6 -1.1; images include the target.  Search for coadd. Got 5 images. Then flip them. Then restore them. The empty "FITS Data" panel would show up.        
Answer: 129324.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: "Update DMTN-024 with conventions acquired during pybind11 development.  These guidelines will then need to be RFC'd before being made an official part of the DM developer guide."
Answer: 135654.0

User story: Think carefully about the 1D and 2D toy models created to play with the production of photometric flats with CBP data. This is to make absolutely sure that the system response function really is recovered as well as we're showing it is.    Then, extend the fidelity of the model in order to see how well we recover the truth in the presence of some or all of the following:    * Noise  * non-rectilinear CBP sample points  * finite CBP point sizes (spread signal out)  * Imperfect CBP photometry  * spot-to-spot variation in CBP spot fluxes  * anything else we think of that seems relevant    Potentially also extend to "not-a-knot" boundary constraints for the spline interpolation to see how much the ringing can be suppressed.   
Answer: 991960.0

User story: "Fixes internal issues with how Datums are created.    See https://github.com/lsst/validate_base/pull/3#pullrequestreview-11220547"
Answer: 5.0

User story: "Calls to checkRaDecFilter should at least include all filters 'uirgz'. Removing the filter check entirely might be reasonable."
Answer: 1820280.0

User story: "In catalog or image search, if the query takes a long time to get the result, the table tab is not shown until the result comes,  user still sees the previous search result during waiting.    It would be nice to show the current table tab immediately, so user can see that the search is going on.  How to repeat the case:  Make the first query: target (1,1), cone, 10 arcsec.  Then make the second query: same target, cone 1000 arcsec.  The second table won't show until the result comes out.  "
Answer: 98043.0

User story: This is an action item from [Camera Image Visualization meeting with IPAC|https://confluence.lsstcorp.org/pages/viewpage.action?spaceKey=~<USER>title=Camera+Image+Visualization+meeting+with+IPAC]    Make gliffy diagram of "yellow box" architecture including I&T diagnostic cluster.
Answer: 1187986.0

User story: This is an action item from [SLAC-IPAC Camera Visualization Meeting|https://confluence.lsstcorp.org/pages/viewpage.action?spaceKey=~<USER>title=Camera+Image+Visualization+meeting+with+IPAC]    Initial "yellow box" interface, and implementation using existing fits file reader.
Answer: 1225191.0

User story: This is one of the action items from [SLAC-IPAC visualization meeting|https://confluence.lsstcorp.org/pages/viewpage.action?spaceKey=~<USER>title=Camera+Image+Visualization+meeting+with+IPAC]    Proposal for support of "cropped image staging" for more efficient image passing to python.  Organize a design discussion for this. 
Answer: 1225195.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 is one of the action items from [SLAC-IPAC meeting|https://confluence.lsstcorp.org/pages/viewpage.action?spaceKey=~<USER>title=Camera+Image+Visualization+meeting+with+IPAC]:    Once implementation of channels/request object/user defined actions is complete, provide demo/example"
Answer: 1225199.0

User story: "This is an action item from [SLAC-IPAC meeting|https://confluence.lsstcorp.org/pages/viewpage.action?spaceKey=~<USER>title=Camera+Image+Visualization+meeting+with+IPAC]:    - generate pure war (without embedded tomcat)  - workaround duplicate nom.tam.fits classes, etc   - Add preferIPv4Stack to tomcat env    preferIPv4Stack=true is added to setenv.sh file in tomcat.  This is done in ife-evn repo.    duplicate of ticket https://jira.lsstcorp.org/browse/DM-7706  closing DM-7706."
Answer: 54978.0

User story: "Measure the wavefront of individual exposures of HSC data from out-of-focus images.  This will involve either solving the transport-of-intensity equation for pairs of intrafocus and extrafocus images using something like [CWFS|https://github.com/<USER>cwfs], or forward modeling the wavefronts of either intra or extra focal images using something like [donutlib|https://github.com/aaronroodman/Donut], or possibly Piff/GalSim.    The big picture will be to incorporate this as a new Task, though that's outside the immediate scope of this ticket."
Answer: 167321.0

User story: "Develop a plan for combining multiple full focal plane out-of-focus images into a single reference wavefront.  This isn't completely trivial, as the aberrations in different exposures will be somewhat different, so some strategy needs to be used to account for the differences.  [This article|http://adsabs.harvard.edu/abs/2014SPIE.9145E..16R] may illustrate how <USER>accomplished this for DECam."
Answer: 816427.0

User story: "Become familiar with <USER>s cwfs (curvature wavefront sensing) package (https://github.com/<USER>cwfs).  Get it running, go through examples, fit some toy wavefronts...."
Answer: 816432.0

User story: "{{sqlalchemy}} does not provide API to load and execute SQL statements from a file. We need to add something like this to {{db}} API to simplify migration of few ctrl packages which depend on {{cat}} functionality."
Answer: 17290.0

User story: "{{validate_base}} allows measurements to be {{None}} if they failed, though SQUASH doesn't accept null measurement values.    # have post-qa filter out null measurements before posting to SQUASH.  # move the configuration that decides what metrics to post to the command line, making it easier to change in the future (and disable AM3 for now).  # when handling errors, don't print JSON since django actually seems to return an HTML error page."
Answer: 4679.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: "Scons v3 is the scons version that supports both Python 3 and Python 2.7 natively. This ticket is for updating Scons and ensuring that the Python 2.7 stack still builds.    This work depends on the Scons developers delivering a new Scons version that works with both. Whilst work is ongoing it may be necessary to help out with the port if we wish to meet our Python 3 target."
Answer: 423556.0

User story: "Putting {{metrics.yaml}} in the {{validate_drp}} directory does not ensure that it will be installed with validate_drp. This is necessary for validateDrp.py to find {{metrics.yaml}} when run from an installed stack; not just validate_drp's Git checkout.    Putting metrics.yaml in an etc/ directory should solve it as sconsUtils automatically copies content from this directory."
Answer: 5603.0

User story: """validation_data_jointcal"" is really ""testdata_jointcal"" and should be named accordingly, before jointcal becomes a stack dependency. Then all the test data I'm using can live there and we won't need optional dependencies on really large data sets (which are always installed by lsst distrib and lsstsw)."
Answer: 27414.0

User story: "Write a tests for jointcal photometric processing on hsc data. Use either the latest validation_data_hsc data, or reprocess an older (smaller) version to get VisitInfo and add it to validation_data_jointcal."
Answer: 70374.0

User story: "Using the latest decam data in validation_data_jointcal, write a test for doing joint photometry on said decam data."
Answer: 67747.0

User story: "Once I have the tests in place for twinkles, write a similar jointcal photometry test for cfht. This would be the time to replace the currently-broken validation_data_jointcal/cfht data with one updated to have VisitInfo."
Answer: 67771.0

User story: "In order to run jointcal photometry on data other than twinkles1, it will probably be necessary to separate the photometric and astrometric reference catalogs. This can probably be managed via configuration parameters (doAstrometry/doPhotometry and astrometrySourceSelector/photometrySourceSelector at least). This would be an opportunity to refactor the guts of {{jointcal.run()}} as well."
Answer: 109868.0

User story: Once I have shown that jointcal photometry can run, I should start testing it with lsstSim's twinkles1 data set. There are "known" values to compare to here, so this test can be more stringent than those using external catalogs.    As part of this, it would be good to make some plots showing the RMS/star across all visits, and compare those to the "known" values/star. That will also help us define the test metric.
Answer: 61848.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: Before I can write any tests for jointcal's photometric fitting, I need to at least get it to run. It may be as simple as the following, but it's not clear whether the code will even run, or what else might be necessary.    {code}          fit = jointcalLib.PhotomFit(associations, spm, self.config.posError)          fit.Minimize("Model")          chi2 = fit.ComputeChi2()          print(chi2)          fit.Minimize("Fluxes")          chi2 = fit.ComputeChi2()          print(chi2)          fit.Minimize("Model Fluxes")          chi2 = fit.ComputeChi2()          print(chi2)  {code}
Answer: 57503.0

User story: Resulted in two new jenkins jobs:    * {{backup/nightly-sqre-github-snapshot}} - a "cron" job that runs nightly, executing the snapshot process from inside a container  * {{backup/build-sqre-github-snapshot}} - builds the docker container used by {{backup/nightly-sqre-github-snapshot}}.    Containers are pushed to https://hub.docker.com/r/lsstsqre/sqre-github-snapshot/
Answer: 6826.0

User story: Currently the image title in the triview has filter name, like u, g, i, ...    It would be nice to add more information about the image, say deepCoaddId or scienceCcdExposureId.     Trey added:  see LsstSdssRequestList.js    [LZ 1-4-2017]  # For DeepCoadd,           Get the baseId from the selected row:                 baseId = deepCoaddId - deepCoaddId % 8            For each filter, the title is:                id = baseId + filterId  ( numerical addition here)                title = id+"-"+filterName  # For science CCD, its id structure is different than deepCoaddId      scienceCcdExposureId = run+filterId + field (  string concatenation)                      
Answer: 50106.0

User story: "Jointcal has a many {{print()}} and {{cout<<}} that clutter up the output. These should be converted to lsst.log levels as appropriate (e.g. most of the python print are probably .info, while many of the cout are .debug)/"
Answer: 115123.0

User story: "How to repeat the problem:    LSST image search, DeepCoadd.     Query One: RA = 0, Dec = -1, images enclosed by 36 arcsec box. This query should fail and no data and images are back.    Query Two: keep the same target, change the box size from 36 to 3600 arcsec. This query should have many rows in and five images are shown.    In the triview table panel, switch back to the Query One tab, the table is switched, but the image panel still shows the 5 images from the Query Two.    "
Answer: 50525.0

User story: "In the LSST image search triview, click back and forth between the coverage map and the image panels/tabs, the selected panel/tab can't be active, so that the layer display is not updated, and all other Firefly tools can't be working on the selected panel/tab. One has to click on the image part in that panel/tab to activate it.     Goal: No need to click on the image part, the selected panel can be active.    Trey added:  This work might be able to be done in MultiImageViewer or MultiImageViewerView  as part of componentWillMount"
Answer: 7225.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 will provide user option to change the symbol and and its size when overlaying a catalog on an image.    Add support for changing drawlayer symbol and size    * catalog default symbol is square and size of 3 to 20.  * add shape options from PointDataObj to support:  'X','SQUARE','CROSS','DIAMOND','DOT','CIRCLE',  'ARROW'  * make the options come up in a dialog when you click on the shape in the drawing layer tool (see DrawLayerItemView.js: makeShape(), also see makeColorChange() ).   *  the change is applied immediately     "
Answer: 21784.0

User story: "Create file list for full backup."
Answer: 1.0

User story: "Implement disaster recovery plan for the /software partition"
Answer: 3.0

User story: "Implement disaster recovery plan for the /home partition.  "
Answer: 4.0

User story: "Current version of the alert_stream producer/consumer + Kafka broker system (DM-7453 and DM-7454) uses Docker compose and just exposes all ports to the host network.  That won't work for scaling up to multiple hosts.  Need to replace this with better networking that will work for multiple hosts."
Answer: 60701.0

User story: "DM-7452 extend the sample alert schema to include a postage stamp cutout file.  Need to  * modify alert_stream repo and Docker images to grab the new alert schema and postage stamp files  * modify producers to add ability to encode and transmit stamps (can only be done with encoding)  * add a consumer to decode and write stamp (to the local filesystem?)  "
Answer: 27600.0

User story: "We should formalize adding new people to the right teams in github. I am not sure what the right way is, maybe each TCAM should handle their new members? If that is the case, TCAMs need admin privileges on github for lsst-* teams. Once we decide, Libby should document in the onboarding procedure.     Same is true for off-boarding... we might want to remove people departing from the project from the github groups (or we may choose to keep them, but in any case, someone should stay on top of that)."
Answer: 348789.0

User story: "This policy needs to be documented, most likely on develop.io"
Answer: 29039.0

User story: Per DM-6817,    {quote}  the CModel vs. psf plot on DM-6818 (plot-t0-HSC-I-mag_modelfit_CModel-psfMagHist.png) reveals... a "bump" at bright magnitudes in the "stars"... [This] seems to be rooted in the psf modeling at the single frame stage.  {quote}    Figure out what's going on here, and work out how to fix it.
Answer: 131501.0

User story: "Identify candidate products for a degenerate implementation."
Answer: 3.0

User story: "Consider alternate formats including:   - alternatives to excel   - alternative flow within the document   - resolving outstanding flaws with the current format   - provide a better user interface"
Answer: 4.0

User story: "Now that the rest of the stack works with python3 (particularly the obs packages), it's time to bring jointcal into the fold."
Answer: 28263.0

User story: "  See DM-8003"
Answer: 101543.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: "Take nightly GH snapshots / expire snapshots according to retention policy."
Answer: 1.0

User story: "Implement unit tests for single frame spatial grid mapper processing task (DM-8520)"
Answer: 139702.0

User story: "Implementing both ZOGY and A&L(ZOGY) (decorrelation) allowing for spatial variations across the image(s) will be done by performing the diffim's on a grid of subimages across the entire image. Thus we would benefit from a superclass task that will     1. break apart the image in a grid of potentially overlapping subimages, allowing for extending the boundaries for the calculation (e.g. convolutions)  2. call a subtask to perform the processing of each subimage  3. re-generate a new complete image from the processed subimages    This story involves developing this superclass task, including documentation. Another ticket will involve writing unit tests and examples."
Answer: 139706.0

User story: "Demo will run a set of SQL queries on IN2P3 cluster."
Answer: 61651.0

User story: "Currently all pybind11 work is done on the branch for DM-6168. This ticket aims to rebase that work onto the latest master and subsequently move it over to a new ticket branch for DM-8467.  The latter ticket is to be used to gather all future porting work.    Note that this ticket excludes work to rebase all currently active pybind11 tickets onto DM-8467. That is to be done by the asignee of the respective ticket (as per the normal periodic rebase process)."
Answer: 4182.0

User story: "The Software Primitives section is still entirely in outline form, and needs to be converted to text.    While it would be fastest to have [~<USER>, [~<USER>, or [~<USER> do this work, as they've discussed these items extensively already, given their levels of oversubscription it may be better to have someone else less familiar with the material try to turn it into text while bugging them as needed for clarification.  "
Answer: 1597634.0

User story: "Even after DM-8497, there will still be significant differences in subsections of the Algorithmic Components sections written by different authors, in both the level of detail and the degree to which a baseline algorithm is assumed.   These will need to be made consistent.    This first requires agreement between stakeholders ([~<USER>, [~<USER>, [~<USER>, [~<USER>, [~<USER>) on what the desired style should be."
Answer: 228150.0

User story: "Turn outlines into text for all of the following Algorithmic Components.    PSF Modeling  Aperture Correction  Single-Visit Photometric Calibration  Image Coaddition  Decorrelated Coadds  Star/GalaxyClassification  Matching: Multiple Visits to Reference Catalog  Matching: Object Generation  Matching: Blended Overlap Resolution  Raw Measurement Calcluation  "
Answer: 228157.0

User story: "Fixes to LDM-151 DRP section in response to [~<USER>'s comments.  "
Answer: 72035.0