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: "requirements:  - easy to know what to provide  - fails fast  - has a way to be backward compatible with persisted configs & existing scripts    existing issues to fix:  - currently config creation is verbose, difficult to read, and difficult to format properly  - has the butler class hierarchy baked into the format"
Answer: 178701.0

User story: "To include Python wrappers, in support of DM-5052"
Answer: 242007.0

User story: "Implement RFC-131:    -Make {{afw::geom::Coord}} pure virtual (so it cannot be instantiated) and to add a new class {{afw::geom::SphPoint}} that represents a spherical point.-    {{Coord}} should contain a {{SphPoint}} rather than inherit from it. This allows {{Coord.offset}} and {{Coord.rotate}} to take a {{SphPoint}} argument, without the confusion of allowing the user to provide a {{Coord}} and wondering what is done with the coordinate system and epoch information.    When implementing, look for opportunities to integrate with sphgeom package, such as borrowing SphPoint from there.    Also be careful to integrate with the upcoming WCS overhaul.    Only support distance if this makes the code simpler in some way (such as being provided by code borrowed from elsewhere). It is explicitly not a requirement."
Answer: 321172.0

User story: "The background matching introduced into pipe_tasks a couple of years ago works only on drift-scan observations and is not applicable to pointed observations (e.g., DECam, HSC, LSST). Making background matching work with pointed observations will take a lot more care and coordinated processing across patches due to the smaller scales involved (arcminutes for CCDs vs many tens of degrees for SDSS runs). However, background matching is currently enabled by default in the stack, which necessitates overrides (which are often neglected, at least initially, by the new user) for pointed observations, which is the vast majority of current use cases.    Given that the current background matching code is only applicable to a single camera supported in our stack, [we have agreed|RFC-137] to remove it and disable {{MakeCoaddTempExpConfig.bgSubtracted}} by default."
Answer: 883235.0

User story: "This issue is a pre-req of DM-3472"
Answer: 1326.0

User story: "  Document capturing situation as of beginning of X16 can be found at:    https://dmtn-016.lsst.io    Further extension is planned in F16 to cover X16 development as well as consequences of the LDM-151 rewrite.     "
Answer: 111731.0

User story: "this story represents a spike to  1. ad-hoc gathering of requirements to create butler API that allows a task to define an output dataset type 2. do any proof-of-concept mock up needed 3. write an RFC & gather input  then  A. If there is major dissent, create another design spike story or  B. Close the RFC, and green light work on DM-4180"
Answer: 2064525.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: "Place-holder for additional alert production database work after investigate design task completes.  We should split this into smaller stories for a total of 18 points this cycle."
Answer: 62754.0

User story: "* Add memman documentation (in LDM-135)  * Refresh XRDSSI documentation (in LDM-135)"
Answer: 66241.0

User story: "Currently metadata associated with exposures is accessed in a few different ways: through the Calib object, through the Wcs object, and through the metadata object.    In conjunction with DM-5502, which is to figure out what metadata is needed, this will provide a single interface to exposure oriented metadata.  One tricky thing is that the Calib object has some subset of the metadata we'll need in a sanitized form, but we won't want to have to remember where to look for metadata.  If we can't extend the Calib object to hold all sanitized metadata, we should create a new metadata object to store all sanitized metadata and remove the pieces from Calib that are currently there."
Answer: 292253.0

User story: "Collect a comprehensive set of exposure oriented metadata used by science code.  This should also include metadata that is not currently needed but that could be utilized in the future.  In practice, I suspect this will involve looking for all calls to PropertySet.get since that is how FITS header metadata is currently passed around."
Answer: 162581.0

User story: "Coordinate the creation of a new version of LDM-148 incorporating DPS-WG-generated functional breakdowns."
Answer: 1141493.0

User story: "Coordinate the creation of a new version of LDM-230 incorporating DPS-WG-generated operations concepts."
Answer: 1141493.0

User story: "Write sections that can be incorporated into LDM-148 describing the functional breakdown of the Data Access Center Processing System, including, for each major element:  * overall function  * inputs, outputs, and control interfaces  * components used  * descriptions of functions to be performed    (Story points are for KTL drafting and initial contributions)"
Answer: 1141531.0

User story: "Write sections that can be incorporated into LDM-148 describing the functional breakdown of the Data Backbone, including, for each major element:  * overall function  * inputs, outputs, and control interfaces  * components used  * descriptions of functions to be performed    (Story points are for KTL drafting and initial contributions)"
Answer: 1141531.0

User story: "Write sections that can be incorporated into LDM-148 describing the functional breakdown of the Batch Processing System, including, for each major element:  * overall function  * inputs, outputs, and control interfaces  * components used  * descriptions of functions to be performed    (Story points are for KTL drafting and initial contributions)"
Answer: 1141532.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Write sections that can be incorporated into LDM-148 describing the functional breakdown of the Observation Processing System, including, for each major element:  * overall function  * inputs, outputs, and control interfaces  * components used  * descriptions of functions to be performed    (Story points are for KTL drafting and initial contributions)"
Answer: 1141532.0

