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: "Starting this morning, (2017-07-31 ~ 03:00am EDT), {{pipe_tasks}} on master fails {{tests/testPhotoCal.py}}.  See first attached file ({{consoleText.txt}} for full log from Jenkins job.  second attached file {{pipe_tasks_failure_build.log}} for the same error with a local build on my desktop."
Answer: 3445.0

User story: "Use cert from DM-11423."
Answer: 3887.0

User story: "Obtain a new 1yr tls cert for *.lsst.codes."
Answer: 1.0

User story: "Once we have useable coadds from the HiTS 2014 fields matching our HiTS 2015 dataset, these should be used as templates for the AP prototype pipeline (soon to be {{ap_pipe}}). The pipeline will still accept another visit as a template, but the default will be to use the coadds from a specific location in the dataset repo."
Answer: 167247.0

User story: obs_lsstSim tests that "raft", "sensor", and "channel" are of type `str`, but this fails in python 2.7 since these may be unicode.
Answer: 304.0

User story: "Add additional DocuShare roles to Documenteer. Make it so that any {{ls.st}} functionality is available from reStructuredText (support LTS, LEP, LCA, DMTN, SQR, Document, etc.)"
Answer: 149.0

User story: "Add defects files as tarball in calib directory."
Answer: 57360.0

User story: "Do a storage analysis, similar to DM-10904, for an output repo from a HSC RC reprocessing     "
Answer: 20032.0

User story: "Follow up on security vetting actions."
Answer: 41821.0

User story: "After the merge of DM-11300, validate_drp has dropped the repo from the output filename.  Thus, {{<repo>_<filter>.json}} has become {{_<filter>.json}}."
Answer: 10102.0

User story: "A variety of issues with verify-worker nodes have appeared in June and July, e.g., hardware issues and troubleshooting for verify-worker10, DIMM errors on verify-worker05, etc. Doagnose and address."
Answer: 1.0

User story: "Security vetting of the DAQ system revealed issues with iptables, etc., that also exist on the lsst-dev systems. This story covers the discovery and followup activities to remedy the issues."
Answer: 7.0

User story: "Formatters are described some in DM-4542, and implemented for {{RepositoryCfg}} as {{RepositoryCfgPosixFormatter}} (in {{fmtPosixRepositoryCfg.py}}. But they are not documented in LDM-463, they need to be documented there. They are also not used in the general case ({{read}} and {{write}}) in PosixStorage, only for getting the repositoryCfg.  For this story: document formatters and create an implementation plan for PosixStorage.  (they do not need to be implemented in SwiftStorage right now because SwiftStorage just defers to PosixStorage)"
Answer: 59223.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: "jenkins started failing to fetch on pre-existing lsst/lsstsw clones this  morning.  This is first time this failure mode has been observed.    This jenkins jira issue suggests that the problem is specific to the  version of git shipped with el7 when doing a shallow clone/fetch over  http[ s ]:    https://issues.jenkins-ci.org/browse/JENKINS-37229    Current jenkins master:      {code:java}      $ cat /etc/redhat-release      CentOS Linux release 7.1.1503 (Core)        $ git --version      git version 1.8.3.1        $ git fetch --tags --progress https://github.com/lsst/lsstsw.git +refs/heads/*:refs/remotes/origin/* --depth=1 --verbose      POST git-upload-pack (gzip 16429 to 5558 bytes)      POST git-upload-pack (gzip 17233 to 5661 bytes)      POST git-upload-pack (gzip 18033 to 5754 bytes)      POST git-upload-pack (gzip 19633 to 5938 bytes)      POST git-upload-pack (gzip 22833 to 6302 bytes)      fatal: git fetch-pack: expected shallow list  {code}  "
Answer: 1.0

User story: "As shown in DM-11272, the QA dashboard prototype (DM-10619) is not scalable to a whole tract of data.  One solution to this is to plot density plots rather than scatter plots, using bokeh+datashader.  For this ticket, make a simple bokeh server app with just a single datashader density plot of the whole-tract catalog with configurable X- and Y-columns."
Answer: 6972.0

User story: "The new deblender API appears to have large residuals in most blends and completely fails in certain cases, even when using identical constraints. This ticket will attempt to identify and fix these issues."
Answer: 4150.0

User story: "DM-4141 introduced a {{sys.exit}} call in {{CmdLineTask.parseAndRun}} which provides a Unix exit code, but also appears to bring down the MPI layer before it can finish up. We need to disable this feature for ctrl_pool."
Answer: 1238.0

User story: "The HSC production run just hit DM-11369, so we need to get the fix released."
Answer: 1337.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 reference catalogs supplied with the twinkles data I have are in the a.net format, and do not contain flux errors. When we update them to the new style format, we should also add flux errors of some sort, so that they can be used with jointcal's new photometry system.         Update: after much thought and discussion, we decided that the twinkles1 jointcal testdata no longer serves a useful purpose, and is holding us up from removing a.net refcats and {{obs_lsstSim}}. Instead of trying to update the included refcat (the HTM indexed version that [~<USER> found was not a drop in replacement), I'm going to delete the twinkles data and tests all together. We'll be getting some DC2 data built on obs_lsst soon enough, and we will have to write entirely new tests for that anyway."
Answer: 828000.0

