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: "LeastSqFitter1d's constructor's {{order}} parameter is {{unsigned int}}. However it is stored as {{int}} and {{LeastSqFitter2d}} uses {{int}} in both places.    I suggest switching to {{int}}. The existing code always supplies a small positive integer, so it's safe and trivial to fix. However, it will require the same change to the pybind11 interface file.    I further suggest not changing this until after the pybind11 transition. Then change it and make sure the whole stack builds."
Answer: 163040.0

User story: "[~<USER> in DM-8825 points out that ci_hsc is broken.  It appears to have broken between build [#932 (Jan 3, 2017 5:57:59 PM)|https://ci.lsst.codes/job/ci_hsc/932/] and [#933 (Jan 4, 2017 1:57:00 AM)|https://ci.lsst.codes/job/ci_hsc/933/].  Diagnose and fix."
Answer: 988.0

User story: "SQuaSH API is being used by different clients (e.g. the bokeh apps and SQRE Bot service) we really need a versioning scheme so that a client can look at the version number and know if it can integrate with it.    Semantic version  MAJOR.MINOR.PATCH seems appropriate. When the MAJOR number increments, it means that backward incompatible changes have been made. When MINOR increments, new functionality has been added that should be backward compatible. Finally, a change to PATCH means that bug fixes have been made to an existing functionality.    We could have a semantic version for individual endpoints used by different services.    Django REST Framework has a number of different versioning schemes. I would suggest using the AcceptHeaderVersioning scheme.  [http://www.django-rest-framework.org/api-guide/versioning/#acceptheaderversioning]"
Answer: 542402.0

User story: "This is a meta-story to group Butler error reporting improvement requests"
Answer: 1782876.0

User story: "This is a meta-story to group documentation related stories for Butler"
Answer: 1782877.0

User story: "Creates a download dialog with the following features:   - capture the selected rows from the given table   - option to include email notification   - zip file with or without sub-folders     Also, create a download button to launch the dialog.  Button should:   - track a given table or an active table   - track when row(s) have been selected with visual indication"
Answer: 3144.0

User story: "[~<USER> proposed using a non-negative matrix factorization (NMF) technique for deblending footprints by estimating SED's for the various galaxies. Through the conversation we outlined an algorithm to implement for the multi-color deblender that adds the constraint of symmetry from the SDSS deblender. This ticket involves reading the literature on NMF, developing the algorithm, and having it evaluated by others."
Answer: 8666.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: "Just in case we still care about keeping the conda installs up to date, there is a new version of the sims stack out.  The EUPS build number is b2599.  I understand if our policy is to just let the conda installs fade into oblivion while we wait for our new binary install system to come on line."
Answer: 1824757.0

User story: "Neglect of proper motion in the reference catalog can cause zonal astrometric errors in wide-field surveys ([Tholen, Micheli & Elliott 2013|http://adsabs.harvard.edu/abs/2013Icar..223..625T]). We therefore require a means to transform reference catalog positions to the epoch of observation.    The PS1 PV3 catalog contains columns with the proper motions for RA and Dec in arcsec/year ({{pmRa}}, {{pmDec}}) with associated errors, and the mean epoch in seconds relative to the UNIX epoch ({{epoch}}).  It would be good to support this scheme even if another is chosen."
Answer: 878739.0

User story: Please allow users to save the SWIG .i files when running {{build_templates.py}}. This is probably most easily done by using argparse.    I also used "package name" instead of "module name", because I didn't know what "module" meant. But if you're keen on the latter, I'll be happy to change it. Just let me know, preferably with a brief explanation so I can add some information to the help string.
Answer: 33.0