User story: "Develop a ConOps document that can be included as appropriate sections of LDM-230 describing the Data Access Processing System that manages L3 computing in and interfaces to the Data Access Center, specifying automated operations sequences, how human intervention can occur, and processes to handle changes and updates.    (Story points are for KTL drafting and initial contributions)"
Answer: 1141540.0

User story: "Develop a ConOps document that can be included as appropriate sections of LDM-230 describing the Data Backbone that contains, manages, and provides access to the Science Data Archive, specifying automated operations sequences, how human intervention can occur, and processes to handle changes and updates.    (Story points are for KTL drafting and initial contributions)"
Answer: 1141540.0

User story: "Develop a ConOps document that can be included as appropriate sections of LDM-230 describing the batch processing environment, specifying automated operations sequences, how human intervention can occur, and processes to handle changes and updates.    (Story points are for KTL drafting and initial contributions)"
Answer: 1141539.0

User story: "make the compass sticky when scroll the image"
Answer: 1639.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: "After some work we have realized that the following needs to be done to field groups:    * Tabs group should have a field group smart wrapper component  * field group needs to reinit on id change   * remove mixin, use Higher-Order Components instead  * support a function for a value, this function will return a value or a promise  * hidden fields - init field group with key/value object  * Sub-field groups? study only, unless it is easy to implement.  * maintain an option to keep unmount field value available  * determine if InitValue needs to be passed around  * passing fieldState around too much  * find reason for react warning every time popup is raised  * look at promise code make sure it is working the way we think  * if practical, remove all export default    FieldGroupConnector.  It is the high order component that replaces the mixin.   FieldGroupUtils.js:  (~line 33): The field value would be a function on the file upload case. Therefore the upload does not activate until validation. In the upload case the function would return a promise. However, It could return a value or an object with a value and a valid status. Now the value key of a field can contain a promise or function or primitive. The function can return a primitive, a promise, or an object with primitive and status.    fftools.js lines 102-158 you can see my experimenting with taking out the connector. It works fine and does eliminate one of the warning messages.    "
Answer: 10048.0

User story: "Turn the L1 ConOps document into appropriate sections of LDM-230, specifying automated operations sequences, how human intervention can occur, and processes to handle changes and updates.     (Story points are for KTL drafting and initial contributions)"
Answer: 1141544.0

User story: Due to the incomplete state of the stack documentation and tutorials, I decided to write down various "tips and tricks" for using the stack as I learn them.  https://confluence.lsstcorp.org/display/SQRE/Tips+and+Tricks+for+using+the+Stack
Answer: 76.0

User story: "After working on a script to test the astrometric matcher, I decided to put together a plan to run similar tests on our algorithmic code.  The rough plan is here:  https://confluence.lsstcorp.org/display/SQRE/Stack+Testing+Plan"
Answer: 92.0

User story: "We encouraged astrometric matching problems for the Bulge verification dataset.  Therefore, I wrote a script that tests the matcher by systematically shifting the coordinates of one sets of the data to see if the matcher still works.  It worked well until ~80 arcsec."
Answer: 94.0

User story: "Prepared and gave a talk at the NSF booth at the Florida AAS meeting on the progress of the verification datasets effort."
Answer: 96.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 fully check the outputs of the processed COSMOS data I needed to combine the information on sources from multiple visits.  This code (written in IDL for now) matching up sources astrometrically across different visits, combines all of the information on separate detections, and measures average quantities (phot and astrom) for unique sources.  The information is then output into four binary FITS files."
Answer: 97.0

User story: "Continued work on processing and QA work on the COSMOS verification dataset.  Running processCcDecam, making diagnostic plots, and nvestigating the results.  Most recently I've  reprocessed the COSMOS data through processCcdDecam using SDSS as the astrometric and photometric reference catalog and am redoing the QA work on those results."
Answer: 101.0

User story: "In order to finish the IDL workflow module for makeCoaddTempExp I needed a program to say which visits overlap a given path.  That's what this script does."
Answer: 104.0

User story: "I wrote a python script using stack components to derive QA metrics and collate other QA-relevant information for a data repository of processed data.  This is currently output to a CSV file that can be loaded into a SQL database."
Answer: 106.0

