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: "The DCR matched template code has dependencies on sims packages that might be replaced with functionality from core software. Once DM-9615 is completed, some of these (such as the bandpass) may be obtained from the relevant obs package."
Answer: 308225.0

User story: "The C\+\+11 containers {{unordered_set}} and {{unordered_map}} only work with hashable types, a concept that was itself added in C\+\+11. Most afw value types were implemented before we adopted C\+\+11, and therefore do not have a specialization of {{std::hash}}. Implementing {{std::hash}} will also make it easier to implement DM-7621, as the [C\+\+11 requirements for hash|http://en.cppreference.com/w/cpp/utility/hash] are stricter than the [Python requirements|https://docs.python.org/3/reference/datamodel.html#object.__hash__].    In most cases, {{hash}} can be quickly implemented by adopting a modified version of the algorithm from Effective Java, Item 9; the only difference between the C\+\+ requirements and the Java ones is that hash functions are implied to be strictly deterministic before C\+\+14, but the EffJ algorithm meets that criterion if the hash for all member variables does.    The classes covered by this ticket are a subset (possibly taken from DM-9936) of the following types:  * {{afw::cameraGeom::CameraPoint}}  * {{afw::cameraGeom::CameraSys}}  * {{afw::cameraGeom::CameraSysPrefix}}  * {{afw::cameraGeom::Orientation}}  * {{afw::coord::Coord}} and its subclasses  * {{afw::coord::Observatory}}  * {{afw::coord::Weather}}  * {{afw::detection::Threshold}}  * {{afw::geom::Angle}}  * {{afw::geom::AngleUnit}}  * {{afw::geom::Box}}  * {{afw::geom::CoordinateBase}} and its subclasses  * {{afw::geom::CoordinateExpr}}  * {{afw::geom::Span}}  * {{afw::geom::SpherePoint}}  * {{afw::geom::polygon::Polygon}}  * {{afw::image::Calib}}  * {{afw::image::Color}}  * {{afw::image::DefectBase}}  * {{afw::image::Filter}}  * {{afw::image::FilterProperty}}  * {{afw::math::FitResults}}  * {{afw::math::Function}} and its subclasses  * {{afw::math::MaskedVector}}  * {{afw::math::Statistics}}  * {{afw::table::BaseRecord}} and its subclasses  * {{afw::table::ConstFunctorKey}}  * {{afw::table::FieldBase}} and its subclasses  * {{afw::table::InputFunctorKey}} and its subclasses  * {{afw::table::KeyBase}} and its subclasses  * {{afw::table::Match}}  * {{afw::table::OutputFunctorKey}} and its subclasses  * {{afw::table::ReferenceFunctorKey}}  * {{afw::table::SchemaItem}}  * {{afw::table::io::Persistable}}  * {{afw::table::io::PersistableFacade}}"
Answer: 852781.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: "C++11 methods that are declared {{noexcept}} enable compilers to streamline code that calls them, in some cases (e.g., STL code) unlocking more efficient algorithms that would be unsafe with throwing methods. These changes are most useful for low-level types, whose methods are also the most likely to be provably non-throwing.    This ticket shall add the {{noexcept}} specifier to any methods that are guaranteed not to throw and are unlikely to be modified to throw exceptions in the future (e.g., trivial getters will usually qualify, but methods for which some inputs are invalid will not even if the existing code performs no input validation). Particular attention shall be paid to constructors, assignment operators, and {{std::swap}} implementations, as these are the methods where {{noexcept}} provides the biggest gains.    The classes covered by this ticket are (based on assumed simplicity, and therefore subject to change):  * {{afw::cameraGeom::CameraPoint}}  * {{afw::cameraGeom::CameraSys}}  * {{afw::cameraGeom::CameraSysPrefix}}  * {{afw::cameraGeom::Orientation}}  * {{afw::coord::Coord}} and its subclasses  * {{afw::coord::Observatory}}  * {{afw::coord::Weather}}  * {{afw::detection::Threshold}}  * {{afw::geom::Angle}}  * {{afw::geom::AngleUnit}}  * {{afw::geom::Box}}  * {{afw::geom::CoordinateBase}} and its subclasses  * {{afw::geom::CoordinateExpr}}  * {{afw::geom::Span}}  * {{afw::geom::SpherePoint}}  * {{afw::geom::polygon::Polygon}}  * {{afw::image::Calib}}  * {{afw::image::Color}}  * {{afw::image::DefectBase}}  * {{afw::image::Filter}}  * {{afw::image::FilterProperty}}  * {{afw::math::FitResults}}  * {{afw::math::Function}} and its subclasses  * {{afw::math::MaskedVector}}  * {{afw::math::Statistics}}  * {{afw::table::BaseRecord}} and its subclasses  * {{afw::table::ConstFunctorKey}}  * {{afw::table::FieldBase}} and its subclasses  * {{afw::table::InputFunctorKey}} and its subclasses  * {{afw::table::KeyBase}} and its subclasses  * {{afw::table::Match}}  * {{afw::table::OutputFunctorKey}} and its subclasses  * {{afw::table::ReferenceFunctorKey}}  * {{afw::table::SchemaItem}}  * {{afw::table::io::Persistable}}  * {{afw::table::io::PersistableFacade}}"
Answer: 675428.0

