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: For forward-compatibility with DM-13163, {{ap_verify}} should create separate repositories for ingestion and calibration. In effect, the current "output repository" should be a convenient "workspace" directory but not a repository.    In addition, the interface module {{pipeline_driver}} should make a distinction between input and output repositories, choosing the location of the latter instead of deferring the choice to {{ap_pipe}}. Neither {{CmdLineTasks}}, nor in the future {{Pipelines}}, are responsible for output paths.    Because the API will change again as part of DM-13163, changes to the interface between {{ap_pipe}} and {{ap_verify}} should be kept minimal; most likely, this will entail removing the ill-advised wrappers added in DM-12257 and calling the existing functions from {{pipeline_driver}} again.
Answer: 20075.0

User story: "Currently, {{ap_pipe}} requires a single input repository with two directories, {{ingested}} and {{calibingested}}, each a repository in its own right. This will be a problem for DM-13163 because most command-line tasks allow the URIs of the data and calib repositories to be independent, and in any case the Stack convention is different from our current usage.    This ticket will change the command line to accept a separate calib repository (the argument should behave the same as {{processCcd.py --calib}}?). The API to {{ap_verify}} will not be changed, as it will almost certainly change when DM-13163 is implemented."
Answer: 4085.0

User story: "If all goes well, this should allow us to start removing our dependence on the NumPy C API (left for another ticket).    This will probably require modifying our pybind11 build to install its CMake config files (unless we're doing that already, which I doubt), since ndarray now uses those to find pybind11."
Answer: 58725.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: We have some early-2014 raw HSC data with no corresponding sky frames available in the calib repo {{/datasets/hsc/calib/20180117/}}. In particular, sky frames of HSC-R and HSC-Z  for as early as dateObs=2014-03-28 are needed by the HSC "RC2" dataset (DM-11345).     Two example early visits are  visit=1202 (HSC-R ) and visit=1166 (HSC-Z), from SSP_UDEEP_COSMOS,  and their dateObs is 2014-03-28    {noformat}  >>> import lsst.daf.persistence  >>> butler = lsst.daf.persistence.Butler("/datasets/hsc/repo")  CameraMapper INFO: Loading exposure registry from /datasets/hsc/repo/registry.sqlite3  CameraMapper INFO: Loading calib registry from /datasets/hsc/repo/CALIB/calibRegistry.sqlite3  >>> butler.get("raw", visit=1202, ccd=0)  <lsst.afw.image.exposure.exposure.ExposureU object at 0x7fb5c35d9960>  >>> butler.get("sky", visit=1202, ccd=0)  Traceback (most recent call last):    File "<stdin>", line 1, in <module>    File "/ssd/lsstsw/stack3_20171021/stack/miniconda3-4.3.21-10a4fa6/Linux64/daf_persistence/14.0-14-g87d16e8+10/python/lsst/daf/persistence/butler.py", line 1410, in get      raise NoResults("No locations for get:", datasetType, dataId)  lsst.daf.persistence.butlerExceptions.NoResults: No locations for get: datasetType:sky dataId:DataId(initialdata={'visit': 1202, 'ccd': 0}, tag=set())  {noformat}
Answer: 1426.0

User story: "Reprocess the two WIDE tracts of the HSC RC1 dataset, as defined in [DMTR-31 Sect. 4.1 |https://docushare.lsst.org/docushare/dsweb/Get/DMTR-31], and the three tracts of the HSC RC2 dataset, as defined in DM-11345, using Stack w_2018_08. Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{skyCorrection.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}}. "
Answer: 41916.0

User story: "Currently, {{ap_verify}}'s ingestion is specific to DECam (in particular, hardcoded references to {{obs_decam}} and its tasks' configs). The code should be generalized to use whichever obs package is specified by the input Datasest, preferably without any special-case handling."
Answer: 100963.0

User story: "Add documentation to DMTN-071 for the Kubernetes Dashboard."
Answer: 1767.0

User story: "Create a full example of a Python module documented in our Numpydoc style and add it to https://developer.lsst.io/docs/py_docs.html    See http://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_numpy.html#example-numpy for an example of this.    Also address the example in https://developer.lsst.io/docs/py_docs.html#examples-of-constant-and-class-attribute-docstrings to show that class attributes are documented separately for init parameters. See https://lsstc.slack.com/archives/C2B6DQBAL/p1518125199000564"
Answer: 17189.0

User story: "As a self-contained module within {{ap_verify}}, {{ingestion}} should have unit tests of its functions. It may be possible to implement a unit test by specifically ingesting only 1-2 files of each type."
Answer: 64733.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Run   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    with the w_2018_06 RC2 outputs from DM-13435"
Answer: 28412.0

User story: "Having solved the issue raised in ticket DM-13486    We now need to understand the discrepancies between obs. and simu. here :    !Capture d’écran 2018-02-09 à 11.18.43.png!     "
Answer: 191912.0