User story:  {{FlagHandler}} is "unpolished ... and a bit dangerous to the unwary" (DM-5247).  It could be improved by leveraging C++11 features, replacing the default constructor with something that defines the (required) general failure flag, and allowing flags to be added individually.    A potential starting point is [here|https://jira.lsstcorp.org/browse/DM-5247?focusedCommentId=45894&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-45894].
Answer: 2327834.0

User story: "Following [recent changes to single frame processing|https://community.lsst.org/t/backward-incompatible-changes-to-processccdtask-and-subtasks/581], {{icSrc}} no longer includes celestial coordinates and {{icMatch}} is no longer being written. {{meas_mosaic}} requires this information. Provide a work-around."
Answer: 43581.0

User story: "Take the example C++ codebase developed in DM-5470, and expose it to Python in the most idiomatic possible way using Cython. Produce a [technical note|http://sqr-000.lsst.io] describing how this was carried out and discussing any particular pain points either in implementation or results."
Answer: 57790.0

User story: "Produce a small C++ codebase that can be used for experimenting with the various technologies we can be used for exposing C++ to Python. It should enable us to experiment with as many of the potential pain points with these technologies as possible"
Answer: 9027.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: "Processing Decam data from raw images currently requires downloading the bad pixel mask files from NOAO, then ingesting them into the calibration repository. It would be much more convenient if we included these with obs_decam itself, pending the ok to do so from NOAO. Our understanding is that we could create a default calibration repository in obs_decam, which would be the parent of users' calibration repos. We will also likely want to convert the provided files from mask images into tables of bounding boxes."
Answer: 1713881.0

User story: "When ingesting calibration files with obs_decam, the current configuration in the mapper policy is to save in the registry the path from the current working directory to the ingested files. This is very fragile and can only work if {{ingestCalibs.py}} is run from within the calibration repository itself, and there are numerous ways in which this can still fail. The ingest script and mapper policy file should be updated to specify a path template, and to symlink or copy the calibration files into the repository as is done for ingesting images."
Answer: 547169.0

User story: "Success criteria:    * Flats should be totally flat, i.e. bias jump problem fixed everywhere, amplifier levels fixed (both of these are currently hit & miss at the moment).  * CRs should be properly interpolated over for non-sky images (as this means no PSF estimate).   * Use un-binned images to confirm that bad pixel masks are correct everywhere.  "
Answer: 895623.0

User story: "{{ObjectMaskCatalog}}, defined in [{{pipe_tasks}}'s {{objectMasks.py}}|https://github.com/lsst/pipe_tasks/blob/e866fdf2ea428bdadf5fea3a03dba008012d28ba/python/lsst/pipe/tasks/objectMasks.py#L8], (ab)uses [its {{readFits}} method|https://github.com/lsst/pipe_tasks/blob/e866fdf2ea428bdadf5fea3a03dba008012d28ba/python/lsst/pipe/tasks/objectMasks.py#L36] to persuade the Butler to initialize a Python class from a non-FITS datasource. Please provide a supported way to get the Butler to read non-FITS data."
Answer: 1866328.0

User story: "The currrent Doxygen documentation generates documentation for options in the config class of tasks. However, the quality of the documentation generated leaves a lot to be desired: Doxygen merely embeds a block of code that just happens to include the help string but also includes a lot of unnecessary code. This makes the config parameters hard to find, hard to parse (by humans) and makes them very inconvenient to use when documenting source code. Provide some method for presenting the config options in a visually pleasing manner."
Answer: 2178889.0

User story: "This ticket will ensure that [SQR-006|http://sqr-006.lsst.io] reflects the LSST the Docs continuous delivery platform as it is deployed in the DM-5404 epic. (SQR-006 was initially written as a planning/design document).    This story should be closed only once the DM-5404 epic is ready to be closed."
Answer: 101410.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: "LTD Mason was originally intended to build docs for DM’s Eups-based packages from our Jenkins CI/CD servers. There is tremendous value in consolidating all of DM’s Sphinx-based documentation deployments to use LSST the Docs rather than Read the Docs. This ticket will design and implement adaptations to LTD Mason to build single repo doc projects (Technotes, Design Documents, the Developer Guide, and even generic software projects) from a Travis CI environment. Also includes a template {{.travis.yml}} and associated documentation to allow others to enable travis builds for their documentation.    We name Travis specifically because it is the easiest platform for implementing CI for generic open source projects."
Answer: 73723.0

User story: "RFC-162 proposes that the Python coding standard should be rewritten in terms of PEP-8. [~<USER> has requested that the proposed new text of the coding standard be submitted for his approval prior to incorporation into developer.lsst.io, presumably as a pull request. This ticket covers that rewriting."
Answer: 243888.0

User story: The Jenkins build of {{ci_hsc}} is failing:    {code}  [2016-03-15T00:41:10.959702Z]   File "/home/build0/lsstsw/stack/Linux64/obs_subaru/tickets.DM-5453-g53dd454477/config/measureCoaddSources.py", line 14  [2016-03-15T00:41:10.959725Z]     config.astrometry.refObjLoader.load(getPackageDir("obs_subaru"), "config", "filterMap.py"))  [2016-03-15T00:41:10.959747Z]                                                                                               ^  [2016-03-15T00:41:10.959755Z] SyntaxError: invalid syntax  [2016-03-15T00:41:11.009328Z] scons: *** [.scons/measure] Error 1  [2016-03-15T00:41:11.011114Z] scons: building terminated because of errors.  {code}
Answer: 837.0

User story: "We need to be able to find repositories based on criteria such as version, validity date, etc.  This story is to provide support & proof of concept that demonstrates this."
Answer: 2801.0