User story: build_templates.py contains afw hard-coded in the module description as follows:  {code}  py::module mod("_$submodule_name$", "Python wrapper for afw _$submodule_name$ library");  {code}    That description seems rather circular in any case. Please consider pointing out the .h file that is being wrapped, instead, e.g.: "Python wrapper for code in lsst/.../x.h" (leaving out the path if it's too difficult to find).
Answer: 59.0

User story: "When attempting to reprocess some hsc data, I ran into a number of problems (one fixed in DM-8822). In this case, some of the python type definition in the obs_subaru {{Mapper.paf}} files are not valid: {{\_\_builtin\_\_.str}} doesn't exist on python3. Fortunately because of our use of futurize, we have {{builtins.str}}.    Although I don't plan to write it as part of this ticket, having a python2+3 validation system for the policy files would be good."
Answer: 8697.0

User story: "There is currently a dependency in Orchestration that waits for the Logger.py utility to complete before ending the Orchestration process.  This is an artifact of when Orchestration was used to send all Logging messages to a database for later analysis.   Since that mechanism is no longer being used, it will be removed from Orca.   "
Answer: 8363.0

User story: Write new plugin to run Pegasus via the orchestration utility "orca".    This will include changes in ctrl_execute to support command line options for templates, change in the template structure, support for command line references to DAG generators, and changes in the default pipeline prefix.    Need to consult with [~<USER> about how current Pegasus jobs are being executed.
Answer: 61493.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: While reprocessing some hsc data, I received the error given below. This is because python3 does not implicitly convert integers with leading zeros into octal. We should make the ctrl_pool code use an explicit octal int for the umask defined at the top of parallel.py, and then use a better formatting string where necessary.    {code}  SyntaxError: invalid token    File "<string>", line 1      import os; os.umask(002); import lsst.ctrl.pool.log; lsst.ctrl.pool.log.jobLog("singleFrame"); import lsst.pipe.drivers.singleFrameDriver; lsst.pipe.drivers.singleFrameDriver.SingleFrameDriverTask.parseAndRun();                            ^  SyntaxError: invalid token  Tue Jan  3 12:38:28 PST 2017  Done.  {code}
Answer: 194.0

User story: "Outline alert distribution system tests and provide scripts/how-tos for running the tests."
Answer: 99478.0

User story: "For the system parameters defined in DM-8819, implement (and write, if necessary) all tools for monitoring."
Answer: 341359.0

User story: "For testing the alert_stream prototype alert distribution system, we will want to monitor a number of different system parameters for the alert producers, consumers, and the Kafka broker(s).  If these are deployed with Docker containers, there are some existing tools that might be useful (Docker api + Python, cadvisor + backend storage) for some of these metrics.  For others (alert latency and throughput, e.g.), will have to write my own tool.    For this story, define the system parameters to measure and identify tool(s) for each. "
Answer: 80547.0

User story: "The build_templates script used to create template files used for pybind11 wrapping has a typo, adding an extra  {code}  namespace{  {code}  line."
Answer: 75.0

User story: "DMTN-017 was written as a LaTeX doc before technotes existed. This story is to port DMTN-017 to a PDF viewer template (DM-4602) for PDF documents that can be published with LSST the Docs."
Answer: 315370.0

User story: "Build listeners that react to OCS commands/events, and then communicate these datagrams to the Level One DMCS, and return ACKS as appropriate. This capability must be verified to work with the UI component specified in story DM-8813"
Answer: 2.0

User story: "A demonstration is planned on Nebula using the following individual processes; each on a virtual machine, talking to each other via messaging:  1) GUI representing OCS  2) DMCS  3) Archive Foreman  4) Archive Controller  5) Forwarder #1  6) Forwarder #2  7) Forwarder #3  8) An auditing service that writes system state changes into a time-series database.    The work reflected here will include fixing bugs found when exercising code, and making certain all message parameters are included - matching the message glossaries"
Answer: 1.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: "Build a front end for the data backbone representing how image data will be verified, then handed off to backbone organizational component. This component will:   1) provide a location for where a CCD image for a particular image_id/visit_id will be staged  2) after transfer, check for the existence of the CCD file AND run a checksum on the file to verify it is intact.    Note: This capability is not the expected final implementation for this part of the archiving component, but it is expected that the function it provides will be included in the final Backbone ingest area."
Answer: 9.0

User story: "Devise simple UI for calling individual OCS command entities with appropriate args."
Answer: 2.0

User story: "The diffimTests.py code in lsst-dm/diffimTests is in major need of refactoring."
Answer: 10380.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 the {{validate_base}} shift, {{validateDrp.py}} now requires a filter to be listed in the {{etc/metrics.yaml}} in order for it to run.  If no match is found, it bails out.    1. {{validateDrp.py}} should instead do "something reasonable".  Likely this means picking 'r' with a clear message that it is doing so.  2. {{validateDrp.py}} should successfully calculate all metrics that it can.  Failing on one metric or with the ocnfiguration of same should not lead to crashing:    {code}  [wmwv@lsst-dev01 tmp]$ validateDrp.py DATA/rerun/20161216  CameraMapper WARN: Calibration root directory not found: DATA/rerun/20161216/CALIB  CameraMapper WARN: Calibration root directory not found: DATA/rerun/20161216/CALIB  1077 sources in ccd 16  visit 903986  953 sources in ccd 24  visit 903988  1174 sources in ccd 18  visit 903990  1049 sources in ccd 23  visit 903986  1140 sources in ccd 25  visit 903990  932 sources in ccd 23  visit 903988  916 sources in ccd 17  visit 903988  778 sources in ccd 22  visit 903986  683 sources in ccd 100  visit 903986  938 sources in ccd 16  visit 903988  Photometric scatter (median) - SNR > 100.0 : 6.9 mmag  /nfs/home/wmwv/local/lsst/validate_drp/python/lsst/validate/drp/photerrmodel.py:74: RuntimeWarning: invalid value encountered in sqrt    return np.sqrt(sigmaSq)  Median value of the astrometric scatter - all magnitudes: 48.763 marcsec  Astrometric scatter (median) - snr > 100.0 : 9.6 marcsec  No stars found that are 199.0 arcmin--201.0 arcmin apart.  Traceback (most recent call last):    File "/nfs/home/wmwv/local/lsst/validate_drp/bin/validateDrp.py", line 95, in <module>      validate.run(args.repo, **kwargs)    File "/nfs/home/wmwv/local/lsst/validate_drp/python/lsst/validate/drp/validate.py", line 104, in run      **kwargs)    File "/nfs/home/wmwv/local/lsst/validate_drp/python/lsst/validate/drp/validate.py", line 242, in runOneFilter      job=job, linkedBlobs=linkedBlobs)    File "/nfs/home/wmwv/local/lsst/validate_drp/python/lsst/validate/drp/calcsrd/pf1.py", line 72, in __init__      PA2.get_spec(spec_name, filter_name=self.filter_name)    File "/nfs/home/wmwv/local/lsst/validate_base/python/lsst/validate/base/metric.py", line 346, in get_spec      name, filter_name, self.name))  RuntimeError: No PA2 spec found for name=stretch filter_name=HSC-I  {code}    The spirit of {{validate_drp}} is that it should just run on a data repo and produce reasonable input.  An additional level is providing specific comparison against  LSST SRD-level performance requirements or specific other performance levels.
Answer: 1905864.0