User story: Recent API changes in DM-8686 broke the Pegasus DAX-generating scripts. Recover from the changes and make it work again.     First error:   {code:java}    File "ciHsc/generateDax.py", line 179, in generateDax      mapper = HscMapper(root=inputRepo, outputRoot=outPath)    File "/home/<USER>lsstsw/stack/Linux64/obs_subaru/13.0-14-gb43a883+1/python/lsst/obs/hsc/hscMapper.py", line 31, in __init__      super(HscMapper, self).__init__(policy, policyFile.getRepositoryPath(), **kwargs)  TypeError: __init__() got an unexpected keyword argument 'outputRoot'  {code}    Also, DM-9438 switched the reference catalog to use the LSST HTM format. Do the necessary changes to make the dax run again. 
Answer: 10071.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: "C++11 allows programmers with more control over how classes are inherited and how methods are overridden. These features allow for safer code, particularly when applied to fundamental data types. They can be retrofitted onto existing code fairly mechanically.    This ticket includes the following changes:  * Declare standalone types {{final}} (do not do this for any type that's part of an inheritance hierarchy, even if it appears to be intended as a leaf class).  * Declare methods {{final}} only if their existing documentation forbids overriding them.  * Declare overriding methods {{override}}.    The classes covered by this ticket are (based on assumed simplicity, and therefore subject to change):  * {{afw::cameraGeom::CameraPoint}}  * {{afw::cameraGeom::CameraSys}}  * {{afw::cameraGeom::CameraSysPrefix}}  * {{afw::cameraGeom::Orientation}}  * {{afw::coord::Coord}} and its subclasses  * {{afw::coord::Observatory}}  * {{afw::coord::Weather}}  * {{afw::detection::Threshold}}  * {{afw::geom::Angle}}  * {{afw::geom::AngleUnit}}  * {{afw::geom::Box}}  * {{afw::geom::CoordinateBase}} and its subclasses  * {{afw::geom::CoordinateExpr}}  * {{afw::geom::Span}}  * {{afw::geom::SpherePoint}}  * {{afw::geom::polygon::Polygon}}  * {{afw::image::Calib}}  * {{afw::image::Color}}  * {{afw::image::DefectBase}}  * {{afw::image::Filter}}  * {{afw::image::FilterProperty}}  * {{afw::math::FitResults}}  * {{afw::math::Function}} and its subclasses  * {{afw::math::MaskedVector}}  * {{afw::math::Statistics}}  * {{afw::table::BaseRecord}} and its subclasses  * {{afw::table::ConstFunctorKey}}  * {{afw::table::FieldBase}} and its subclasses  * {{afw::table::InputFunctorKey}} and its subclasses  * {{afw::table::KeyBase}} and its subclasses  * {{afw::table::Match}}  * {{afw::table::OutputFunctorKey}} and its subclasses  * {{afw::table::ReferenceFunctorKey}}  * {{afw::table::SchemaItem}}  * {{afw::table::io::Persistable}}  * {{afw::table::io::PersistableFacade}}"
Answer: 755901.0

User story: "RFC-209 requires that all classes make use of explicit copy-constructors and assignment operators, as enabled by C++11. We have a large body of legacy code, particularly in {{afw}}, that does not follow this guideline.    All {{afw}} classes should be given explicit (often default) default constructors, copy-constructors, and assignment operators, and equivalent C\+\+98 tricks like private undefined constructors should be removed. Per Effective Modern C\+\+, private undefined constructors shall be replaced with _public_ deleted constructors.    For consistency's sake, the {{default}} statement shall be included in the header file if most existing constructors are inline and in the implementation file otherwise. {{delete}} shall always be given in the header, since the unavailability of a method is part of the API."
Answer: 451098.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: "LSST project standard is to use Calibri for documents. This is a Microsoft font and not available on Travis, or on Linux, or on systems that do not have a Microsoft Office installation. The current latex class uses a default helvetica-like font. Switch to OpenSans and also support xelatex."
Answer: 270.0

User story: "ImageServ v1 API should support the following IVOA recommendations:     1. Server-side Operations for Data Access (SODA v1.0) (include determination of SODA ID representation)  2. Data Access Layer Interface (DAL v1.1)     First implementation on top of existing imgserv code; supports  existing functionality of imgserv through new API style.    Follow these guidance principles:      a) embrace and extend IVOA recommendations, e.g. supporting data representations in both XML(translated) and JSON (native w/schema validation).  b) develop ImageServ v1 API using this new framework    Cutout requirements per SUIT team:  https://confluence.lsstcorp.org/pages/viewpage.action?pageId=54856011"
Answer: 286759.0

User story: "Currently we use a somewhat randomly selected version of upstream pybind11 master (since none of the upstream releases had the bugfixes we needed).  Now that v2.1.0 has been released, we should upgrade to it.  From that point on we should aim to track tagged release versions."
Answer: 602.0

User story: "I am exhausting the memory using meas_mosaic during read.  Usually we think of meas_mosaic as using too much memory during calculation, but I'm hitting the limit during read:  {code}  Mosaic INFO: Reading catalogs ...  Mosaic INFO: Use 28 cores for reading source catalog  slurmstepd: error: Job 43298 exceeded memory limit (150023884 > 131072000), being killed  slurmstepd: error: Exceeded job memory limit  slurmstepd: error: *** JOB 43298 ON perseus-r5c4n2 CANCELLED AT 2017-03-23T22:32:38 ***  {code}  "
Answer: 8732.0

User story: "Please make   {code}  /datasets/comCam/raw/BNL-test/test/LCA-11021_RTM/LCA-11021_RTM-004_ETU2-Dev/4672D  {code}  immutable"
Answer: 88997.0