User story: "Download the ngmix codebase from https://github.com/esheldon/ngmix. Install it and its dependencies in the same environment as the LSST stack. Experiment with using it and understanding how it works"
Answer: 44391.0

User story: "Through S15 (DM-1108) and W16 (DM-3561), [~<USER> has conducted a large-scale investigation into galaxy shear fitting. Please summarize the motivation, methodology and results of this study as a [technical note|http://sqr-000.lsst.io/en/master/]."
Answer: 68141.0

User story: "Adding scipy as a stack dependency is still a nebulous term to me.  David is going to follow up on how to do this exactly (it's already in conda_packages.txt)."
Answer: 23075.0

User story: "A report is to be written on the Astropy integration plan. This report will be in the form of an SPIE paper."
Answer: 110928.0

User story: "This story will examine the overlap between Astropy and AFW and examine different approaches that could be taken to integrate Astropy into the DM software."
Answer: 19919.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-5289 removed the definition of NB0656 but left it in the list of {{HscMapper.filters}}. This has broken Jenkins. Please restore the definition."
Answer: 10.0

User story: "At present validate_drp has a lot of duplication between the various yaml files, including nearly identical twins for normal and quick examples. Much of the duplication could be eliminated by making the validation code a normal task and saving the configuration parameters as a normal config. Advantages include:    - Properties that appear may be camera-specific, such as {{brightSnr}}, {{medianAstromscatterRef}} and {{medianPhotoscatterRef}}, can be set in the usual way: using a config override in the appropriate {{obs_}} package. That said, in many cases reasonable defaults exist based on the quality of our algorithms. The current values used for {{CFHT}} and {{DECam}} are identical; if those are good values then no overrides are needed for those cameras.  - It uses our standard for processing data, including standard methods of specifying data and configuration."
Answer: 283.0

User story: "Data backbone first edit : 1pt (week 1)  Data backbone second edit : 1 pt (week 2)  Third edition : 1 pt week 3&4"
Answer: 382968.0

User story: "Porting code from HSC to LSST brought over a unit test into meas_algorithms for functionality that exists in meas_base in LSST. This is due to the refactoring of code into meas_base on the LSST some while ago. This unit test currently runs with code from meas_algorithms, which means it can not simply be moved, as meas_base comes before meas_algorithms in the build order. This work may involve rewriting the unit test to use different code, or evaluating if it is worth bringing that functionality to meas_base along with the test. The code in question is the detection task."
Answer: 499892.0

User story: "Following the discussion in RFC-156, ensure that a documented, fast, easy to initialize shared stack is available for developers to use on shared systems, certainly to include {{lsst-dev}}."
Answer: 54350.0

User story: "Add {{lsst_ci}} as default build target for Jenkins.    I think this is a simple edit to one line.    Notes of interest:  * {{lsst_ci}} explicitly requires {{lsst_distrib}} in its table file so one could actually replace the {{lsst_distrib}} default target with {{lsst_ci}}, but as we transition I might actually suggest leaving both in place to provide a bit of clarity.  * I'm not currently requesting adding this to the default {{lsstsw}} build product."
Answer: 4185.0

User story: "Add an SFM pluggin for ngmix fitting using one of the simple fitters in ngmix/fitting.py.    This should depend on DM-5429 (or a suitably configured modelfit_ShapeletPsfApprox) for approximating the PSF as a sum of Gaussians.    Testing and tuning this algorithm to get it working well should be deferred to another issue."
Answer: 150851.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "This ticket describes changes which were made to the test runner and analysis scripts during the Dec 2015 - Feb 2016 period.  Most of these changes were made as a part of moving to a large computing cluster, where both the units of work and the output file organization had to be changed to make parallelization possible.    The large number of tests run during this period and the need to more efficiently analyze and compare also introduced some changed to the analysis and plot modules.    Since these changes do not pertain to any single test (though many were done during Dm-1136), I have put them on a separate ticket."
Answer: 4805.0

User story: Create a new "meas_extensions_ngmix" package, and add SFM and Forced plugins to approximate the PSF using a mixture of Gaussians using ngmix's E-M fitter.    There is example code to actually run ngmix in this mode in ngmix's README.md, but the tricky part is probably figuring out how to extract the outputs and write them to records.  If at all possible, we should use the same format as modelfit_ShapeletPsfApprox, so either algorithm could be used to feed CModel (and other ngmix algorithms, when modelfit_ShapeletPsfApprox is configured to use only zeroth-order fitting).    This will also require figuring out the failure modes and defining the appropriate flags.  Given that ngmix has no C++ interface, this work should be entirely Python, and hence it may be desirable to address DM-4009 somehow first.    This issue is almost certainly too large in terms of story points, but anything smaller doesn't really have a very well-defined end-point.  Maybe subtasks?
Answer: 149247.0