User story: "Based on DM-9844, officially deprecate DMTN-026 (which provided guidance for porting packages from SWIG to pybind11) now that the pybind11 port DM-8467 has been merged to master."
Answer: 105077.0

User story: "The script `build_templates.py` associated with dmtn-26 has some minor flake8 issues including an unused import, some variables that are set but never used, and PEP8 violations."
Answer: 102.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: Our codebase is full of template classes that are wrapped into a set of Python classes with suffixes derived from their template type (e.g. {{ImageF}}, {{ImageD}}, {{ImageU}}).    In some places, we've defined a module scoped dictionary with the un-suffixed name to relate these, e.g. {{afw.table.Key\["F"\] is afw.table.KeyF}}.    To enhance both the usuability of our Python interfaces and the ease of writing wrappers, we should:   - Add an Abstract Base Class for each of these template classes (https://docs.python.org/2/library/abc.html), making it appear as though all template instantiations inherit from the same class (in e.g. {{isinstance}} checks).   - Make these ABCs inherit from a custom metaclass (which in turn inherits from {{abc.ABCMeta}}) that allows dict-like access to the registered instantiations from both the string suffixes and the corresponding numpy types (e.g. {{numpy.float32}} for "F"), preserving the dict behavior mentioned above.   - Add a {{\_\_new\_\_}} method to each ABC that accepts a {{dtype}} argument and forwards all other arguments to the constructor of the wrapped template the {{dtype}} key points to.  In other words, make e.g. {{Image(bbox, dtype=numpy.float32)}} call {{ImageF(bbox)}}.  We could probably have the metaclass inject this automatically.    New users to the stack should be able to mostly get by without seeing the templated types at all - they'd only interact with the ABC.  And devs writing the Python wrappers for templated classes could define pure-Python extensions directly in the ABC instead of monkeypatching them into each wrapped template.    This issue covers adding the metaclass to utils and demonstrating its use in at least one template class wrapper.  Using it for other classes could be done on other pybind11 branches, as it strictly represents an addition to the API, and it could be useful to do it there as to get the monkeypatching-avoidance mentioned above.    In addition to the above, this ticket should include an implementation for the decorators described in RFC-270, which have significant code in common with the metaclass (as implemented currently) and a related purpose.  
Answer: 49072.0

User story: "Vincent Gatignol has written a POC which boot a Qserv cluster using heat:  https://github.com/vin-c/qserv/tree/heat-try    Qserv provisioning script should mmove to this technology.    A docker registry mirror should also be started using heat:  https://github.com/vin-c/qserv/tree/heat-docker-registry    See here for managing /etc/hosts"
Answer: 546905.0

User story: "The [shared stack version glob|https://github.com/lsst-dm/shared-stack/blob/master/shared_stack.py#L117] currently only brings in weeklies from 2016. Please update it to include 2017 too."
Answer: 728.0

User story: "If DM-8801 works out, then one option would be to use a difference image generated by the stack as the starting template. This ticket is to add that functionality. "
Answer: 75832.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 possible refinement to the DCR algorithm would be to calculate the best fit solution using a single DCR plane for the entire band (much like a standard coadd), and then fit for a delta off of that solution for each sub-band. This ticket will write and test that approach, but only merge if it looks promising."
Answer: 119325.0

User story: "Run the entire test dataset through processCcd (ISR, ImChar, and Calibrate) to arrive at a set of calexps, a source catalog, and a background model, and document the process."
Answer: 159618.0

User story: "This will most likely be a technical document. The goal is to walk somebody through the steps I have done for the HiTS dataset in a reproducible way. The documentation will be added to as this epic continues. At this stage, it will prepare me to automate the prototype AP pipeline once I successfully run each step."
Answer: 247733.0

User story: "This picks up where DM-7928 left off. With a dataset in place and the main images ingested, the calibration products (biases, flats, etc.) also need to be ingested. To verify they are in an accessible location, this ticket will be complete when one or more raw HiTS images is run through ISR with processCcd."
Answer: 45976.0