User story: "Publish dochub-prototype HTML to {{www.lsst.io}} via LSST the Docs."
Answer: 5760.0

User story: "Via DM-9879 we've found some useful {{exclude}} paths for the flake8 configuration:    {code}  [flake8]  max-line-length = 79  ignore = E133, E226, E228, N802, N803  exclude =    bin,    doc,    **/*/__init__.py,    **/*/version.py,    tests/.tests/  {code}    This can be added to the Python Style Guide at https://developer.lsst.io/coding/python_style_guide.html#flake8-configuration-files"
Answer: 1745.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: <USER>hit some test failures because of a broken sqlite3 module. He writes:  {quote}  At the beginning of  daf_persistence/13.0-2-g7f7a1db+1/python/lsst/daf/persistence/registries.py ,  "haveSqlite3" was set to False because "import sqlite3" failed.    At line 77, the IF block was skipped because "haveSqlite3" is False.  The execution continued to reach line 89,  and PosixRegistry(root="filename.sqlite3") was created.    I think one of the following modifications is desirable:    1. Raise error when "not haveSqlite3 and re.match(r'.*\.sqlite3', location)"    before line 77.    2. Alter os.path.exists(location) to os.path.isdir(location) at line 88.  {quote}    Line numbers refer to the HSC master branch, at https://github.com/HyperSuprime-Cam/daf_persistence
Answer: 46595.0

User story: "In the DCR template generation code, when exposures are warped that operation is currently performed in-place, over-writing the array values and wcs info. This could potentially lead to bugs down the road, so either the implementation should be made more robust or checks should be put in place to verify that it is safe."
Answer: 697375.0

User story: "DM SQuaRE requests access to some nova-scheduler filter-scheduler options. At a minimum {{DifferentHostFilter}} and {{SameHostFilter}}. Ideally {{ServerGroupAffinityFilter}} and {{ServerGroupAntiAffinityFilter}} also. There are are other useful filter-scheduler options but these solve an immediate problem. There is no way to ensure separate or same hosts/Cells/AZ/etc for systems. This allows us to ensure either separate or same hosts based on the software system requirements.    https://docs.openstack.org/mitaka/config-reference/compute/scheduler.html  "
Answer: 1539683.0

User story: "The previous lfr.lsst.codes Nebula Instance became read-only then on hard restart went into ERROR status. It's no longer recoverable. Rebuild and snapshot lfr.lsst.codes."
Answer: 17165.0

User story: "The ability for non-admins to view their own recently deleted instances fills a some requirements for DM SQuaRE to increase usage of Nebula. There is already a Blueprint filed with OpenStack[0|https://blueprints.launchpad.net/nova/+spec/non-admin-check-own-deleted-instances].    This should be discussed at the next OpenStack conference. LSST SQRE advocates for 1) A policy attribute for making deleted instances visible to users. 2) The implementation does not have to be a complete list. It can be soft deletes that are still in the database.    There is already support for this for admins in the OpenStack CLI. Through {{openstack server list --deleted}} and/or {{openstack server list --status DELETED}}.  "
Answer: 1539720.0

User story: "  Update documentation    https://developer.lsst.io/services/datasets.html     for use of JIRA in locking down /datasets"
Answer: 1539748.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 the   1. [ ] validation_data_cfht  2. [ ] validation-data_decam  3. [ ] validation_data_hsc    repositories with output from release 13.0 processing.    4. [ ] Tag each repo with '13.0'"
Answer: 637689.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: Using daf_persistence 13.0-5-g87674b4 (w_2017_12) in Princeton I get an error; I cannot test this at lsst-dev as w_2017_11 doesn't seem to be installed.  The paths are correct for lsst-dev, however, so you should be able to repeat this there.    The error is:  {code}  import lsst.daf.persistence as dafPersist  butler = dafPersist.Butler("/datasets/comCam/repo")  r = butler.get('raw', run='4672D', ccd='S00', visit=261576101)    ---------------------------------------------------------------------------  NoResults                                   Traceback (most recent call last)    <ipython-input-9-ac5a11c0f585> in <module>()        1 butler = dafPersist.Butler("/tigress/HSC/LSST/comCam")  ----> 2 r = butler.get('raw', run='4672D', ccd='S00', visit=261576101)        /tigress/HSC/LSST/stack/Linux64/daf_persistence/13.0-5-g87674b4/python/lsst/daf/persistence/butler.pyc in get(self, datasetType, dataId, immediate, **rest)      943         location = self._locate(datasetType, dataId, write=False)      944         if location is None:  --> 945             raise NoResults("No locations for get:", datasetType, dataId)      946         self.log.debug("Get type=%s keys=%s from %s", datasetType, dataId, str(location))      947         NoResults  : No locations for get: datasetType:raw dataId:DataId(initialdata={'ccd': 'S00', 'run': '4672D', 'visit': 261576101}, tag=set([]))  {code}    But if I query the registry directly I see my data; using dat_persistence 13.0-3-gc00b09a also seems to work.  {code}  $ sqlite3 /tigress/HSC/LSST/comCam/registry.sqlite3   SQLite version 3.9.2 2015-11-02 18:31:45  Enter ".help" for usage hints.  sqlite> select visit from raw where ccd='S01' and run = '4672D' and visit = 261576101;  261576101  {code}
Answer: 353040.0