User story: "Currently, we have showHistogram and showXYPlot. We need to add a method that can show any Plotly multitrace chart, connected to a Firefly table or with predefined data.    The function will accept plotlyData array, plotlyLayout object, and optional fireflyData array. It will assume that the tables, which are referenced by plotlyData (or fireflyData fields) are being fetched in a separate call.    For examples check firefly/demo/ffapi-highlevel-charttest.html"
Answer: 22960.0

User story: "Many of the reference catalogs provided with {{testdata_jointcal}} are in the old astrometry.net format, which is now deprecated. We should update those provided refcats to the new style format, which will also simplify the test configuration."
Answer: 799208.0

User story: "This ticket follows on DM-11077 for review and editing treatment to the multi-band analysis tutorial in the Getting Started tutorial series.    Draft: https://pipelines.lsst.io/v/DM-11393/getting-started/multiband-analysis.html"
Answer: 312944.0

User story: "This ticket follows on DM-11034 for reviewing and editing work of the display tutorial in the pipelines.lsst.io getting started series.    Draft content: https://pipelines.lsst.io/v/DM-11392/getting-started/display.html"
Answer: 312473.0

User story: "This ticket follows DM-10637, the addition of a Getting Started tutorial series based on DMTN-023, and is a means for reviewing that work before it is merged.    Draft content root: https://pipelines.lsst.io/v/DM-11391/getting-started/index.html"
Answer: 312478.0

User story: "Update the prototype pipeline (soon to be {{ap_pipe}}) so it works when a user runs the {{verify_ap}} script from the command line.    Also write some tests for {{ap_pipe}} since none currently exist!"
Answer: 83700.0