User story: "Currently, the diffim algorithms have been assessed using (elliptical, rotated) gaussian only PSFs. In this ticket we will add other more realistic ones (TBD, including Moffat (?), double gaussian (?), Kolmogorov (?)). We will also build a library of actual PSFs from DECam images to use in these simulations, as well as looking into using Galsim PSFs."
Answer: 15968.0

User story: "Implement forced-photometry and calculations of *actual* SNR for simulations, across all images (input science/template, and various diffims). Analysis of statistics of these measurements will enable detailed assessment of diffim algorithms on simulations."
Answer: 76051.0

User story: "This ticket covers the first component of necessary improvements to the diffim algorithm testing suite:     1. implement noiseless templates  2. implement static noise plane (sky-limited) with no shot noise from stars  3. ensure realistic stellar flux distribution  4. better plots of comparisons rather than violin plots (histograms, etc.)  "
Answer: 5.0

User story: "DM-8792 implements new parameters in the metrics app so that it can be used by the SQuaRE Bot, example:    https://bokeh.lsst.codes/metrics?job__ci_dataset=cfht&metric=AM1&window=weeks    Note that to deploy this to production DM-6330 is required."
Answer: 67632.0

User story: "Create a service (at api.lsst.codes) that will tell whether a metric value has changed more than some threshold between the last run and the one before it.    Then hook that service up to our chatbot, so that you can query it, and so that it will also periodically poll to determine whether it should complain if metric values have changed more than they should have.    Initial polling frequency is 8 hours, initial threshold is 1% change."
Answer: 68827.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: From my office desktop:  {code:java}  $ ping -i0.2 -c 10 -q lsst-dm-mac.lsst.org  PING lsst-dm-mac.lsst.org (140.252.32.108) 56(84) bytes of data.    --- lsst-dm-mac.lsst.org ping statistics ---  10 packets transmitted, 0 received, +10 errors, 100% packet loss, time 1869ms  pipe 10  $ ssh -vvv <EMAIL>  OpenSSH_7.2p2, OpenSSL 1.0.2j-fips  26 Sep 2016  debug1: Reading configuration data /home/<USER>.ssh/config  debug1: Reading configuration data /etc/ssh/ssh_config  debug1: /etc/ssh/ssh_config line 3: Applying options for *  debug1: auto-mux: Trying existing master  debug1: Control socket "/home/<USER>.ssh/master/<EMAIL>:22" does not exist  debug2: resolving "lsst-dm-mac.lsst.org" port 22  debug2: ssh_connect_direct: needpriv 0  debug1: Connecting to lsst-dm-mac.lsst.org [140.252.32.108] port 22.  debug2: fd 3 setting O_NONBLOCK  debug1: connect to address 140.252.32.108 port 22: No route to host  ...  {code}    From the production jenkins instance:  {code:java}  $ ssh -i /var/lib/jenkins/.ssh/id_rsa <EMAIL> -vvv  OpenSSH_6.6.1, OpenSSL 1.0.1e-fips 11 Feb 2013  debug1: Reading configuration data /etc/ssh/ssh_config  debug1: /etc/ssh/ssh_config line 56: Applying options for *  debug2: ssh_connect: needpriv 0  debug1: Connecting to lsst-dm-mac.lsst.org [140.252.32.108] port 22.  debug1: connect to address 140.252.32.108 port 22: Connection timed out  ssh: connect to host lsst-dm-mac.lsst.org port 22: Connection timed out  {code}
Answer: 47840.0

User story: "Checking removal of hipchat validator post-function"
Answer: 173.0

User story: "monthly test of tickets related to UI changes and bug fixes   file tickets with steps to reproduce the bugs"
Answer: 229681.0

User story: "monthly test of tickets related to UI changes and bug fixes   file tickets with steps to reproduce the bugs    DM-10065 needs to be thoroughly tested. "
Answer: 185746.0

User story: "monthly test of tickets related to UI changes and bug fixes  File tickets with steps to reproduce the bugs    3/1/2017: Tested DM-8578.  "
Answer: 127343.0

User story: "monthly test of tickets related to UI changes and bug fixes.  file tickets with steps to reproduce the bug.      2/1/2017 Reviewed DM-8660: Unit test for Geom.  2/2/2017 Reviewed DM-8670: Light Curve UI (wise data).  2/3/2017 Reviewed DM-7780: FlipXYTest  2/7/2017 Reviewed DM-9247: All Sky catalog query  2/8/2017 Reviewed DM-9248: All Sky mode  2/9/2017 Reviewed DM-8661: Unit Test for ImageData  2/12/2017 Reviewed DM-7946: UnitTestForCentralPoint  2/15/2017 Reviewed DM-7780: FlipXYTest  2/16/2017 Reviewed DM-8839: Image header unit test  2/17/2017 Reviewed DM-9470: Compass layout  2/21/2017 Reviewed DM-8845: UnitTest for ImagePlot class  "
Answer: 96631.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: "Test all the tickets affecting UI when merged into dev. File Jira tickets  with the steps to duplicate the bugs.      Jan. 3 2017 Tested https://jira.lsstcorp.org/browse/DM-8548 and found the bug. See comment in the ticket.  Jan. 3 2017 Reviewed DM-8648 in git hub.   Jan. 4, 2017 Tested/reviewed DM-8548.   Jan. 9, 2017 Found a bug and issued ticket DM-8957:Original plot Inconsistent does not abort  Jan. 12, 2017 Reviewed DM-8957: Original plot does not abort and over writes active plot  Jan. 12, 2017 Reviewed DM-8049: Crop related classes need to be refactored  Jan. 17, 2017 Reviewed DM-7827: Create LSST File group processor for packaging (download the LSST images)  Jan. 20, 23, 2017 Reviewed DM-8668: LC period finder  Jan. 31, 2017 Tested DM-8985: mask"
Answer: 57971.0