User story: "These are the last science-impacting features we aim to include in the release:  * DM-9855: Select images for coadd based on PSF quality  * DM-9795: CModel priors are weighted incorrectly relative to likelihood (/)  * DM-9862: Update meas_mosaic's wcs/fcr output files to reflect LSST coordinate system   * DM-9885: Rename deepCoadd_srcMatch as deepCoadd_measMatch (blocked by RFC-306) (/)  * DM-9828: Enable rectangular binSizes in SubtractBackgroundTask (/)  * DM-9985: Reduce Wcs pickle size (/)  * DM-9926: Reduce memory footprint of meas_mosaic read (/)  * DM-9556: All NaNs in coord_ra and coord_dec columns in deepCoadd forced src tables (/)    In the future we also hope to include:  * DM-5766: Implement spatial exposure selection task"
Answer: 20087.0

User story: "I'm looking at ETU2 data from TS8 at BNL, and am getting lots of warnings {{assembleCcd WARN: No WCS found in input exposure}}.   This is true but uninteresting -- that's information, not a warning.    Please change the level to DEBUG;  if there's no Wcs and we try to use one we'll certainly get an error of some sort, and turning on DEBUG would be appropriate.  This isn't something that indicates problems with the data, but something systematic about its source."
Answer: 171187.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 current mechanism to pass URL parameters from the Django application to the individual bokeh apps is based on the Referer header parameter. This is not working properly because  this parameter is optional, see for instance https://tools.ietf.org/html/rfc7231#section-5.5.2.  Depending on the browser configuration it may not include it.     We should make the Django application add a custom parameter in the HTTP Response to fix this problem.    https://docs.djangoproject.com/en/1.8/ref/request-response/"
Answer: 10658.0

User story: "We notice Safari>=10.1 is dropping the web socket connections to the bokeh server and we probably should open an issue.    This ticket provides a minimum code example to reproduce the bug."
Answer: 101744.0

User story: "The existing simulation data used for testing the DCR template building code is missing some important metadata. Those simulations should be brought up to date, and re-created with all the required metadata."
Answer: 191178.0

User story: "This is an issue for CI as the conda env may become stale."
Answer: 675155.0

User story: "We see errors installing both osx and linux packages like the following:    {code:java}     CondaRuntimeError: Runtime error: RuntimeError: Runtime error: Could not open u'/Users/square/jenkins/workspace/release/tarball/DarwinX86/miniconda2/4.2.12.lsst1/pkgs/mkl-11.3.3-0.tar.bz2.part' for writing (HTTPSConnectionPool(host='repo.continuum.io', port=443): Read timed out.).  {code}    I believe the best resolution is to mirror the public conda channels internally.  Another, less desirable, option would be build retrying into the conda command."
Answer: 10212.0

User story: "The bibtex files in {{lsst-texmf}} are not checked for errors. Add a simple travis job to include checks."
Answer: 209.0

User story: "Bucket ticket to cover non-specific SuperTask collaboration activities (see linked meeting notes)."
Answer: 8490.0

User story: "Write a set of user stories and consequent SuperTask design implications that address SQuaRE needs."
Answer: 100683.0

User story: "Extend DocHubProto to produce a complete HTML index page."
Answer: 201.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: "With the need to support more advanced table manipulations, we need to replace our internal fixed-length IPAC table format with something more suitable.  This ticket is to research and report on the pros and cons of selected embedded/in-memory databases as well as preliminary performance expectations.    The 3 popular java-based embedded databases I looked at are Derby, H2 and HyperSQL.  I'll list the pros and cons of each below.    Derby:  Pros:   * full-functioned relation database with lots of features  * lots of documentation    Cons:  * slowest    H2:  Pros:  * simple and fast  * full-text search  * embedded sql client via servlet    Cons:  * one author    HyperSQL  Pros:  * great performance with lots of features  * good documentation    Cons:  * slow down proportionally to the size of data    I've also recorded some performance numbers during the evaluation.  The operation I am recording is the time it takes to persist an in-memory table.  Table size is the file size in ipac table format.  Times are in seconds.  The test is done on my laptop with SSD drive.  The databases are tuned to use disk-base tables with a large cache size.  Code is written using jdbc driver with pre-compiled prepare statement and bulk insert.    ||table size||Derby||H2||HyperSQL||IPAC table||  |50k rows, 25 cols, 21mb|4.8|1.0/0.5|0.6/0.3|1.8|  |300k rows, 25 cols, 128mb|28.4|3.6/2.1|4.7/6.1|10.9|  |1mil rows, 25 cols, 423mb|108.4|10.5|31.7/59.0|35.7|    ~* if there are 2 numbers, then it's first try vs subsequence tries~    In conclusion, I feel comfortable recommending H2 based on our needs.  Although, I am sure HyperSQL would be just as good after additional tuning.   "
Answer: 4559.0

User story: "This was not wrapped as part of DM-8467, but is now needed anyway."
Answer: 2901.0

User story: "Write down and get the DMLT to agree to a description of what reprocessing of the HSC PDR will be performed on the LSST VC over the timescale of the S17 cycle, and some indication of what happens thereafter."
Answer: 14473.0

User story: "Implement RFC-306."
Answer: 3703.0

User story: "This ticket is a parent ticket to collect and link to IRSA system ticket raised against TSViewer and Firefly in general during test round campaign and demos to prepare for public release around mid-April.    links to IRSA Jira https://caltech-ipac.atlassian.net/browse/IRSA-142 and https://caltech-ipac.atlassian.net/browse/IRSA-174"
Answer: 568639.0

