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: "While wrapping these packages, pay particular attention to exception translation (see Jim's bullet point 3: https://jira.lsstcorp.org/browse/RFC-182?focusedCommentId=48644&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-48644)."
Answer: 55796.0

User story: "During X16, new functionality was exposed to Python plugins in meas_base. Write a complete pedagogical example. It should go beyond our current pure Python plugins to demonstrate use of:    * FlagHandler;  * SafeCentroidExtractor;  * Other relevant, undocumented functionality.    This should be added to the package level documentation for meas_base, so it appears in some extended version of https://lsst-web.ncsa.illinois.edu/doxygen/x_masterDoxyDoc/meas_base.html."
Answer: 93297.0

User story: "In the case of a fits.gz file, the Encoding-Type is gzip. This breaks our S3 uploads in LTD Mason because boto3 doesn’t actually let us set Encoding-Type. This is a simple removal of any attempt to set that header."
Answer: 28.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 with this ticket are:  # minimize  # testGaussianProcess  # testLeastSquares  # spline  # interpolate  # spatialCell  # function"
Answer: 217293.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}testExposureTable.py{color}  # {color:#14892c}testFootprint1.py{color}  # {color:#14892c}testFootprint2.py{color}  # {color:#14892c}testFootprintEllipse.py{color}  # {color:#14892c}testFootprintMergeCatalog.py{color}  # {color:#14892c}testGaussianPsf.py{color}  # {color:#14892c}testHeavyFootprint.py{color}  # {color:#14892c}testRgb.py{color}  # {color:#14892c}testTicket2019.py{color}"
Answer: 299371.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."
Answer: 162968.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 unit test for pipe tasks creates a dozen stars, to use in coaddition testing. However the results of running the test show over a hundred sources found. Investigate why the extra sources are being detected, and fix to increase the robustness of the test. If this relates to other sections of the codebase (deblender) investigate if it is appropriate to make changes to those components to make them more robust instead of creating a simple hack in the unit test."
Answer: 1851015.0

User story: "Add pybind11 as third party package to the stack. Update sconsUtils to support building with pybind11. Use daf_base DateTime to demonstrate that this works."
Answer: 37277.0

User story: "Meeting runs Tues 28 to Thurs 30 June; that means we'll likely lose Nate for the whole week, given travel."
Answer: 51764.0

User story: Chart options "Reset" button should be resetting to the default options.    How do we know the options are the default?    - Chart is created from ChartSelectDropDown, options selected there are "the default"  - Default chart, created with the default parameters,  - Chart is created via API, options passed via the API function are "the default"    
Answer: 138053.0

User story: Make chart options "in-place" popup, similar to table options for consistent look. It will also alleviate resizing, because the chart size won't need to change when options are open.
Answer: 68809.0

User story: I'd like to do some cleanup, which would facilitate further development. This includes:  - moving chart related code to a separate package (now it is in visualize)  - converting components created with React.createClass to es6 classes  - reorganize store and controllers to have all charts related things under 'charts'. Now we have 'charts' for charts ui, xyplot for xyplot charts, histogram for histogram charts, and tblstats for table statistics.      Fixed bugs    * missing chart mount action, when a chart is removed and then recreated on the same table    Steps to reproduce: load a table (default scatter plot created), create histogram, delete scatter, create new scatter.       The last scatter did not produce mount action, and the plot was not tracking table changes, like filter.    * undefined shows as a label when no server call is necessary    Steps to reproduce: load table (default scatter created), clear options and choose the same columns , click apply.    "undefined" are shown as axis labels
Answer: 71964.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: "Need to be able to view multiple charts simultaneously in the chart area    User would like to see multiple XYplots from the same data displayed at the same time. One example will be to display different color-color plots using all 4 bands data from WISE catalog.  It is also possible we want to display histogram data at the same time as color-color plots.    Nov. 1, 2016 Implementation notes:  - Refactored charts display: ChartPanel.jsx is displaying various chart types, each type defines it's own Chart, Options, and Toolbar  - ChartsTableViewPanel.jsx is completely replaced by ChartPanel.jsx and chartTypes/* components  - MultiChartViewer shows multiple charts in a way similar to MultiImageViewer. An active chart toolbar is displayed on the top, active chart has an orange border.  - Delete button now shows up in the top right corner of the chart area.    "
Answer: 230499.0

User story: "need to support external API and the API for histogram    for now only addXYPlot and showPlot are implemented"
Answer: 158250.0

User story: "In {{utils}} the file {{python/lsst/p_lsstSwig.i}} defines special cases for boost features that are removed as part of DM-5880. This ticket removes the special cases."
Answer: 543927.0

User story: "The labels in HMS format no longer show hh:mm:ss anymore.  The porting introduced the bug.  "
Answer: 269.0