User story: "Extend the design sketch for the new data repository database system to camera-specific units of data, demonstrating that it is a viable solution to the data-relationship problem identified by the SuperTask WG."
Answer: 50126.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 behavior of {{shebangtron}} is mangle all {{#!}} statements.  This breaks {{scons}} in an otherwise py3 based installation.    Steps to reproduce:    {code:java}  git clone https://github.com/lsst/base.git  cd base/  setup -k -r .    $ scons  scons: *** SCons version 2.5.0 does not run under Python version 3.5.2.  Python 3 is not yet supported.  {code}    "
Answer: 13344.0

User story: "Attend, prepare and host the local DAQ installation workshop at NCSA, July 18-20, 2017"
Answer: 4.0

User story: "As per RFC-308, we will remove the trailing repo from butler root /datasets/decam/repo  "
Answer: 44460.0

User story: "As per RFC-308, we will remove the trailing repo from butler root /datasets/ctio0m9/repo  "
Answer: 1355534.0

User story: "As per RFC-308, we will remove the trailing repo from butler root /datasets/comCam/repo"
Answer: 1355534.0

User story: "In DM-8289 we switched the order of operations when PSF-matching warps to warp first and PSF-match second (so that we don't undo the matching by warping).  I add a config parameter matchThenWarp  to invoke the old behavior while while the epic was in progress.  Now, that that it has been tested, it is time to remove the matchThenWarp branch. "
Answer: 2901.0

User story: "There is a 90 minute session at LSST 2017 about AP Verification Metrics.  This ticket is to plan and prepare for the session, which includes    * determining how to structure the session; meeting organizers sent suggestions  * inviting relevant non-AP staff to attend (esp. SQUARE)  * preparing relevant talks and/or demos  * aggregating and summarizing feedback after the session"
Answer: 53099.0

User story: "* https://ci.lsst.codes/job/stack-os-matrix/25405/label=centos-7,python=py2/consoleFull  * https://ci.lsst.codes/job/stack-os-matrix/25498/label=centos-7,python=py2/consoleFull    This appears to be due to a race condition in writing the packages. {{lsst.skymap}} is only {{import}}-ed before {{Task}} execution once: in {{makeSkyMap.py}}. If that runs at the same time as something else that's updating the packages, the skymap package version could be overwritten."
Answer: 1168.0

User story: In Firefly catalog searches, it allows user to enter position to search on tables without position information, e.g., "Gaia G-band Time Series of Variable Sources".     In irsaviewer, it returned error   "Fail to load table. Error: edu.caltech.ipac.firefly.server.query.DataAccessException: DataAccessException:Unexpected error from:unknown"    In current dev version, it continues until put in background monitor, then the "Unexpected error" appears. Another ticket DM-11376 was  created for the backgrounding bug.  
Answer: 181817.0

User story: "So as to not 'orphan' pre-existing {{newinstall.sh}} installs that have an {{EUPS_PKGROOT}} pointed at {{sw.lsstcorp.org}}, an http redirect should be put in place to the new URL.    [~<USER> has agreed to change the {{sw.lsstcorp.org}} CNAME when we are ready.  [~<USER> has provided a copies of the tls private key/cert."
Answer: 20363.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 we envision {{ap_pipe}} as a library of functions that may be called by {{ap_verify}} or other drivers. It will likely be useful to be able to test {{ap_pipe}} independently of {{ap_verify}}.  This ticket is to add a CommandLineTask utility within the {{ap_pipe}} package that utilizes the package library functions."
Answer: 233525.0

User story: "Decide what to include (probably just the overlap fields being used in {{verify_ap}}?), issue RFC, and package according to https://developer.lsst.io/services/datasets.html"
Answer: 53612.0

User story: Based on this:  http://flask.pocoo.org/docs/0.12/patterns/apierrors/    All the blueprint methods in imgservREST_v0.py should be decorated with a handler similar to the one as follows:    @app.errorhandler(ValueError)  def handle_invalid_input(error):      response = jsonify({"exception": "ValueError", "message":error.args[0]})      response.status_code = 400  # ValueError == BAD REQUEST      return response  
Answer: 1744.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> reports this error:  {code}  [lsstprod@cca010 ~]$ cd /sps/lsst/dev/lsstprod/hsc/SXDS/utils/assembleCoadd  [lsstprod@cca010 assembleCoadd]$ source setup.sh  [lsstprod@cca010 assembleCoadd]$ assembleCoadd.py _parent/output --output _parent/output --id filter=g tract=0 patch=9,6 @g.list --clobber-config --doraise  [...]  safeClipAssembleCoadd INFO: Found 7943 potential clipped objects  Traceback (most recent call last):    File "/sps/lsst/software/lsst_distrib/w_2017_28/stack/miniconda3-4.2.12-7c8e67/Linux64/pipe_tasks/13.0-44-g89df7c8/bin/assembleCoadd.py", line 65, in <module>      SafeClipAssembleCoaddTask.parseAndRun(args=extra[1:])    File "/sps/lsst/software/lsst_distrib/w_2017_28/stack/miniconda3-4.2.12-7c8e67/Linux64/pipe_base/13.0-9-g1c7d9c5+11/python/lsst/pipe/base/cmdLineTask.py", line 514, in parseAndRun      resultList = taskRunner.run(parsedCmd)    File "/sps/lsst/software/lsst_distrib/w_2017_28/stack/miniconda3-4.2.12-7c8e67/Linux64/pipe_base/13.0-9-g1c7d9c5+11/python/lsst/pipe/base/cmdLineTask.py", line 223, in run      resultList = list(mapFunc(self, targetList))    File "/sps/lsst/software/lsst_distrib/w_2017_28/stack/miniconda3-4.2.12-7c8e67/Linux64/pipe_base/13.0-9-g1c7d9c5+11/python/lsst/pipe/base/cmdLineTask.py", line 373, in __call__      result = task.run(dataRef, **kwargs)    File "/sps/lsst/software/lsst_distrib/w_2017_28/stack/miniconda3-4.2.12-7c8e67/Linux64/pipe_base/13.0-9-g1c7d9c5+11/python/lsst/pipe/base/timer.py", line 121, in wrapper      res = func(self, *args, **keyArgs)    File "/sps/lsst/software/lsst_distrib/w_2017_28/stack/miniconda3-4.2.12-7c8e67/Linux64/pipe_tasks/13.0-44-g89df7c8/python/lsst/pipe/tasks/assembleCoadd.py", line 344, in run      doClip=self.config.doSigmaClip)    File "/sps/lsst/software/lsst_distrib/w_2017_28/stack/miniconda3-4.2.12-7c8e67/Linux64/pipe_tasks/13.0-44-g89df7c8/python/lsst/pipe/tasks/assembleCoadd.py", line 1118, in assemble      result = self.detectClip(exp, tempExpRefList)    File "/sps/lsst/software/lsst_distrib/w_2017_28/stack/miniconda3-4.2.12-7c8e67/Linux64/pipe_tasks/13.0-44-g89df7c8/python/lsst/pipe/tasks/assembleCoadd.py", line 1261, in detectClip      if numpy.max(overlap[clipIndexComp]) < self.config.maxClipFootOverlapDouble:    File "/sps/lsst/software/lsst_distrib/w_2017_28/python/miniconda3-4.2.12/lib/python3.5/site-packages/numpy/core/fromnumeric.py", line 2297, in amax      out=out, **kwargs)    File "/sps/lsst/software/lsst_distrib/w_2017_28/python/miniconda3-4.2.12/lib/python3.5/site-packages/numpy/core/_methods.py", line 26, in _amax      return umr_maximum(a, axis, None, out, keepdims)  ValueError: zero-size array to reduction operation maximum which has no identity  {code}    On investigation, this appears to be due to a logic error in the code ({{<}} instead of {{<=}}).
Answer: 1311.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: "Following DM-11355, the {{EUPS_PKGROOT}} used to distribute the stack has changed to {{https://eups.lsst.codes/stack/src/}}. Update the shared stack on {{lsst-dev01}} (and Tiger/Perseus, for Princeton users) to pull from that."
Answer: 9845.0

User story: "At present, the weekly release tags are published into the published eups tarball repos but there is no current/latest release tag along the lines of `latest` or `w_latest`."
Answer: 456715.0

User story: "Sync the new calibs for HSC extending into 2017 April at {{/scratch/pprice/CALIB-LSST-20170105}} into {{/datasets/hsc/calib/20170105/}}"
Answer: 47792.0

User story: "Excellent tutorial from udacity  https://classroom.udacity.com/courses/ud615  covering:    - Introduction to microservices  - Building the containers with docker  - Kubernetes  - Deploying microservices    https://github.com/udacity/ud615/tree/master/kubernetes    Kubernetes concepts (pods, secrets, configmaps, depoloyment, services, etc.)  https://kubernetes.io/docs/concepts/    Tutorial on minikube:  https://kubernetes.io/docs/tutorials/stateless-application/hello-minikube/    Another tutorial on minikube and development workflow:  https://github.com/udacity/ud615/tree/master/kubernetes    Kubernetes: Up and Running book:  https://www.safaribooksonline.com/library/view/kubernetes-up-and/9781491935668/  - Pods  - Secrets"
Answer: 2.0