User story: In order to implement the "mean zero point" functionality of PhotoCalib, I need to compute the integral over the bounding box. {{BoundedField}} does not include facilities for integration/differentiation. Fortunately, my primary usage is {{ChebyshevBoundedField}}, which has a relatively straight-forward recurrence relation for integration.    I suggest an interface like the following on {{BoundedField}}, with a virtual "not implemented" default:    {code}  // Compute the integral of this function over its bounding-box.  double integrate() const;  {code}
Answer: 11699.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 build of {{starlink_ast}} fails sometimes because the build system tries to build files that rely on Starlink tools to be created but which do not need to be created because we committed derived versions. This approach breaks down sometimes because the timestamps of the derived files can be older than the timestamps of the source file, causing make to attempt a rebuild. The timestamps from a git checkout can not be fixed so the breakage is random.    I will modify the makefile so the rebuild is never attempted."
Answer: 37.0

User story: "There are some issues with flake8 compliance and unittests expected to fail on the integration branch. This ticket is to fix these issues to provide a better base for future work."
Answer: 4165.0

User story: "[~<USER> would like an internal DM risk process. LDM-512 should contain this process. Some work has been ported over from Gaia but it needs to be LSST-ified and approved."
Answer: 1845301.0

User story: "In https://sqr-017.lsst.io/#specification-tests we talk about creating more types of Specifications (windows, tolerances, generic functions). Probably the best way to accommodate this is to create a new family of Specification subclasses, where Specification is now an abstract base class.    This refactoring work will also make DM-9559 easier to implement (creating Specifications from specification repositories)."
Answer: 31872.0

User story: "A few metrics (eg, AD1, PA2) as being rendered in the qa-dashboard has having multiple values per dataset run.  This might be an issue with the format being submitted by {{post-qa}} or it may be internal to the dashboard (or both)."
Answer: 730299.0

User story: "ltdstatus (and, when kubified, probably the indexer) hang on GKE.  I think it's a memory condition, because they're doing a lot of threads in parallel.    Two things I want to try: 1) increase the size of the cluster instances a notch, 2) put a limiter on number of simultaneous threads spawned in our scatter/gather."
Answer: 345.0

User story: "Recently, while processing MADCASH (observations of local dwarf galaxies), I noticed a vast improvement in astrometric matching when I set:  {code}  calibrate.astrometry.matcher.numBrightStars=150 calibrate.photoCal.matcher.n  umBrightStars=150  {code}    We should make these the default for HSC."
Answer: 74.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 DM-5466, we needed to pass the results from {{ParseTask.getInfo()}} to the butler as a dataId. This is normally valid, since both are dictionaries, and even though {{getInfo()}} often contains extraneous entries that aren't relevant, the butler will usually ignore them. However, when parsing calibration files this dictionary contains some values that are set to {{None}}, since they will be filled in later. These extraneous keys are then placed in {{ButlerLocation.additionalData}} ([butlerLocation.py:221|https://github.com/lsst/daf_persistence/blob/master/python/lsst/daf/persistence/butlerLocation.py#L221]), which throws an exception as it is a PropertySet and does not support python {{None}} as a value.    DM-5466 has a work-around that strips these None values from the dictionary, but this is inelegant. The main driver for excluding None from PropertySet seems to compatibility with FITS headers. This seems like an unwarranted mixing of data model and persistence formats. Unless there is some advantage to not being able to store None in our dictionary-like objects, it seems preferable to shift the burden of accommodating FITS's peculiarities onto the persistence layer rather than PropertySet.   "
Answer: 1071668.0

User story: "- Set up obs_comcam (provided by [~<USER>) on {{lsst-dev01}}.  - Use RFC-301 data to build master-bias, dark, flat.  "
Answer: 192768.0

User story: "We should change the templates for {{fcr}} and {{wcs}} to the following:  {code}  jointcal-results/%(tract)d/wcs-%(visit)07d-%(ccd)03d.fits  jointcal-results/%(tract)d/fcr-%(visit)07d-%(ccd)03d.fits  {code}    This will avoid problems in copying/updating directories at NAOJ during incremental releases.  "
Answer: 117.0

User story: "Port outstanding work and release.    Essential:  * DM-9541: Bug related to MPI pickling when running coaddDriver (/)  * DM-9812: Clean up outputs from CharacterizeImageTask and CalibrateTask (/)  * DM-9438: Switch default reference catalog for HSC to PS1 in LSST format (/)  * DM-9855: Select images for coadd based on PSF quality (x)  * DM-9810: Make PSFEx oversampling configurable (/)  * DM-9856: Add option to deblender to turn off smoothing. (/)  * DM-9795: CModel priors are weighted incorrectly relative to likelihood (x)  * DM-9871: Move wcs and fcr datasets out of {{pointing}} directory in obs_subaru (/)  * DM-9874: Increase matcher.numBrightStars (/)  * DM-9862: Update meas_mosaic's wcs/fcr output files to reflect LSST coordinate system (x)    If possible (otherwise, will go into post-release update):  * DM-9885: Rename deepCoadd_srcMatch as deepCoadd_measMatch (blocked by RFC-306)  * DM-5766: Implement spatial exposure selection task"
Answer: 3088.0