User story: SingleFrameVariancePlugin can produce the following numpy warning, with no hint as to where the problem is coming from:  {code}  /Users/<USER>UW/LSST/lsstsw/miniconda/lib/python2.7/site-packages/numpy/core/_methods.py:59: RuntimeWarning: Mean of empty slice.    warnings.warn("Mean of empty slice.", RuntimeWarning)  {code}  I tracked it down by adding the following code to the calling code:  {code}  import warnings  with warnings.catch_warnings():      warnings.filterwarnings('error')  {code}    It would be nice if the measurement plugin handled this situation more gracefully, such as turning the warning into an exception or testing for it and handling it.    One way to reproduce this problem is to run {{tests/testProcessCcd.py}} in {{pipe_tasks}}. However, it is commonly seen when running {{processCcd}} on other data, as well.
Answer: 96213.0

User story: "On DM-5084 [~<USER> switched PropagateVisitFlags to match against icSrc instead of src because we weren't yet matching `icSrc` to `src` in ProcessCcdTask.  That's now been done on DM-4692, so we can revert this.    After doing so, please verify with ci_hsc that this is working, as that's where the only test of this feature lives."
Answer: 66307.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: {{pex_config}} is able to report where a config parameter is set.  Please add a command line option {{--show history=config.parameter.name}} to the cmdLineTask parser.    The implementation will probably want to use something like:  {code:python}  import lsst.pex.config.history as pch  pch.Color.colorize(False)  print pch.format(config.calibrate.astrometry.solver, "matchingRadius")  {code}  
Answer: 308006.0

User story: "To get jointcal to build in the stack, we need to satisfy the SuiteSparse dependency by creating an external package for SuiteSparse.    Assuming it builds cleanly, this should satisfy the remaining requirement of RFC-153, now that the licensing question has been answered there."
Answer: 55942.0

User story: "Incorporate the new task into the command-line task. The goal of this ticket is to implement DipoleFitTask along-side the existing DipoleMeasurementTask, eventually to replace it.    This is likely to have additional stories added, including testing, possibly as part of DM-5412."
Answer: 96490.0

User story: "Test new task on real data (which data, TBD); inspect results by eye and compare with existing DipoleMeasurementTask output. This is necessary prior to incorporation into the imageDifference command-line task.    This test may also indicate that further optimizations are necessary (DM-5721)."
Answer: 2024752.0

User story: "These scripts will be improved (i.e. more genericity) and integrated inside Qserv code. Qserv will be deployed on ccqserv100 to ccqserv125"
Answer: 30238.0

User story: "Before we start digging into jointcal, it'd be good to get the whitespace/oldpython/indentation/lint/etc. questions sorted out. This ticket is for that."
Answer: 1507.0

User story: "After a recent change to {{daf_persistence}} and possibly other packages I'm finding that many packages leave {{repoCfg.yaml}} files lying around after they run unit tests.    I'm not sure what is best to do about these files. If they are temporary, as I am guessing, then I think we need some way to clean them up when the tests that generated them have run. If they are intended to be permanent (which would be surprising for auto-generated files) then they should probably be committed?    I hope we can do better than adding them to .gitignore."
Answer: 450.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: "I would like email notification of the completion of Jenkins jobs that I submit (but no others). It would especially helpful if the email included a link to the console log and a summary of success or failure.    As it stands, it is painful to figure out when a job succeeds or fails. I have to either watch endless irrelevant messages go by on the Jekins HipChat room or, when the job stars, immediately launch a browse window to watch the console log. Neither is very satisfactory, especially if I need to go somewhere else while the job runs.    The current system would be acceptable if the jobs ran quickly, but most of mine take an hour.    A fine alternative (in case it is easier) is to have a copy of the HipChat notification of jobs I submit sent directly to me on HipChat. That will trigger a notification if I'm connected to HipChat or an email if not, so it would be fine."
Answer: 1077444.0

User story: "We need to ensure that the latest version of the application(javascript) is loaded. Conditions: 1. once loaded, it should be cached by the browser. 2. name of the script has to be a static, so it can be referenced by api user. 3. it also has to load dependencies(gwt scripts) after the main script is loaded.  To do this, we created a tiny firefly_loader.js script whose role is to load the main script and then its dependencies. firefly_loader.js is configured to never cache so that the latest main script is always picked up. The main script is appended with a unique hash on every build.  This ensures that the browser will pick up the new script the very first time, and then cache it for future use. "
Answer: 121922.0

User story: "Create drop down container to display search panel, catalog search panel, image search panel, etc.     "
Answer: 18049.0

User story: "The search panel to do the catalog search"
Answer: 109030.0

User story: "A dialog to edit all the filters on the data for table and XY plot.     AND, OR conditions?    implemented:  * display column's units and descriptions  * add single column filter with auto-correction  * add free-hand filters field with validation and auto-correction  * reset, clear filters as well.  * 'Column' is sticky... scrolling left/right will not affect it.    "
Answer: 155165.0

