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: "Bokeh does not currently support a 'symlog' axis scaling that allows for both large dynamic range & negative numbers.  This is desirable for some of the quantities plotted in the QA dashboard.  The bokeh lead developer seems to think this should be pretty straightforward: https://github.com/bokeh/bokeh/issues/6517.    Once this is implemented, drop in the ability to switch scales between linear and symlog (or log) on the QA dashboard."
Answer: 745142.0

User story: "Save/Exit should communicate it's going to log you out of Hub, should have a save and an exit without saving function, and should also be able to take you back to the Hub landing page rather than leaving you at a dead Lab page, if possible.  "
Answer: 5996.0

User story: "See spreadsheet (based on PMCS by Kevin) here: https://docs.google.com/spreadsheets/d/1_JIEfVlpw08K8uxzdYHslVRIrMoXAQY7G4qs9tGwjR0/edit#gid=1970617727    All T/CAMs have been asked to provide input.    Deadline for this work is 2017-07-14 so that it can be included in review presentations."
Answer: 4778.0

User story: "POSIX requires that a glob pattern is left unchanged when it is syntactically incorrect, or doesn't match any files, whereas python's {{glob.glob}} returns an empty list.    Please change {{ingest.py}} and {{ingestCalib.py}} to obey POSIX semantics (so we'll get a warning if the filename glob doesn't match any files).  "
Answer: 6065.0

User story: "Reprocess the HSC RC dataset using the pipe_drivers tasks.     The processed results should go to {{/project/hsc_rc/w_2017_27/DM-11273}} as a Butler repo. "
Answer: 25802.0

User story: "The prototype QA dashboard (DM-10619) was only implemented using one patch-worth of HSC data.  With a factor of ~100 more data (e.g., a whole tract), performance may suffer to the point where qualitatively different solutions for some things may be required, such as perhaps density (or partial-density) plots for the scatter image, which may require different solutions for selection, etc.  This will require re-running {{coaddAnalysis.py}} again on an HSC tract, saving the data table, and plugging that in as the data in the prototype dashboard.  This ticket should spawn new tickets to solve whatever issues arise from using this larger data set."
Answer: 37431.0

User story: Our DocTree currently describes LDM-151 as the "L2 Pipeline Design". It does not provide a design for L1 (or calibration products) pipelines.    In fact, LDM-151 covers all of these pipelines, and we should make this clear in the diagram.    (I don't think it's critical to fix this before the review, though.)
Answer: 1308.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 reading raw or rawish files you often have a WCS in the header but not one of the custom LSST WCS extensions; this is not interesting to the user, but it's currently logged as INFO (and it's pretty common -- e.g. when assembling biases you get it for every bbox read by {{constructCalib}} scripts):  {code}  afw.image.ExposureInfo INFO: Empty WCS extension, using FITS header  {code}    Please move this to DEBUG.  "
Answer: 7053.0

User story: "There is code in {{obs_subaru}} to handle crosstalk between amplifiers, but it's special-cased for the 4-amp Hamamatsu CCDs that we use in HSC and (new) SuPRIMECAM.  Please generalise this to handle any CCD.    It's a little tricky as the crosstalk occurs between pixels that are read at the same time, so you have to pay attention to where the amplifiers are on the devices (this information is available from cameraGeom).    Note that this ticket does *not* ask for a solution to the general problem of cross talk between different CCDs in a camera (e.g. DECam).  "
Answer: 78333.0

User story: "There are times that one wishes to label saturated pixels but not interpolate over them; please add an option to not call {{saturationInterpolation()}}  "
Answer: 380.0

User story: "Add the python code in firefly_client to dispatch the same actions at the java script does to control the firefly blank slate viewer.    * Add the API  * Create a new jupyter note book page that demonstrate the binding similar to the way the ffapi-slate-test.html does for the javascript"
Answer: 17334.0

User story: "The QA dashboard prototype (DM-10619) has been developed in parallel with learning how bokeh works.  Once this initial learning phase is mostly over (that is, when I understand how to use the key bokeh features required for the QA dashboard as planned), I will need to reorganize and clean up the dashboard-implementing code.  After doing this, move development to a qa-dashboard repo under LSST-DM."
Answer: 747959.0

User story: "Effective drill-down QA exploration will necessarily include the flexibility to allow users to define custom callbacks that can operate on some dataID(s) selected interactively through the dashboard.  Here, implement this capability within the QA dashboard prototype framework, potentially using JupyterLab (depending on the conclusions reached by DM-11254)."
Answer: 747969.0

User story: "The QA dashboard can be much more useful for drill-down exploration if custom callbacks were attached to the interactive plots.  As a first step toward allowing users to implement custom callbacks, identify and implement one or more callbacks of this sort that would be generally useful, and put this into the prototype dashboard."
Answer: 747977.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 data points in the QA dashboard prototype can only be selected using the bokeh mouse tools (rectangle select, free-drag select, etc.) on two dimensions at a time (either in the x-y plane or in ra-dec space).  The dashboard should allow an additional more flexible query option that can filter the points that get displayed in the first place.  This should be relatively straightforward to implement using the pandas {{DataFrame.query}} method, which already accepts and parses a string to implement queries."
Answer: 3378.0