User story: "[~<USER>'s background is in extragalactic science on high-latitude fields, and he frequently forgets to think about how algorithms will perform in crowded stellar fields.  When the first draft is complete, we should have someone experienced in that area read closely to check that he hasn't made any incorrect algorithmic assumptions as a result."
Answer: 500490.0

User story: "The technote platform uses a metadata.yaml file to provide authoritative single-sourcing of document metadata (https://sqr-000.lsst.io/#metadata-standard). One of those is the {{last_revised}} date. The problem with using this by default is that the revision date quickly gets out of sync with the Git history while a documented is being actively drafted. Solution:    # Make it so that {{last_revised: none}} causes {{documenteer}} to obtain the date from Git history instead. When a document is being ‘released’/‘archived' (or being initially ported from another format) the {{last_revised}} field can be set to a date.  # Potentially make the Git-based date smart so that revisions to ancillary files don’t affect the {{last_revised}} date of the content.  "
Answer: 84490.0

User story: "Correctly handling wavelength-dependent photometric and PSF effects is one of the biggest qualitative differences between the current state-of-the-art and what we have in mind for LSST, and that makes it easy to get wrong.  We need to make sure all steps that produce high-quality fluxes or rely on high-quality PSFs have access to object colors and a reasonable approach to using them.  "
Answer: 190034.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "DM-6259 will produce rough, draft-level diagrams that will require cleanup and standardization."
Answer: 42532.0

User story: "DM-6258 will produce rough, draft-level diagrams that will require cleanup and standardization."
Answer: 42534.0

User story: "DM-6257 will produce rough, draft-level diagrams that will require cleanup and standardization."
Answer: 42535.0

User story: "DM-6256 will produce rough diagrams that will require cleanup and standardization.    [~<USER> has made some suggestions for the current diagram that I'll implement on this issue, so I'm assigning it back to me.  I'll also go ahead and integrate his updated DRP overview diagram (currently on Confluence) into LDM-151 here.  "
Answer: 42638.0

User story: "DM-6255 will produce some rough, draft-level diagrams that will need cleanup and standardization."
Answer: 42539.0

User story: Includes coadd measurement, multifit, and forced photometry.    Could be faster to write than other sections because we can lift from "blended-measurement" document that already exists in LDM-151 repo; could be harder because that document has already exposed a number of unresolved questions that may need to be addressed (by at least getting agreement among pundits on the best-bet approaches) before we can plan.
Answer: 31770.0

User story: "Write more detailed descriptions and possibly draw a rough diagram for the single-frame processing and simultaneous calibration components of Data Release Production.    Does not necessarily involve turning this section into prose."
Answer: 30085.0

User story: "We want diagrams in LDM-151 to have consistent notation and colors, and to be produced using the same tool.  Someone needs to look at the diagrams produced so far to gather requirements, decide on and document these conventions, and select the tool we'll use to produce them."
Answer: 502674.0

User story: "Redo bakeoff in the case of arbitrary rotation in DCR effect."
Answer: 317251.0

User story: "The original matrix inversion technique and the competing technique will likely have different sensitivities.  This should be a comparison of the algorithms, likely based on numbers of dipoles, along with performance (memory and runtime) considerations.    This will be done on 2-D images with DCR along one axis."
Answer: 317252.0

User story: "DM-6248 adds a large, complex diagram that will need to be cleaned up and converted to use the same conventions and colors as other diagrams in LDM-151."
Answer: 502673.0

User story: "Implement a competing (potentially a forward modeling approach) algorithm for correcting DCR in templates."
Answer: 141166.0

User story: "Insert the content from the DRP Data Flow diagram on Confluence into LDM-151, adjusting it to the outline developed on DM-6247."
Answer: 11547.0

User story: "Write outline for Data Release Production section of LDM-151, using the DRP Data Flow diagram as the organizing principle."
Answer: 4287.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: "Study the performance when using the (currently, spatially invariant) correction term to the base A&L algorithm in terms of runtime, detection threshold, reported measurement noise, and false positive rate for similarly tuned versions of both the base algorithm and that with the correction applied."
Answer: 83726.0

User story: "The initial implementation of the A&L + noise whitening correction term assumes a single matching kernel and variance value(s) for the image(s) in the correction kernel.  We should assess how well that assumption performs in simulated and real images.  One test would be the variance and covariance in the noise as a function of position in a set of typical images."
Answer: 95088.0

User story: "We now need more fine grain controls over regions:    From API, user can:    * load region file  * delete region layer  * add a region entry to a layer  * delete a region entry from a layer    When this ticket is complete, region conversion should be completed."
Answer: 20350.0

User story: "The algorithm to calculate the label position does not work well for the Ecliptic coordinate system.  The algorithm needs to be modified to work for all the coordinates."
Answer: 24721.0

User story: "Resource load for second half of F16    (SP estimate from first half)"
Answer: 376647.0