User story: "Covered the following tutorials from:    https://www.safaribooksonline.com/library/view/learning-path-devops/9781786463937/video1_16.html?autoStart=True    Chapter 1 : Beginning Docker     Getting Docker Inside a Vagrant VM    Containers Versus Virtual Machines    How Docker Works?    Running the Containerized Commands   Managing Your Containers   Committing Changes to a Container Image   Sharing a Container on the Index   Finding and Using Third-party Containers   Writing and Building a Dockerfile   Adding Files to Your Container   Setting Default Container Properties    Building on Existing Containers    Setting Up Trusted Builds    Using Volumes and Mounts    Ports and Networking   Linking Containers     And Chapter 2. Creating and running containers on Kubernetes    from Kubernetes Up and Running:    https://www.safaribooksonline.com/library/view/kubernetes-up-and/9781491935668/ch02.html    "
Answer: 1.0

User story: "See  DM-11531 which will be implemented first."
Answer: 800712.0

User story: "CatalogCalculation plugins can get added to the schema in non deterministic order. The completion criteria for this ticket is when the ordering of catalog calculation keys in a schema remains constant for a constant list of plugins to run."
Answer: 1208.0

User story: "Provide access to developer-specified GPFS directories for datasets, home directories, and scratch directories."
Answer: 1.0

User story: "Allow CI to build/deploy JupyterHub"
Answer: 42061.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 recent change in {{AstrometryTask.solve}} increases the exposure bounding box by the matcher's maximum offset ({{matcher.maxOffsetPix}}. However, a parameter already exists to provide this growth in the reference catalog loader ({{refObjLoader.pixelMargin}}). Because the exposure bounding box is increased artificially after recording the catalog loading radius, loading the normalised persisted matches results in [many missed matches|https://community.lsst.org/t/coadddriver-py-error-hsc-data-processing/2093/9].    To fix this:  * Remove the additional grow  * Set the default {{refObjLoader.pixelMargin}} to match the default {{matcher.maxOffsetPix}}.  * Add notes advising the user that the two parameters should be linked.  * Stop {{AstrometryTask}} from reaching into the responsibility of the reference catalog loader (it shouldn't need to know about the details of the {{refObjLoader}} configuration)."
Answer: 62275.0

User story: "The {{w_2017_29}} tag failed due to this error message from {{lsst-dev}}:    {code:java}    notice: lsstsw tools have been set up.  eups distrib create: Server directory /lsst/distserver/production does not exist; creating   eups distrib: [Errno 13] Permission denied: '/lsst'  {code}  "
Answer: 2971.0

User story: "When you get an error from a callback there's a missing set of quotes that prevent you from cutting-and-pasting the command to help with debugging.    Please add the missing two characters.  "
Answer: 926.0

User story: "The code which updates the amplifier bounding boxes when CCDs are assembled mis-handles flipped amplifiers when the data is pre-assembled (i.e. like HSC/PFS Hamamatsu or CFHT), but unlike LSST.    Please fix this."
Answer: 38839.0

User story: "When there is no Wcs associated with an image being displayed, please write a simple linear WCS that displays the LSST 0-indexed coordinate system.    This has the important side effect of working round a ds9 bug whereby  {{WCSA/B}} are not displayed in there is no {{WCS}}"
Answer: 3942.0

User story: "When we moved to 32-bit masks the test coverage failed to reveal that the code in afw that drives ds9 was not updated.    Please fix this.  "
Answer: 169.0

User story: 1. After changing to Time Series Tool tab in PDAC, clicking on "Add Marker" does not do anything on the image.     It works in the PDAC source search result.   It also works in the IRSA Time Series Tool in operation.     2. on Time Serial Tab tool, select one image, and click on at 'Lock by click'. Add a Point marker on the image.      'Manipulate Overlap display' icon is shown with '2' at the icon corner. Click the icon, and click 'delete' by the layer of Selected Point'. The point marker is gone, and  'Lock by click' still shows 'checked'.     Add another point marker on the image, no marker is not added.
Answer: 46062.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: 1. Search WISE source from PDAC, m81  2. Highlight one source, click on the "View Time Series ..." button for that source  3. change to the time series tab  Several issues:    1. The overlay position is not the same as the position of the selected source from the search result, (previous tab). What is it?  2. change the number of images displayed to 1, use arrow key to go down the table, the displayed image jumps around, sometimes is in the middle of the image display area, sometimes is at the left side, sometimes at the right side.  3. click on "Lock by Click" option to lock on a point. click on the image to see the position. then use cursor to go down the table, the "selected point" is in the layer dialog, but the point is not overlaid on the image.      Bug #2 does not appear in the IRSA operation version of time series tool for uploaded  table data. It looks to me it was introduced after the IRSA release.    Regarding issue 3,   All kinds of overlays ( 'Select Area', 'Distance Tool', 'Marker', 'Footprint', 'Region', 'NorthUpCompass', and 'Web Grid') in addition to 'selected point' in current Firefly development has the similar issue as stated. This issue will be fixed for those overlay cases.   
Answer: 19875.0

User story: "We now have eotest callable from within the DM Stack. Fix its driver script for producing PDF reports to work with the data products as stored by stack execution, and use this to demonstrate that it's doing the same thing as the stand-alone eotest.  "
Answer: 211590.0