User story: "It is anticipated that a small error in the wavelength calibration will impact the determination of the atmospheric transmission in the blue end of the curve, because of its sharp cut-off.    Here I have implemented a recalibration of the first order (geometric) solution using known spectral features from the SED of the observed star.    The illustrations speak for themselves :    !Capture d’écran 2018-02-07 à 12.01.49.png!     "
Answer: 191919.0

User story: "[~<USER> pointed out the diagram of the HSC focal plane in obs_subaru, which I wouldn't have thought to check. To make it more obvious for future me, I've created a readme and added a note about the diagram to it."
Answer: 25862.0

User story: "Implement a per-object Galactic Extinction correction for use with the color-analysis QA plots to replace the per-field placeholder included in DM-13154.  It looks like there is code in \{\{sims_photUtils}} (and dependencies) to do this, so this will be an attempt to get that working with the analysis scripts.         Note that this requires the A_filter/E(B-V) extinction coefficients for the HSC filters (awaiting a response from the HSC team, the placeholder noted above is just using SDSS filter values)."
Answer: 229017.0

User story: "Use the latest weekly to match to the HST data to get a larger dataset for classification/training use."
Answer: 34394.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 error is seen near the edge of the COSMOS tract. It used to write out  a tiny corner of a coadd.   {code:java}  Traceback (most recent call last):    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/ctrl_pool/14.0-1-ga2912ff+25/python/lsst/ctrl/pool/parallel.py", line 496, in logOperation      yield    File "/home/<USER>stack/pipe_drivers/python/lsst/pipe/drivers/coaddDriver.py", line 316, in coadd      detResults = self.detectCoaddSources.runDetection(coadd, idFactory, expId=expId)    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_tasks/14.0-39-g03bf09b5+1/python/lsst/pipe/tasks/multiBand.py", line 303, in runDetection      detections = self.detection.makeSourceCatalog(table, exposure, expId=expId)    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_base/14.0-6-ge2c9487+33/python/lsst/pipe/base/timer.py", line 150, in wrapper      res = func(self, *args, **keyArgs)    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/meas_algorithms/14.0-10-g59393990+2/python/lsst/meas/algorithms/detection.py", line 292, in run      clearMask=clearMask, expId=expId)    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/meas_algorithms/14.0-10-g59393990+2/python/lsst/meas/algorithms/dynamicDetection.py", line 180, in detectFootprints      factor = self.calculateThreshold(exposure, seed, sigma=sigma)    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/meas_algorithms/14.0-10-g59393990+2/python/lsst/meas/algorithms/dynamicDetection.py", line 107, in calculateThreshold      lq, uq = np.percentile(fluxes, [25.0, 75.0])    File "/software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/site-packages/numpy/lib/function_base.py", line 4269, in percentile      interpolation=interpolation)    File "/software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/site-packages/numpy/lib/function_base.py", line 4011, in _ureduce      r = func(a, **kwargs)    File "/software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/site-packages/numpy/lib/function_base.py", line 4386, in _percentile      x1 = take(ap, indices_below, axis=axis) * weights_below    File "/software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/site-packages/numpy/core/fromnumeric.py", line 134, in take      return _wrapfunc(a, 'take', indices, axis=axis, out=out, mode=mode)    File "/software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/site-packages/numpy/core/fromnumeric.py", line 57, in _wrapfunc      return getattr(obj, method)(*args, **kwds)  IndexError: cannot do a non-empty take from an empty axes.  {code}
Answer: 88217.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: "Investigate adding the mosaic.py step into the DESDM workflow wcl, using the software setup of DM-13115, i.e. Python 2 stack {{w_2017_50}} and Python 2 DESDM.     Don't merge anything to prod_wcl as python 3 and other tests continue to be rely on the w_2017_33 version."
Answer: 20168.0

User story: "Assess the performance of the classifier on data with different depths and seeings."
Answer: 167409.0

User story: "The classifier is occasionally failing on bright objects where it should have the best inputs, look into what these objects are and how to mitigate this.  This has been extended into looking into all failures more."
Answer: 69063.0

User story: "Follow-on to DM-13271 to clean up data ingest issues now that lsst-projectmeta-kit 0.3.0 is emitting metadata.jsonld on Lander pages in the wild.    This ticket also covers re-building LaTeX document landing pages so that they include {{metadata.jsonld}} files."
Answer: 9757.0

User story: "In the Gen3 butler, the tracts and patches defined by a SkyMap will be loaded into a database, and that will make it much more important to recognize when the same SkyMap has already been loaded.  While SkyMap objects already support equality comparison, it'd be nice if they could also produce a stable hash that can be used to uniquely label them.    -Since that basically amounts to being able to hash the SkyMap's configuration, I think it makes the most sense to actually add this hashing support directly to {{pex_config}}.  Being able to compare hashes to check for config equality seems like it'd be generally useful to.-    I'm currently planning to do this with {{hashlib.sha1}}, rather than just the {{hash}} builtin, because I want something that's guaranteed to be stable between Python versions.    Note that these in-memory hashes will not be equivalent to hashes of the files in which these objects are stored."
Answer: 1915.0