User story: "There is one skipped test in {{testSourceTable.py}}: {{testPickle}}. This segfaults, likely when a source catalog is pickled. Fix this.     Should all kinds of catalog be pickleable? If so, make sure all are being tested."
Answer: 6242.0

User story: "Jointcal produces a number of compile-time warnings (which one can miss without the scons fix described in RFC-246). We should clean these up, which might be helped by compiling with both gcc and clang, and comparing their messages. It may be best to do this after we've dealt with other problems (like the boost pointer memory management), as that may take care of some of the warnings along the way. On the other hand, there's quite a bit of low-hanging fruit in the form of variables that are defined but never used."
Answer: 240166.0

User story: "The executables that come with cfitsio (in particular {{fpack}} and {{funpack}}) are useful, and should be installed along with cfitsio."
Answer: 924060.0

User story: "This ticket captures work done to publish the display_firefly backend for afw.display to eups, including researching and learning the steps to do it.    * tag the ws4py and firefly_client dependencies appropriately  * rebuild display_firefly using Jenkins  * publish display_firefly using Jenkins    enabling:  {code}  export EUPS_PKGROOT=https://sw.lsstcorp.org/eupspkg  eups distrib list display_firefly # returns version to use in next line  eups distrib install display_firefly master-g0a33da8b30+2  {code}"
Answer: 1.0

User story: "Review RFC-252 and draft LDM-493 document."
Answer: 96419.0

User story: "Per discussion on DM-8636: provide a fleshed-out set of topic templates. This goes well beyond a list of headings to include a detailed discussion of the contents of each section, mock-ups of auto-generated content, etc.    Will base this on fully filled out examples made by hand, in DM-8717.    "
Answer: 144651.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: "Current Firefly has implemented many DS9 region features, like allowing users to overlay DS9 region on an image, overlay a marker, a foot print, etc. There are still some features Firefly only implemented in the front end. This ticket requires to make a table with the following columns:    DS9 region features  Firefly region features (with limitations)  Firefly region features the front end supports  Firefly region features the server supports    This table needs to include the information provided by the related tickets below.   "
Answer: 162453.0

User story: "We have some experience in making Jupyter widgets after writing two. We need to have a design discussion and come up with a guideline for writing more widgets. This will enable other developers to work in this area too.     required members: [~<USER> [~<USER> [~<USER> [~<USER>     11/28/2017 TG   Note regarding DialogRootContainer:    To avoid interference with notebook keyboard shortcuts, the recommended way register the element that might be a target of the input events with Jupyter.keyboard_manager (IPython.keyboard_manager for backward compatibility).  How can we make sure that we call  Jupyter.keyboard_manager .register_events(dialogRootEl) one time only and that the dialog root container is already attached by the time register_events is called.     jupyter-widgets  take care of [registering the widget](https://github.com/jupyter-widgets/ipywidgets/blob/34091c58f5f21a947503031d48f623a23fa58b86/widgetsnbextension/src/extension.js#L130), (the descendant elements of the output cell). [register_events](https://github.com/jupyter/notebook/blob/ee419c0a1714b45865a314bca3f941b6bf4485cf/notebook/static/notebook/js/keyboardmanager.js#L238) function is automatically turning on and off the keyboard manager handling. The dialogs are not widget descendants and are not taken care of.      More info in [here](https://github.com/Caltech-IPAC/firefly_widgets/pull/7)."
Answer: 1144895.0

User story: "After some iteration with [~<USER>, [~<USER>, and [~<USER>, want to modify the content from how it was in the earlier version of the sdp repo into the new Task template so it's in the form we want to be useable by developers etc. in the future.    Will include a description of config parameters, task runners, argument parsers, etc that are relevant for CL Tasks — and then try to abstract out the common features."
Answer: 145601.0

