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: "Document how-to update cluster from Qserv release:    See  http://www.slac.stanford.edu/exp/lsst/qserv/2015_07/HOW-TO/cluster-deployment.html"
Answer: 30335.0

User story: "Document in the wiki how the test and development systems are connected and configured."
Answer: 19086.0

User story: "Current watcher implementation (in {{admin/bin/watcher.py}}) is based on direct watching of zookeeper updates via kazoo. If we are to re-implement CSS based on mysql then watcher needs to be updated to support it. Mysql does not have watch mechanism, so it has to be done via polling or using some other mechanism if synchronous notifications are needed."
Answer: 144250.0

User story: We investigate the use of Python scripts that work against OpenStack APIs to start up VMs and configure them for use, for example, in processing, build & test scenarios, etc.   We are initially working against  the ISL OpenStack, and intend to test against the "nebula" system when it becomes available.  (This type if work was initiated in issues DM-1787, DM-1788 in a previous Epic, and we continue within the context of DM-1273, )    
Answer: 20819.0

User story: "See https://confluence.lsstcorp.org/display/DM/Qserv+Release+Procedure for recipe."
Answer: 341312.0

User story: "See https://confluence.lsstcorp.org/display/DM/Qserv+Release+Procedure for recipe."
Answer: 286325.0

User story: "See https://confluence.lsstcorp.org/display/DM/Qserv+Release+Procedure for recipe."
Answer: 268970.0

User story: "See https://confluence.lsstcorp.org/display/DM/Qserv+Release+Procedure for recipe."
Answer: 200707.0

User story: "See https://confluence.lsstcorp.org/display/DM/Qserv+Release+Procedure for recipe."
Answer: 160964.0

User story: "See https://confluence.lsstcorp.org/display/DM/Qserv+Release+Procedure for recipe."
Answer: 108428.0

User story: "See https://confluence.lsstcorp.org/display/DM/Qserv+Release+Procedure for recipe."
Answer: 60441.0

User story: "Installing the non-official obs_decam package from <USER>s Github   and processing some DECam data blindly     "
Answer: 19917.0

User story: "CSS currently does not have any notion of locks. The snapshots of CSS should be taken per query, for each query and they should be done in coordination with Query Metadata. This will ensure tables used by a running query never gets altered or deleted while the query is running."
Answer: 55830.0

User story: "The CSS Facade and KVInterface currently do not support updates. This story covers adding support for basic updates."
Answer: 58351.0

User story: "This story covers adding mysql-based implementation of KVInterface. The implementation will be done in C++, and it will be exposed to the python layer."
Answer: 58386.0

User story: When I put DM-2194 into "Invalid" state, I expected to get a popup where I could enter a comment to explain why the ticket is invalid, but I didn't.  This then required additional spam to provide the explanation.
Answer: 1944.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: Having some sort of automatic "lint check" of the repos.yaml file is desirable due to the length of time required to do a full up test of lsstsw.  It should be possible to cobble a sanity checker together that can be run from travis-ci.
Answer: 13040.0

User story: "Switch configuration for use by individual tenants of AURA"
Answer: 1915220.0

User story: "Buy switches to deploy MPLS over the fibers. "
Answer: 1915222.0

User story: "Cisco Xenpack for extra long distance 10Gbs"
Answer: 1915224.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: "Open day with vendors to describe the needs and requirements of the mountain to base and La Serena to Santiago networks. This is the first formal meeting in the procurement process. Vendors will be invited to propose their solution along with cost."
Answer: 1916673.0

User story: "We currently OR together all mask bits, but we need to be cleverer about how we handle pixels that are bad in some but not all inputs.    This is a port of work carried out on [HSC-152|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-152]."
Answer: 2741.0

User story: "Add a new mask plane for regions with no data - fully vignetted, edge patches in coadd.    This is a port of [HSC-669|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-669]."
Answer: 10062.0

User story: "As agreed at [Data Access Mtg 2015/07/13|https://confluence.lsstcorp.org/display/DM/Data+Access+Meeting+2015-07-13], add dax_ prefix towebserv, webservcommon, webserv_client, dbserv, imgserv, metaserv"
Answer: 2555.0

User story: "Creating a graphical representation of execution framework"
Answer: 40250.0

User story: "Update https://confluence.lsstcorp.org/display/SYSENG/2015+July+08-10+CCS-DAQ-OCS-DM+Workshop+IV    with comments about how the integration testing went."
Answer: 199.0

User story: I have seen the following issue several times, though I am not sure if it is 100% reproducible:  - In HipChat I open Bot: Jenkinds Demo  - I follow the link in the room description  - I enter the data for my run and press "Build"  - I am taken to a page asking me enter my GitHub credentials, which I do  - I am taken back to the Jenkins page, but my job has not started and the page's fields are restored to their default values    At this point I can re-enter the parameters for my run and press Build and it all works. So this is not a big deal. But it is a silent failure and it can confuse users (it certainly has confused me).    I think the ideal behavior would be for Jenkins to start the build after authentication. But if that is too hard, then would it be possible for Jenkins to retain the parameters I had set and to warn me that I have to press Build again to start the build?    Alternatively, could the system could force me to authenticate before I fill out the build fields and press Build?
Answer: 358411.0