User story: "Assist Nate in packaging antlr4 as a third-party TaP eups package"
Answer: 2595.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 debugging coaddition, I have an alternate API for AssembleCoadd.run() that I use in my local copy of pipe_tasks so that I can quickly  coadd any list of tempExp DataRefs in a notebook without going through the long "selectExposures" task which converts a list of calexp data refs to a list of temp exp dataRefs. Would this be useful to anyone else?    {code}       @pipeBase.timeMethod  -    def run(self, dataRef, selectDataList=[]):  +    def run(self, dataRef, selectDataList=[], tempExpRefList=None):           """!           \brief Assemble a coadd from a set of Warps     @@ -327,13 +327,14 @@ discussed in \ref pipeTasks_multiBand (but note that normally, one would use the                    - nImage: exposure count image           """           skyInfo = self.getSkyInfo(dataRef)  -        calExpRefList = self.selectExposures(dataRef, skyInfo, selectDataList=selectDataList)  -        if len(calExpRefList) == 0:  -            self.log.warn("No exposures to coadd")  -            return  -        self.log.info("Coadding %d exposures", len(calExpRefList))  -  -        tempExpRefList = self.getTempExpRefList(dataRef, calExpRefList)  +        if tempExpRefList is None:  +            calExpRefList = self.selectExposures(dataRef, skyInfo, selectDataList=selectDataList)  +            if len(calExpRefList) == 0:  +                self.log.warn("No exposures to coadd")  +                return  +            self.log.info("Coadding %d exposures", len(calExpRefList))  +  +            tempExpRefList = self.getTempExpRefList(dataRef, calExpRefList)  {code}
Answer: 475151.0

User story: "Process WIDE_VVDS (tract=9697) and WIDE_GAMA15H (tract=9615) data with w_2018_03   and add the output products to the repo of DM-13463.  Pipeline steps and configs are the same as DM-13463.     The visit IDs are as defined in DM-11345 [this comment|https://jira.lsstcorp.org/browse/DM-11345?focusedCommentId=90372&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-90372 ]"
Answer: 4503.0

User story: "Following DM-13451, {{ap_pipe}} requires as input a repository that actually contains as subdirectories two other repositories. This is an awkward requirement for users, and will likely block DM-13163 because the {{CmdLineTask}} framework assumes a more conventional repository. {{ap_verify}} should be modified to produce, and {{ap_pipe}} to accept, a single repository containing all ingested data.    This issue must be worked on after DM-12938, since changes to the input repository structure are incompatible with the hard-coding described there."
Answer: 8985.0

User story: "Getting lots of these:  {code}    sigNoise = maskedImage.getImage().getArray()/numpy.sqrt(variance.getArray())  /tigress/HSC/stack/hsc3-perseus-20171206/stack/miniconda3-4.3.21-10a4fa6/Linux64  /pipe_tasks/6.0b5-hsc+1/python/lsst/pipe/tasks/assembleCoadd.py:359: RuntimeWarn  ing: invalid value encountered in greater    varArray[:] = numpy.where(varArray > 0, varArray, numpy.inf)  {code}"
Answer: 2.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Currently a drawback of WarpCompare is any epochs where a source doesn't look like the other epochs gets clipped. This leads to some loss of signal in bright sources. While future work on the image comparison will improve this (background matching, image-to-image psf matching, etc....) for now, we probably want a nuclear option config:    If an artifact candidate fits entirely within a template coadd source, then don't clip it. This means that unfortunate CRs or supernovae won't be clipped, but will improve the photometry. For the HSC release,  coadd photometry seems to be a higher priority.   "
Answer: 7508.0

User story: "Re-run {{installTransmissionCurves.py}} in {{/datasets/hsc/repo}} with a newer {{obs_subaru}} after DM-13485 is fixed (likely {{w_2018_06}})"
Answer: 7864.0

User story: "It is desirable to have the authoritative Registry schema definition in a machine readable (YAML) format.  This document should contain all information needed to initialize the Registry database with sqlalchemy."
Answer: 13996.0

User story: "Per discussion on IHS-614, please upgrade sqrbot so that it supports authenticated access to JIRA, then work with [~<USER> to get it an account which it can use to provide status on IHS-project tickets."
Answer: 326801.0

User story: "We need a mechanism to retrieve the status of the job creation for the bulk insertion of jobs as part of the ETL task, see DM-12604.    Also need a SQUASH_ELT_MODE configuration parameter to handle some operations during the ETL such as preserving the original timestamp of jobs instead of using auto {{now()}}."
Answer: 3155.0

User story: The image drop down needs to be modified to support HiPS.  There should be an app option so that this functionality can be turned off and on.    The image dropdown is in for sections so do the following:   * Section 1 - Add option 'HiPS - multi order image'   * Section 2 - when HiPs is select change this to be only "Search" and "URL"   * Section 3 - change this to have 'Name or Position' and 'Field of View' both of these can be left blank (maybe a help line to say that)   * Section 4 - Add the HiPS selection table from ticket DM-12555    Section 4 will probably need a little more work than just added the hips table that might happen in a second ticket.
Answer: 25150.0