User story: "See https://dmtn-016.lsst.io"
Answer: 2.0

User story: "We need a Jenkins instance where the default python in the PATH is python3 (where version >= 3.4 with 3.5 preferred). The underlying OS does not matter.    A prerequisite of this is a modification to the {{lsstsw}} {{bin/deploy}} script to allow Python3 to be installed ({{miniconda3}} EUPS package?) rather than python2.    Modifying the EUPS {{scons}} and {{python}} packages is outside the scope of this ticket. A build of a third-party EUPS package is sufficient demonstration of the capability."
Answer: 39963.0

User story: "imageDifference.py crashes with a vague error on initializing the sourceSelector task. The problem turns out to be that sourceSelector needs a schema passed in."
Answer: 230.0

User story: "There will likely need to be changes made in how stripe82 images are located and returned by dax_imgServ when qserv is setup to provide stripe82 data."
Answer: 276558.0

User story: "Add {{:jira:`DM-1234`}}-type roles to documenteer so that JIRA tickets, epics and RFCs can be referenced easily from all of our Sphinx-based projects."
Answer: 6054.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: In order to lock memory, the memory locking limit within the container for the qserv worker needs to be raised. My understanding is the container uses whatever is the host setting so the limit has to be set for the container user and whatever the user is inside the container. The particular limits is:    memorylocked 64 kbytes    notice that by default it's 64K. That needs to be raised to say 75% of the real machine size. I wouldn't make it unlimited as a memlock mistake may crash the whole machine. The limits are specified in "/etc/security/limits.conf". You will know that you are successul when you ssh into the container as the qserv worker user and the "limit" command tell you have can lock lots of memory.    We would also set the CAP_IPC_LOCK privilege but setting the soft/hard limit above should be good enough. So, let's start with that. 
Answer: 14700.0

User story: "Create a new project in JIRA (DM Baseline Plan), spec provided here: https://confluence.lsstcorp.org/display/DM/ProjMgmtWG%3A+The+New+DLP  I am sure we will fine tune it, but it is a (hopefully good) start."
Answer: 24949.0

User story: "It is not clear whether, or how, the diffim decorrelation convolution kernel (PCK; see DM-5914) will work for non-uniform PSFs or noise/variance. This will be investigated using the simple implementation from DM-5914.     Tasks:  1. Determine whether variation in the PCK across the field is significant enough to matter for typical LSST images  2. If it does matter, investigate options for performing interpolation of the PCK across the field, or via calculating the PCK across the field from the spatially-varying matching kernel.     Report related to this research will be added to the relevant technote (DMTN-021)."
Answer: 148613.0

User story: "Attend the Science Pipelines working group face to face meeting in Tucson."
Answer: 27.0

User story: "Work with <USER>and <USER>to flesh out the high level MOPS design to a point where we can plane the risk associated with each component."
Answer: 4.0

User story: "Attend the Science Pipelines working group meeting by video con."
Answer: 10.0

User story: "Attend the Science Pipelines Working Group meeting in Seattle."
Answer: 8.0

User story: "When no {{fallbackFilterName}} is set, we can get a confusing error message when failing to load a calib:  {code}  RuntimeError: Unable to retrieve dark for {'filter': 'U', 'date': '2016-05-12T02:58:56.591', 'ccd': 0, 'basename': '2016-05-12skyflats_02', 'object': 'FLAT', 'visit': 883, 'expTime': 20.0006, 'channel': 16} and no fallback filter specified: Unknown value type for filter: <type 'NoneType'>  {code}  This is unrelated to the calib load failure, and merely reflects the fact that {{fallbackFilterName=None}}."
Answer: 6913.0

User story: "Jon is trying to run tests with large result which kills proxy/czar because it runs out of virtual memory. Would be nice to reduce memory use and find a way not to keep query result in memory."
Answer: 20108.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 issue will leverage LSST the Docs and Travis CI to build and publish versioned pdfs of the LDM-151 document.    This work covers    # Creating a super-minimal HTML landing page (effort will specifically not be put into making this look modern)  # Configuring the Travis build  # Provisioning the LTD product.  # Provide path instructions in the README"
Answer: 165.0

User story: "There are legitimate concerns about performance of the new dipole fitting algorithm in crowded fields. This will be evaluated (on real data? if no existing data, then realistic simulated data) and contrasted with other possible alternatives. This is in response to Zejlko's concern and suggestion that DipoleFitTask should constrain only positions using pre-subtraction images, and only fit fluxes using the diffim."
Answer: 1925537.0

User story: "AWS appears to prevent the overwrite of an existing final rds snapshot.  This scenario may arise when creating/destroying a dev env multiple times.  This can be avoided by disabling the final snapshot when destroying an rds instance.  One way to resolve this would be to add a terraform var to signal this is his is a development env."
Answer: 8735.0