User story: "[Discussion on clo|https://community.lsst.org/t/how-do-we-update-eups/478/14] indicates that not only does EUPS (distrib) use a {{TAP_PACKAGE}} environment variable (and maybe a {{.tap_package}} file), but also there is [policy|https://community.lsst.org/t/how-do-we-update-eups/478/14] about how they should be set.    However, there doesn't seem to be any documentation covering this, and certainly the policy is not recorded on our [instructions for distributing third party packages|http://developer.lsst.io/en/latest/build-ci/third_party.html]. Please ensure that it is."
Answer: 70599.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 schema should in general not be a function of whether particular features are enabled or disabled so that users can have confidence looking for columns.  However, {{MeasurePsfTask}} only creates the {{calib_psfReserved}} column when {{reserveFraction > 0}}.  This causes warnings when attempting to propagate flags from calibration catalogs to deep catalogs."
Answer: 1368.0

User story: "In porting {{meas_algorithm}} changes from HSC to LSST, modifications to the {{SdssShape}} algorithm were discovered. These changes should be transferred to LSST."
Answer: 8745.0

User story: "Make sequence diagram for Base site messaging and enumerate each message, then provide a narrative description of each message (including logical flow control if applicable) AND an example message payload for the message dictionary. 4  Meetings about message exchange style.  Meetings about using queue fanout for return messages from forwarders and distributors, or binding using routing keys. 4  Rapid prototyping of some of these ideas for evaluation. 4"
Answer: 456409.0

User story: "SSIA.  The final hours of the final day were very valuable."
Answer: 23303.0

User story: "Per RFC-145 we need to catch stories without valid Team field."
Answer: 1540333.0

User story: "Per RFC-133, users will sometimes need to do full table scan through L1 catalogs, and our baseline does not allow for full scans on the L1 catalog. It'd be good to maintain a replica of L1 for such scans. This story involves changing LDM-141 and adding hardware for the replica. "
Answer: 1453734.0

User story: "Per RFC-133, we should check with science collaborations whether we are not missing any killer use case by not enabling shared scans on L1 catalogs."
Answer: 1705933.0

User story: "The butler changes in DM-4683, in particular the removal of {{.mapper}} from the interface exposed by a {{Butler}} object, broken {{obs_cfht}}, {{obs_decam}}, and {{ci_hsc}}.    This issue will fix those changes, and search for additional broken things.    This work is proceeding in conjunction with DM-5370 to test that the CI system, e.g. {{lsst_ci}}, is sensitive to these breakages and fixes."
Answer: 2578.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: "Create an {{lsst_ci}} package to be built for the continuous integration testing.    Plan:  1. Create empty package that has dependencies on {{obs_cfht}}, {{obs_decam}}, {{obs_subaru}}, {{testdata_cfht}}, {{testdata_decam}}, {{testdata_subaru}}. (/)  2.  Ensure above builds. (/)  3.  Add {{obs_lsstSim}} and ensure that it builds. (/)    The following were moved to DM-5381:  [ [~<USER> : How can I get strikethrough to work in the following list?]  3. Add dependencies on {{validation_data_cfht}} and {{validation_data_decam}}, and {{validate_drp}}.  4. Run CFHT, DECam quick examples in {{validate_drp}}.  5. Test for successful running of the above examples.  Fail and trigger Jenkins FAILURE message if these examples fail.  6. Check performance of CFHT, DECam runs against reference numbers.  Fail if there is a significant regression.  7. Decide how to include {{ci_hsc}}, which currently can take at least 30 minutes to process the image data.--"
Answer: 7197.0

User story: The default value of {{MeasApCorrConfig.refFluxName}} is presently "base_CircularApertureFlux_17_0". This should be changed to "slot_CalibFlux". That is what the slot is intended for. The slot usually points to "base_CircularApertureFlux_17_0", but {{obs_sdss}}, at least, overrides this.    Additional jobs:  - Update {{obs_sdss}} {{config/processCcd.py}} to remove the override for this value, since it will no longer be needed.  - Check for and remove unnecessary overrides in other obs_ packages
Answer: 4779.0

User story: "Most developers who install {{lsstsw}} will want {{anaconda}} instead of {{miniconda}}. I suggest either switching entirely or offering an easy way for a user to specify one or the other -- preferably something that lives outside of {{lsstsw}}, e.g. an environment variable or a config file in {{~/.config}}"
Answer: 569195.0

User story: "The goal of this ticket is to enable communication between CC-IN2P3 and Qserv team in order to prepare for Pan-STARRS data ingestion into Qserv. This data ingestion step is necessary for the large scale tests of Qserv foreseen for summer 2016.    Specifically, we need to understand:    - What is the size of the data set to be imported to CC-IN2P3?  - Where the Pan-STARRS data set to be imported is currently located?  - What mechanisms will the host of Pan-STARRS data make available to CC-IN2P3 for downloading the data set?  - Does the envisaged ingestion mechanism into Qserv requires that the data transit through the Qserv master server or will each Qserv worker be able to ingest its own chunk of data?  - After the ingestion process is finished, do we need to keep a copy of the ingested data out of Qserv?      Given the size of the dataset likely involved in this process, this project will probably require that we (both Qserv and CC-IN2P3 experts) set up specific mechanisms and equipment for efficient transport, storage and ingestion of these data. Timely planning and several testing campaigns seem necessary for this project to make progress.      "
Answer: 1837189.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: "previously the image select panel would only modify a plot.  Now give it the ability to add a plot."
Answer: 63110.0