User story: "Make more reruns of COSMOS to different depths, one with 3 visits, one with 5 visits, one with 10 and one with 20. Some of the bands do not have 20 visits and will include the maximum number if it is less than the desired number.     "
Answer: 125420.0

User story: "The atmospheric attenuation as a function of airmass in libRadtran is not understood :    This is libRadTran :    !Capture d’écran 2018-02-05 à 17.18.50.png! This is Modtran :    !Capture d’écran 2018-02-05 à 17.19.34.png!    They should look similar.    Why not?"
Answer: 197338.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: "Retrieval of 500 Gemini-GMOS observations from the online archive.    The proposal was to monitor the stability of aerosol scattering above Pachon.    The data needs to be reduced before analysis :    -create an obs_package,    -gather calibration frames.    I will try to find someone to do it for us."
Answer: 197411.0

User story: "Change the remaining parts of the code from the old python objects to afw objects. Once we do this we can remove all of old DIAObject and DIAObjectCollection as they are essentially wrapper classes for afw record object and afw table respectively. This also includes changing the methods on this class to store and load DIAObject and DIASources separately rather than using the catch all load and store commands."
Answer: 117592.0

User story: "Removes the score and match methods from DIAObjectCollection and puts them, for now, into AssociationTask. Once AssociationTask moves into lsst-distrib we can move the further into meas_algorithms."
Answer: 35890.0

User story: "The simplest implementation of alert filtering in the Kafka system assumes that every filter consumes a complete alert stream. That is, 100 filters means we duplicate the ten million event stream 100 times. That'll soon get prohibitively expensive.    Prototype a way around this issue. Suggested first approach is to use a multi-threaded (or multi-process) approach to filtering: rather than a container executing a single filter only, a single container can execute multiple filters at the same time. Does that work? If not, can we think of something better?    Deliverable is a prototype implementation of a filtering system that will not use infinite bandwidth."
Answer: 207314.0

User story: "The code in {{display_matplotlib}} to set the zoom (from the command line) to matplotlib's idea of the zoom fails for the {{inline}} backend.  Please avoid the exception."
Answer: 88825.0

User story: I will review the paper:    "SCARLET: Source separation in multi-band images by Constrained Matrix Factorization"    for PUB-56.     
Answer: 26064.0

User story: "I've completed measuring the HSC wavefront for the handful of existing HSC donut exposures.  The next task is to use this information to constrain pieces of a larger optical model that wouldn't be easy to constrain using in-focus data.  I think this should include things like solving for the chip-to-chip wavefront discontinuities and degrees of freedom in the non-static part of the wavefront model.  This ticket is to write the math for this down, to then get feedback, and to think about model simplifications (e.g. no chip discontinuities) that may make initial progress easier."
Answer: 201646.0

User story: "Development of scripts to start ancillary processes that are not part of the codebase but are necessary to run the test environment."
Answer: 2.0

User story: "Proposed having the Spectrograph commandable SAL component (CSC) be its own device, described in LSE-72. This will simplify code for Spectrograph instead of using the code for the archiver CSC."
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: "Harden scripting and procedures for configuration to version control system. Connect to puppet."
Answer: 5837.0

User story: "Add dashboards for use cases:   * Subsystem general status (casual user view)   * Operators health/ping monitor   * Operators view (TMG)"
Answer: 5829.0

User story: "Add application-level monitoring for the Batch Scheduler."
Answer: 5839.0

User story: "Reprocess the HSC RC1 dataset, as defined in [DMTR-31 Sect. 4.1 |https://docushare.lsst.org/docushare/dsweb/Get/DMTR-31], using Stack w_2018_03. Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}} (-DM-10129-/-DM-11020-).      Summarize the total node-hours needed. "
Answer: 7317.0

User story: "Extend antlr4 parser beyond simple statement, for example:    {{SELECT COUNT ( * ) as OBJ_COUNT FROM Object WHERE qserv_areaspec_box ( 0.1 , - 6 , 4 , 6 ) AND scisql_fluxToAbMag ( zFlux_PS ) BETWEEN 20 AND 24 AND scisql_fluxToAbMag ( gFlux_PS ) - scisql_fluxToAbMag ( rFlux_PS ) BETWEEN 0.1 AND 0.9 AND scisql_fluxToAbMag ( iFlux_PS ) - scisql_fluxToAbMag ( zFlux_PS ) BETWEEN 0.1 AND 1.0)))));}}"
Answer: 111784.0

User story:  Parse a query like "SELECT objectId, ra_PS FROM Object WHERE objectId=1234" with the new antlr4 parser.
Answer: 60178.0

User story: "Prepare and finalize data readiness, generate appropriate ObjectIDs and queries for KPM30 run."
Answer: 82056.0

User story: "Set up communication protocol between master and worker loader service."
Answer: 525705.0