User story: "Implement RFC-298."
Answer: 46135.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 development playground (multi-node, consisting of czar, several workers, and some test data) is needed for prototyping data distribution and replication.  It is anticipated that this will be a non-containerized deployment on NCSA OpenStack VMs in order to facilitate rapid development.    The general plan for this effort includes the following steps:  # create and configure 1 *master* and 10 *worker* nodes  # external access to the cluster via the *Floating IP* of the *master* node  # user accounts and security: create user *qserv*, configure *ssh*, etc.  # allocate 11 volumes (one per node) for data and databases  # setup an NFS server on *master* to export some local folder to all workers for sharing *LSST* Stack and other relevant *LSST* packages  # setup the minimally required *RPM*s to support the software deployment and development efforts  # build a local copy of the *LSST* stack and other relevant package on the exported volume  # configure and start *Qserv* (using *Docker* container) on all nodes  # *IMPORTANT*: make a snapshot of the VMs of all instances  # import a data set (a subset of chunks of PDAC's *wise* or *stripe82*)"
Answer: 18530.0

User story: "This is a follow up to the FlagHandler modification DM-9249.  Posted this last deletion to flagDecorator.py in case anyone unknown was using it."
Answer: 74600.0

User story: "The talk is a contributed talk for Python in Astronomy 2017, http://www.lorentzcenter.nl/lc/web/2017/896/info.php3?wsid=896&venue=Oort"
Answer: 69120.0

User story: "When importing {{meas_mosaic}}, the coordinate system for writing out the wcs/fcr files was not adapted to that expected from LSST (which always associates the detector origin with the electronics, whereas HSC's is such that a given detector's origin, pixel (0, 0) is associated with its LLC w.r.t. to the focal plane), but rather the tasks in {{meas_mosaic}}'s *updateExposure.py* were adapted to account for the rotated CCDs.  It was assumed that this was the only place those corrections were every used.  This turns out not to be the case since the wcs used to create the coadd gets attached to it in *coaddInputs*.  If {{meas_mosaic}} was run and *doApplyUberCal=True* (which are both the case for our HSC data processing), the wcs’s that are getting attached to the coaddInputs are not in the coordinate system appropriate for LSST for any nQuarter != 0 ccds.    Since this is already causing an issue in {{pipe_tasks}}'s *propogateVisitFlags.py*, see issue highlighted in DM-9383, (and could very well be causing issues elsewhere as yet undiscovered), we have decided these outputs need to be written out in the coordinate system expected by LSST."
Answer: 49017.0

User story: "The {{git}} version check used by the {{deploy}} script is broken such that a local version of {{git}} will always been built.  This check either needs to be fixed or removed."
Answer: 643683.0

User story: "Participate in once-weekly meetings. Includes limited time to prepare and communicate with no-WG members."
Answer: 47327.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: "Participate in once-weekly meetings. Includes limited time to prepare and communicate with no-WG members."
Answer: 24449.0

User story: "Plotly is an open source plotting package that is more oriented toward science than Highcharts. Provide a second set of eyes in evaluation of Plotly.js and support DM-9816.    Study some of the following:  Can we control tooltips?  What control do we have during selection?  In general, can monitor or have hooks into their events?  How hard to port histograms, scatter and density?  Do they support optimized updates and not complete redraws?  How  would a Plotly react component work?  Overall we want a sense if we should go to the next step of replacing Highcharts. We need to understand how much efforts would be involved."
Answer: 10449.0

User story: "As shown in DM-8059, the deblender can be improved by turning off the smoothing of the templates.  This ticket is to add this option as a config parameter to the deblend task."
Answer: 6232.0

User story: "In HSC, there are a number of ways that the PSF modeling with psfex can be poor.  Most of the time this is because the seeing is too good, but there can be other things that cause problems.  We would like to reject these images when building the coadd.  This ticket is to write an image selector that selects on the quality of the PSF based on the residuals of the second moments."
Answer: 49104.0

User story: There is code in {{afw}}'s FITS support that skips empty PDUs when you just ask to read a file.  This is convenient, but unfortunately it is applied to {{afwImage.readMetadata()}}, meaning that it is impossible to read the metadata from an empty PDU.    Part of the problem is that we overload {{0}} to mean, "the first real dataset";  I'm filing an RFC to change that.
Answer: 16081.0

User story: lsst.afw.image.makeVisitInfo.py has the following in it's docstring:  "This function will be replaced by a VisitInfo constructor once we switch to pybind11  (it is too much hassle with SWIG)"    Now that the pybind11 conversion is complete and VisitInfo has been implemented, this comment should be updated.
Answer: 1301.0

User story: "The DCR template generation code currently creates an exposure of type `calexp` as the matched template, which can be used with the current image differencing code by setting   {code}  from lsst.ip.diffim.getTemplate import GetCalexpAsTemplateTask  {code}  and   {code}  config.getTemplate.retarget(GetCalexpAsTemplateTask)  {code}    However, the exposure is not a true `calexp` and lacks some of the expected supporting data, such as background and source tables. A better type might be `matchedTemplate` with the same obsid as the matched exposure. This ticket is to define that output and hook it into imageDifference.py properly.  "
Answer: 706982.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 current DCR template generation code requires the user to supply the name of the telescope, and has telescope-specific code that interfaces with the butler. This code should be re-written to be less fragile and to remove the lines that depend on the telescope."
Answer: 87918.0

User story: "The Name class allows relative and fully-specified names to be computed for metrics and specifications in the {{validate_base}} framework."
Answer: 37533.0