User story: "Add 3 color support.  Basically take the panel an be able to repeat of red,green, and blue.  We might want to use a disclosure component.    What has been done: (copied from github commit message)  Add 3 colors support to image selection dropdown, disclosure component is used for r, g, b field group tabs.    For SizeInpuFiield component, fixed validation, add props 'showFeedback' for feedback display and add valid range in error message popup.  (this update is based on the following issues as SizeInputField is used in other panel     - Popup message should have the range are part of the message     - The feedback at the bottom should be optional, turned on by a property.     - When a value such as ‘111d’ is entered,  It does not validate correctly. )    Some Issues:   - should 'disclosure' component's status be kept?   - image creation doesn't work if any of r, g, b is disabled."
Answer: 56208.0

User story: "Implement     * dss, sdss, blank image tabs  * a reusable radius input field   * implement upload file tab  ( the reusable upload file component is done in DM-5584)  "
Answer: 37253.0

User story: "This is the first stop in image select panel:    * Design basic panel  * Implement tabs: issa, 2mass, wise  * implement ability to replace a image"
Answer: 12967.0

User story: "Update {{pipe_flow}} to change dependencies and examples to reflect migration to {{pipe_supertask}}"
Answer: 205270.0

User story: "Need to update documentation with latest changes on {{pipe_base}}, {{pipe_supertask}} and {{pipe_flow}}"
Answer: 208275.0

User story: "Create a new package {{pipe_supertask}} and move all supertask code and activator there. Will soon create a poll to pick a better name."
Answer: 2437.0

User story: "Test the error estimation code using bootstrap resampling."
Answer: 14703.0

User story: "DM-1136 was done with a single Psf, partly to avoid some of the problems we found with PsfShapeletApprox.  In this issue, I will look at consistency of the measurement for different Psfs."
Answer: 13285.0

User story: "Deliverable: change request and document diffs for LSE-140"
Answer: 23849.0

User story: "Deliverable: together with [~<USER>, identify the changes needed and develop initial content in EA."
Answer: 23848.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Update {{ProcessCcdTask}} so that it can be used with different datasete types as appropriate for the ISR task. This will allow us to get rid of obs-specific variants {{ProcessCcdSdssTask}} and {{ProcessCcdDecamTask}}    The plan is to change {{ProcessCcdTask}} as follows:  - set {{doMakeDataRefList=False}} in the call to {{add_id_argument}}  - get the dataset type from the ISR task (default to "raw") and set it in data container  - make the dataRef list by calling {{makeDataRefList}} on the data container    Question for DECam folks: do you want two executable scripts for DECam (one that processes data from the community pipeline and one that performs ISR)? Or do you prefer one exectutable (in which case you switch between performing ISR and reading the output of the community pipeline output by retargeting the ISR task)? If you prefer one binary, then which should be the default: perform ISR or read the output of the community pipeline?
Answer: 11750.0

User story: "Week 1: Admin mtg, group mtg, ICI mtg, interview. 1pt  Week 2: Meetings, ICI task planning and prioritization 2pt  Weeks 3&4: Interviews, admin and group meetings, ARI SOW"
Answer: 46061.0

User story: "Support for lsst-dev cluster, OpenStack, and accounts  for week ending February 7, 2016."
Answer: 1.0

User story: "Create a result container for table data.  This task is composed of:  - create actions, action creators and reducing functions  - dynamically add/remove table from view  - support expanded mode  - TabPanel support for deleting tabs."
Answer: 15541.0

User story: "DAX deployments may be based on nginx. We need to do some basic research about available nginx authentication options, since to-date we've been focused on Apache HTTPD."
Answer: 56035.0

User story: "Revise our LSST IAM Design Doc based on our work over the Oct 2015 - Mar 2016 period."
Answer: 227219.0

User story: "Currently all of the logic that goes into using bright object masks falls into obs_subaru and pipe_tasks. This ticket should move parts (such as the bright object mask class) out of obs_subaru, into a camera agnostic location. The work should also duplicate relevant camera configurations and parameter overrides in the other camera packages. Bright object masks were originally introduced in DM-4831"
Answer: 114448.0