User story: "Set up communication protocols between the master and worker loader service."
Answer: 525705.0

User story: "psutil has had some major updates since RFC-176 with some significant speed ups.    This also seems to fix a DeprecationWarning triggered by the current version (which is my main motivation for updating this).    psutil is only used in utils.tests at this time."
Answer: 1334.0

User story: "Current implementation of QuantumGraph (with different name) is rather minimalist and is optimized mostly for efficient storage. We want to extend it to make usable for other cases as well. "
Answer: 137914.0

User story: "Currently, {{ap_pipe}} ingests and processes data. For its ongoing conversion to a {{CmdLineTask}} (DM-13163) and forward-compatibility with {{Pipeline}} classes, {{ap_pipe}} should work on an externally provided repository.    For the time being, this functionality should be moved to {{ap_verify}} (which currently requires uningested data), and the final responsibility for ingestion will be determined later."
Answer: 11566.0

User story: "Investigate libraries and frameworks available for SQL interaction with Parquet data files.  Would these perform sufficiently to theoretically replace MySQL as a shard data store?"
Answer: 130138.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 addition to Pipeline class (which is mostly OK in current prototype) we need a bunch of tools to manipulate/verify pipelines. Some basic functionality that we already know we want from that:   * validate that Pipeline is properly ordered   * re-order tasks in Pipeline according to data dependency, check for any loops    These are based on inputs/outputs defined for each task and in new scheme of things it should be based on SuperTask configuration, so some preliminary support for new SuperConfiguration will also be needed.  "
Answer: 18634.0

User story: "We had to redeploy the production {{squash-api}} to a node with more memory to avoid the 502, 504 Gateway errors seen during DM-12604.    Changed nginx/uwsgi configuration to use uwsgi protocol and sockets to improve memory usage."
Answer: 3.0

User story: "Capture NOAO Mosaic geometry FITS keyword definition for CCD Amplifiers as described in LCA-13501. The NOAO Mosaic keywords are used for assembling images from multi-CCD cameras and are widely used. "
Answer: 118.0

User story: "Build and install all of the SAL software on the new dedicated machine on the LSST L1 TestStand (lsst-l1-us-fault)    for  the DM HeaderService.    Build and install the DM HeaderService on this new machine.    Successfully run the DM HeaderService tests as done in the last Pathfinder Integration activity 4b."
Answer: 124.0

User story: "Develop, propose and discuss with key principals a set of key/pair values for the header of the ATSCam."
Answer: 126.0

User story: "Some gains are zero, that's bad (leads to inf variance, and therefore NaNs).    The other values are meaningless as this is currently being used for any given raft, so lets set them all to 1 for now. Also set all the readNoise values to 10 for now."
Answer: 122.0

User story: "Some gains in comCam (as derived by running eotest) are set to 0.0.  While we will fix this, the ISR should check for non-positive gains and generate a warning.    In the interests of allowing ISR to run with incomplete/bad cameraGeom, we should set the gain to 1.0 after generating the warning.     "
Answer: 988240.0

User story: "LSST internal reviewers suggested using a set of simulations using real galaxy data as a more robust test of the new deblender. This ticket involves creating another 10k simulated blends (this time with real galaxies) and running both the new and old deblenders on it."
Answer: 15775.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: Creating flats for obs_comCam generates errors like the following as the code tries to make a pretty picture.  While this is a nice idea I don't think that the default should be to generate these warnings.   {code}...  flat INFO: Writing {'filter': '550CutOn', 'ccd': 'S20', 'calibDate': '2017-05-23'} on lsst-dev01.ncsa.illinois.edu:4089146  Unable to fit image for detector "S00" into image of camera  Unable to fit image for detector "S01" into image of camera  Unable to fit image for detector "S02" into image of camera  Unable to fit image for detector "S10" into image of camera  Unable to fit image for detector "S11" into image of camera  Unable to fit image for detector "S12" into image of camera  Unable to fit image for detector "S20" into image of camera  Unable to fit image for detector "S21" into image of camera  Unable to fit image for detector "S22" into image of camera  flat WARN: Unable to create camera image: 'ComCamMapper' object has no attribute 'map_flat_camera'  {code}
Answer: 5713.0

User story: "Run   # visitAnalysis  # coaddAnalysis  # colorAnalysis  # compareVisitAnalysis  # compareCoaddAnalysis    with the w_2018_04 RC2 outputs from DM-13256"
Answer: 40174.0

User story: "Reprocess the two WIDE tracts of the HSC RC1 dataset, as defined in [DMTR-31 Sect. 4.1 |https://docushare.lsst.org/docushare/dsweb/Get/DMTR-31], and the three tracts of the HSC RC2 dataset, as defined in DM-11345, using Stack w_2018_06. Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{skyCorrection.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}}. "
Answer: 20296.0