User story: "In Swig `MatchList` objects are (un)pickled by creating a `Catalog` of the contained `Record` type and the (un)pickling that.  With pybind11 this is not possible because `MatchList` is just a Python `list` of `Match` objects. Pickling them individually (via the same route) does not make much sense.  It is unclear if this pickling support is actually needed anywhere outside of {{testSourceMatch.py}} where it is currently disabled (as of DM-8415).  This ticket aims to either fix or permanently remove this functionality when the need for it becomes clear."
Answer: 80880.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: "Implements RFC-261. Update DM C++ Style Guide (primarily section 6) to enable automatic code layout with {{clang-format}}.  This involves adding a version controlled LSST {{clang-format}} style that is as much as possible compliant with the current layout rules. And subsequently removing or modifying the existing layout rules to be compliant with the output created by {{clang-format}} using this style.    The intended end result is that users can simply run {{clang-format}} (with the LSST provided style) to automatically fix all C++ code layout issues.    Users are still free to not use {{clang-format}} as long as the output looks the same."
Answer: 79019.0

User story: "Implements RFC-260."
Answer: 45993.0

User story: "This ticket covers merging the F16 work on validate_drp (e.g., refactoring to use {{validate_base}}) to master, and updating the Jenkins job (including post-qa v1.2.2) to submit {{validate_drp}} job data to SQUASH."
Answer: 4344.0

User story: "This is for the implementation of RFC-262: the re-organization of the {{/datasets}} directory to facilitate closing of RFC-257."
Answer: 52560.0

User story: "we need to have a chart type that could have multiple scatter/line plotted in it.    The issues that need to be resolved in the future tickets:  * Color input field  * Color bar display when color map is specified for the 3rd column/expression. (There is a number of issues with display: two tick sets, no update when color scale changes. We also need to make sure it's on the opposite side of yaxis.)  * Size map scaling: to make sure all points are visible, we need to make sure point size in pixels falls into the valid range since the size represents the values (4px and up, otherwise the points will be invisible, also upper size limit px)  * Axes scale ratio: in addition to xyratio, which is now aspect ratio of the chart area, users want to control scale ratio of the axes. This ratio should be preserved when zooming or doing other plot interactions.  https://github.com/Caltech-IPAC/firefly/pull/398"
Answer: 270263.0

User story: steps to repeat in Firefly app:  # do a catalog search   # there will be coverage and a another tab with the same label as the catalog tab    I think the system mistakingly thinks that the catalog is image meta data    also fixed:  DM-8602: Cols link does not work when launched from "Charts" popup.  -Ticket will be closed.  when no image available, remove fits data tabs  drop down menu when there’s nothing in the results after the last component has been removed.  DM-8206: Coverage is not shown if active table set before table loads   
Answer: 32763.0

User story: "steps to repeat in Firefly app:  # do a catalog search to bring up a scatter plot  # use rubber band to zoom in a few times  # bring up option panel by clicking on 'gear' option  # change the X/Y ratio, then click on 'apply' button    You will see that the XY scatter plot reset back to have all the data plotted.  I think we should keep the current zoom level after the ratio change."
Answer: 84271.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: "makeCoaddTempExp's lowest-level work method {{createTempExp}} interacts with  disk via the Butler.  When building coadds in Spark, or example, this required us to re-write an implementation of {{createTempExp}} instead of reusing the stack. {{createTempExp}} currently takes a list of dataRefs corresponding to the calexps that overlap the patch for a particular visit.  These reads could be pushed to the higher-level calling method at the expense of memory.      Making {{createTempExp}} more reusable would require either:  a) Making {{createTempExp}} able to accept either a list of dataRefs or just a list of calexps. This actually appears to be the intent of the docstring writer). <-- naively, I suspect this will win.  b) Holding 4 full calexps in memory (or 4 partial calexps in memory)  c) Easily reproducible container that can interact with the disk, database etc...    This ticket involve investigating the computational feasibility, and implementing  best option.   "
Answer: 1108627.0

User story: "Once RFC-266 is accepted, {{/gpfs/fs0/scratch/pprice/UH-Cosmos/*.fits}} needs to be copied into {{/datasets/hsc/raw/cosmos}} and ingested into {{/datasets/hsc/repo}}."
Answer: 45988.0

User story: "For chatops to work well, we want to have a coherent and documented API.    We do not want to be in the business of writing our logic in Coffeescript.  So we want to have an endpoint (strawman: https://api.lsst.codes) and a set of metadata that any service behind there must return.  Then the front end of the chatbot is pretty much reduced to poking the API and reformatting the reply."
Answer: 5.0