User story: "I have seen two build failures in row from {{master}} on the jenkins {{lsst-dev}} node while running the stack demo.    https://ci.lsst.codes/job/release/job/run-rebuild/473/console  https://ci.lsst.codes/job/release/job/run-rebuild/474/console    {code:java}  Failed (4238 of 4238 flags do not match) in column flags_negative.  astrometry_net_data bin detected-sources_small.txt expected input output_small README Warning: output results not within error tolerance for: lsst_dm_stack_demo-master  *** The simple integration demo completed with some statistical deviation in the output comparison.  {code}  "
Answer: 145.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: "Prototype TravisCI Flake8 linting using the DM Python Style Guideline.    1. Implement Flake8 linting with DM's options:    {code}  [flake8]  max-line-length = 110  ignore = E133, E226, E228, N802, N803  {code}    2. Apply to some lsst-sqre microservices repositories for evaluation and testing.    3. Test different integration options with Github. Such as blocking PRs to master until Flake8 passes."
Answer: 60617.0

User story: "astshim presently prints AST error messages to stderr. Improve this so that the messages and up as the text of exceptions, instead.    This work requires the new AST capability of registering an error handler which has just been released."
Answer: 8436.0

User story: "For time series functionality in PDAC v1, the FireflyClient must use 'suit' in the URL instead of 'firefly'; and IRSA's server can be used if 'irsaviewer' is substituted instead. There are several places in the firefly_client v1.0.0b3 (beta3) where 'firefly' is hard-coded. FireflyClient needs an update to allow users to specify this part of the URL for the websocket."
Answer: 21803.0

User story: "Implement new starSelector baseClass"
Answer: 586351.0

User story: "Create new sourceSelector BaseClass as described in RFC-198."
Answer: 118090.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 test run for the {{decam}} dataset succeed yesterday morning but the periodic evening build failed with the stack trace below.  Perhaps this is related to the {{daf_persistence}} changes yesterday?    https://ci.lsst.codes/job/validate_drp/dataset=decam,label=centos-7,python=py2/863/    {code:java}  Traceback (most recent call last):    File "/home/jenkins-slave/workspace/validate_drp/dataset/decam/label/centos-7/python/py2/lsstsw/stack/Linux64/validate_drp/master-gb01c0af08e/bin/validateDrp.py", line 97, in <module>      validate.run(args.repo, **kwargs)    File "/home/jenkins-slave/workspace/validate_drp/dataset/decam/label/centos-7/python/py2/lsstsw/stack/Linux64/validate_drp/master-gb01c0af08e/python/lsst/validate/drp/validate.py", line 104, in run      **kwargs)    File "/home/jenkins-slave/workspace/validate_drp/dataset/decam/label/centos-7/python/py2/lsstsw/stack/Linux64/validate_drp/master-gb01c0af08e/python/lsst/validate/drp/validate.py", line 204, in runOneFilter      verbose=verbose)    File "/home/jenkins-slave/workspace/validate_drp/dataset/decam/label/centos-7/python/py2/lsstsw/stack/Linux64/validate_drp/master-gb01c0af08e/python/lsst/validate/drp/matchreduce.py", line 148, in __init__      repo, dataIds, matchRadius)    File "/home/jenkins-slave/workspace/validate_drp/dataset/decam/label/centos-7/python/py2/lsstsw/stack/Linux64/validate_drp/master-gb01c0af08e/python/lsst/validate/drp/matchreduce.py", line 208, in _loadAndMatchCatalogs      calexpMetadata = butler.get("calexp_md", vId, immediate=True)    File "/home/jenkins-slave/workspace/validate_drp/dataset/decam/label/centos-7/python/py2/lsstsw/stack/Linux64/daf_persistence/13.0-4-g886c4ba/python/lsst/daf/persistence/butler.py", line 945, in get      raise NoResults("No locations for get:", datasetType, dataId)  lsst.daf.persistence.butlerExceptions.NoResults: No locations for get: datasetType:calexp_md dataId:DataId(initialdata={'filter': 'z', 'visit': 176837, 'ccdnum': 14}, tag=set([]))  cp: cannot stat ‘/home/jenkins-slave/workspace/validate_drp/dataset/decam/label/centos-7/python/py2/validate_drp/Decam_output_z.json’: No such file or directory  /home/jenkins-slave/workspace/validate_drp/dataset/decam/label/centos-7/python/py2/archive/decam/processCcd.log: 5,072 B / 93.7 KiB = 0.053  {code}  
Answer: 38760.0

User story: "While validating on HSC data, we encountered a use case for rectangular bin sizes in {{SubtractBackgroundTask}}.  We propose two new config fields:    * binSizeX  * binSizeY    By default they will be None and populated with the value in binSize. This change will be 100% backwards compatible. Everyone's config files will produce the same results.   "
Answer: 22179.0

User story: "Change label name 'Basic' to 'Other' mission case. This case won't show images for first release but will get updated later in future release to handle images in a more advanced way independently of the mission type."
Answer: 2914.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: "Like the {{Mappings}} they adapt, a {{Transform}} may or may not have a forward transformation, and may or may not have an inverse transformation. Test methods should be added to {{Transform}} to let clients defend against calling a missing transformation."
Answer: 17067.0

User story: "pep8 tasks have a number of silly pep8 errors including duplicate imports and some impressively too-long lines."
Answer: 616241.0