User story: "There is code in meas_algorithms that explicitly imports ds9 as  {code}  import lsst.afw.display.ds9 as ds9  {code}  This has the side effect of setting ds9 to be the default backend for {{afwDisplay}}.  As we now have multiple backends in the stack (ds9, firefly, ginga?, matplotlib) this is a practical as well as a theoretical problem and, moreover, switching to the {{afwDisplay}} interface is safe and easy.  "
Answer: 574531.0

User story: "Provide documentation of system level Kubernetes install experience."
Answer: 2960.0

User story: "{color:#000000}Refine Kubernetes 1.9.x install for openstack and VMware ESXi 6.5{color}."
Answer: 2960.0

User story: "Verify systems function as specified."
Answer: 79103.0

User story: "After prototype installation and configuration, work with PDAC team to specify required software versions. Update software as required."
Answer: 40242.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 DM-13203 item 1, 4, 5.   # Generate a meaningful error message when a column filter expression applied to a table is invalid.  This may not require any extra parsing effort for the filter expressions - the system knows the name of the column and the text typed in the filter field, and can just wrap the underlying error message with something like "The filter expression 'xyzzy' applied to column 'foobar' is invalid.".  For the purposes of debugging it may be useful to provide a UI action (e.g., a disclosure triangle) that makes it possible to see the full underlying exception text.   #    #    # Ensure that, when an invalid filter expression is entered, after dismissing the error message the user is returned to the _same state of their data and previously-specified filters as before the failed attempt to construct a filter_.  This does not require arbitrary undos, but only that the displayed state of the table is not changed before the filter has been determined to be valid.   # Do not use the word "Reload" for the button that dismisses the error dialog.  "Back", "Close", "Cancel" would all be better choices.  Consider asking for feedback from others, e.g., Vandana, for this choice.  "Reload" _strongly_ suggests - to me - that the underlying data retrieval operation would be repeated rather than just abandoning the filter attempt.
Answer: 58771.0

User story: "Represent Alert Production in the Lossy Compression Working Group."
Answer: 39265.0

User story: The docstring for {{cameraGeom.utils.makeImageFromCamera}} could be cleaned up (return type specified, binSize and other parameters clarified), and the "Unable to fit image for detector" warning message should include the exact exception message that was raised (figuring out the nature of the problem is difficult otherwise). That {{print()}} should probably also be turned into a log message.
Answer: 109530.0

User story: "Firefly requires a persistent websocket connection to the server in order to function properly.  In the case when the client is disconnected from the server, Firefly should periodically attempt to reconnect.  This can happen when one closes his/her laptop or switching from one network to another.    When Firefly is no connected to the server, there should be an indication showing that it's no longer connected.     "
Answer: 70040.0