User story: "Add all hard copy support so we can create a png with all the overlays."
Answer: 10478.0

User story: "Drawing layers are not handling and sharing the mouse quite  right.  Also the mechanism to determine to is priority for the mouse needs work as well. This is all necessary to make markers work correctly, since every marker is an individual drawing layer.     Also, the draw layer utilities are all in PlotViewUtil.js.  They need to be moved to something closer to the draw layers."
Answer: 19162.0

User story: "Write a technical note describing the detailed project management procedures derived by the pmp-wg. Source material is [~<USER>'s document at https://github.com/lsst/ldm-pmt/."
Answer: 23860.0

User story: "The server hard to make a hard copy now takes a StaticDrawInfo object.  We want to use only a region array.  Change the server side to support this."
Answer: 10159.0

User story: "The fields group can be out of sync with actions if they are trying to use store data when that actual value is changes.  This is a classic side-effect issue.  It can be solved with sagas.    Our current example.  The color panels updating from the plot when the activePlotId changes.    More to do:  * field groups need a sega to more effective respond to out side actions  * the dispatchChangeFieldGroup needs better, more documented parameters  * update multiple fields at the same time.  * should we have the field group support reset to init state? probably not, but look into it.  * change init values?  * Check example dialog and see if the large/smaller example is validating correctly."
Answer: 21718.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: "Add a panel to use DD catalog information to allow user to input catalog constraints as editable table component.    This is to get a table with one or more extra column which are input field. The extra column needs  a different default cell renderer (TextCell) - see TableRender.js.  This table component needs to be hooked up to the fieldgroup or some way so it can be used in the catalog search panel.   The catalog search panel will need to be adapted to display this table constraints to fully complete the search query options.    The implementation:  It contains the redesigned panel based on IRSA current OPS catalog search. A table with input constraints and sql area input are added.   There is a lot in that PR. In particular, usage of table renderers and 'fieldgroup' together with a changed BasicTable component to be able to get the value from input field custom column 'constraints'.   The panel will be reviewed also by IRSA and some input requirements were left out for now (mainly aesthetic details). Another left-out is the text are component and the validation of it. That should be addressed in the other ticket DM-6136. "
Answer: 82370.0

User story: "Catalog panel (DM-5388) needed an input area for polygon input search but it needs a review and connect the validation reducer to it."
Answer: 2108459.0

User story: "VO search panel is a tab part of the catalog drop down panel that should be migrated. This was an outlier of DM-5388 ticket."
Answer: 72078.0

User story: " finish up DM-5388 ticket by fixing the UI style of the panel"
Answer: 20568.0

User story: "Tiny change that should have been included in DM-5641."
Answer: 21.0

User story: "Third-party packages should never be added as dependencies without an RFC, and if we are going to distribute them via {{eups}}, we need to ensure that their licenses are compatible.  Add text to the Developer Guide reflecting this."
Answer: 35185.0

User story: "Expanded view not doing fit/fill consistently. Sometimes is seems to fit/fill and resize it correctly, other times it stays at the zoom level.  It should always fit/fill and change zoom level with resize when in expanded mode. (unless zoom type is FORCE_STANDARD)."
Answer: 170881.0

User story: "ngmix does not have a license, which means we shouldn't distribute it. Work with Erin Sheldon to see if he is willing to add one."
Answer: 60001.0

User story: "Reproduced building on Ubuntu 16.04.    https://groups.google.com/forum/#!topic/astrometry/aDCjhfMYhpE    The current version (0.67) does build successfully standalone.    These two patches fix 0.5.0:  https://github.com/dstndstn/astrometry.net/commit/7ded70917d7cf1efa1d3af6d0da8b336ebbf9d92.diff and https://github.com/dstndstn/astrometry.net/commit/7c65b3cefc4f33c59af90c1a40b5f246002cdf28.diff  Though only the first one is needed, I believe the second one is part of the build already."
Answer: 1358.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: "Run tests on the ngmix PSF approx plugin similar to those which were run on ShapeletPsfApprox.  We will test both for how long the plugin takes to run, and how often it fails.    Note previous report on CModel and SPA was DM-4368"
Answer: 21517.0

User story: "Test that the ngmix PSF approx plugin works correctly in our measurement framework by testing it with CModel and comparing results with those produced with ShapeletPsfApprox."
Answer: 21519.0

User story: "Build a measurement plugin which allows PSF approximation to be done using ngmix.  After consulting with Erin, it was decided that this would make use of the EM code and would produce as its output some variable number of Gaussians.  These will be turned into MultiShapeletFunction outputs.    A suitable set of configuration options and output failure flags will also be provided."
Answer: 41270.0

User story: "Many pages in the Developer Guide are change-controlled. These pages should have a clear admonition element (such as a {{note}} directive) that states    #. The page is change controlled  #. The person/organization responsible for approving changes (or another process like RFC).    This will provide great transparency over what parts of the developer guide are informational versus requirements. This will also make it easier for a DM team member to understand who to set as a potential reviewer for any changes."
Answer: 2160121.0