User story: "The QA dashboard prototype currently allows to select sets of pre-defined computations on columns to be the x- and y-data for the primary scatter plot.  This would add the ability to define custom x- or y-data either as user-entered columns or simple mathematical computations on columns.  This will involve investigating what existing solutions for mathematical parsing/sanitizing of text input might be applied here. "
Answer: 13099.0

User story: "A new set of templates are provided, which we should use starting with the July NSF/DOE review.  Please change lsst-texmf to use them.  "
Answer: 44.0

User story: The x- and y-value histograms in the QA dashboard prototype (DM-10619) currently individually normalize the different categories (e.g., stars and galaxies).  The advantage to this is that you can see details in the individual distributions; the disadvantage is that you don't see the overall shape of all the sources combined.  In this ticket, add this combined "all" category to the histograms.
Answer: 38735.0

User story: "Look into how we might use the bokeh QA plots within a jupyterlab environment, to enable more custom interaction.  The purpose of this ticket is first to get familiar with the JupyterLab environment, and then to investigate and understand the interaction of bokeh & JupyterLab, rather than attempt to make a full demo QA dashboard as demonstrated in DM-10619 to function within JupyterLab."
Answer: 38751.0

User story: "Initial documentation set for {{pipe_base}} in the https://dmtn-030.lsst.io architecture. Includes converting existing content found in DM-10639."
Answer: 69418.0

User story: "composite objects should get passed to the std_<datasetType> function of the mapper, if there is one."
Answer: 1585.0

User story: "ci_ctio0m9 is an integration test package that aims to protect obs_ctio0m9 and the calib creation scripts in pipe_drivers (which haven't been captured in CI yet). It's based on SCons (like ci_hsc), so we can't put it in lsst_ci until we have python 3 support in SCons. In the mean time, please add it as a job executed by timer (like ci_hsc is)."
Answer: 1103.0

User story: "Per https://jira.lsstcorp.org/browse/RFC-348, add (approximate) history of nondetections to the alert packet.    Also clarify (per https://jira.lsstcorp.org/browse/RFC-350) that DIASource records will include filterName."
Answer: 610171.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: "Need to look for local Docker registry as a place for private images in the context of Kubernetes"
Answer: 182976.0

User story: Make the following changes to Lander:    - Always include the "View on DocuShare" button for controlled document types (LDM, LSE, LPM, and so on). Implement as a whitelist, and use the ls.st short link form. This makes the {{--docushare-url}} command line optional have a good automatic default.  - Do not show the DRAFT notice for builds on {{master}} and {{docushare-vN}} branch/tag names.
Answer: 2867.0

User story: "Displaying CModels and residuals is currently done with matplotlib. There are hooks for additional backends, and one should be added for afw display"
Answer: 750472.0

User story: "The current default PSF-based image selection leaves large holes in the distribution of coadds. Takashi Hamana recommends adopting:  {quote}  max_medianE = 0.007  max_scatterSize/medianSize^2 = 0.009  {quote}  This involves modifying the current defaults and adding a new selection criterion."
Answer: 1507.0

User story: "This ticket reports the effort to support LSST DM document CI configuration (including LTD and Lander landing pages)."
Answer: 65550.0

User story: "Need to specify roles and rules for different users/groups and namespaces for the cluster"
Answer: 77322.0

User story: "Need to add Ingress controller, most likely, nginx to Kubernetes cluster to expose some of the services."
Answer: 77337.0

User story: "Kubernetes is now running both in Nebula and a separate VM cluster. Is possible to mount GPFS on the VM machines to investigate persistent storage options for various services.     /home will need to be mounted as read/write  same with /scratch  /datasets can be mounted later on as read-only"
Answer: 77323.0

User story: "The image constructors such as {{DecoratedImage}} and {{Exposure}} do *not* obey the {{INHERIT}} keyword.    This is a rather murky piece of fits, but the intention of {{INHERIT}} is to allow an HDU to also read the PDU.  This is necessary when reading e.g. {{DecoratedImage}} or an LSST {{Exposure}} as much of the useful information ({{EXPTIME}} etc.) is in the PDU -- e.g. it's not repeated in each of the 16 amplifier HDUs.    I added support for {{INHERIT}} a while ago, but not in the code path that's used to read Images (mea culpa).  For this ticket I'm going to just adjust things to call the free function that handles this correctly, but see  DM-11235.  "
Answer: 6168.0

User story: "{code:java}  ln -s /project/hsc_rc/  /datasets/hsc/repo/rerun/RC/  {code}"
Answer: 14333.0

User story: "While testing the proximal gradient methods (ADMM, SDMM, and GLMM) on more simplistic functions, [~<USER> and I have been noticing strange behavior in the algorithms, noticeably that under certain circumstances the solutions diverge.    This ticket is meant to be a placeholder for sub-tickets that will dive into specific cases where we have noticed that the algorithms fail to understand and correct the behavior."
Answer: 24156.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: "Design guidelines for squash Kubernetes deployment.   "
Answer: 79152.0