User story: "Now that the [new API is alive|https://squash-restful-api-demo.lsst.codes/] we need the {{code_changes}} resources that are consumed by the SQuaSH monitor apps    NOTE: the performance on retrieving the data from the new implementation will be evaluate only after DM-12604 is done"
Answer: 91020.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 [~<USER>:  {code:java}  src/image/TransmissionCurve.cc:93:46: warning: ‘_multipliedByImpl’ overrides a member function but is not marked ‘override’ [-Winconsistent-missing-override]  std::shared_ptr<TransmissionCurve const> _multipliedByImpl(  ^  include/lsst/afw/image/TransmissionCurve.h:237:54: note: overridden virtual function is here  virtual std::shared_ptr<TransmissionCurve const> _multipliedByImpl(  ^  src/image/TransmissionCurve.cc:587:10: warning: ‘write’ overrides a member function but is not marked ‘override’ [-Winconsistent-missing-override]  void write(OutputArchiveHandle & handle) const {  ^  include/lsst/afw/table/io/Persistable.h:134:18: note: overridden virtual function is here  virtual void write(OutputArchiveHandle& handle) const;  ^  src/image/TransmissionCurve.cc:676:10: warning: ‘write’ overrides a member function but is not marked ‘override’ [-Winconsistent-missing-override]  void write(OutputArchiveHandle & handle) const {  ^  include/lsst/afw/table/io/Persistable.h:134:18: note: overridden virtual function is here  virtual void write(OutputArchiveHandle& handle) const;  ^  {code}"
Answer: 2605.0

User story: "WarpCompare has no temporal information for the pixels that are outside the boundary of the psfMatched Warps. These pixels are marked NO_DATA. The BBoxes in the CoaddInputRecorder should be shrunk so that we can have an exact CoaddPsf for sources that fall in the border of calexp. "
Answer: 31757.0

User story: "Use scikit learn to investigate how well different ML algorithms perform as classifiers as a first step towards a complete method that includes all the errors and other information."
Answer: 10221.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Implement the algorithm determined in DM-13406 in software. Doing this will involve looking at the various optimizer options that exist and evaluating what would be the best software package to use."
Answer: 459336.0

User story: Use the priors determined in DM-13404 to work out a procedure for fitting an elliptical Gaussian. This work is likely to be done "on paper" (either real paper, or latex)
Answer: 93264.0

User story: "As it has been many years since I have worked through this branch of optimization, spend some time reading literature on optimization and more specifically optimization using prior probabilities."
Answer: 63566.0

User story: "Using shapes as defined by SdssShape (and HSM when SdssShape has failed) create prior probability distributions for shape given radius, and radius given flux. These distributions should all be psf corrected such that all measurements corresponds to a default gaussian with a fwhm of 4 pixels."
Answer: 63569.0

User story: "The butler gen3 requirements and use cases were reviewed in December 2017. This resulted in some action items and cleanup requests before the document could be baselined. This ticket covers that work."
Answer: 22940.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: "h1. Data    There are two datasets: Ronchi + clear, Ronchi + order blocking filter. We will perform the procedure below for both datasets separately.    Only do this on the photometric nights (per the logs). (That may mean we can only do this for a subset of the objects.)    h1. Data reduction     * Choose photometric data from three runs. (Spend less than 0.5 days choosing data.)   * Flat field & bias subtraction, etc, using dome flats   ** Problems with dome flats (ghosts, etc) are thought to be sub-dominant; we assume they are   * Extract spectra using [~<USER>-magic   * Look at sensitivity of spectra to how we do the extraction (fn of aperture size, etc)   ** (Convince yourself you have spectra whose shape is independent of aperture)   * Ignore data contaminated by second order light above ~700nm   * Generate a wavelength solution allowing for DCR    At this point, we expect to have wavelength calibrated spectra with an unknown wavelength-independent calibration.    h1. Analysis The First   * For each object, find the observation at the median airmass and divide all spectra by the spectrum taken at median airmass.   ** The median observation gives us (The SED * atmosphere of median observation * Detector). Once we've divided each observation by this, we have (The atmosphere/(atmosphere of median observation)).   * We want atmospheric models executed at the same conditions at the same airmass as the observations. Degrade to spectral resolution of the data. Divide each modelled transmission by the model at the median airmass; they should be the same as the previous data.    ** Chris will provide these models using Modtran.   * *Deliverable:* figures which either confirm that they are the same, or which demonstrate they are not. Success criterion is 5% agreement between models and observations.   * *Stretch goal:* repeat with non-photometric conditions.    h1. Analysis The Second     * For each object:   * At each wavelength, we will solve for the intensity as a function of airmass.   * Extrapolate to zero airmass   ** This gives us the product of the SED and the detector.   * Divide each spectrum by the zero airmass spectrum.   ** That gives us atmospheric transmission to be compared to the models above.   * *Deliverable:* the same as Analysis The First.   * *Stretch goal:* the SED “makes sense”, given what we know about the SED and the detector. Plot our prediction relative to these.    h1. Deliverables    * The deliverables described above will be presented on a Confluence page.  * [~<USER>, [~<USER>, [~cstubbs], [~<USER>, [~<USER> will convene at 11:00 Eastern on 5, 12 and (if necessary) 19 Feb to discuss progress."
Answer: 62222.0

User story: "Update the DM Python Style Guide to require {{cls}} as the first argument to metaclass member functions."
Answer: 173892.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "This ticket captures the SPs used during tests of the SQuaSH RESTful API to make sure it works with the datasets and verification jobs currently created in CI. It includes revision of {{nginx}} and {{uwsgi}} configuration and the dimensioning of the cluster node in GKE during the tests.     The first part of the tests was done after DM-12603 and the second part after DM-13275."
Answer: 1.0

User story: "Write the overall framework for the Science Platform test specification, LDM-540, and add the specific content for the LDM-503-1 milestone tests.    A later ticket will cover the context for the 2018 cycles' milestone tests."
Answer: 132931.0

User story: "Following approval of RFC-437, drop {{GaussianCentroid}}."
Answer: 6199.0

User story: "Default {{lsst.verify}} http timeout for SQuaSH API requests was set initially to 30s, a larger timeout is required to upload verification jobs of 500M-1G. It will be set to 900s.    Also, allow 202 (Accepted) status code for these long requests.  "
Answer: 4327.0

User story: "Set  {code:java}  self.doAttachTransmissionCurve = True{code}  in {{SubaruIsrTask}}."
Answer: 4671.0

User story: "Turn on visit-level sky subtraction by default for HSC, which I believe means updating the coaddition configuration to expect its outputs to be available."
Answer: 4226.0

User story: "Implement the first part of RFC-440: update the calibrations in /datasets/hsc/repo"
Answer: 5701.0

User story: "A recent merge has broken docker image build scripts used by developers and Travis and Jenkins CI (undefined variable $DOCKER_RUN_DIR in several Dockerfiles)  "
Answer: 9927.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: "03/21/2019    suit is set up to run Java and Javascript tests.    We have the tests for dbserv and metaserv under suit/src/test. Unfortunately they will not be relevant after Legacy PDAC is eliminated. We need tests for DAX VO interfaces, that we are or will be using.    Known issues affecting LSST TAP search: DM-17295, DM-18447.  Related errors:   * 'SQLException:Query processing error: QI=?: Failed to instantiate query: AnalysisError:Spatial restrictor w/o partitioned table' (DM-17295, test case: spatial restriction on DeepCoadd)   * 'SQLException:Unable to return query results: Failure while merging result' (DM-18447, test case: TOP on sdss_stripe82_01.RunDeepSource)   * sdss_stripe82_01.RunDeepSource has variance for 'ra' has wrong ucd: 'stat.variance;pos.eq' instead of 'stat.variance;pos.eq.ra'.         01/26/2018    We need to create a testing program to test SUIT search processors calling DAX API independent of SUIT UI.     It should be able to test the basic DAX API calls. it should cover some combinations of   * project, database, table name, position for table data   * project, image set, position, cutout size for image data    Additional info:    LSSTDbServTest.java and LSSTImgServTest.java contain DAX API tests relevant to SUIT. Since SUIT uses metaserv to create column constraints table, we need to add tests for metaserv queries. We also need to validate that metaserv and dbserv return are consistent: metaserv table query should not return the columns that are not returned by {{SELECT *}} query to dbserv."
Answer: 601824.0

User story: "Currently we can display the unit for each column in the table display.     It will be very useful to display the data type for each column.     we should use the similar check on/off option for unit display for this option. "
Answer: 259009.0

User story: The {{INEXACT_PSF}} area can be wide, so it might be helpful to be able to distinguish between sources whose footprints just touch this mask, and those whose PSFs are well and truly ruined. For other pixel flags, we use the "center" feature (which checks a 3x3 area around the object center); we should do the same for {{base\_PixelFlags\_flag\_inexact\_psf}}.
Answer: 198.0

User story: "Remove all elements (and associated tests) in current prototype of Butler and Registry that will be redesigned (as opposed to keeping everything working during redesign)."
Answer: 5694.0

User story: "Jenkins flattens GH usernames."
Answer: 49.0

User story: "Now that the butler prototype is becoming the new butler, flake8 tests should be enabled."
Answer: 963.0

User story: "Now that the prototype butler is becoming the gen3 butler we need to rename it to be daf_butler. This requires moving the repository and updating the module hierarchy."
Answer: 1004.0

User story: "02JH has a terrific prepuller design that does not require mapping the socket.  I want to adapt it so that it looks not just for existing images but the current version thereof."
Answer: 46617.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: "Reviewing existing SuperTask prototype and discussing new design and next implementation steps at Middleware design/hack week at Princeton. "
Answer: 8778.0

User story: "Attend meeting in Princeton to discuss butler gen3 and supertask."
Answer: 5831.0

User story: "This ticket is for creating an in-memory datastore and adjusting the tests to run with it and the existing posix datastore.  "
Answer: 260628.0

User story: "This would exercise {{Datastore}} and {{Formatter}} by requiring:    * Pass-through of credentials  * SHA instead of filename  * Serializing into memory rather than file  * Write to file then upload.    Only implement for one or possibly two {{DatasetType}}s."
Answer: 815306.0

User story: "I have received example data from Te-Wei from the current version of phosim.  Master {{obs_lsstSim}} does not work with this.  I need to update the scripts to deal with this version of phosim."
Answer: 156935.0

User story: An example configuration could be:    {code:yaml}  datastore:    cls: 'lsst.butler.datastores.posixDatastore.PosixDatastore'    root: './butler_test_repository'    create: true    storageClasses:      SourceCatalog:        formatter: "lsst.butler.formatters.fitsCatalogFormatter.FitsCatalogFormatter"        cls: lsst.afw.SourceCatalog      Exposure:        formatter: "lsst.butler.formatters.fitsFormatter.FitsFormatter"        cls: lsst.afw.image.Exposure        components:          image: Image          mask: Image          variance: Image          wcs: TablePersistable          psf: TablePersistable          photoCalib: TablePersistable          visitInfo: TablePersistable          apCorr: TablePersistable          coaddInputs: TablePersistable  {code}  
Answer: 38895.0

User story: "Develop and instantiate a monitoring view for NCSA TMG operations staff use."
Answer: 17311.0

User story: "Examples are {{FitsCatalog}}, {{YAML}}, {{Image}}, {{Exposure}}, etc."
Answer: 899041.0

User story: "Implement a prototype that supports {{get/put}} on (optionally) compressed Datasets.    Needs to propagate / store compression options. Butler can possibly use {{ChainedDatastore}} to store both compressed and non-compressed versions.    Interaction with {{Registry}} is a separate ticket."
Answer: 1247573.0

User story: "These are things such as md5sum, object-size, etc. Would be nice if it could be generic. I could imagine something generic like {{Datastore.getInfo(uri) -> BlobInfo}}, or something more specific such as {{Datastore.getSize(uri) -> int}}.    Where should they live? Perhaps in SQL table for {{Datastore}} configuration. Possibly living in the same database as {{Registry}}? Or in some (YAML) config file."
Answer: 93514.0

User story: "Change the unit test logging for qserv to record debug level messages so it is easier to debug intermittent failures. "
Answer: 7564.0