User story: "Due to time constraints, {{Point2DList}} is originally being implemented as a C++-only class emulating STL lists. A python interface should be added when feasible.    Using pybind11, it would be relatively easy to make {{Point2DList}} behave similarly to a standard Python {{list}}; conversely, using swig to wrap the class's very C++-like interface would be difficult and is best avoided."
Answer: 91036.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: {code}  tests/testMeasureImage.py    /home/jenkins-slave/workspace/stack-os-matrix/label/centos-7/python/py2/lsstsw/miniconda/lib/python2.7/site-packages/astropy/config/configuration.py:687: ConfigurationMissingWarning: Configuration defaults will be used due to OSError:Could not find unix home directory to search for astropy config dir on None    warn(ConfigurationMissingWarning(msg))  Traceback (most recent call last):    File "tests/testMeasureImage.py", line 38, in <module>      import lsst.meas.modelfit.display    File "/home/jenkins-slave/workspace/stack-os-matrix/label/centos-7/python/py2/lsstsw/build/meas_modelfit/python/lsst/meas/modelfit/display/__init__.py", line 1, in <module>      from .densityPlot import *    File "/home/jenkins-slave/workspace/stack-os-matrix/label/centos-7/python/py2/lsstsw/build/meas_modelfit/python/lsst/meas/modelfit/display/densityPlot.py", line 63, in <module>      class HistogramLayer(object):    File "/home/jenkins-slave/workspace/stack-os-matrix/label/centos-7/python/py2/lsstsw/build/meas_modelfit/python/lsst/meas/modelfit/display/densityPlot.py", line 80, in HistogramLayer      defaults2d = dict(cmap=matplotlib.cm.Blues, vmin=0.0, interpolation='nearest')  AttributeError: 'module' object has no attribute 'cm'  -----------------------------------------------------  {code}
Answer: 33.0

User story: "Moved here from DM-6297 because it depends on DM-8674 to be merged."
Answer: 4286.0

User story: "In preparation for a new multi-color deblender the API for {{lsst.meas.deblender.baseline.deblend}} needs to be modified to (optionally) accept lists for the {{footprint}}, {{maskedImage}}, {{psf}}, and {{psffwhm}} parameters.    The {{PerParent}} and {{PerPeak}} classes will also be modified to organize parent and peak objects in different colors, and the underlying code will be modified as needed to use the new objects.    When this ticket is completed there should be no difference in the behavior of {{lsst.meas.deblender.baseline.deblend}} from using the current deblender API (other than the new/modified classes), but this will be the last ticket before a long-lived branch is created to store work on the new deblender."
Answer: 31647.0

User story: "Use pybind 11 to wrap the SpanSets class."
Answer: 32987.0