User story: "If the RFC is adopted, change the sky patch data identifier naming convention from {{1,2}} to {{1x2}}.  "
Answer: 95123.0

User story: {{git-lfs}} is provided as an eups package on the shared stack, but if one follows the instructions at https://developer.lsst.io/tools/git_lfs.html after typing {{setup git_lfs}} everything will appear to be correct, but it won't work.    The solution is to either type {{git lfs install}} despite the fact it's already installed, or add   {noformat}  [filter "lfs"]   clean = git-lfs clean -- %f   smudge = git-lfs smudge -- %f   process = git-lfs filter-process   required = true  {noformat}  to their {{~/.gitconfig}} file (which the instructions already have people editing).    Someone should update the docs so other don't fall into this trap. It's a trivial fix, but I don't know how to edit the docs.
Answer: 4222.0

User story: "DM-11163 allegedly passed Jenkins & ci_hsc, but seems to break everything for me, with all my visit infos that used to be correctly populated coming back with Nans for the expTimes and DateTime()s for the dates when running {{constructBias.py}}    Working on fixing this now..."
Answer: 18981.0

User story: The LDM-152 logging section mentions logging to an event system.  This functionality was been removed from the main stack with the removal of ctrl_events, which implemented that.    In Section 4.5.1:    "Logs must be able to be written to local disk files as well as sent via the event sub- system."    We do not have anything in the main stack (that I'm aware of) that implements sending logging events.    In Section 4.5.3:    "n adapter was written to enable log messages to be sent via ActiveMQ events, but this is not currently being used, as log collection mechanisms are adequate."    While technically correct, as it stands, someone can not use this today without reintegrating ctrl_events into the stack.  I know of no plans to do this.    Since log collection mechanisms we're using are adequate, why mention events at all?  In fact, at one time weren't we considering using logstash?   If so, that might be more appropriate to talk about instead.
Answer: 1056095.0

User story: "Interface with Qserv developers to characterize and remediate hardware performance issues."
Answer: 89280.0

User story: "Currently you have to set {{clobber=True register.ignore=True}} to achieve this which is non-obvious.  "
Answer: 11120.0

User story: "Currently ingestCalibs.py defaults to putting its registry into {{.}} by default; please put it in the output directory instead.  "
Answer: 15.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> noticed that tasks fail if the output is a non-empty non-repo folder.  To reproduce with {{w_2017_26}}:     {code:java}  $ mkdir out  $ echo 1234 > out/a  $ processCcd.py /datasets/hsc/repo --id visit=444 ccd=4  --output out  {code}    This gives errors:   {code:java}  Traceback (most recent call last):    File "/software/lsstsw/stack/Linux64/pipe_tasks/13.0-38-gf73ba12/bin/processCcd.py", line 25, in <module>      ProcessCcdTask.parseAndRun()    File "/software/lsstsw/stack/Linux64/pipe_base/13.0-9-g1c7d9c5+5/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+5/python/lsst/pipe/base/argumentParser.py", line 512, in parse_args      namespace.butler = dafPersist.Butler(inputs=inputs, outputs=outputs)    File "/software/lsstsw/stack/Linux64/daf_persistence/13.0-20-g8cd6840/python/lsst/daf/persistence/butler.py", line 531, in __init__      self._setAndVerifyParentsLists(repoDataList)    File "/software/lsstsw/stack/Linux64/daf_persistence/13.0-20-g8cd6840/python/lsst/daf/persistence/butler.py", line 905, in _setAndVerifyParentsLists      repoData.cfg.extendParents(parents)    File "/software/lsstsw/stack/Linux64/daf_persistence/13.0-20-g8cd6840/python/lsst/daf/persistence/repositoryCfg.py", line 167, in extendParents      if all(x == y for (x, y) in zip(self._parents, newParents)):  TypeError: zip argument #1 must support iteration  {code}      If the folder is empty (i.e. skipping {{$ echo 1234 > out/a}} in the example) then the task runs just fine.
Answer: 30667.0

User story: "This ticket covers a demonstration of a pipelines.lsst.io build with content contributions from stack packages. We'll use the {{verify_metrics}} package since it's a data-only package that's easy to setup with EUPS (few dependencies).    The build tool itself ({{build-stack-docs}}) is being developed on a separate ticket (DM-11004) in the documenteer package.    For pipelines_lsst_io, this work will be merged into a *DM-10635* integration branch to allow continued documentation deployments from {{master}} for the stack-less pipelines.lsst.io documentation builds on Travis.    This work won't be deployed via CI."
Answer: 593176.0

User story: "When poking at rawish data it can be very convenient to label saturated pixels, but not interpolate over them (e.g. when investigating CTE in the serial registers of Hamamatsu CCDs)  "
Answer: 18288.0

User story: "We begin working with a Rucio installation on NCSA vsphere system lsst-dbb-*.ncsa.illinois.edu (lsst-dbb-rucio.ncsa.illinois.edu for Rucio proper.)   Installation is coordinated with admins so that puppet configuration provide the configuration consistently/reproducibly. "
Answer: 1.0

User story: "Test data exchange between System Engineering tool (MagicDraw) and existing planning tools. "
Answer: 50611.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: "Populate framework in mapped dependencies (MagicDraw)."
Answer: 240819.0

User story: "Develop service architecture with relationship mapping."
Answer: 1378.0

User story: "[~<USER> designed a nice replacement for the camera model using yaml description.    This ticket is to, as an experiment, move it to {{obs_base}} without activating it, so that it can be tested and integrated where people so choose.    An RFC will be filed regarding switching to it as our default camera description once the move is complete."
Answer: 21879.0

User story: "Port the LSSTStyle class from the lsst-texmf docs (made by [~<USER>) to documenteer's sphinxtex sub-package so that it can be used by Sphinx-based technotes.    See https://github.com/lsst/lsst-texmf/blob/master/docs/conf.py#L74"
Answer: 25942.0

User story: "We're adopting the submodule pattern for lsst-texmf-based LaTeX documents. To implement this with the cookiecutter project generation:    1. Get cookiecutter to handle submodule setup with a [post-generation hook|https://cookiecutter.readthedocs.io/en/latest/advanced/hooks.html].  2. Change the  [Makefile template|https://github.com/lsst/lsst-texmf/blob/master/templates/presentation/%7B%7Bcookiecutter.slug%7D%7D/Makefile] to use lsst-texmf from the submodule instead of from the Docker container's environment.  3. Update README with instructions from https://github.com/lsst/lsst-texmf/pull/75  "
Answer: 1197486.0

User story: "Revisit qserv status monitoring (SHOW PROCESSLIST etc.) and ensure that it will be usable for monitoring the status of qserv disconnected queries"
Answer: 132471.0

User story: "Implement retrieval of the result of disconnected queries."
Answer: 47478.0

User story: Current state of the ASYNC query processing is:  - czar can parse "SUBMIT SELECT ..." query  - it drops SUBMIT and processes SELECT normally  - {{async}} flag is set in UserQuery and in QMeta but it is not used by anything     To continue implementing the first step is to:  - return jobID to user as soon as query is submitted to qserv pipeline  - that is going to be done via separate result table  - qserv will store result of SELECT in a result table which is not accessible for now (result retrieval will be done later in DM-11191)
Answer: 37551.0

User story: "Reprocess the HSC RC dataset using w_2017_36 following the same steps as in DM-10129/DM-11020"
Answer: 107784.0

User story: "The goal it to set up a collection of virtual machines to create a condor pool allowing for testing Pegasus in environment _without_ a shared filesystem.    "
Answer: 2.0

User story: "Reprocess the HSC RC dataset using w_2017_34 following the same steps as in DM-10129/DM-11020"
Answer: 93404.0

User story: "Reprocess the HSC RC dataset using w_2017_32 following the same steps as in DM-10129/DM-11020"
Answer: 71955.0

User story: "Reprocess the HSC RC dataset using w_2017_30 following the same steps as in DM-10129/DM-11020"
Answer: 51814.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: "Reprocess the HSC RC dataset using w_2017_28 following the same steps as in DM-10129/DM-11020"
Answer: 27445.0

User story: "Rewrite more of imgserv according to PEP8 and Python 3 improvements"
Answer: 109.0

User story: "This involves travel to Chile for at least two NCSA system personnel."
Answer: 430517.0

User story: "Ship to Tucson or Chile as appropriate:  *     Remove the items from NCSA inventory   *     NCSA pays for shipping and insurance to Tucson   *     Tucson will accept, unbox and inventory the items for Aura.   *     Tucson will reseal boxes & ship to Chile  "
Answer: 290591.0

User story: "Receive & unpack hardware. Plan for setup and testing, and ready work area."
Answer: 171451.0

User story: "After final review/approval, submit order to vendors. Follow up as necessary."
Answer: 31455.0

User story: "Per srp:   I'd like to get a separate HTCondor central manager running, which will work with HTCondor execute pods deployed to the Kubernetes cluster.  We can either do this by removing a node from the lsst-elastic nodes.    Centos7, same 'hardware' config should be fine. It should have the same firewall ports open that the HTCondor config had when we ran on lsst-dev.  "
Answer: 1480.0

User story: "We'd like to be able to reproduce a RC processing run on a weekly release (or any rerun, but that's beyond the scope of this issue) from the files in the output data repository.  [~<USER> believes the logs saved in the weekly RC data repositories (see https://confluence.lsstcorp.org/display/DM/Reprocessing+of+the+HSC+RC+dataset) contain enough information to reconstruct the command-lines run (including the data IDs passed).    DRP team should check these logs to see if this is true.  This activity should be limited to perhaps a half-day of work; if the information may be present but is too difficult to extract from the logs we should pursue other options."
Answer: 1630974.0

User story: "Code has been added to identify and remove result rows from failed job attempts. It needs to be tested by disabling a worker node and then bringing the node back online. This needs to be done in the middle of the query and before the query starts."
Answer: 53546.0

User story: "When an NMF minimization using the GLMM algorithm fails to converge it is often useful to have more information from the history of the traceback to understand why convergence failed. This ticket will modify the {{Traceback}} object to properly store the X, Z, U matrices as well as the f and g steps used in each iteration."
Answer: 2700.0

User story: As part of dealing with DM-10302 and DM-10933, we can do an "easy" thing and change {{fluxSigma}} to {{fluxErr}} in all stack code and catalogs. This is less daunting than changing Sigma everywhere, involving only 296 changes over 68 files, instead of 2117 over 287. It's also a clearer change: anywhere we have {{fluxSigma}} we almost certainly meant to say {{fluxErr}}, whereas some of our {{Sigma}}s elsewhere are really {{Sigma}}.
Answer: 567134.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: "astshim currently follows AST's handling of the {{Id}} attribute: an arbitrary string that is not copied when the object is deep-copied. However astshim almost always makes deep copies, where AST does not. In particular, when adding a {{Mapping}} to a {{FrameSet}} AST will use a shallow copy (preserving {{Id}}) but astshim will make a deep copy (nulling {{Id}}), and indeed it is probably impossible to set the {{Id}} of a {{Mapping}} in a {{FrameSet}}.    I suggest we break AST's rule and copy {{Id}} when making a deep copy. One could imagine providing a flag, but I think it is simpler not to do so. The user can manually set or clear {{Id}} in the copy if necessary."
Answer: 396830.0

User story: Please fix the typo for "metadata" in makeRawVisitInfo.py:  {code}  Key=\"{}\" not in medata  {code}  
Answer: 107.0

User story: "Reprocess the HSC RC dataset using w_2017_26 following the same steps as in DM-10129/DM-11020"
Answer: 4361.0

User story: "We need to be able to get darktime from {{VisitInfo}} when using e.g. master darks, so please add code to write suitable metadata.  "
Answer: 1002.0

User story: "Please create {{VisitInfo}}  whenever we read an {{Exposure}} from disk if suitable metadata is available.    Currently this is done in the {{std_raw}} method, but it's also needed when e.g. reading master dark calibration frames from {{DecoratedImages}}.  "
Answer: 1060.0

User story: "Implement RFC-353 by replacing all use of {{Coord}} and its subclasses with {{SpherePoint}}.    Things to keep in mind:  - afw will no longer support coordinate conversions. We do not rely on this now (except for a very small number of cases of use of FK5 J2000 instead if ICRS that is likely a mistake).  - {{SpherePoint}} and {{Coord}} have slightly different APIs (for instance {{SpherePoint}} is immutable) so some usage will need to change.  - {{Coord}} has some methods that {{SpherePoint}} does not. These may have to be added to {{SpherePoint}} or implemented as free functions.    This would also be a good time to eliminate the {{SpherePoint(double raDecRad[2])}} constructor. This was added to support {{Transform}} but turned out to be unnecessary."
Answer: 377690.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: "It should have a change record, note of repository URL, etc."
Answer: 5853.0

User story: "Get list of what resources we need for k8s/jupyterlab together."
Answer: 25751.0

User story: "By the All Hands Meeting, we should be able to demonstrate verification metrics by reporting object counts for pipeline stages. This ticket covers writing code for applying the verify framework to output data, analyzing each stage, and supporting SQuaSH export (though the export itself is the responsibility of verify_ap).    The following metrics are covered:  * Fraction of science image sources that become DiaSources after image differencing.  * Fraction of previously-known DiaObjects that have detections in a new difference image.  * Number of DiaSources that create new DiaObjects in a difference image.  * Number of DiaObjects associated with only one DiaSource"
Answer: 221800.0

User story: "Create new WBS structure for use with new planning packages."
Answer: 129210.0

User story: "After DM-10253 and DM-10565 things were working well with obs_ctio0m9, but changes to some defaults in meas_astrom meant that the {{processCcd.py}} config merged there is no longer correct. This ticket exists to make those changes."
Answer: 79.0

User story: "Deploy Kubernetes cluster on new VM cluster to test containerized services. "
Answer: 13490.0

User story: "Post-installation cleanup and decommissioning."
Answer: 178661.0

User story: "During designated maintenance window, make final placements and installation for refresh."
Answer: 80824.0

User story: "Rack and configure network hardware."
Answer: 87561.0

User story: "[~<USER> and his summer student Max Jerdee have been making improvements to the {{proxmin}} package, which contains the GLMM algorithm used in the deblender. This ticket will update the {{deblender}} repo to use the new API."
Answer: 38618.0

User story: {{meas_mosaic}} writes its WCS as FITS header with no attached image, which requires loading code to use the following pattern:  {code}  md = butler.get("wcs_md", ...)  wcs = lsst.afw.image.makeWcs(md)  {code}  instead of simply  {code}  wcs = butler.get("wcs", ...)  {code}  Using a header-only format also limits us to FITS-standard WCS mappings.    Because {{Wcs}} inherits from {{afw::table::io::Persistable}} it already has {{writeFits}} and {{readFits}} methods that utilize our FITS binary table format, which will be able to save more complex WCS solutions.  It's also compatible (or will be soon, on DM-10728) with the "FitsCatalogStorage" butler storage type, so we should be able to fix this by:   - Redefining "wcs" to be a "FitsCatalogStorage" dataset, instead of a "FitsStorage" exposure in all mappers;   - modifying meas_mosaic (and possibly jointcal, if needed) to use {{butler.put}} directly.   - modifying any code that consumes the {{wcs}} dataset to use {{butler.get}} directly.    In addition, this issue should include creating a simple command-line script that can be used to convert a data repository from the old format to the new one.
Answer: 355569.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 Calibs team has decided that calib construction should work in this way:  * {{construct*.py}} writes the outputs to the rerun (butler output) directory.  * {{ingestCalibs.py}} moves the calibs into the calib directory (with a link option for testing)  "
Answer: 14895.0

User story: "Using off the shelf MariaDB container will impact Qserv configuration. Indeed:  - sciSQL shared library  - database directory  - configuration files  need to be available in MariaDB container.  "
Answer: 109403.0

User story: "The routine {{exposureFromImage}} needs to create and add a {{VisitInfo}} when converting types such as {{DecoratedImage}} that have associated metadata.  "
Answer: 29349.0

User story: "Make kernel list look like we want it to when we do this for real.  "
Answer: 5506.0

User story: "Create at least 2 tasks; one for building the image and another for pushing the image to a registry.  The tasks should be defined within the context of a gradle project.  As part of building a project, one can optionally generate a docker image and push it to a registry  Need to define tags and versions for the repository.  Need to create account used for docker login.  "
Answer: 27411.0

User story: "{{squash-dash}} is a frontend interface to embed SQuaSH bokeh apps. It is meant to run with the {{squash-api}} and {{squash-bokeh}} microservices.  It uses Django templates, bootstrap, font-awesome and jquery for the web application. The deployment creates a pod with two containers, one for the django application + uwsgi and another one runs nginx as reverse proxy and also to serve the static assets.   The build of the docker images and the ks8 deployment are automated through a Makefile. Added support to local deployment with minikube.  See README for Instructions."
Answer: 132427.0

User story: "Create the {{squash-db}} microservice, it will run MariaDB from the official docker image and use a persistent volume to store the data. Add suport to Minikube and GKE."
Answer: 57736.0

User story: "Migrate SQuaSH REST API (from qa-dashboard) to the new squash-api repository    "
Answer: 50538.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 a start at a design for the {{verify_ap}}.  It will require changing the API for the prototype ap pipeline, but should contain place holders for anything we know we need but do not have yet.    This will give us a better idea what the processing flow looks like and also give us a place to add metrics calculations and a place to stick things like association.    We wrote down the following pseudocode as a starting point:  {code}  main():      find input data      "--dataset"      load_dataset_config --> yaml file with stuff like "HiTS" : "hits_data"      (for starters, self-contained datasets that we know will work)      input_repo_dir = eups.getPackageDir(datasetname)"mapper" : "obs_package"      ?? eups setup obs_package ?? (supposedly this can be done within python?)      "--output"      copy stub input repo to output      "--dataIdString" (note: often just "--Id" as a command line string in other places)      ap_pipe.ingest_raws(data_location, repo_location)      ap_pipe.ingest_calibs(data_location, repo_location)      ap_pipe.process(repo_location, rerun, parallelization_level, dataIdString)      --> how to get templates? in same repo with input data?      ap_pipe.diff(repo_location, rerun, parallelization_level, dataIdString)      ap_pipe.assoc(repo_location, rerun)      ap_pipe.afterburner?? --> and/or, the afterburner could live in the same package as main, and be called as verify_ap_afterburner  {code}
Answer: 41745.0

User story: "2015 data exist someplace (may be on lsst-dev, but could be re-gotten from the NOAO science portal).  Package these data up in the format mentioned in DM-11116."
Answer: 38989.0

User story: "We envision the datasets for {{verify_ap}} to be eups packaged git LFS repos.  The following structure is a first cut at what such a package may look like:  {code}  ups/dataset_name.table (this should contain obs package needed to work with these data)  data/[LFS data files]  input_repo/_mapper (indicates the mapper to use with the data in this repository)  {code}  This could potentially contain more information: e.g. templates for use with other datasets."
Answer: 11543.0

User story: "Setup an independent HTCondor central manager outside of the Kubernetes cluster to direct worker nodes inside of Kubernetes."
Answer: 16082.0

User story: "When the Kubernetes elastic node cluster has been set up, deploy the HTCondor Central Manager and worker pods to it."
Answer: 45830.0

User story: "Create and test the YAML files used to deploy HTCondor"
Answer: 45837.0

User story: "Create, deploy and test HTCondor docker containers"
Answer: 11601.0

User story: At present, the docker containers that are published as part of the weekly pipelines/apps tag/release process are using python 2.7.  In addition, they are from scratch builds which should no longer be necessary as weekly binary "tarball" builds are being published.
Answer: 108072.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 is principally to support PFS, but HSC may derive some benefit too.    Tickets to be pulled over:  * DM-10558: disable or remove butler caching  * DM-11243: Refine PSF-based image selection"
Answer: 20057.0

User story: "* Installing software needed  (DESDM software, lsst plugins for DESDM software, LSST stack with patch comma symbol changed to x)  * Initialize test home_archive on shared filesystem  * Use Steve's glidein script to aquire nodes from the slurm cluster  * Run same mini-sized test run previously."
Answer: 60829.0

User story: "* Modify to use database table instead of csv file for determining visit+ccd tract+patch overlap.    (Hsin-Fang created an sqlite file for use in her HSC runs.    Started with it.)  * Modify to use pre-created butler registry files.  (Prototype created butler registry files specific to the current execution mostly to prove that could.    Since butler registry files aren't a file catalog doesn't hurt to use pre-created butler registry files.)  * Change operations butler template file (directory and filename patterns) from WCL to yaml.    (Still have problems when inputs come from multiple processing attempts as the pattern differs)  * Add in python version of DESDM QCFramework that monitors stdout/stderr for particular patterns."
Answer: 390.0

User story: "When reading an exposure (or sub-exposure), we get lots of messages:  {code}  afw.image.ExposureInfo INFO: Empty WCS extension, using FITS header  {code}  This is a very common, and benign, state of affairs (e.g. reading raw data from almost all telescopes), so please change the level to DEBUG.  "
Answer: 26258.0

User story: "Per RFC-352, all {{Task}}​s (modulo approved exceptions; see the RFC for details) are expected to provide a {{run}} method as their primary point of entry, and may also provide {{runDataRef}} for operating on dataRefs. Please update the documentation in pipe_base to explain this requirement (and the procedure for obtaining an exemption)."
Answer: 1343310.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: Provide the Database/DAX group (and the larger LSST team) input on performance requirements for database queries and other interactions with the LSST database and DAX services, beyond the long-standing "fast" and "slow" query requirements from the Data Access White Paper.    This input should be based on experience with existing archives, in particular IRSA, but also other contemporary systems providing access to wide-area survey data.         *The following information was sent to <USER>December 2017 by <USER>*  Here are some performance targets based on wise catalog and image searches at IPAC.     One thing to notice is that we need more concurrency for the images than the database searches.  A user might click on a table row and firefly might request 5 - 10 images or a user might page though groups of 25 images.     A user typically does only one or two DB searches concurrently.     Let me know if you need more details.     Trey  _________________________________     *Catalog:*     Meta search - 400 milliseconds - 10 concurrent  Radius search -  50 arcsecs - 2.5 second - 20 concurrent  Radius search - .1 deg - 1.25 minutes - 10 concurrent  Radius search  - .5 deg - 2.25 minutes - 10 concurrent        *Image:*  my image transfer times were around 12.2 MB/sec     Image - 1.1 MB cutout - .2 sec - 50 concurrent  Image -  6.6 MB cutout - .6 sec - 50 concurrent  Image -  22 MB cutout - 1.5 sec - 50 concurrent  Image -  - 40 MB  cutout - 2.8 sec - 50 concurren
Answer: 751516.0

User story: "While implementing DM-9195, I realized that jointcal did not actually use a photometric reference catalog. This is a retro-active ticket for the work that was done to implement the reference flux support, and all the necessary pieces of the photometry fitter to use it."
Answer: 47555.0

User story: "Add pandoc so we can get PDF exports."
Answer: 7144.0

User story: "MultibandDriver attempts to run detection if no calibrated exposures are found. It should skip trying to do this if there is no data present at all."
Answer: 956.0

User story: [~<USER> reports more failures in processing the HSC RC dataset with a recent version of the stack:  {quote}  Using the latest stack (w_2017_25) I'm reprocessing the RC dataset in DM-11020.  I'm seeing more failures (81 ccds) in the single frame processing stage, compared to w_2017_17 (46 ccds).    Out of the 81 failures:  62 failed with: "Unable to match sources"  4 failed with: "No objects passed our cuts for consideration as psf stars"  4 failed with: "No sources remaining in match list after magnitude limit cuts"  11 failed with: "PSF star selector found [123] candidates"    I'm not sure if this is expected or not.  Maybe somebody from the Science Pipeline would want to know? (edited)     The difference seems to be those failed with "Unable to match sources".  There were only 27 of those in w_2017_17.  (All with the same RC dataset, 320 visits in total)  {quote}    We need to understand what went wrong here and fix it.
Answer: 33267.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: "Submit plan and estimate to project. Address concerns and feedback."
Answer: 140934.0

User story: "Prepare FY18 acquisition planning document for submission to project,"
Answer: 140920.0

User story: "Given requirements, determine components, get quotes, and prepare cost estimate for acquisitions."
Answer: 140920.0

User story: "Review project plans and milestones, and gather requirements for facilities upgrades and additions."
Answer: 92017.0

User story: "Refresh and/or augment vendor quotes for development capacity increase, and submit to project office for final sign-off."
Answer: 141005.0

User story: "Refine initial development capacity increase plan based on review of initial plan. Work with vendors to get necessary quotes."
Answer: 83389.0

User story: "Assess needs and arrive at proposal for increasing capacity of storage and compute resources for development resources."
Answer: 83387.0

User story: "Refresh and/or augment vendor quotes for lsst-db refresh, and submit to project office for final sign-off."
Answer: 101938.0

User story: "Refine initial lsst-db plans based on review of initial plan. Work with vendors to get necessary quotes."
Answer: 9839.0

User story: "Assess needs and arrive at proposal for increasing capacity and transitioning to supported infrastructure."
Answer: 9842.0

User story: "Finalize details of plan due additional facility information from Chile."
Answer: 38722.0

User story: "Refresh and/or augment vendor quotes for full DAQ test system, and submit to project office for final sign-off."
Answer: 101959.0

User story: "This tutorial will be added to the Getting Started tutorial series at pipelines.lsst.io (DM-10637 and DM-11034). The tutorial will explore the forced photometry catalogs and cover a semi-realistic analysis of the catalog, and involve making plots and understanding measurement algorithms.    The tutorial can borrow from [pipe_analysis's tasks|https://github.com/lsst-dm/pipe_analysis]."
Answer: 40551.0

User story: "Work with developer and ICI staff to refine full-scale DAQ/L1 test system plan based on initial small-scale test system results.  Work with vendors and ICI staff for initial proposal for the full-scale DAQ/L1 test system.  Set up Loaner machines and installed BBFTP software as well as additional packages such as /usr/bin/time.  Developed command line instructions for running BBFTP as a non-interactive session.  Timed without network tuning.  Incrementally made changes to network values for both sending and receiving with timings done as each value changed. These included kernel changes as well as NIC and userspace adjustments.  Ran into occasional issues - especially compile and install issues that had to be analyzed and worked through.  https://confluence.lsstcorp.org/display/JP/Dell+Loaner+Tests  "
Answer: 11881.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: "Work with vendors and ICI staff for initial proposal for the full-scale DAQ/L1 test system.  Developed system wide drawing defining components and the type of network connectivity between components.  Built detailed list of component tasks:  https://confluence.lsstcorp.org/display/JP/Procurement+-+2017+-+Final  Met with vendors for detailed machine discussions that explored the proper CPU architecture for the needs LSST has in the Level 1 system."
Answer: 11646.0

User story: "Emphasis on final preparations for and attendance at the LSST al-hands meeting, NSF review followup, cycle planning for F17b."
Answer: 101987.0

User story: "Emphasis on final preparation and participation in the NSF review, preparation for the August LSST all-hands meeting."
Answer: 48128.0

User story: "Emphasis for June is continued replan refinement, preparation for the DM review, action items fro the May DMLT F2F meeting, continued capacity planning."
Answer: 11617.0

User story: "Investigate and potentially implement monitoring for the PDAC based on project requests and requirements."
Answer: 57455.0

User story: "Investigate monitoring options for the Nebula cluster nodes."
Answer: 99576.0

User story: "Enhance and extend monitoring based on proect requests and experience with other projects and services. Potential activities include:  * Building organized clusters (dell, lenovo): qserv cluster, sui cluster and verify cluster  * Addition of SSL check, SMTP check, checking of whether backups and DR is working properly  * Addition of external backup monitoring, e.g., campus-level monitoring of the monitoring system head node, with notification"
Answer: 99606.0

User story: "Investigate and potentially install existing monitoring and displaymodules and plugins. E.g., check_open_manage, check_mk and check pnp4nagios."
Answer: 99607.0

User story: "Organize nagios configuration using puppet.This includes determining the correct puppet module(s), and replacement or workaraunds for puppet db."
Answer: 57501.0

User story: "Produce and publish full set of schemas for consolidated database."
Answer: 94995.0

User story: "Develop consolidated database operational data flow diagram"
Answer: 94995.0

User story: "Gather schemas for all databases within the consolidated database"
Answer: 94995.0

User story: "Convert prototype schema(s) for selected database(s)."
Answer: 11158.0

User story: "Perform assessment of SQL Server and Oracle for suitability given known requirements."
Answer: 11152.0

User story: "In order to persist {{lsst.afw.geom.SkyWcs}} in afw tables and FITS binary tables we want to expand afw table to support variable-length strings. It already supports variable-length numeric arrays, so [~<USER> thinks adding this feature should be fairly straightforward."
Answer: 8735.0

User story: "DM-10559 introduced a warning when makeWcs() fails to construct a wcs, but the level was too high. It should be reduced DEBUG level warning."
Answer: 73.0