User story: "The Panopticon ES cluster had issues with their filesystem I/O yesterday and today. I did a hard reboot on each machine followed by an Ansible role to restart the cluster. This eventually resolved this issue.    Machines involved:  p-es-1-<USER>b16f725f-f86b-4349-8d9e-f07e63665029  p-es-2-<USER>5593f930-4613-4420-831c-2029fddd92cc  p-es-3-<USER>62cda1e4-7c00-4817-9bea-8deb057b3032  p-es-4-<USER>d0f1f1be-3e26-4d4e-b821-244e7d903b5b  p-es-k-<USER>(p-es-5-<USER> 6dfaab48-aadf-4135-b933-23844685922b  p-es-6-<USER>1e7c2b7d-354f-45e0-b17c-bb761f03a2c0    {code}  han:vagrant-nebula-panopticon <USER> vagrant ssh p-es-k  Welcome to Ubuntu 16.04.2 LTS (GNU/Linux 4.4.0-21-generic x86_64)     * Documentation:  https://help.ubuntu.com   * Management:     https://landscape.canonical.com   * Support:        https://ubuntu.com/advantage  Last login: Mon Feb 27 05:44:14 2017 from 24.255.16.161  vagrant@logging:~$ sudo su -  sudo: unable to execute /bin/su: Input/output error  vagrant@logging:~$ df  -bash: /bin/df: Input/output error  vagrant@logging:~$ du  -bash: /usr/bin/du: Input/output error  vagrant@logging:~$ dig logging.lsst.codes  -bash: /usr/bin/dig: Input/output error  vagrant@logging:~$ exit  {code}  "
Answer: 1549805.0

User story: "The Panopticon ES cluster had issues with their filesystem I/O. I did a hard reboot on each machine followed by an Ansible role to restart the cluster. This eventually resolved this issue.    Machines involved:  p-es-1-<USER>b16f725f-f86b-4349-8d9e-f07e63665029  p-es-2-<USER>5593f930-4613-4420-831c-2029fddd92cc  p-es-3-<USER>62cda1e4-7c00-4817-9bea-8deb057b3032  p-es-4-<USER>d0f1f1be-3e26-4d4e-b821-244e7d903b5b  p-es-k-<USER>(p-es-5-<USER> 6dfaab48-aadf-4135-b933-23844685922b  p-es-6-<USER>1e7c2b7d-354f-45e0-b17c-bb761f03a2c0    {code}  han:vagrant-nebula-panopticon <USER> vagrant ssh p-es-k  Welcome to Ubuntu 16.04.2 LTS (GNU/Linux 4.4.0-21-generic x86_64)     * Documentation:  https://help.ubuntu.com   * Management:     https://landscape.canonical.com   * Support:        https://ubuntu.com/advantage  Last login: Mon Feb 27 05:44:14 2017 from 24.255.16.161  vagrant@logging:~$ sudo su -  sudo: unable to execute /bin/su: Input/output error  vagrant@logging:~$ df  -bash: /bin/df: Input/output error  vagrant@logging:~$ du  -bash: /usr/bin/du: Input/output error  vagrant@logging:~$ dig logging.lsst.codes  -bash: /usr/bin/dig: Input/output error  vagrant@logging:~$ exit  {code}  "
Answer: 31807.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 network for instance es-3.lsst.codes (p-es-3-<USER>141.142.209.205 62cda1e4-7c00-4817-9bea-8deb057b3032) was unresponsive. I disassociated and reassociated the IP address. That alone didn't work. Next I did a hard reboot. This and approximately 20 minutes was enough for it to work again.    This problem caused ELK stack to stop logging. Logstash couldn't access the machine and stopped logging to ES.  "
Answer: 1549825.0

User story: "The network for instance es-3.lsst.codes (p-es-3-<USER>141.142.209.205 62cda1e4-7c00-4817-9bea-8deb057b3032) is unresponsive. I disassociated and reassociated the IP address. That alone didn't work. Next I did a hard reboot. This and approximately 20 minutes was enough for it to work again.    This problem caused ELK stack to stop logging. Logstash couldn't access the machine and stopped logging."
Answer: 31828.0

User story: "Write up a lightweight specification+design for the {{dochub-prototype}} project (the build infrastructure for www.lsst.io) to help [~<USER> make the initial implementation.    {{dochub-prototype}} is itself a prototype for what will become DocHub (https://sqr-013.lsst.io)."
Answer: 1520.0

User story: "Plotly is an open source plotting package that is more oriented toward science than Highcharts.    Study the following:  * Can we control tooltips?  * What control do we have during selection?  * In general, can monitor or have hooks into their events?  * How hard to port histograms, scatter and density?  * How hard to create a heat map to replace density?  * Do they support optimized updates and not complete redraws?    Overall we want a sense if we should go to the next step of replacing Highcharts.  We need to understand how much efforts would be involved."
Answer: 59049.0

User story: "Mitigate the temporary loss of docs.scipy.org as an intersphinx target in pipelines.lsst.io and developer.lsst.io builds. Solution is to remove the {{-W}} flag to prevent warnings from becoming errors that block merges.    See also: https://community.lsst.org/t/how-docs-scipy-org-and-intersphinx-affect-your-doc-builds/1717?u=<USER>
Answer: 53.0

User story: "We're writing the {{icExp}} files in {{CharacterizeImageTask}}, which we don't use, but greatly increases our disk usage.     We want the denormalized match catalogs from {{CalibrateTask}} and from multiband processing."
Answer: 9860.0

User story: "<USER>asks that we also include a 1.3 arcsec target seeing in the {{ConvolvedFluxPlugin}}.  This target seeing is larger than any expected seeing in the coadd, and so we'll always get a useful result."
Answer: 209.0

User story: "Add a configuration option that lets PSFEx decide when to oversample PSF images.    "
Answer: 10051.0

User story: "Now that we have a logging framework, convert existing microservices to use it."
Answer: 8584.0