User story: "The {{ConvolvedFluxPlugin}} currently refuses to measure a source if the target seeing is smaller than the actual seeing.  This was a bad choice, as having a potentially-incorrect measurement is more useful than having nothing at all (so long as there's a flag indicating the problem)."
Answer: 1601.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: When processing data from the community pipeline instcal files, the ccdnum that the butler uses, and which is used to create a detector object, is not the same as the ccd number specified in the original image headers. For example,    {code}  >>> calexp = b.get("calexp", visit=406295, ccdnum=10)  >>> calexp.getDetector().getId()  10  >>> calexp.getDetector().getName()  'S22'  >>> calexp.getMetadata().toDict()['DETNAME']  'S22'  {code}    But if I check the headers, I get  {code}  >>> calexp.getMetadata().toDict()['CCDNUM']  11  >>> calexp.getMetadata().toDict()['DETECTOR']  'S3-164_107419-16-2'  {code}  where S3-164_107419-16-2 is the ID for the detector S23 aka ccdnum=11 ([table of detector IDs|http://www.ctio.noao.edu/noao/sites/default/files/instruments/Controllers/MONSOON/Technical_Documents/DECAM/Hardware/DESDOC_5998-v1_CCD_Names.txt]).    The original source of this confusion seems to be in the decam policy entry for instcal, which specifies:  {code}  template:    "%(visit)07d/instcal%(visit)07d.fits.fz[%(ccdnum)d]"  {code}  compared to the raw format, which is  {code}  template:    "%(date)s/%(filter)s/decam%(visit)07d.fits.fz[%(hdu)d]"  {code}    It is likely necessary for instcal ingest to duplicate the behavior of the raw file ingest of MEF files, to prevent this conflation of HDU numbers with CCD Ids. 
Answer: 34673.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 story is to implement discovery of Old Butler parent repositories by following the _parent symlink as described below. There is a little special case behavior to implement too, in the case of an {{outputRoot}} input argument for an initialized {{CameraMapper}}    h1. Parent Discovery With New Butler Repositories  It is easy to create the list of parent repositories with New Butler repositories. Each repository has a RepositoryCfg file which has a parent list. Elements of the parent list can be either URI to the repository root or cfgRoot of parent RepositoryCfg files, or can be a RepositoryCfg repr string that describes a parent repository. The Repr string typically contains overrides or additions to a RepositoryCfg that exists elsewhere at root or repoCfg.    To create the list, Butler need simply load the RepositoryCfg, get its parents, load those, and so on. This is already implemented.    h2. Parent Discovery With Old Butler Repositories  Generating a list of parents of an Old Butler repository is usually easy as well: if a repository is determined to be an Old Butler repository (it is probably enough to say it is Old if the repository does not have a RepositoryCfg.yaml file) then it can be searched for a _parent symlink. If one is found, add that repo to be created as a parent. It should also be searched for a _parent symlink, and so on until a repo without a _parent symlink is found.    h1. Handling outputRoot  There is one known special case where following the _parent symlinks will sometimes not work, because the _parent symlink is created during CameraMapper init, after repository discovery.    This occurs when the CameraMapper is instantiated by Butler and an outputRoot input argument is passed in for the CameraMapper. Butler builds its list of input and output repositories early during Butler init, this includes finding Old Butler input repositories by following _parent symlinks. Butler then initializes a Repository class for each repository, which in turn will init the CameraMapper (if it’s not already an instance). During CameraMapper init, outputRoot gets used as root, and a new _parent symlink is created in the new root linking to the original root. That is to say, root becomes ``_parent`` and outputRoot becomes root. But because this happens during CameraMapper init, it happens too late to be discovered by Butler’s repository-discovery _parent search mechanism.    To solve this specific use case, if mapperArgs contains ‘outputRoot’ then butler will create 2 RepositoryCfgs. root will be an input repository, and outputRoot will be a read-write output repository."
Answer: 191320.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: "Child Repositories need to be able to perform lookups in the sqlite Registry of one or more parent repositories.    Old Butler repositories used to find the registry by looking in the current repo, then following the _parent symlink until a registry was found.    New Butler repositories do not access their parent repositories directly.    The shorter term fix is for butler to pass all of a repo’s parent sqlite registries to a repo (via an ordered list of registry objects, each of which is of course a reference). The butler will use that list, whose order will be 1. a local sqlite registry (if present), 2. all the parent registries in order, and 3. use a PosixRegisry on the local repository. In the case of no results found when searching sqlite registries, butler will verify that the tables specified for the policy are in the registry. If they are, butler will return ‘no results’. If the tables are not in that registry, butler will look in the next registry.    (The better/longer term fix is “output registries”, where butler updates a repo-local registry when writing a dataset to a repo, and never does lookups in parent registries.)  "
Answer: 128021.0

User story: "Currently we don't have options for asymmetric errors. Need to be able to input asymmetric errors in options panel.    Also might need options for error bar look, like whiskers length."
Answer: 134910.0

User story: "The light curve and the image meta data view have reveal some weaknesses in our expanded view approach. It is going to create user confusion.     To fix the we need to do the follow:    * When expanded the image meta data and light curve views should just expanded and not use the general expanded view.  * The general expanded view should be reserved only for the tri-view user loaded images and the API  * The sort needs to be adjusted to handle this and the concept of the images being expanded needs to be tweaked.  * Bug: at times there are two expanded icons appear, on the toolbar and on the image  * Bug: When match is on then image are expanded and then collapsed the images are no longer centered correctly."
Answer: 36034.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: "For Calibration Mappings in CameraMapper, in New Butler repositories, the Calib Mapping needs access to another registry.     For this, implement Repository Relationships.    * Butler needs a way to “relate” registries from 2 input repositories so that metadata lookup can be done in one and then completed in the other.  *The relationship between the calib repository and the raw repository’s registry must be recorded in the persisted cfg of the output repository. (It must be in the output repository’s cfg because the relationship does not affect the contents of any of the input repositories, but it does affect the contents of the output repo, so that is where it should be stored).  * A typical use case example is for a repo containing Raw images and a repo containing Calib images: For a given exposure number, look up the exposure date+time in the raw registry, and then in the Calib repo use that date+time to find the dataId for the Calib image that was valid for that date+time.  "
Answer: 237276.0

User story: "Transfer Feb2013 COSMOS data to /datasets/decam/ and butlerize it.      Run some processing to verify the butler repo is useable.  "
Answer: 54473.0

User story: "The production jenkins instance is running {{2.19.2}}.  {{2.19.3}} was a critical security release and there are a number of minor bugfixes in {{2.19.4}} that may be effecting our end users, such as https://issues.jenkins-ci.org/browse/JENKINS-10912."
Answer: 77.0

User story: Request from [~<USER> via slack: "update CI to generate it using following command `./1_build-image.sh -CD`".    As jenkins is currently using a fork of the qserv docker scripts with some minor modifications, testing will be required to migrate to the qserv master branch.  
Answer: 4580.0

User story: "Currently the parameter {{assignStrayFlux}} is not implemented in {{lsst.meas.deblender.baseline.deblend}}, however the parameter {{findStrayFLux}} sets the {{ASSIGN_STRY_FLUX}} bit of the stray flux options. It would make more sense to deprecate {{findStrayFlux}} and remove it in a future release and instead use {{assignStrayFlux}} as it was likely intended to be used."
Answer: 36142.0

User story: meas_algorithms has several "naked" matplotlib imports that happen at the top level, and thus prevent anything that imports meas_algorithms from subsequently setting the backend. A simple fix is to move those imports into the functions where matplotlib is used, so they only occur if matplotlib is run, and preferably wrap them in try:except and log.warn on any errors.    This is a stop-gap until 5790 is properly dealt with.
Answer: 6032.0

User story: "This issue just exists to track progress. Work will be done on DM-8467."
Answer: 1906.0

User story: "Wrapping {{testSourceTable.py}} with pybind11 was part of DM-6297 but didn't really fit there."
Answer: 10342.0

User story: "I would like to migrate the SDSS DR9 HTM indexed reference catalog from Colin's scratch space to the datasets area so I can include it in the collection of HTM catalogs available."
Answer: 76172.0