User story: "This is a quick coding foray, to try to shake loose unforseen implementation dependencies or speed-bumps with TAP integration.    Time-boxed at 4 points to fit into a single sprint with Brian's current resource loading -- this is intended to be only a clarifying start."
Answer: 36938.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: There are currently two separate query IDs defined for queries in czar code:  - "user query ID" - defined in {{Czar::submitQuery()}}, used for constructing table names for result table and message table  - "QMeta query ID" - ID obtained from QMeta after registering the query (by {{UserQuerySelect::_qMetaRegister()}})    Currently user query ID is used by the rest of the czar code to track the processing of this query, QMeta ID is not used yet for anything except QMeta registration and updates.     QMeta ID will be used for async query identification and there is no actual reason to keep two IDs around, so we should replace user query ID with the QMeta-generated one everywhere. One minor issue is that currently message table name is built and table is locked before we register query in QMeta. Need to understand it and see if we can reverse that logic.
Answer: 2695.0

User story: "Test potential improvements in many-vertical-shards test (20,50) run-times with query optimizer settings."
Answer: 53354.0

User story: "This would allow integration tests in CI not to break when some Qserv dependencies change. Indeed CI uses a Docker container which include qserv-dev to build current Qserv version."
Answer: 2114227.0

User story: Currently runquerys.py script falls over when running high-volume tests:    * "LV": 75,  * "FTSObj": 3,  * "FTSSrc": 1,  * "FTSFSrc": 1,  * "joinObjSrc": 1,  * "joinObjFSrc": 1,  * "nearN": 1    We need this to be working again to validate recent work on schedulers and to support upcoming work on large results, etc.
Answer: 44457.0

User story: "In debugging DM-4692, we found that {{PcaPsfDeterminer}} was very aggressive in rejecting outliers from individual principal components, which lead to unconstrained solutions in large regions of particular images (validation_data_cfht visit 849375 ccd 22 is a good example). This also caused significant changes in the PSF model when small numbers of psf candidate stars were added or dropped from the input catalog. We believe this behavior lead to ~10 milimag variations in PSF photometry. We were able to reduce this sensitivity by setting an ad-hoc work around configuration of {{spatialReject=6.0}}, but we did not study this in depth."
Answer: 1793286.0

User story: "[~<USER> suggests that we have a star selector based on the PSF model. He asked me to file this ticket and assign it to him. Jim: feel free to edit this description to explain the need in more detail.    This would be a good candidate for an efficient way to identify sources suitable for aperture correction DM-5309"
Answer: 2268670.0

User story: "As a follow-on to discussions at the Feb 2016 JTM, document the policy question(s):    Should LSST grant data rights based on eduPersonAffiliation values set by university identity providers (via InCommon/eduGAIN)?    Explain the eduPersonAffiliation values and controls around those values.    Deliver this document to Beth & Don and other stakeholders."
Answer: 228721.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "There have been a couple of issues that have arisen when deploying test instances vs updating an existing instance due to slight differences between plugin versions.  This would be avoided by putting all plugin versions under change control.    Including:  * The versions of all jenkins components need to be explicitly specified  * The stored job {{config.xml}}'s should be updated to reflect plugin version changes  * The hipchat notification configuration should be updated to fix breakage caused by the production core/plugin update earlier this week  "
Answer: 2902.0

User story: "Following DM-2984, we are confident that the ISR performed by the LSST and HSC stacks is equivalent. Extend that work to cover the whole of single-frame processing ({{ProcessCcdTask}}).    There are two deliverables for this issue:  * A collections of plots and/or comparison scripts that run on the pipeline outputs that can be used to compare their quality in all the ways we think matter. This should probably be in a new repo. Some of these tests should compare the results of the two pipelines against each other (as that's easier to do), but others should be useful for tracking the quality of the pipeline even after we abandon the HSC fork.  * A set of new JIRA issues that capture the code transfers we think we will need to get the LSST pipeline up to the same level of quality as the HSC one."
Answer: 119601.0

User story: "Document the simple simulator produced in DM-4899.  This will also involve some refactoring and adding unit tests to make it usable by others in the group."
Answer: 86601.0

User story: Once jointcal is part of the stack, we need to get it under continuous integration, buildable by Jenkins, etc. There is only one unittest in the package currently, but at least getting that test built and run will catch a number of basic problems.    This requires having its dependencies (CHOLMOD from SuiteSparse) under CI as well.    As part of this, it would be good to have at least one "integration test" that runs jointcal as part of processCcd, to catch problems that appear when that interface changes.
Answer: 161331.0

User story: "This ticket continues DM-3704 and refactors processDiffim."
Answer: 1859370.0

User story: "The original DM-3704 was to refactor all ImageDifference task. This issue was split into 3 tasks:  1) Split image difference task into two tasks (1) to generate an image difference, and (2) to run detection and measurement on it: processDiffim.py  2) Refactor the Image Difference portion  3) Refactor the processDiffim portion    This ticket refactors the new task that just generates and image difference. "
Answer: 1859377.0

User story: "In DM-5206 I modified the way WCS headers are written when persisting FITS files. I attempted to write a test case that checked this was being done correctly for both {{Wcs}} and {{TanWcs}}, but I mistakenly managed to check {{TanWcs}} twice. Please correct the test."
Answer: 149174.0