User story: "Add:    - Edit on GitHub button  - LSST branding  - Edit on GitHub button  - LTD edition dashboard links"
Answer: 418007.0

User story: "There are a few issues in the Color Stretch dialog box:  # When the asinh or gamma algorithm is selected,  the asinh parameters and gamma parameters are always reset to the default.  The user-entered values can not be kept and used.   # When there are two or more images, when the lower/upper range in one of the image is set, the lower/upper range in all the rest images are set to the same lower/upper range.    # The rangeValues are always reset each time when the Color Stretch dialog is open.  "
Answer: 21639.0

User story: "As conda binary packages are planned to be available on a regular basis (ie, weekly) starting in the w16 cycle, we should start making container images with this packages similar to how {{packer-newinstall}} uses eups distrib install packages. "
Answer: 760586.0

User story: "The eups distrib install based docker container build  in {{packer-newinstall}} is currently using a shell to template a trivial Dockerfile in order to set some entry parameters that are not directly supported by the packer docker provider.  There appears to now be at least one packer plugin that could replace this functionality is a more maintainable way.    https://github.com/avishai-ish-shalom/packer-post-processor-docker-dockerfile"
Answer: 649753.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: Please provide a minimal level of documentation for meas_extensions_photometryKron, to include:  * A doc directory with the usual content so that docstrings get generated by Doxygen;  * A package overview;  * All docstrings should be appropriate for parsing by Doxygen (ie, should start with {{"""!}} where necessary).  
Answer: 23201.0

User story: "Currently we set {{Cache-Control: max-age=31536000}} so that Fastly caches uploads from LTD Mason for a year on its POPs. This has the side-effect of also having browsers potentially cache documentation on the client for up to a year. In practice, browsers churn through their cache space more quickly, but I've noticed that Safari has no cap on its cache space, and therefore can hold onto pages for a long time.    The solution is to set a {{Surrogate-Control}} max age to 1 year, and have {{Cache-Control: max-age=0, private, must-revalidate}}. This will be done on LTD Keeper during the copy phase of a build into an edition (since it is reasonable for a client to cache a build forever), but then give us the flexibility to update an edition instantly.    In the future we may want a more nuanced solution where CSS and JavaScript, for example, are cached longer on the browser."
Answer: 106551.0

User story: "More work needs to be done on the triview layout controlling:    * When there is a table with image meta data is loaded, the images need to show with the meta data tab selected  * When any data is pushed then drop downs needs to close  * when a table a catalog table is loaded and there are no plots then then the tri-view should be up with the coverage tab selected. When there is plots then the coverage tab should not be selected.  * we need a way to remove load a table and then only see the table, same with xy-plots  * catalog and image meta data are determined by looking at the data.  However, we might need this logic in a single function  * when a table is loaded and we cannot determine what type it is then the table and the xyplots only should some up.  * When all data is deleted the default tab should open.  (in IRSAViewer case the is the select image panel)"
Answer: 34515.0

User story: "In tickets/DM-5750 the bokeh python library was integrated in the squash django project. In order to exemplify its use the KPM CI chart is showing only hardcoded values for now.    In this ticket we will implement methods to read the data from the database and the post_save mechanism to update the bokeh session when new data is available.   "
Answer: 21726.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 DM-5844, it was attempt to run multiple instances of the bokeh server using nginx as a reverse proxy/load balancer between instance.  However, this is unreliable in practice.  The qa dashboard connects to bokeh and establishes a session which is passed to the u-a.  The u-a then makes a direct websocket connection to bokeh with this connection information.  As there appears to be no state sharing mechanism between bokeh instances, this only "works" if both the qa dashboard and the u-a connect to the same bokeh instance.    An nginx module to add "sticky" cookie based http routing to nginx was tested as working:  https://github.com/<USER>nginx-rpmbuild    If qa dashboard is modified to pass on a cookie from the u-a to it's connection with the bokeh server, this should ensure the dashboard and u-a are connecting to the same bokeh instance.
Answer: 1429899.0

User story: "We ([~<USER>) have been unable to get django to properly produce logs when running under {{uwsgi}}.  We have access logs via the proxy server (nginx) but these logs are important for debugging purposes."
Answer: 1429929.0

User story: "Per discussion at the SQRE co-working session on Thursday, we agreed to implement minimal authentication for the MVP version of the qa dashboard as an external reverse proxy, such as https://github.com/bitly/oauth2_proxy."
Answer: 18528.0

User story: "Study <USER>s diagrams and descriptions (Parallelization in Data Release Production, Data Release Production Top-Level Overview), consider inputs/outputs of high level pipelines and parallelization of the DRP, draw a diagram to illustrate the data flow. "
Answer: 4266.0

User story: "Replace boost::bind with std::bind"
Answer: 17082.0

User story: "Replace boost::scoped_array with std::unique_ptr specialisation"
Answer: 15787.0

User story: "Replace boost::ref"
Answer: 21734.0

User story: "The following are used:    * {{boost::call_traits}}  * {{boost::enable_if}}  * {{boost::enable_if_c}}  * {{boost::false_type}}  * {{boost::is_arithmetic}}  * {{boost::is_complex}}  * {{boost::is_const}}  * {{boost::is_convertible}}  * {{boost::is_integral}}  * {{boost::is_same}}  * {{boost::remove_const}}  * {{boost::true_type}}    Replace these with equivalents from std where possible."
Answer: 25712.0

User story: "The following are used:    * {{boost::random::mt19937}}  * {{boost::random::uniform_01}}  * {{boost::random::uniform_int_distribution}}    Replace these with equivalents from std if possible."
Answer: 25900.0

User story: "Replace by deleting copy constructor."
Answer: 21841.0

User story: "Replace {{boost::lambda}} with C++11 lambda"
Answer: 17225.0

User story: "Use {{std::to_string}} for integer to string conversions instead of {{boost::lexical_cast}}.  Also investigate how often `boost::lexical_cast` is used for the inverse operation and make appropriate replacements if possible."
Answer: 28390.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 following fixed width integer types are used in the stack:    * {{boost::int16_t}}  * {{boost::int32_t}}  * {{boost::int64_t}}  * {{boost::int8_t}}  * {{boost::uint16_t}}  * {{boost::uint32_t}}  * {{boost::uint64_t}}  * {{boost::uint8_t}}    This ticket aims to replace them with their equivalents from {{cstdint}}."
Answer: 26069.0

User story: This is the initial jenkins job that "ties" all the components together.    It needs to:    * execute validate_drp  * push metadata about the jenkins build to qa dashboard  * push the validate_drp metrics to qa dashboard
Answer: 28662.0

User story: "A well-defined JSON schema is needed for {{validate_drp}}’s JSON output so that it can be easily, and consistently ingested into the QA Database. The schema will also make the JSON more self-describing, and potentially useful for other tools to build upon as well.    The schema is being drafted in a thread at https://community.lsst.org/t/json-schema-for-squash/777?u=<USER> Once an informal consensus is reached the schema will be implemented in {{validate_drp}} on this ticket."
Answer: 27804.0

User story: The LSST stack fails to build on OS X 10.10 "Yosemite" using XCode 7.2.1, the last version that is compatible with that operating system. I have attached a build log from [~<USER>.    [~<USER> suggests trying the following (HipChat UW DM room, 2016-05-12 18:12 Pacific): in BinnedWcs.h change:  {code}  virtual PTR(afw::image::Wcs) clone() const {      return PTR(afw::image::Wcs)(new BinnedWcs(_parent, _xBin, _yBin, _xy0));  }  {code}  to:  {code}  virtual PTR(afw::image::Wcs) clone() const {          return PTR(afw::image::Wcs)(std::make_shared<BinnedWcs>(_parent, _xBin, _yBin, _xy0));  }  {code}    with the following explanation (HipChat SQuaRE room 2016-05-12  18:26 Pacific):    {{enable_shared_from_this}} usually holds a {{weak_ptr}} to this internally, and the first {{shared_ptr}} to manage an instance is assigned to the internal {{weak_ref}}. It looks to me like this particular version of the STL only allows {{std::shared_ptr<A>}} to be assigned to a {{weak_ptr<B>}} if {{A}} is implicitly convertible to {{B}}. In this case the first {{shared_ptr}} to manage the {{BinnedWcs}} is a {{shared_ptr<Wcs>}}, and I think a static cast is required to get from {{Wcs *}} to {{BinnedWcs *}}, so the compiler barfs.
Answer: 319.0

User story: "send websocket channel information via url.  keep channel information on browser reload.    This is needed for Firefly Python API and external (when Firefly viewer is invoked trough URL) API.  "
Answer: 137.0

User story: "AFW needs to depend on Astropy in its EUPS table file:    https://github.com/lsst/afw/pull/62"
Answer: 239.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: We want to create a recipe and stubs of code (archive in a box) so others can take it, with minimal configuration changes and minimal customized data access code, to have a simple archive UI for their data. It will come with all the built-in images and catalogs access, all the image, catalog, and XY plot functions.    Please put in more detailed description of the "Archive in a box" concept
Answer: 2006677.0

User story: "L1 Forwarder components and Distributor components are located on opposite sides of the Emulator (the Long Haul network component) and move files across the path when configured and  given a 'go' signal via messaging. Forwarder/Distributor pairs are set up dynamically for each file transfer (similar to a readout event). Results are temporarily forwarded to a status queue sink, where messages are processed for the publishing of results."
Answer: 362797.0

User story: "All principle entities for L1 are in place and the messaging is working as intended. The message dictionary includes some message types for prototyping and will likely double in size as the interface between OCS is firmed up in the coming weeks. The implementation thus far is a 'ready, set, go' set of states. Test files from 10 Forwarders are sent to 10 distributors thru a WAN emulation device, and the result can be timed. The DMCS component is a simple CLI to initiate messages as currently written. This component will be expanded as requirements are determined.    Still under development is a component layer between the Condor controller and the NCSA Foreman entity so that resource availability can be queried and provide a communication link for ancillary information as needed."
Answer: 362859.0

User story: "Includes support for   * butler manages input & output repos  * repo tagging  "
Answer: 28579.0

User story: "[~<USER> committed a fix Jan 15 to how aperture correction is applied that I accidentally lost when refactoring in DM-4692. https://github.com/lsst/pipe_tasks/commit/d904e3d188698b4f57bf3dad1516b0bf201078f5 Restore the fix.    The need for this fix suggests a design flaw in measurement that will be fixed as part of DM-5877"
Answer: 1615.0

User story: "vagrant and packer will be replaced by openstack python API and cloud-init which are more flexible.    - A pseudo-DNS will be provided thanks to avahi/mdns  - Only one public/floating IP willl be used (in order to allow booting large clusters laters)"
Answer: 60772.0

User story: "Intersphinx is the native Sphinx means of referencing documentation and APIs from other projects.    #. Document use of intersphinx  #. Provide a means of adding new projects to the intersphinx inventories of projects, such as technotes, the DM Developer Guide, or Pipelines documentation."
Answer: 476266.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 packages numexpr and bottleneck are required for pandas functionality that sims_movingObjects utilizes.    http://pandas.pydata.org/pandas-docs/stable/install.html#install-recommended-dependencies    Currently, numexpr and bottleneck are not installed on Jenkins (or, I assume, buildbot), making it impossible to incorporate sims_movingObjects into CI.  The sims team would appreciate it if they were added."
Answer: 371524.0

User story: "This is the ticket for the v12.0 release prep.     Edit: Release announcement at https://community.lsst.org/t/lsst-stack-version-12-0-winter-2016-extra-2016-release/874  "
Answer: 90204.0

User story: "Some examples in the DMTN-002 seem slightly out of date.    Update supertask documentation and code to catch up with some recent developments in the stack. "
Answer: 490.0

User story: "ci_hsc has a test that verifies that extendedness as measured on coadds broadly agrees with the star selection done for PSF estimation on individual frames.  This tests a bunch of stuff, including aperture corrections on the coadds and propagation of flags from visits to coadds.    It doesn't test that aperture correction vs. extendedness logic is correct in processCcd.py, but just copying this test to the appropriate validation function in ci_hsc should do the trick.  This is currently broken, but should be fixed in DM-5877."
Answer: 71797.0

User story: "We need to avoid duplicate requests which result from minor differences in TableRequest parameters, which are not used to get data.  For example, loading catalog table, which triggers table statistics, and then getting an XY plot, results in 3 requests, returning identical data.    1. RequestClass=ServerRequest; *tbl_id=tbl_id-1;* UserTargetWorldPt=10.68479;41.26906;EQ_J2000;m31;ned; SearchMethod=Cone; catalog=wise_allwise_p3as_psd; RequestedDataSet=wise_allwise_p3as_psd; radius=200; use=catalog_overlay; catalogProject=WISE    2. RequestClass=ServerRequest;RequestedDataSet=wise_allwise_p3as_psd; catalog=wise_allwise_p3as_psd; use=catalog_overlay; UserTargetWorldPt=10.68479;41.26906;EQ_J2000;m31;ned; catalogProject=WISE; radius=200; SearchMethod=Cone    3. RequestClass=ServerRequest; *tbl_id=xyplot-tbl_id-1;* catalog=wise_allwise_p3as_psd; use=catalog_overlay; UserTargetWorldPt=10.68479;41.26906;EQ_J2000;m31;ned; SearchMethod=Cone; RequestedDataSet=wise_allwise_p3as_psd; catalogProject=WISE; radius=200; *decimate=decimate=ra,dec,10000,1,,,,*    The difference between 1 and 2 is tbl_id parameter. The difference between 2 and 3 is tbl_id and decimate parameters. As well as the order of the parameters. None of which change the catalog search result.    Test Case: Test Searches, Test catalog, AllWISE Source, radius=200"
Answer: 1451.0

User story: "We would like to include a larger set of HSC data for validation.  I tested this while in Tucson.  My working dir was {{/tigress/pprice/<USER>}.  The raw and processed data should be stuffed into validation_data_hsc"
Answer: 211454.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: "Change mouse readout to use MouseReadoutCntlr.     * Use {{VerySimpleMouseReadout}} as a reference.   * Change to use {{MouseReadoutCntlr}} for options instread of ImagePlotCnltr  * Add a second (vertical) Mouse readout to be used in the api mode. The readout should be set into {{ApiUtilImage.jsx}}, {{initAutoReadout}}.  It should replace {{VerySimpleMouseReadout}}       & add an API readout"
Answer: 43354.0

User story: "Add ability to launch the viewer and load images, xyplots, and tables from the api. We use to call this firefly.getExternalViewer()  Also, we have this concept of 'root path' through out the code. The api use can set a root path so he can use his when we are cross site. Need to implement.  "
Answer: 10485.0

User story: Work with <USER>(IRSA) to tabulate science use cases for tools. Then transform the science use cases to functional use cases ("this is how we want the tool/interface to behave").    This work is  to identify common functional and scientific use cases between PTF/ZTF and LSST to inform LSST on how the SUIT web portal might be organized for user interaction with LSST data. 
Answer: 32224.0

User story: "Having collected data in DM-6039, push all this through the master calib creation scripts and ingest master calibs into registry.    This is a necessary but not-necessarily-sufficient ingredient for making progress on DM-5465."
Answer: 244689.0

User story: "Go to the NOAO portal and download a sufficient number of darks, biases and flats (in each band) from around the time of the CTIO trip to produce master calibs."
Answer: 244687.0

User story: "Estimates of the noise in the bias frames coming from the USNO monocam run around ~20e- RMS. This is higher than with the same readout configuration in the lab, and could be due to several things.    This ticket is to take a look at a few bias frames and investigate the structure of the noise. If it is periodic and at a constant phase then using master biases will significantly improve the SNR in the calexps produced, but if it is not, then whether or not bias frames should be used at all should be considered."
Answer: 453519.0

User story: "Using the master calibs produced in DM-6036, push all the monocam data through processCcd.    Others will run sanity checks on the output (initial astrometry & photometry). From there I believe people will look at using the data to test jointcal & sim_astrom etc, but this ticket just related to the initial reduction.    As more data comes in from the 2nd telescope, a little further hacking may be necessary to keep everything running. Some of this will likely be hacky or need one-off solutions/header modification, hence the higher-than-normal number of story points assigned to what one might expect to be an hour-long job."
Answer: 244694.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 the construct*.py scripts added to pipe_drivers to produce temporally relevant master biases, darks, flats (and fringe frames?) for the recent USNO observing with monocam.    A small amount of hacking will be required due to the fact that the current ingestion model assumes that each CCD frame has a USNO counterpart which tells about the telescope pointing etc, but the bias frames do not have these.    Once the master calibs are produced, get them ingested."
Answer: 244702.0

User story: "Allow bibtex-based references in technotes using [sphinxcontrib-bibtex|https://github.com/mcmtroffaes/sphinxcontrib-bibtex]. Includes:    - Changes to documenteer Sphinx configuration for technotes.  - Addition of bibliography in technote boilerplate.  - Documentation of our requirements to use bibtex for different types of references.    DMTN-010 will be used as a pilot case."
Answer: 636580.0

User story: "In the era of CBPs, we care about absolute system throughput, and thus need to accurately know the gain of amplifiers in the CCDs.    Initially, this can be done by lab-based Fe55 characterisation (modulo the non-linearity, though that itself will need to be need to be characterised and corrected for), but changes in the relative gains of the various amplifiers need to be monitored, and this must be done in a way that is not degenerate with the optical transmission in any way.    Theoretically it should be possible to use cosmic ray muon tracks, and tracks from radioisotope contamination of the glass/dewar, to measure the (change in the) relative gains of the amplifiers.    Early work has shown that this does work in principle, but this ticket is for some further effort to see whether this method can provide the necessary accuracy given the amount of data available remains to be seen.    This ticket would normally need to be significantly more points, but as it builds on earlier work, it can, at least for initial results, be done quite cheaply.    Initial investigation will inform further work, which will be carried out in S17 as DM-8276."
Answer: 274984.0

User story: "The error message is not showing consistently when mouse is over tha exclamation icon."
Answer: 3446.0

User story: "Currently, validation is performed only if a field has changed. We need to be able to validate all fields on form submit.    The issue is not limited to initial (ex. empty) value being invalid. The invalid message is lost when a field is unmounted/re-mounted.    You can test the following way:  - http://localhost:8080/firefly/;a=layout.showDropDown?view=AnyDataSetSearch  - Open chart settings, enter 1000 into X/Y ratio - the field is shown as invalid  - Switch to histogram and back, the invalid message is gone, the field appears to be valid    Another test case is Example Dialog tab 'X 3', 'X 3'  tab test field initial value 88 is invalid (it should be between 22 and 23), but it appears valid. "
Answer: 33594.0