User story: "I made some random cleanup of the qserv code while playing with css v2. I want to push these changes to master, thus I am creating this story for this. It involves improvements to logging in UserQueryFactory and Facade (both are now per-module), removing unnecessary namespace qualifiers, and whitspace cleanup."
Answer: 15646.0

User story: When we are analyzing a query, sometimes there are situations where we need to know the schema of tables involved in a query. It will also be useful for checking if user is authorized to run query, and for queries like "SHOW CREATE TABLE". This story involves writing code that will provide access to schema.
Answer: 1228603.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 a port of work performed on HSC but without a ticket. Relevant commits are:    * [05bef6|https://github.com/HyperSuprime-Cam/meas_astrom/commit/05bef629adc37e44ea8482aab88e2eb38a47e3a0]  * [4a6be5|https://github.com/HyperSuprime-Cam/meas_astrom/commit/4a6be51c53f61e70f151de7f29863cb723197a99]  * [69d35a|https://github.com/HyperSuprime-Cam/obs_subaru/commit/69d35a890234e37c1142ddbeff43e62fe36e6c45]  * [9c996d|https://github.com/HyperSuprime-Cam/obs_subaru/commit/9c996d75c423ce03fb54c4300d9c7561b5c1ea99]"
Answer: 32063.0

User story: "This is a port of [HSC-1005|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1005]."
Answer: 25953.0

User story: "Presently one can compare two image-like objects using free functions imagesDiffer, masksDiffer and maskedImagesDiffer in lsst.afw.image.testUtils. These should be replaced by assertXNearlyEqual methods that afw adds to lsst.utils.tests, as per DM-2193.    If necessary, we could leave the old functions around for awhile. But I would prefer to simply get rid of them if we can.    One subtlety is that the current functions take numpy arrays, not afw image-like class instances. Examine the existing users of the code to determine how best to deal with that."
Answer: 178785.0

User story: If user query has "ORDER BY", then lua  can't just execute "SELECT * FROM result" because the order for such query is not guaranteed. To fix that, we need to add "ORDER BY" clause to the "SELECT * FROM result" query on the lua side.    Once we have the above, we might want to remove "ORDER BY" from the query class which runs a merge step on the czar (this has to be done in query analysis step).
Answer: 21085.0

User story: "Hold Request for Information meetings in Chile with equipment vendors. "
Answer: 44477.0

User story: "There seems to be a possible race condition in log4cxx::spi::LoggingEvent::~LoggingEvent. I've had multiple segmentation faults in that function. In all cases, another thread was involved in writing. In at least 2 cases, the second thread was in XrdCl::LogOutFile::Write.  "
Answer: 34793.0

User story: "Qserv doesn't seem to relaunch no more chunk query in case it fails (see DM-2643)    And this function is now unused:  {code:bash}  qserv@clrinfopc04:~/src/qserv (master)$ grep -r populateState core/  core/modules/qdisp/Executive.cc:void populateState(lsst::qserv::qdisp::ExecStatus& es,  {code}  "
Answer: 1586.0

User story: "Given the new state model and mandatory command set for top-level subsystems, update LDM-230 to match"
Answer: 867335.0

User story: "lsst/log API looks stable now, so removing the wrapper would simplify the code."
Answer: 271301.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: SDSS-III does not use the fpC file format for science images.  Science images are now released as ["frame" files. | http://data.sdss3.org/datamodel/files/BOSS_PHOTOOBJ/frames/RERUN/RUN/CAMCOL/frame.html]  The primary science image (hdu0) comes background subtracted and calibrated to units of nanomaggies, with the backgrounds and flat-field conversions included as extensions. The astrometric information is in hdu3 instead of a separate asTrans file.     obs_sdss should be able to ingest frame files and map them to load as dataset "raw." It should also optionally replace the backgrounds and de-calibrate to convert the units back from nanomaggies to counts.     This will be implemented as lsst.obs.sdss.sdssMapper.Sdss3Mapper.
Answer: 2527545.0

User story: "Read over the revised LSE-209 and LSE-70 documents"
Answer: 17286.0

User story: "We examine solutions for repairing corrupt files within an iRODS 4.1.x zone."
Answer: 88238.0

User story: "work done to provide network connectivity, troubleshoot and monitor connections for the above efforts"
Answer: 1.0

User story: "Review either the current version #26 and/or the newest version when it become available."
Answer: 6.0

User story: "Quick start guide for developers still points qserv_testdata to the old repo, it needs to be changed to the new github location."
Answer: 9.0

User story: "The {{mjd}} method has been deprecated since 2010. Remove it."
Answer: 368.0

User story: "We have a working plan of putting the buildbot-scripts under jenkins demo into usage as a production CI system as an intermediate step towards a fully decomposed build."
Answer: 19852.0

User story: "Preliminary work to extend the Process Execution Framework to accomodate changes needed by SUI and others.    This story captures work done in June, prior to incorporating the activity into the baseline plan. Work will be logged under DM-3003 starting July 1st."
Answer: 1204.0

User story: "Presentation giving overview of ISO work, esp. w.r.t AUP and master security plan."
Answer: 1499.0

User story: "Working on drafting whitepaper and abstract for SCADA security challenges faced by LSST."
Answer: 1500.0

User story: "Internal and external recruiting.   Input on NCSA re-organizaiton to ensure proper placement of LSST activities in the NCSA organization.  Meetings."
Answer: 2886.0

User story: "Began to work use cases, and found that they were long, considering the number r of aspects that need to be considered,  Presented to the TOWG,  got guidance to think in terms of processes, but to take that the effort estimates would  have a reasonable basis.  Got guidance to think about the sites's needs but to congress a central approach.    Agree that this would be the struggle for the week."
Answer: 46299.0

User story: "By popular request. "
Answer: 335.0

User story: "Implement three search processors, which use the External Task Launcher (DM-2991):    - to get a table (possibly in binary FITS format)  - to get an image  - to get JSON"
Answer: 43.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Implement and external task launcher, which forks a [python] process and gets back the results. The results can be a table, an image, or a JSON.    "
Answer: 31.0

User story: "Make it possible to add plots (not connected to a displayed table) to StandaloneUI.  Add showXYPlot to python API."
Answer: 69.0

User story: "FITS binary table contains data types and structures that cannot map directly to IPAC table.  We need to define ways to handle these cases."
Answer: 1.0

User story: "Integrate javascript build tools webpack with gradle."
Answer: 2.0

User story: "Run both the HSC and LSST ISR routines on two to three visits worth of HSC engineering data. Compare the results. Where differences exist, either:    * Create and work other tickets to resolve them;  * Explain their origin and why we don't think they are a problem."
Answer: 378794.0

User story: "Assuming RFC-68 is approved, transfer the HSC code to LSST as described there."
Answer: 221757.0

User story: "We need to create polygon-based masks of the usable area of the focal plane, persist them with exposure, and include them in coaddition of PSFs and aperture corrections.    This includes HSC issues HSC-972, HSC-973, HSC-974, HSC-975, HSC-976.    At least some of this will be blocked by DM-833, which is the port issue for coaddition of aperture corrections."
Answer: 46209.0

User story: The HSC fork has coaddition code in two places: pipe_tasks and hscPipe.  The code in hscPipe is what we use (though that depends on the code in pipe_tasks in places), while the code in pipe_tasks is more similar to what's currently on the LSST side.    We want to bring the refactored version in hscPipe back to LSST, but we want to put it directly in pipe_tasks to remove the code duplication that currently exists on the HSC side.    Work on this issue should begin with an RFC that details the proposed changes.    Note that this should not bring over the "safe coadd clipping" code, which is DM-2915.
Answer: 60210.0

User story: "If two separate footprints from the same catalog happen to be merged because an existing merged object overlaps both of them, the flags of which peaks are being detected in which bands is not being propagated. This is causing the apparent dropout of some sources in a merged catalog which were detected in single frame processing.    Taken from ticket HSC-1270"
Answer: 213102.0

User story: "This improves handling of several edge case failure modes, tweaks the configuration to improve performance, and adds some introspection useful for Jose Garmilla's tests.    Includes HSC-1288, HSC-1284, HSC-1228, HSC-1250, HSC-1264, HSC-1273, HSC-1240, HSC-1249, HSC-1238, HSC-990, HSC-1155, HSC-1191"
Answer: 96591.0

User story: "This is a code transfer from HSC-1247."
Answer: 211809.0

User story: "It would be useful to have a parameter that indicates how much any given galaxy is blended. This will be useful for testing how photometry or shears are affected by blending effects.    Ports code from HSC-1260."
Answer: 66195.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: "Work in support of evaluation Discourse as a DM platform for internal and external interactions."
Answer: 64123.0

User story: "The fix to DM-2883 (remove illegal PVi_j cards) isn't quite right, and the error was masked by a piece of code elsewhere that duplicated the functionality.    The issues is that while PV1_[1-4] cards are indeed valid, the ones that SCAMP writes are not.  So we should remove them too, if there are any other SCAMP TPV coefficients.    The masking code was a unilateral removal of PVi_j cards dating back years.  "
Answer: 1585.0

User story: "Design how to redesign CSS, we currently take a snapshot when char starts. It is too static. "
Answer: 34409.0

User story: iRODS can support access to a tape archive with the use of a "tiered resource" where one resource has the role of the cache, and a second has the role of archive.    Use of such a tiered resource construct could be valuable to data management.   Because a iRODS plugin for HPSS is readily available, we examine the set up and use of the tiered resource testing against NERSC HPSS.
Answer: 100813.0

User story: "On boarded Mattais Carrasco-Kind to work in the process execution in the context of Level 3 processing.   Misc."
Answer: 13057.0

User story: iosim is an application-specific benchmarking tool that is developed to be responsive to the request from LSST to select and investigate file systems ahead of actual benchmarks, and in advance of having workflow and other infrastructures needed to investigate file systems under realistic load.  The week the software was    -- Optimized to allow for faster test cycles.   -- Threads were supported by squashing all thread IO into a single simulation process.  -- Information from the original "model" program is propagated to the simulation program, allowing for comparison to the model.  -- initial matplotlib plots allowing a degree of visualization of the performance of a simulated run was added    The goals to deliver this capability in a few week when common systems at NCSA are available for testing.
Answer: 2455692.0

User story: "ITIL is a standard breakdown of processes used in an IT system.  While full ITIL may very well be too heavy LSST operations, it provides a useful checklist for he use cases being developed in the TOWG.   I created an ITIL type spreadsheet to check against the dump of the workflows in the EA  tool  "
Answer: 56464.0

User story: "Debbie Bard leaving created some new work creating the Psf Libraries we need.  While this od not a major task except for computer time, there is some setup required.  I will get an account at SLAC and learn to run the PhoSim utilities she and Michael have developed.    In the short term, Simon is going to do some runs for me.  Meanwhile, I will get into Debbie's account and run her configuration at SLAC.    The outputs then need to be checked to be sure that the Psfs are reasonable."
Answer: 57342.0

User story: "Code cleanup, including migrating some parts to c++11 (in particular, auto_ptr --> unique_ptr)"
Answer: 17259.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 class needs to be refactored to be in consist with FitsRead class which treats all data type as float.  Thus the bitpix in this class does not have to be treated based on its value."
Answer: 25731.0

User story: "This class contains the codes which are not used.  It needs to be simplified and refactored. "
Answer: 15943.0

User story: "Removing the {{datarel}} package entirely has proved to be difficult (DM-2928, DM-2948), so instead I'm simply going to remove non-ingest code (and dead ingest code) from the package, along with its dependencies on {{ap}} and {{testing_endToEnd}}.  Other dependencies will be retained even if they aren't necessary for the code that will remain in {{datarel}}, to support {{lsstDoxygen}}'s use of {{datarel}} as a top-level package for documentation generation."
Answer: 4208.0

User story: "The buildbot scripts have an explicit dependency on the {{datarel}} package, which we'd like to remove from the stack.  It uses {{datarel}} as the top-level product when building the cross-linked HTML documentation; {{lsstDoxygen}}'s {{makeDocs}} script takes a single package, and generates the list of packages to include in the Doxygen build by finding all dependencies of that package.    So, to remove the explicit dependency on {{datarel}}, we need to either:   - find a new top-level product with a Doxygen build to pass to {{makeDocs}} (e.g. by adding a trivial Doxygen build to {{lsst_distrib}})   - modify the argument parsing in {{lsstDoxygen}} to take a list of multiple products (it *looks* like the limitation to one package is only in the argument parsing), and pass it a list of top-level products in the buildbot scripts.    This is currently a blocker for DM-2928, which itself a blocker for DM-1766, which has now been lingering for a few weeks now.  I'm going to look for other ways to remove the block on the latter, but I don't have a solution yet."
Answer: 1450440.0

User story: "I created some lsst to sdss conversions using the Kurucz SEDs and the sims_photUtils methods. A notebook located here: https://github.com/<USER>lsst_colorTransform/blob/master/LSST-SDSS%20Color%20Transformations.ipynb contains plots and more information."
Answer: 2777717.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: SourceMeasurementTask is gone, but we still have code that refers to it, including:  {code}  /Users/<USER>LSST/lsstsw/build/meas_algorithms/python/lsst/meas/algorithms/debugger.py:     21: from lsst.meas.algorithms.measurement import SourceMeasurementTask     26:     measurement = ConfigurableField(target=SourceMeasurementTask, doc="Measurements")    /Users/<USER>LSST/lsstsw/build/meas_algorithms/python/lsst/meas/algorithms/detection.py:    209: The example also runs the SourceMeasurementTask; see \ref meas_algorithms_measurement_Example for more explanation.    /Users/<USER>LSST/lsstsw/build/meas_deblender/examples/utils.py:     15: class DebugSourceMeasTask(measAlg.SourceMeasurementTask):     41:         measAlg.SourceMeasurementTask.preMeasureHook(self, exposure, sources)     74:         measAlg.SourceMeasurementTask.postMeasureHook(self, exposure, sources)     80:         measAlg.SourceMeasurementTask.preSingleMeasureHook(self, exposure, sources, i)    102:         measAlg.SourceMeasurementTask.postSingleMeasureHook(self, exposure, sources, i)    /Users/<USER>LSST/lsstsw/build/meas_deblender/python/lsst/meas/deblender/deblendAndMeasure.py:     31: from lsst.meas.algorithms import SourceMeasurementTask     50:         target = SourceMeasurementTask,    /Users/<USER>LSST/lsstsw/build/pipe_tasks/python/lsst/pipe/tasks/calibrate.py:    180: <DT> initialMeasurement \ref SourceMeasurementTask_ "SourceMeasurementTask"    189: <DT> measurement \ref SourceMeasurementTask_ "SourceMeasurementTask"    /Users/<USER>LSST/lsstsw/build/pipe_tasks/python/lsst/pipe/tasks/imageDifference.py:     36: from lsst.meas.algorithms import SourceDetectionTask, SourceMeasurementTask, \    104:         target=SourceMeasurementTask,    /Users/<USER>LSST/lsstsw/build/pipe_tasks/python/lsst/pipe/tasks/measurePsf.py:    136: The example also runs SourceDetectionTask and SourceMeasurementTask; see \ref meas_algorithms_measurement_Example for more explanation.  {code}    I will handle pipe_tasks calibrate.py as part of DM-435.
Answer: 1995572.0

User story: "There is a leap second coming up in July 2015 and it needs to be added to {{DateTime.cc}}."
Answer: 214.0

User story: "https://confluence.lsstcorp.org/display/LSWUG/LSST+Stack+Installation  seems to be a subset of  https://confluence.lsstcorp.org/display/LSWUG/Getting+Started+with+the+LSST+Software+Stack  with significant differences (e.g. no mention of CernVM FS).  The former  is only linked from the top page of LSWUG (in the child tree) and from  https://confluence.lsstcorp.org/display/LSWUG/Using+the+LSST+Stack.      Should these be reconciled somehow?"
Answer: 2165529.0

User story: "This might be because it is still in gitolite rather than on GitHub, or it might be because it's data and not code."
Answer: 2165538.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 discussed recently on HipChat (Science Pipelines Standup), there's code in {{ProocessImageTask}} that assumes an "astrometer" attribute on a {{CalibrateTask}} instance.  Since this is just needed to match a new set of sources against the reference catalog here, we should probably be using one of the new matcher objects, either by getting one from {{CalibrateTask}} via a documented interface, or by constructing a new one.
Answer: 83657.0

User story: "The buildbot insists on names of the form  {code}  <USER><<EMAIL>>  {code}  despite having already asked for a fullname;  it clears the form if it's unhappy (fortunately, back works).    Can we make it less picky?  "
Answer: 20930.0

User story: "The Histogram has 6 constructors to handle 6 bitpixel data types which are byte, short integer,  integer, long integer, float and double.  Since FitsRead has now only works on float, there the  Histogram should be refactored accordingly."
Answer: 5304.0

User story: "To support the RFD process adopted in [RFC-53], an RFD issue type in the RFC project is required.  While we could add RFD-specific fields to it, I think it's simplest if it's just generic with details provided in the Description."
Answer: 81204.0

User story: "Install current version of the OCS software onto two VMs"
Answer: 22941.0

User story: "When we write Wcs to extra HDUs in Exposures they are truncated if other than TAN/TAN-SIP.  Please don't write them.    A better long term solution is needed.  In particular, we shouldn't be duplicating this information unnecessarily, and we need to be able to persist e.g. TPV to the tables so as to support CoaddPsf.  These issues are not included here."
Answer: 14725.0

User story: "This ticket implements RFC-57, by:   - renaming datarel to daf_ingest (there is already a daf_ingest package, but it's *completely* empty, so I'll just force-push it all away)   - removing everything from the renamed package that doesn't relate to ingest (including pruning dependencies)   - removing ap and testing_endToEnd from the CI system  "
Answer: 9610.0

User story: "The routine in WcsFormatter.cc generatePropertySet ignores any PVi_j cards.  This means that we are unable to round-trip e.g. TPV headers.  "
Answer: 995.0

User story: I share the concern that we're going to spend a *lot* of effort on handling illegal WCS headers, but this one's easy, and we already have a partial fix for the SDSS headers which use a string but no "J" prefix.    Skymapper uses "J2000.0" not 2000.0 for its EQUINOX.  Our code silently converts this to float using atof, and thus interprets it as 0.0 and deduces FK4 (which we don't support).  
Answer: 268.0

User story: "Port issue HSC-1199 to LSST stack to address UNMASKEDNAN mask propagates to all amplifiers"
Answer: 115546.0

User story: "Prepare a Document for the Initial Design of the Base and Summit Networks"
Answer: 397580.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Once the Approximate code in {{afw.math}} has been cleaned up (see DM-2920), set the default for background subtraction to be the Chebychev Approximation (i.e. useApprox=True).  Ensure any other relevant config defaults (e.g. binSize, approxOrderX) are adjusted appropriately.  This will change the outputs of the {{lsst_dm_stack_demo}}, so the "expected" files will need to be replaced along with this change in default settings (see DM-2778 for some comparisons of the demo outputs using the interpolation vs. approximation background estimation schemes).
Answer: 180199.0

User story: "When I implemented DM-2797 I made a few errors in pipe_tasks:  - PhotoCalTask mis-calls two methods of Colorterm by providing filterName, which is not needed  - ColortermLibrary.getColorterm mis-handles glob expressions (the two arguments to fnmatch.fnmatch are swapped).    We also need a unit test for applying colorterms, but that will require enough work that I have made a separate ticket for it: DM-2918. Meanwhile I have tested my changes by running Dominique's CFHT demo. This proves that the colorterm code runs, but does not prove that the terms are correctly applied."
Answer: 2741.0

User story: "We have an algorithm on the HSC fork that modifies AssembleCoaddTask to clip outliers in a much safer way, based on detecting contiguous regions in the difference between a non-clipped coadd and an aggressively-clipped coadd, and only rejecting pixels that are outliers in a single epoch.    One complication for this code transfer is that some of the coadd code has been refactored on the HSC side, and there may be code in hscPipe that duplicates much of what's in pipe_tasks.  We may need help from [~price] to resolve those inconsistencies before tackling this issue.    Once that's done, HSC code can be transferred from the following issues:   - [HSC-1166|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1166]   - [HSC-1202|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1202]"
Answer: 203052.0

User story: "Port HSC code from issues:  * [HSC-1250|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1250]  * [HSC-1245|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1245]  * [HSC-1237|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1237]  * [HSC-1268|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1268]  * [HSC-1274|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1274]  * [HSC-1265|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1265]  * [HSC-1228|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1228]"
Answer: 118256.0

User story: "Port content from HSC-1144, HSC-1236, HSC-1223, HSC-1219, HSC-1203, HSC-1153."
Answer: 385988.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 attached scripts use the afw.cameraGeom.Camera provided by obs.lsstSim.LsstSimMapper as well as a camera generated directly from the description/focalplanelayout.txt and description/focalplanelayout.txt from obs_LsstSim to generate pixel coordinates from a catalog of stars.  These ought to return identical pixel coordinates.  They do not.    If you run cameraTest.py you will get a catalog that lists the pixel coordinates in the control camera (the camera provided by LsstSimMapper), the pixel coordinates in the test camera, and the difference between the two.    Note: the scripts use CatSim code, so sims_catUtils will need to be set up.    Instructions for accessing the CatSim databases are here    https://confluence.lsstcorp.org/display/SIM/Accessing+the+UW+CATSIM+Database    "
Answer: 2227008.0

User story: "See https://confluence.lsstcorp.org/display/DM/Qserv+Release+Procedure for recipe."
Answer: 74786.0

User story: "obs_cfht's camera mapper is missing the new packageName class variable, so it is not compatible with the current stack.    I suggest fixing obs_sdss and obs_subaru as well, if they need it."
Answer: 44615.0

User story: "Can we have a popup for closing tickets?  I often want to comment on the code review when moving a ticket to Done  "
Answer: 5060.0

User story: "We need to clean up gitolite and cgit:  * Repositories that have moved to GitHub should be removed (or, possibly, mirrored back from GitHub).  * Empty repositories (like contrib/eups.git) and obsolete repositories (like LSST/DMS/afw_extensions_rgb.git) should be removed altogether.  * contrib/data_products.git (the Data Products Definition Document source) should be moved to GitHub in the lsst org.  * contrib/processFile.git should be moved to GitHub in the lsst-dm org unless the author adds some test cases and it can be integrated into the CI system as a top-level product (in which case it can go into the lsst org).  * The primary authors of other contrib repositories should be contacted to see if they should be moved to GitHub in the lsst-dm or another org (possibly a new lsst-contrib org).  In particular, contrib/<USER>* (Paul Lotz of the Telescope and Site subsystem) and contrib/pyreb (IN2P3 work for the Camera subsystem) contain current work that should be moved."
Answer: 103240.0

User story: "Qserv has code to support:   * qserv_areaspec_box   * qserv_areaspec_circle   * qserv_areaspec_ellipse   * qserv_areaspec_poly    but only the first one (box) is exercised in our integration tests. This story involves adding queries to test the other 3."
Answer: 367141.0

User story: "host/attend DM LT meeting "
Answer: 2.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "worked on a tool chain to   -- Extract file IO patterns from program strike.  -- Represent in a flat file.  Generate codes --   -- To make many dependent copies dummy files and directories   -- To generate a python code to read and write files like the original application.  -- To generate a c-code to read and write files like the original application.    a driver program to run the pseudo codes in parallel.    The system runs on toys and needs to be show to work on traces from       "
Answer: 6.0

User story: "Travel to CC IN2P3.  of establish operatal coordination between the sites"
Answer: 28.0

User story: "Per RFC-54, the reference anaconda version used by lsstsw will be updated to 2.2.0.  No changes to newinstall.sh should be necessary."
Answer: 18.0

User story: "Per discussion on RFC-55, it was determined that  lsst_apps and lsst_libs and lsst_thirdparty maybe be treated as separate top level products that lsst_distrib need not depend on them nor do they need to be included as part of CI builds."
Answer: 227.0

User story: "An L3 child table might very well have an LSST data release Object table as its director, while almost certainly not living in the DR database. To support it, we should keep track of the database name holding director's table. Note, this is related to DM-2864 - the code touched in that ticket should be checking the director's db name.    Don't forget to add a unit test that will exercise it!"
Answer: 3910.0

User story: "While trying to use the isrTask to interpolate over bad columns in PTF data I discovered that the code assumes that the Exposure has a Detector attached.    Please remove this restriction.  "
Answer: 8701.0

User story: "For sampling in full table scans, and possibly for other selections where the objectId is decomposed into bitfields, WHERE clauses will want to use formulas applied to objectId."
Answer: 1844478.0

User story: "Selecting a column that does not exist results in confusing error. Example:    {code}  SELECT badColumnName  FROM qservTest_case01_qserv.Object   WHERE objectId=386942193651348;  {code}    ERROR 4120 (Proxy): Error during execution:  -1 Ref=1 Resource(/chk/qservTest_case01_qserv/6630): 20150605-16:23:42, Error in result data., 1, (-1)    Similarly,     {code}  select whatever   FROM qservTest_case01_qserv.Object;  {code}    prints  ERROR 4120 (Proxy): Error during execution:  -1 Ref=1 Resource(/chk/qservTest_case01_qserv/6630): 20150605-16:23:52, Error in result data., 1,   Ref=2 Resource(/chk/qservTest_case01_qserv/6631): 20150605-16:23:52, Error merging result, 1990, Cancellation requested  Ref=3 Resource(/chk/qservTest_case01_qs (-1)    (note, sourceId does not exist in Object table)      "
Answer: 46034.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: SCAMP writes distortion headers in form of PVi_nn (i=1..x, nn=5..16) cards, but this is rejected (correctly) by wcslib 4.14;  there is a discussion at https://github.com/astropy/astropy/issues/299    The simplest "solution" is to strip the values PV1_nn (nn=5..16) in makeWcs()  for CTYPEs of TAN or TAN-SIP and this certainly works.    I propose that we adopt this solution for now.  
Answer: 6978.0

User story: "The tasks defined in DM-2191 are probably not sufficiently general to handle the {{icSrc}} dataset generated by {{CalibrateTask}}. An {{icSrc}} specific task will need to be defined.    [~<USER> is anticipating a {{CalibrateTask}} rewrite at some point; we should keep this issue on hold until the plan there is more concrete."
Answer: 1579337.0

User story: "The new Butler dataset types created as part of the HSC deblender merge will need transformation tasks so they can be ingested to the database.    See also DM-2191."
Answer: 2386360.0

User story: "Somyl will go to "
Answer: 93458.0

User story: "Clean up and release prototype implementation of Butler v2."
Answer: 108986.0

User story: "Transferring knowledge from K-T to the DB team."
Answer: 1.0

User story: "Transferring knowledge from K-T to the DB team."
Answer: 1.0

User story: "Transferring knowledge from K-T to the DB team."
Answer: 1.0

User story: "Transferring knowledge from K-T to the DB team."
Answer: 2.0

User story: "To make headway on aperture corrections, we are bringing the HSC implementation of BoundedField over."
Answer: 14598.0

User story: "Open day with all interested vendors  to layout the projects for equipment on Mountain-Base and La Serena-Santiago links."
Answer: 60703.0

User story: "Obtaining a quote from a company in Canada for a special clad cable for the Tololo-Pachon link"
Answer: 411984.0

User story: "{code}   QuerySession description:    original: SELECT objectId, taiMidPoint FROM   Source ORDER BY objectId, taiMidPoint ASC;  has chunks: 1    needs merge: 1    1st parallel statement: SELECT objectId,taiMidPoint FROM LSST.Source_%CC% AS QST_1_    merge statement: SELECT objectId,taiMidPoint ORDER BY objectId,,taiMidPoint ASC    ScanTable: LSST.Source  {code}    Merge statement has syntax error"
Answer: 14663.0

User story: "When I tried to install sims the other day, I got the attached error in one of the daf_base unit tests.  The test calls two different methods of calculating the system time and compares them.  Obviously, my computer was running something else at the time and the lag between the two calls was long enough to cause a failure in the unit test.  I immediately started the build up again and everything worked fine.  Other users might not know to do that.  Perhaps the test should try itself several times and only declare a failure if all attempts fail.    For good measure: this was on OSX 10.10.3"
Answer: 121.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "A suitable multi-cpu capability must be created for measurement tests.  We are hoping to just use a pipe_task, but to do so, the butler must be customized to allow it to read our cutouts and psfs from galaxies and psfs generated from GalSim and PhoSim.    This will be a relatively simple story if pipe_tasks running on 2 or 3 machines at UC Davis proves to be an adequate solution for running our shear experiments."
Answer: 38570.0

User story: "Weekly DMLT meeting  Weekly ISO meeting  Weekly NCSA local group meeting    Met with NCSA networking person (Paul) to discuss progress and plans  Attended End-to-End networking meeting    Attended remotely the CCS-DAQ-OCS-DM Workshop for SCADA presentation by ISO    Worked on/discussed AURA procurement contract amendment and to understand property management procedures at AURA and NCSA    Discussed/planned agenda, made travel arrangements, prepared slides for trip to CC-IN2P3  2-day meeting in France with CC-IN2P3 group    4-day DMLT face-to-face meeting and T/CAM day    Interview with candidate for systems lead    Cleaned up Jira tickets from April  Reviewed reporting requirements and Jira procedures with NCSA employee (Bruce) and managers (Doug, Brett)    Attended several NCSA leadership development and training courses"
Answer: 1.0

User story: "We build the recent Version 10.1 stack release in a Centos 6.6 docker container. As we do so, we also gather strace logs for candidate packages  (for example, afw) for analysis within an effort to create load simulators for file system testing/profiling.   As another product of the effort,  I will make a docker image of the latest release installed on Centos 6.6 and push to  docker hub."
Answer: 131063.0

User story: "When I wrote the initial version of display_firefly I found a few minor issues in the way I'd designed the Display class; at the same time, [~<USER> found some missing functions in the backward-compatibility support for ds9.    Please fix these;  note that this implies changes to afw, display_ds9, and display_firefly.  "
Answer: 22994.0

User story: "Use a GFPS VM server (provided temporarily by NCSA SET) to test and evaluate GPFS server functionality.  The idea being to figure out some initial use cases for GPFS and determine hardware requirements for actual implementation."
Answer: 121167.0

User story: "It'd be useful to write a document about Qserv geared towards users, describing what queries Qserv supports now, what will be supported in the future, what restrictions we are imposing and such. "
Answer: 15949.0

User story: Modify mysql proxy and implement "show processlist" command, which should display list of currently running queries.
Answer: 1033784.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 new colorterms code that we adopted from HSC may not have complete unit tests. The existing colorterms test is pretty good, but may have holes. I'm more concerned about the unit test for PhotoCalTask, which does not apply colorterms at all (likely an existing issue).    Also, be sure to test that the obs_cfht config override loads correctly (presumably with a unit test in obs_cfht) and similarly for obs_subaru."
Answer: 548361.0

User story: "The archive DMCS can experience orphaned threads if a connection is made from external processes waiting for data to arrive.   If the external process goes away, the thread that was created to handle that connection will be waiting on a data structure to be updated.   If the data doesn't arrive, the thread remains alive when it should be checking to see if the connection that created it is still viable, and die if it isn't viable."
Answer: 24275.0

User story: Implement RESTful interfaces for Database (see all D* in https://confluence.lsstcorp.org/display/DM/API), based on the first prototype developed through DM-1695. The work includes adding support for returning appropriately formatted results (support the most common formats). This covers "POST" type requests only, "GET" will be handled separately.
Answer: 1288840.0

User story: "The 3T cable from La Serena to Santiago is expected to be completed September 2015 at which time Reuna can test the segments along the route.  "
Answer: 1951029.0

User story: "Defining the contracts and execution between AURA and Reuna and Reuna and Telefonica who is supplying and installing the fibers for the mountain to base link"
Answer: 418876.0

User story: "Defining the contracts between AURA and Reuna and Reuna and Telefonica who is supplying and installing the fibers for the La Serena to Santiago link"
Answer: 418891.0

User story: "Purchase 2x10Gbs Transceivers and install at Pachon and La Serena.  Run tests to confirm integrity of the link  Utilize the link for AURA live traffic on the fiber backbone"
Answer: 1984268.0

User story: "Current implementation of the creating chunks for views in wmgr is likely not doing right thing. Need to find an example of the partitioned views and implement correct procedure."
Answer: 2546534.0

User story: "The connection will made with the Telefonica 4 dark fibres to the 24 fiber cable from the gate to Pachon.  Tests will then take place over the whole mountain to base link."
Answer: 1984357.0

User story: "Telefonica will install the cable from Tololo to Pachon Sahred Infrastructure building and terminate. Testing of this portion will be carried out."
Answer: 1984363.0

User story: "Telefonica will install the fiber cable from the Gatehouse to Tololo. This will be tested once terminated. We will oversee and monitor the installation and be present for testing."
Answer: 1984367.0

User story: "Including query abort"
Answer: 90092.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: "Skeleton implementation of the Query Metadata - including the APIs and core functionality (accepting long running query and saving the info about it)"
Answer: 51519.0

User story: "The multi-node integration tests have to be updated to work with the latest changes to qserv, in particular the loader, which broke already working tests lately."
Answer: 37071.0

User story: "Hold conversations with the two major fiber laying contractors to prepare the path from Tololo to Pachon with a trench"
Answer: 420327.0

User story: "<USER>recommended some HSC changes for the Colorterm class. To quote Paul: changed Colorterms so it's not a global, and it can now be configured using Config. See https://github.com/HyperSuprime-Cam/meas_astrom/blob/master/python/lsst/meas/photocal/colorterms.py    This sounds useful. Note that the HSC colorterms.py is in meas_astrom but as of DM-1578 the LSST version is in pipe_tasks."
Answer: 12885.0

User story: "Preparation for fiber cable from Cerro Tololo to Cerro Pachon"
Answer: 122703.0

User story: "The new astrometry task should be the default astrometry task, but we need to make sure it is good enough first."
Answer: 145209.0

User story: the deploy script for lsstsw does not contain the     if ! PATH="$PREFIX/bin:$PATH" conda list --no-pip --json system >/dev/null; then          echo "No system package to upgrade"    fix, which accounts for the fact that there is no 'system' package to update on Macs.  This prevents lsstsw from properly deploying.
Answer: 141095.0

User story: "I'm fairly certain meas_modelfit is included in lsst_apps and hence in CI, but id doesn't seem to be included in the LSST Doxygen build:    http://lsst-web.ncsa.illinois.edu/doxygen/x_masterDoxyDoc/search.php?query=modelfit"
Answer: 1987360.0