User story: Before starting to write tasks to produce some of the items in the list on DM-10895, the current state of both calib production (the {{pipe_drivers}} scripts) and their application in {{isr}}, as well as other parts of {{isr}} (e.g. overscan subtraction) need to be validated.    For this ticket, use obs_comCam to pull up biases, darks and flats for the TS8 data and look at them. (this means both the raws and the masters).    Look at the overscan regions, examine their properties: what do their historgrams look like, how well described are they by a constant, a line, a ploynomial, a spline? What is their 2D structure like? Are they all the same as each other? Is each one the same for each run? Is there evidence of the "bias instability"?    What do dark-subtracted darks look like?    What do flat-fielded flats look like?    By the end of this ticket we will know more about all of this, but probably not everything about everything.
Answer: 185412.0

User story: "Effectively the same as DM-11297, but for AP."
Answer: 15443.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 are currently processing what is known as the HSC RC dataset, where RC ==> Release Candidate, on a bi-weekly basis (for all even numbered weeklies). See [https://confluence.lsstcorp.org/display/DM/Reprocessing+of+the+HSC+RC+dataset] for full details. The purpose of this processing is to have a fully processed dataset as the pipeline evolves and be able track any quality/performance changes (for better or for worse - to properly praise/bless the former and catch & fix/revert the latter). Clearly, the dataset involved should be representative of the widest range of data quality/observing conditions expected, and is currently available to us through public HSC data. The RC dataset we have been using is not satisfactory in this respect. This issue is to remedy this situation by redefining (and perhaps renaming? RC ==> CI ??) the set of HSC tracts/visits to include in our bi-weeklies processing.    A list of known data "characteristics" that this dataset should cover include tracts that suffer from the known issues to date, including:   - a very well-behaved tract   - a tract that includes visits that have proven challenging for astrometric fitting (see DM-11090)   - a tract that includes visits that have proven challenging for photometric fitting (see DM-11927)   - a tract including "too-good-seeing" visits (see DM-9855)   - a tract including a wide range in seeing conditions (to test PSF-matching, see DM-8289)   - tracts covering a range of "challenges" for deblending (possibly those identified in DM-9168)   - a tract at the survey's edge (to check for issues arising due to patchy coverage - verify if 8766 WIDE still fills this bill)   - a tract including galaxies suitable for assessing total magnitudes for "big" galaxies (list of examples along with "best" total magnitude estimates to be compared against being compiled by HSC member Song Huang)   - a tract with observations in both the old i and new i2 HSC filters (see RFC-390)   - PLEASE ADD YOUR FAVORITE PATHOLOGY HERE    We will have to keep this dataset to a reasonable size (perhaps [~<USER> could comment on what "reasonable" means to her in numbers?) While we will certainly want to add pathological areas as we find/gain access to them (e.g. crowded fields), the set we define and agree upon here will be considered the canonical one until a need to expand/redefine is identified.
Answer: 279352.0

User story: "We decided to store refcats as tarballs of HTM-indexed fits catalogs in the `ref_cats` directory. Update the README's and add a small example tarball into the directory."
Answer: 10170.0

User story: "With default hsc setup, running measureCoaddSources.py without data requires {{ref_cat_config}}.  Add this dependency to the pre-run of measureCoaddSources.py in the pegasus workflows."
Answer: 20.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "I just noticed that the choice of interpolation kernel used for CoaddPsf (in {{makeCoaddTempExp.py}} and {{assembleCoadd.py}}) is not configurable. For undersampled data we'll want to dial that back from the default {{lanczos3}} to {{bilinear}}, so it needs to be configurable."
Answer: 482.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: "Following {{obs_subaru}}, it would be nice to change the configuration files of {{obs_decam}} so to also use the PS1 catalog in LSST format and remove dependence on astrometry.net."
Answer: 51493.0

User story: "After DM-11163 (and its related tickets), visitInfos are created for calibs (we need darkTimes and expTimes etc).    However, some of the metadata in the {{testdata_cfht}} contains values which make {{makeRawVisitInfo}} unhappy. Luckily, the {{megacamMapper}} had a {{_standardizeDetrend}} method for stripping out this which upset things downstream.    This ticket just adds the {{TELEAZ}} and {{TELEALT}} keywords to those removed. This should only be called for biases, and therefore not upset anything else."
Answer: 34.0

User story: "Pin documenteer >0.1,<0.2 in these projects to preserve existing assumptions about dependencies.    For technotes, the right approach might be to update to documenteer 0.2 and make the necessary changes to their conf.py files."
Answer: 25680.0

User story: "With the recent increase in mask size, it's become more important to start compressing MaskedImages and Exposures.    A recent-ish discussion on Slack revealed that we can enable HDU-level lossless compression with no quantization and still have CFITSIO do all the work:    https://lsstc.slack.com/archives/C2JPL2DGD/p1496857629076802    (see in particular [~<USER>'s experiment about a page down from the start of the conversation).    In terms of how this works in our code, I think we should do the following:   - Images, Masks, MaskedImages, and Exposures (or at least the latter three) should be written with lossless HDU-level compression enabled by default.   - We should add a {{flags}} argument to the {{writeFits}} method that controls whether compression is enabled (much like {{SourceCatalog}}'s flags that control whether to write (Heavy)Footprints), and use the same tricks to allow those flags to be propagated through {{butler.put}} calls.   - All routines that read the various image classes should transparently handle both compressed and uncompressed images.    Some things to check after doing the work:   - We need to still be able to read files written with old versions of the pipeline.   - Reading subsets of images (especially in coadditoin) shouldn't be *too* much slower (hopefully we can control this a bit changing the tile size/geometry.    [~price], we ([~<USER>, [~<USER> and [~<USER>) thought you'd be a good candidate for this, and [~<USER> agreed that it'd be something HSC could support you doing.  Mind putting it somewhere on your stack of things to do?"
Answer: 72467.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "In order to test the deblender on a large patch of HSC data (see DM-11909), a new task {{MultibandDeblendTask}} needs to be created that takes a collection of catalogs as an input to run the new deblender. This ticket will result in the creation of the task, including a modification to {{MultibandDriver}} that will call {{MultibandDeblenderTask}} after merging the coadd catalogs, and before calling {{MeasureCoaddSources}} (as opposed to the current scheme, which calls {{SourceDeblendTask}} inside of {{MeasureCoaddSources}}."
Answer: 187729.0

User story: {code}  im = afwImage.ImageF(10, 20)  ima = im.array    afwImage.ImageF(ima)  afwImage.Image(ima, dtype=ima.dtype)  {code}  fails with  {code}  ----> 5 afwImage.Image(ima, dtype=ima.dtype)    /Users/lsst/products/DarwinX86/miniconda/latest/envs/lsst-13_0/var/opt/eups/DarwinX86/utils/13.0-7-gd7d2357/python/lsst/utils/wrappers.pyc in __call__(self, *args, **kwds)      272         if cls is None:      273             d = {k: v for k, v in zip(self.TEMPLATE_PARAMS, key)}  --> 274             raise TypeError("No registered subclass for {}.".format(d))      275         return cls(*args, **kwds)      276     TypeError: No registered subclass for {'dtype': dtype('float32')}.  {code}  
Answer: 475626.0

User story: "Create a microservice with two containers one for the bokeh server and another one for nginx. Automate the deployment on kubernetes. Make it work locally on minikube and on GKE.  "
Answer: 9916.0

User story: "I want to know the dimensions of the image without reading the entire image and without parsing the header myself."
Answer: 7049.0

User story: "This involves restructuring the `decam_hits` package to match the layout in https://github.com/lsst/templates"
Answer: 33099.0

User story: "As we generalize the prototype AP pipeline to non-DECam, non-HITS datasets we should have a more general name than `decam_hits`.  I suggest `ap_pipe`."
Answer: 33102.0

User story: "Provide a way to automatically determine presented kernels."
Answer: 10337.0

User story: "For qa analysis it is useful to have plots and statistics based solely on the objects that were used for any particular calibration.  We have so far been making *calib_psfUsed*-only plots as the PSF modeling was the only provided such a flag in the output catalogs.  As of DM-9050, we now also have *calib_astrometryUsed* & *calib_photometryUsed* flags for the astrometry and photometry fitting.  This issue is to add the relevant/useful plots to the analysis scripts based on these objects."
Answer: 91959.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "When we begin analyzing metrics for {{verify_ap}}, those metrics will need to have metadata on the job being run. This could include the dataset/camera/filter IDs (see [SQR-019|https://sqr-019.lsst.io/]), provenance and pipeline version (see [Community post|https://community.lsst.org/t/package-version-tracking-and-checking-stack-provenance/840]), and information about the server running the pipeline (requested on {{#dm-squash}} to control for environmental effects on performance metrics).    This ticket is to decide a coherent strategy for delivering metadata to {{verify_ap}}'s {{verify.Job}} object, and then adding the necessary infrastructure to {{verify.ap.metrics}}. We may need multiple sources of information; for example, reporting camera IDs could naturally be a feature of the {{verify.ap.Dataset}} class, and ultimately read from config files, while server information should be foolproof to keep arbitrary users from masquerading as official trial runs."
Answer: 737369.0

User story: "Make one coadd patch both ways, subtract, verify that the residuals are negligible."
Answer: 174256.0

User story: "Recreate characteristic CModel test plots described in https://github.com/dr-guangtou/synpipe/blob/master/draft/synpipe_submit.pdf based on the LSST stack.    Input data is the latest HSC RC dataset at time of carrying out this work: see https://confluence.lsstcorp.org/display/DM/Reprocessing+of+the+HSC+RC+dataset for details."
Answer: 149713.0

User story: "This will demonstrate that the Synpipe machinery and supporting scripts has been properly ported to LSST.    https://github.com/dr-guangtou/synpipe/blob/master/draft/synpipe_submit.pdf"
Answer: 143602.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: Attempting to process a ccd in the repo {{/datasets/decam/repo}} with {{w_2017_28}} failed with the following:  {code:java}  Traceback (most recent call last):    File "/software/lsstsw/stack/Linux64/pipe_tasks/13.0-44-g89df7c8/bin/processCcd.py", line 25, in <module>      ProcessCcdTask.parseAndRun()    File "/software/lsstsw/stack/Linux64/pipe_base/13.0-9-g1c7d9c5+11/python/lsst/pipe/base/cmdLineTask.py", line 509, in parseAndRun      parsedCmd = argumentParser.parse_args(config=config, args=args, log=log, override=cls.applyOverrides)    File "/software/lsstsw/stack/Linux64/pipe_base/13.0-9-g1c7d9c5+11/python/lsst/pipe/base/argumentParser.py", line 521, in parse_args      self._processDataIds(namespace)    File "/software/lsstsw/stack/Linux64/pipe_base/13.0-9-g1c7d9c5+11/python/lsst/pipe/base/argumentParser.py", line 626, in _processDataIds      dataIdContainer.makeDataRefList(namespace)    File "/software/lsstsw/stack/Linux64/pipe_base/13.0-9-g1c7d9c5+11/python/lsst/pipe/base/argumentParser.py", line 137, in makeDataRefList      refList = list(butler.subset(datasetType=self.datasetType, level=self.level, dataId=dataId))    File "/software/lsstsw/stack/Linux64/daf_persistence/13.0-25-g49e493d/python/lsst/daf/persistence/butler.py", line 1471, in subset      return ButlerSubset(self, datasetType, level, dataId)    File "/software/lsstsw/stack/Linux64/daf_persistence/13.0-25-g49e493d/python/lsst/daf/persistence/butlerSubset.py", line 96, in __init__      idTuples = butler.queryMetadata(self.datasetType, fmt, self.dataId)    File "/software/lsstsw/stack/Linux64/daf_persistence/13.0-25-g49e493d/python/lsst/daf/persistence/butler.py", line 1211, in queryMetadata      tuples = repoData.repo.queryMetadata(datasetType, format, dataId)    File "/software/lsstsw/stack/Linux64/daf_persistence/13.0-25-g49e493d/python/lsst/daf/persistence/repository.py", line 259, in queryMetadata      ret = self._mapper.queryMetadata(*args, **kwargs)    File "/software/lsstsw/stack/Linux64/daf_persistence/13.0-25-g49e493d/python/lsst/daf/persistence/mapper.py", line 127, in queryMetadata      val = func(format, self.validate(dataId))    File "/software/lsstsw/stack/Linux64/obs_base/13.0-33-g9f98c6c/python/lsst/obs/base/cameraMapper.py", line 382, in queryClosure      return mapping.lookup(format, dataId)    File "/software/lsstsw/stack/Linux64/obs_base/13.0-33-g9f98c6c/python/lsst/obs/base/mapping.py", line 222, in lookup      result = self.registry.lookup(properties, self.tables, lookupDataId, template=self.template)    File "/software/lsstsw/stack/Linux64/daf_persistence/13.0-25-g49e493d/python/lsst/daf/persistence/registries.py", line 361, in lookup      cursor.execute(cmd, valueList)  sqlite3.OperationalError: no such column: object  {code}    DM-5883 may have caused this because it added new columns to the registry and hence the need to rebuild the registry.    The same processCcd command worked with {{w_2017_14}}
Answer: 53179.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: "Generally validate that the new version of obs_comCam is doing what it should be, including:    - Use calibs from DM-9872 to run {{ProcessCcdTask}} on flat field & Fe55 data, check that results are sensible.    - Discuss what else should be done with respect to poking at TS8 data with [~<USER>, and add to this ticket."
Answer: 3271.0

User story: Apply the suite of existing QA plots to the regular RC processing being carried out at NCSA.    Look for ways we could boil down the statistics being calculated to a number of metrics which are (fairly) reliable at catching actual problems.    Devise a "QA procedure" which we can apply regularly to sanity check the output of each RC run with minimal human intervention.
Answer: 995619.0

User story: Including:    * Different PSFs  * Different weights  * More realistic distortions    These should be complex ("non-trivial"), but not necessarily realistic.    If issues are encountered when running any of these, file new tickets for further investigation.
Answer: 198678.0

User story: "Make a deep training set for BFD with different noise properties than the main sample, and make it possible for BFD to run with this training set."
Answer: 191709.0

User story: "The aim here is to see if this can be used to explain the high shear biases seen in metacalibration based measurement.    Try, for example:    * Write a one-off alternate implementation of the coaddition code and check by manual testing that it gives the same results.  * Test that PSFs are added correctly.  * Make single depth coadds where you just resample and don't add images."
Answer: 191748.0

User story: CILogon added isMemberOf claim to users who authenticated from "National Center for Supercomputing Applications" identity provider.  Setup PDAC so that it will only grant access to user who is a member of 'lsst_pdac'.
Answer: 11247.0

User story: "DM-3705 brings the ndarray NumPy API up to level 1.7. This allows us to suppress the warnings about it by forcing that API level to be used. Unfortunately, that requires sticking {{#define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION}} at the top of every module that uses ndarray.    Find some way to do this and do it."
Answer: 458700.0

User story: "There is a swig-problem-workaround in {{CalibTask.updateMetadata}} that should be removed now that we're using pybind11 everywhere (it survived this long because I fixed the {{VisitInfo}} stuff for PFS that was still using swig).  "
Answer: 1692.0

User story: "Need to add directory for calibs and templates."
Answer: 55.0

User story: "Per discussion on slack, it is OK to migrate the {{validate_drp}} build for squash results to py3."
Answer: 59543.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 {{#runOneRepo}} function has {{outputPrefix=None}} in its signature:    https://github.com/lsst/validate_drp/blob/d179ec1a66ecc19a12565113329be2cd3073c715/python/lsst/validate/drp/validate.py#L162    Then immediately enters into a loop that uses {{outputPrefix}} as a receiver without checking to see if it is a valid object.    https://github.com/lsst/validate_drp/blob/d179ec1a66ecc19a12565113329be2cd3073c715/python/lsst/validate/drp/validate.py#L203"
Answer: 4390.0

User story: "The {{ExposureInfo}} code assumes that there's a {{DATE-OBS}} keyword in the headers which generates warnings for things like biases and flats that don't have such a keyword.    It'd be possible to work around this, but science frames (from imagers and spectrographs) should always have a time stamp so in this case I think it's simpler just to put in a clearly irrelevant date -- you can't use an invalid date as we check for that.  "
Answer: 291.0

User story: "For WISE images PDAC in  PDAC v2, the input cutout size was ignored for the coadded images. steps to repeat:  # select WISE images in LSST search panel  # user target m51, input cutout size 600 arcsec  # then use the same target, do NOT specify size  # Compare the images returned, they are the same    The 600arcsec images should be much smaller, and show a pretty spiral galaxy  "
Answer: 12849.0

User story: "Implement Python threading into while loops for checking messages on topics using DDS/OpenSplice."
Answer: 21569.0

User story: "Prepare an LCR describing the WBS, budget, etc for the DRP replan."
Answer: 21091.0

User story: In {{CameraMapper.search}} I see:  {code}  self.log.debug("Loading %s registry from %s", description, path)  {code}  but  {code}  self.log.info("Loading Posix %s registry from %s", description, storage.root)  {code}    Please change both to be {{info}}.    At the same time, please change {{path}} to {{localFileObj.name}} which is more consistent and useful.  
Answer: 1144.0

User story: "Synpipe has several different components to it. Make a high level overview of these pieces for the purposes of deciding which parts to bring to LSST, or what priority each part will receive in the port."
Answer: 49.0

User story: Update [Common Dataset Organization and Policy in the Developer Guide|https://developer.lsst.io/services/datasets.html]  the "Format" section to reflect the addition of RFC-362.
Answer: 31645.0

User story: "Make a pegasus workflow to do ~same processing steps as in DM-10129/DM-11020,   including makeSkyMap.py, sub-tasks of singleFrameDriver.py, mosaic.py, sub-tasks of coaddDriver.py, and sub-tasks of multiBandDriver.py, with the HSC RC dataset previously defined ([visit IDs here|https://confluence.lsstcorp.org/display/DM/S17B+HSC+PDR1+reprocessing#S17BHSCPDR1reprocessing-RCdataset]).     This does not need to be generic and is merely a stop-gap, before SuperTask-related design is ready. "
Answer: 72264.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: "{{RepositoryArgs.mapperArgs}} is assumed to be dict-like (e.g. {{if 'root' not in mapperArgs}}), but it can be initialised to {{None}}.    The init function needs to guarantee that {{mapperArgs}} is dict-like. I think that we should also fix the default value ({{RepositoryArgs.\_\_init\_\_()}} has a default {{mapperArgs=None}}), although we could just add the test;  but I think it's clearer to set the default to a valid value too.    N.b. mapperArgs is omitted from the class docstring, which otherwise duplicates most of the {{\_\_init\_\_}} docstring.  "
Answer: 26585.0

User story: "When passing arguments such as {{-calibRoot XXX}} to a command such as {{createCalibs.py}} it is ignored when the butler calls {{_addParents}}.  I don't understand exactly what this call is doing, but it fails to pass the {{calibRoot}} down with the result that the butler gets instantiated using the default {{calibRoot}} which is incorrect.    The obvious fix is to change line 855 of butler.py (in {{_addParents}}) to:  {code}                  args = RepositoryArgs(cfgRoot=repoParentCfg.root, mode='r',                                        mapperArgs=repoData.repoArgs.mapperArgs)  {code}  although I think that there's another similar bug that I haven't yet had a chance to get to the bottom of.  I'll edit this ticket when I get a chance.    The how to repeat should be the same as DM-11284 but I haven't had a chance to check."
Answer: 14199.0

User story: "Testing new visualization and PDAC features.     Tested:  DM-7225, please see pull request for detailed comment"
Answer: 20118.0

User story: "Add a jenkins job to build the jupyterlabdemo containers via the {{bld}} script in this repo: https://github.com/lsst-sqre/jupyterlabdemo    The build should also be triggered automatically as part of the weekly release process."
Answer: 20021.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: I just noticed that one of the calibration scripts is loading the same Posix calibration registry around 40 times (which isn't cheap).    The problem seems to be that {{rerun/<USER>tmp/repositoryCfg.yaml}} has many copies of the parent in its {{_parents}} list:  {code}  !RepositoryCfg_v1  _mapper: !!python/name:lsst.obs.pfs.pfsMapper.PfsMapper ''  _mapperArgs: {calibRoot: /datasets/PFS/LAM/XCALIB}  _parents: [../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM,    ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM,    ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM,    ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM,    ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM,    ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM,    ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM,    ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM,    ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM,    ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM,    ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM,    ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM,    ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM,    ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM, ../../../../../../../datasets/PFS/LAM]  _policy: null  _root: null  dirty: true  {code}    While poking at this, I noted that the   {code}  python/lsst/daf/persistence/butler.py", line 909, in _setAndVerifyParentsLists      parents, repoData.cfg.parents, e))  RuntimeError: Inputs of this Butler: ...  {code}  error message doesn't give the paths to the butlers in question -- if it did, it'd make the problem much easier to debug.
Answer: 18610.0

User story: "Create initial DIAObjectCollection API.    Nominally a DIAObjectCollection is a list of DIAObjects with convenience functions for accessing data in the collection, scoring association between DIAObjects and DIASources, and matching DIASources into existing or new DIAObjects."
Answer: 25796.0