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: "Something has happened at an org level and now I'm getting failure messages from Travis about my build.         Sadly, there's a fair amount of work that needs to happen here to get this to work, as much as I would like to, and some of them I can't do now.         Things that need to happen:   # We use non-open Oracle plugins, which require signing into an Oracle Account.  This means I need to get some kind of creds into Travis to get them to be able to pull down the oracle connector from the maven repository.   # Even if #1 worked, the tests fail because I'm using a private branch of the cadc-adql code that hasn't been merged yet.  This was to get the catalog.schema.table names working.  It is in the plan for Patrick @ CADC to merge this, but it hasn't happened yet.   # Because of #2, I'm calling a monkeypatch script to get things to work, and disabling tests in the build currently.  So I'd need to get Travis to call the build.sh script instead.    Right now, I'm just going to say it's not worth it, but in a month or so, it might be."
Answer: 112309.0

User story: "PhotoCalib is now defined in terms of nanojansky, but our reference catalogs are saved in Jy, and remain in Jy when the user loads them. We need to get our refcat loaders to produce nJy to keep our calibrations self-consistent.    It may be enough to just multiply fluxes and flux errors by 1e9 after the data is read from disk, but [~<USER> may have other suggestions.    We will have to add a few work-arounds for this to {{PhotoCal}} and other tasks that use the {{Calib}} object, as it will remained defined in Jy. If only we could do DM-10153 simultaneously (but I think that would be maddening)."
Answer: 142556.0

User story: "Set up CI infrastructure for conda builds of pytrax (on Linux, Mac), and python setuptools package (on Ubuntu), to provide immediate feedback on codebase status for pytrax. Requirements:   * Be accessible to all pytrax developers   * Support and test Python 3.5, 3.6, 3.7   * Build conda packages on Linux and Mac   * Build pip-installable package on at least Linux   * Run on every push to the core repository's `master`   * Run basic tests (just importing the package) with all builds. More advanced tests will be added later.    The CI will be done using Microsoft Azure Pipelines, as they allow for free builds of private repositories.    Because pytrax is collaboratively developed with the MPC, we cannot (solely) use LSST's usual CI infrastructure as MPC collaborators need to have access to it. We will add it to LSST's CI once we start integrating with Prompt Processing pipelines."
Answer: 10054.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're moving towards adoption of pytrax (currently at [https://github.com/mlh2000/pytrax] and private at the moment) as the core moving object linking algorithm implementation library. The details will be presented in DM-16421.     The pytrax algorithm appears sound, but the codebase could use some software engineering help. This story covers the initial fixes to be done to the codebase, including:   * Moving to a standard directory structure   * Using a single, standard, setup.py script for installs   * Initial README.md developer documentation   * Initial conda packaging"
Answer: 5982.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "In DM-16932, the SQuaRE Bot becomes less an application that knows the specifics of different commands, and more a router from Slack messages/events into Kafka topics. This ticket is to create the MVP deployment of SQuaRE Bot Jr (the next generation SQuaRE Bot). The goal is to have an app that can be registered with the Slack API. Emitting Kafka topics will be done in subsequent tickets.    Some specific features:   * Demonstrate an app based on aiohttp.web ([https://aiohttp.readthedocs.io/en/stable/)] as a proof-of-concept of an asyncio-based app, rather than something like our typical synchronous Flask apps. This does mean figuring out logging, configuration, routing, and deployment methods.   * Since we need a staging environment (rather than using api.lsst.codes) this ticket will also stand up a Kubernetes cluster and explore new methods of ingress with Let's Encrypt certificates.   * Add a Travis-based Docker build pipeline."
Answer: 16008.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 dimension package introduced in DM-15034 and modified in DM-15675 are a big improvement on what we had before, but the logic for constructing and expanding DataIds in particular is getting quite complex and hard to follow.  Issues include:    * Use of {{\_\_new\_\_}} for {{DataId}} to avoid unnecessary copies  *  (Intentional) pointer aliasing in {{DataId.entries}}.   * Upgrading and downgrading of implied-dependency links from {{DataId.entries}} to the main dictionary.  * Lots of code to traverse {{DimensionGraphs}} in different ways in {{expandDataId}}, {{SqlPreFlight}}, and {{DimensionGraph}} itself, none of which can currently be expressed as an iterator.  * Nomenclature is still confusing: because a Dimension instance represents a table, we're stuck with "entry" as a row in that table, and "link" as its primary key.    These work well and solve real problems, but they also make it hard to reason about what's going on.    There are also some problems on the horizon that we need to solve; any major refactor at this stage should at least consider these as well:    * The {{ExposureRange}} Dimension is totally special-cased in preflight right now, because we need different entries for different DatasetTypes within the same Quantum.  But this will also be true of other Dimensions in future PipelineTasks (especially if we ever unify Exposure and Visit into Observation).   * We need to add a level of indirection between data ID keys and Dimension field names, to permit different Instruments to have different preferred observation IDs associated with different database fields.   * We need to add support for per-Instrument Dimension metadata tables.   * We'd like to remove the need for PipelineTasks to deal with both uppercase Dimension names and lower-case link names, since there's almost a one-to-one mapping between them (and there will be once ExposureRange is turned into a join for CalibIdentifier).    This is not a high priority, as we don't need any of this to get the current set of PipelineTasks working (though it may let us avoid hacks in CPP PipelineTasks).  
Answer: 390731.0

User story: "CADC has introduced a couple of build breaking changes that I have to fix.  Luckily those are contained in this readme:    https://github.com/opencadc/uws/blob/master/README.md"
Answer: 1443.0

User story: "As a first step to getting spatial queries to work, we should enable end users to use the qserv functions through the TAP interface.  This means adding a list of functions to the parser, and getting the plumbing right.  Once we do this, then we can rewrite ADQL spatial functions to use the qserv functions.  "
Answer: 23091.0

User story: "Following improvements are required in docsteady:   * parametrize the subsystem   * make the script more robust avoiding errors if some fields are not provided   * add  list of issues   * ensure that all LSST documents are rendered as citations, when mentioned in test cycles, or in any multiline field"
Answer: 27357.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: "Based on the description of OPS Rehearsal #1 (LDM-643), produce a dataset appropriate for the rehearsal.   Currently this will likely be some TS8 data but may need to be altered slightly to appear to be a unique set."
Answer: 503020.0

User story: We perform initial testing for batch job submissions to CC-IN2P3 Sun Grid engine queues, where we check, amongst various things,  on ability to utilize LSST software in /cvmfs, LSST software in singularity images, access /sps,  target machines with various profiles, etc.   We also test HTCondor glide-in scenarios to NCSA (HTCondor startd  running as the "job" submitted to CC-IN2P3 batch compute nodes, connecting to HTCondor Central Manager at NCSA for payload job submission, orchestration, etc.) 
Answer: 145488.0

User story: "Update the AT Header Templates following the Auxiliary Telescope Header Information mapping to CSC as discussed at the December 2018 Tucson meeting. The matrix describing it is here:    https://confluence.lsstcorp.org/display/SYSENG/Auxiliary+Telescope+Header+Information+Topic+Mapping"
Answer: 148539.0

User story: "Bucket story  for SST meetings and work in Mar 2019."
Answer: 148401.0

User story: "Bucket story  for SST meetings and work in Feb 2019."
Answer: 100802.0

User story: "Bucket story  for SST meetings and work in Jan 2019.     "
Answer: 66280.0

User story: "Testing running multiple instances of the ingress controllers and rules to deviate traffic either way"
Answer: 2.0

User story: "Tested use of a variety of file transfer tools for data transfer from CC-IN2P3  to NCSA, targeting  future use for transfer of processing resuts, as well as general mock-up for long distance transfer to NCSA from others sites( (inform on approaches from transfers from Chile, SLAC, etc)."
Answer: 27.0

User story: "Process the full 1.2i data  using the ctrl_pool/pipe_drivers tool. Run the singleFrame, coadd, and multiBand steps. "
Answer: 5.0

User story: "Update LDM-294 DMCCB"
Answer: 26059.0

User story: "Need to include metadata from the execution environment in the InfluxDB data model. In particular data from the HSC re-processing at NCSA is not being inserted in InfluxDB after DM-16660. "
Answer: 119299.0

User story: "In order to leverage lsst/templates, it's necessary for the project creation microservice to be able to use templatekit's APIs to inspect templates and create projects or files. This is easier if templatekit could be versioned and deployed to PyPI. In turn, this is easier if the templatekit code is independent from the data repository (lsst/templates).    This ticket is to migrate templatekit into github.com/lsst-sqre/templatekit and deploy it as a package on PyPI."
Answer: 25850.0

User story: "obs_lsstCam has been renamed to obs_lsst but this line in jointcal config wasn't updated:      [https://github.com/lsst/obs_lsst/blob/923c7018331960f8ff70b1a42301512db4d69b25/config/jointcal.py#L9] "
Answer: 70.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 that many people have issues using pyenv to install Documenteer if their personal environments have small idiosyncracies:  {quote}somehow the pyenv kept getting created with the python binary from the default miniconda installation and not the one from the conda env, and so the site_packages were all messed up, and complained about missing modules, but then after deactivating it was not restoring back to the conda env variables (even though the conda env looked to be activated, with the ps1 line and all) So as far as paths seemed to show things were fine, but the venv was tied to the wrong binary and that somehow was persisting after the venv was deactivating  {quote}  Given that, it's probably best to not recommend creating a venv virtual environment for Documenteer (just delete that content from the instructions).    The ultimate end game is to distribute documenteer and its whole dependency tree as part of the conda base environment created by newinstall/lsstsw."
Answer: 37795.0

User story: "Currently you can't change the config options that specify DatasetTypes to something new without explicitly registering them yourself first.  Make this something the command-line activator can (optionally) do for you.     "
Answer: 46.0

User story: "Create a routine that can ingest data to the gen2 butler.   Because of limitations of the command line (max 2mb of text), this either has to be done programmatically, or split up into manageable chunks if handed off to a command line subprocess."
Answer: 33104.0

User story: "Based on the API arrived at in DM-16925, file an RFC describing the plans for transitioning to PhotoCalib. In particular, this should describe changes that science users will have to make to their code to support this transition.    The story point count includes work to file the RFC, participate in discussion, and make minor changes to the plan based on the results. If significant further work is required before proceeding, that should be captured on other tickets.    The adopted RFC should trigger DM-10156."
Answer: 98103.0

User story: "Where possible, add a (deprecated, following the procedure in RFC-557 unless that RFC has been rejected by the time you get to this) backwards compatible API to PhotoCalib to enable it to act as a drop-in replacement for Calib.    Per discussion of 2018-12-19, the most important goal here is to provide conversion to/from magnitudes using the same API as Calib uses, but, in general, the aim of this ticket is to minimize avoidable disruption to “science users” when PhotoCalib replaces Calib, without imposting an unmanageable development load. (To meet the latter goal, I suggest timeboxing initial work on this to no more than a week or so before sending for review.)"
Answer: 154116.0

User story: "Design and implement directory scanning task"
Answer: 33297.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 that the API reference link for {{lsst.afw.display.BLACK}} isn't being rendered in the DM-16858. This ticket is to check on that, and ensure that module-level attributes are being documented by the Sphinx infrastructure."
Answer: 83.0

User story: "Install the lsst-texmf repository in full into its Docker distribution. This will fix issues where \{\{generateAcronyms.py}} attempts to find a glossary file in etc/, but it is missing.    Also check that Python is installed in the Docker image (and drop Java since GaiaAcr.jar is replaced by generateAcronyms.py).    See also: https://github.com/lsst/lsst-texmf/issues/147"
Answer: 1419.0

User story: "The adaptArgsAndRun api for PipelineTask needs to include a butler object."
Answer: 35.0

User story: "{{Calib.h}} has a handful of free functions for converting between physical flux and magnitude ({{abMagFromFlux}}, {{fluxFromABMag}}) and their errors ({{abMagErrFromFluxErr}} and {{fluxErrFromABMagErr}}). The former two are used 10 times total outside of Calib and its tests, the latter two are used 8 times (error uses are in PhotoCalTask and fgcmcal). The flux/mag conversions can be trivially replaced by astropy (e.g. {{(flux*units.Jy).to_value(units.ABmag)}}), but it's less clear what to do with the error calculations. Unfortunately astropy doesn't support that error propagation directly (though I'm sure they'd be happy to take a PR from us) to do so.    {{lsst.afw.image}} doesn't seem like the right place for them to live. Possibly {{lsst.utils}}? They'll get more useful names (e.g. {{nanojanskyErrToABMagErr}}, {{abMagErrToNanojanskyErr}}?) too.    Replacing the flux/mag functions with {{astropy.units}} blocks DM-10156."
Answer: 769066.0

User story: "RFC-556 raised several points that need to be incorporated; this ticket branch will hold them as part of the CCB approval."
Answer: 81945.0

User story: "DeblendAndMeasureTask has not been updated since 2014. It has bitrotted.  "
Answer: 1058.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: Sent email to Xiuquin Wu, <USER>and <USER>ipac to collect the following:   # Do you need any additional hardware to make the service fault tolerant?        # Is the software ready to make use of any (above) new hardware? If no, what is your best estimate on when should we plan to have any new hardware ready?        # When planning a maintenance, what process(es) should be followed to effect a "rolling upgrade"?    For example: If service runs in a "primary-failover" model, then the process might be: run update on backup, then promote backup to primary, then upgrade [new] backup server.    Or another example: if service runs in an "all-servers-active" mode: update one or more at a time, wait for those to recover, then repeat until all servers are updated.        # Who would perform the "service migration" actions during a rolling upgrade?        # Do developers still need root?        # Does moving to kubernetes change necessity of root access?        # Does moving to kubernetes change anything else relating to fault tolerance and/or hardware needs?
Answer: 361427.0

User story: Sent email to Fritz Muller and <USER>to gather the following information:   # Do you need any additional hardware to make the service fault tolerant?        # Is the software ready to make use of any (above) new hardware? If no, what is your best estimate on when should we plan to have any new hardware ready?        # When planning a maintenance, what process(es) should be followed to affect a "rolling upgrade"?    For example: If service runs in a "primary-failover" model, then the process might be: run update on backup, then promote backup to primary, then upgrade [new] backup server.    Or another example: if service runs in an "all-servers-active" mode: update one or more at a time, wait for those to recover, then repeat until all servers are updated.        # Who would perform the "service migration" actions during a rolling upgrade?         Additional questions not directly related to fault tolerance:   # Do you (developers) still need root?   # Does the move to kubernetes change necessity of root access?   # Still need "/lsst" mount?   # Still need "/datasets" mount?
Answer: 361428.0

User story: [~<USER> reasonably points out in the review for DM-16819 that the "run" argument to {{Butler.\_\_init\_\_}} is confusing if one isn't already thinking about {{lsst.daf.butler.Run}} (and that will be beneath the notice of many users).  We should find some other way to construct a read-write Butler.     
Answer: 666839.0

User story: "Test galaxy models consisting of two elliptical components with their radial profiles describe by N Gaussians on COSMOS (HST, then HSC)."
Answer: 240623.0

User story: "File creation with webdav in nginx doesn't set the user of appropriately as the file owner, nor the group. Investigate a way to at least fix the file owner."
Answer: 32876.0

User story: "Turn MeasureMergedCoaddSources into a PipelineTak"
Answer: 45956.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 doing the review for DM-16650, I realized that `fgcmcal` had an error in the units used to compute the "absolute" calibration from the reference catalog.  
Answer: 3263.0

User story: "the manuscript is available online :  https://www.overleaf.com/read/yryfbzrdryhm   "
Answer: 275923.0

User story: "Implementing RFC-554, there will be a lot of renaming but some code needs dependency cleanup and API change.    This ticket covers moving modules from pipe_supertask into pipe_base and new package ctrl_mpexec. Further re-factoring of ctrl_mpexec contents will be done on a separate ticket."
Answer: 25779.0

User story: "Convert existing python docstrings to numpydoc format."
Answer: 2846.0

User story: An option that might improve the DcrModel is to make the model relative to a reference image. Each subfilter model plane would act like a "rubber sheet" that can enhance or suppress the flux of the reference image in a pixel, rather than storing the absolute flux for that subfilter. This may make it easier to apply regularization, and ideally will also prevent noise being amplified.    If this feature ends up creating more problems than it solves, or otherwise does not perform as well as the original code, it should be closed as Won't Fix.
Answer: 65942.0

User story: "\{\{git clone https://github.com/guyonnet/slitless_image_reduction/}}    clone croaks & install it    Install and configure SExtractor    Get the pipeline running.    Then port it to py3 so it can be run from the same env as the stack.     "
Answer: 3054.0

User story: "Currently, fits file generated from forwarder are not compressed. Fits file needs to be compressed using fpack mechanism."
Answer: 162354.0

User story: "Some SAL topics have array data type which, when converted to Avro, are not supported by the InfluxDB sink connector.     Example:    https://github.com/lsst-sqre/kafka-efd-demo/blob/master/schemas/ts_xml/develop/MTMount_Elevation.json#L103    This is the error message we get from {{Kafka-connect}}:    {noformat}    Task threw an uncaught and unrecoverable exception. Task is being killed and will not recover until manually restarted. (org.apache.kafka.connect.runtime.WorkerSinkTask)  java.lang.IllegalArgumentException: You can't select * from the Kafka Message. Field:'Elevation_Interlocks' resolves to a Schema 'ARRAY' which will end up with a type not supported by InfluxDB API.  {noformat}  "
Answer: 46087.0

User story: "Convert the deblending task to the PipelineTask framework. This will involve creating two new PipelineTasks to do the same work, one for single band, and one for multiband deblending as they have different quantum units of processing."
Answer: 10698.0

User story: "In addressing a review comment, a type-o was introduced. This ticket will fix that."
Answer: 61.0

User story: "goals:   * Test results that's easy to understand   * Minimize the work needed to create a test   * Tests must be isolated from others. Minimizes bad results."
Answer: 5353.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're seeing repeated failure to sync information about active branches, etc, between GitHub and Jira (DM-9697, DM-14876). We've previously tried to address this my removing inactive branches from GitHub, but but this has not properly resolved the problem (possibly because we haven't been aggressive enough about this trimming, but we don't want to lose anything precious).    Best current bet is to upgrade to the new Jira-GitHub integration system, https://github.com/integrations/jira. (This replaces the old Jira-DVCS-Connector, which we are currently using)."
Answer: 457239.0

User story: "Now that the environment is defined in scipipe_conda_env package, we have to update lsstsw and newinstall.sh to use the new github package instead of the environment defined in lsstsw.    At the moment the lsstsw revision used for the environment is {{fcd27eb}}.    This commit (update linux/osx conda packages) corresponds to the     d8778d3    reference in scipipe_conda_env."
Answer: 56035.0

User story: "PipelineTask command line activator should be able to accept config overrides which are lists from the command line."
Answer: 4351.0

User story: "Add pyvo to JL environment"
Answer: 21.0

User story: Running deepCoadd_skyMap (and similar Datasets) through gen2convert does not result in the set the "skymap" dimension key, which breaks PipelineTasks that use those Datasets as inputs.  This is due to missing translation rules in the gen2convert package.     
Answer: 290.0

User story: "Requested by Zeljko. To include an overview of capabilities as well as potential cost savings. Initial text provided by [~<USER>."
Answer: 39189.0

User story: "While converting PhotoCalib to be defined in nanojansky, I realized it would be good to add versioning to its persisted output. [~<USER> says that SkyWcs is probably the best example of how to do this (sadly, we have neither a standard nor a common convention for how to version persisted afw objects).    For example, we are going to want to add a wavelength dependency in the future, which will definitely change the persistence."
Answer: 2980.0

User story: "Got the following while butlerizing some Dev runs in the {{LCA-11021_RTM-006-Dev}} folder of the SLAC test stand data:   {{ingest.parse WARN: translate_detector failed to translate detector: 'RTM-006'}}    Is it valid to add to the raft serial dict?     One example file:    {{/project/rgruendl/SLACmirror/SLACgpfs/jh_archive-test/LCA-11021_RTM/LCA-11021_RTM-006-Dev/5884D/xy_stage_acq/v0/38955/S22/E2V-CCD250-217-Dev_10.50_10.60_021_5884D_20180426174356.fits}}"
Answer: 4982.0

User story: "using the qserv integration test dataset, a query like {{select objectId from Object where objectId > 0}} returns far fewer rows than {{select objectId from Object}}, which should be an equivalent query since objectId is always greater than 0."
Answer: 373078.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, the classes in {{lsst.verify.compatibility}} do not use any Gen 3 elements, including {{lsst.pipe.base.InputDatasetConfig}} and {{lsst.pipe.base.OutputDatasetConfig}}. However, [~<USER> [suggested|https://github.com/lsst/ap_verify/pull/55#discussion_r241553699] that these config classes can be used in Gen 2 task configs without inadvertent side effects. Adopting them as part of the {{MetricTask}} API now will make it much easier to transition to Gen 3.    This ticket covers the following work:  * Update {{MetricTask}} documentation to require that subclasses use {{*DatasetConfig}} appropriately.  * Rewrite {{MetricTask}} input/output methods to use the configs in a way that is compatible with Gen 2 repositories.  * Rewrite {{TimingMetricTask}} (and any other extant {{MetricTasks}}) in terms of {{*DatasetConfig}}. This should reduce the amount of source code at the cost of an extra config field."
Answer: 38895.0

User story: "Format sql queries with query parameters for better debugging"
Answer: 5545.0

User story: "Follow up DM-15911 to determine smooth sizes and weights for a 4-component Gaussian approximation to a Sersic profile (rather than 8)"
Answer: 90618.0

User story: Write minimal shims that implement *some* Gen2 APIs using Gen3 implementations.  That will start with just get and put on DataRef and Butler, for Tasks that (at most) just pass Data IDs around without looking at what's in them.    Future ticket could add some data ID translation, if we decide that's better than putting conditional logic in the Tasks themselves.    Also add a "gen" attribute to both Butler classes, so conditional code can actually be written.
Answer: 7454.0

User story: [~<USER> would like to be able to build docker images under jenkins and push them to docker hub.  This requires a docker hub "role" account to be setup and credentials installed into jenkins.
Answer: 11256.0

User story: "ingestCalibs [modifies the validity ranges of calibs|https://github.com/lsst/pipe_tasks/blob/master/python/lsst/pipe/tasks/ingestCalibs.py#L97-L175], since there may be some overlap in the validity ranges after adding new calibs. However, this applies the new validity range to all calibs, even those that do not have an overlapping validity range. It also operates on all types of calibs, so that when ingesting flats, the validity ranges of biases can be modified.  The end result is that is not currently possible to maintain more than a single validity range within the entire calibs registry."
Answer: 353104.0

User story: "Preparation of the talk presented to UW group showing updates on SQuaSH, in particular the adoption of the InfluxDB+Chronograf+Kapacitor stack.    "
Answer: 4.0

User story: "The C++ documentation guide recommends providing package documentation using Doxygen groups, which are being phased out. The section on package documentation should be rewritten (possibly as a link) pointing developers to the new Sphinx-based system."
Answer: 31691.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 that if doCrosstalk is set to True, rather than raising like all other parts of isr (right?!) when failing to find the necessary calibration products, processing continues, and sets all xtalk bits in the mask plane.         Fix should be to raise if parameters aren't found, in keeping with doBias, doFlat, etc."
Answer: 40191.0

User story: Update test specification template following comments from PR 6 in LDM-533:   * remove text: "Follows the list of test cases documented in this specification"   * remove "Critical Event" from the test cases head table   * change "Requirements" with "Verification Elements"   * Use "Predecessor" instead of "Intercase Dependencies"   * add the \section heading for appendix A to the appendix template
Answer: 20208.0

User story: "Currently a quantum graph does not contain information about arguments to be passed to the __init__ function of a pipelinetask. This causes init input arguments to not be copied to a new collection during processing. This ticket will add init input arguments to the quantum graph."
Answer: 3214.0

User story: Lead a discussion and propose ways to provide the information for "preferred/popular data" from project point view, how application should respond to the given information and present UI accordingly.  
Answer: 141904.0

User story: LSST has "Proof of Concept" work with Google in GKE.  There was issue with multicast capability that Firefly cache relies on for its auto-discovery broadcast. According to [~<USER>, this issue has been resolved with Weave net. We need to test Firefly servers on GKE to confirm it that multiple Firefly servers can communicate with each other.
Answer: 74299.0

User story: "http://adsabs.harvard.edu/abs/2018AJ....156..186M produced classified lightcurves for the HiTS dataset.  This ticket is to produce an initial comparison of that catalog to the results of our ap_pipe processing."
Answer: 194616.0

User story: "We need a secret storage system for:    1) moving Jenkins to NCSA  2) standing up a k8sified Kafka message bus  3) retooling JupyterLab deployment to use terraform.    So: it's time to stand up Vault so we get that thing."
Answer: 22998.0

User story: "It's currently a pain to write any tests for successful Gen2->Gen3 conversion or PipelineTask execution in ci_hsc beyond just testing that the code ran through to completion.  That's currently a blocker for the tests I would have liked to add on DM-15503.    Rewriting the ci_hsc SConstruct to separate the data IDs from the execution script and make the validation tests regular unit tests should solve both of those problems.    This is a potentially open-ended problem; shouldn't spend more than a day actually working on it, as we don't need to make it perfect."
Answer: 413312.0

User story: "Skymap supports turning index pairs into a sequential number. A method is needed to turn these sequential numbers back into pairs."
Answer: 4870.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: "Partition and create new FS for data backbone, including determining mount options and creating appropriate permissions."
Answer: 3.0

User story: "There is a common pattern in man of our tasks where dataset types share a common sub string. This ticket will introduce a way to template these names and format them at configuration time."
Answer: 14961.0

User story: "To include:   * Images repository   * LDM-564   * LDM-503"
Answer: 33.0

User story: "Deliverables:  * REST services for monitoring and managing the Replication System  * Web UI for displaying the status and managing the Replication system and Qserv"
Answer: 144063.0

User story: "Background: https://github.com/LSSTDESC/DC2-production/issues/307    Quick how to reproduce from [~<USER>:   {code}  processCcd.py /datasets/DC2/repo --rerun private/<USER>--id visit=1237924 raftName=R43 detectorName=S22  {code}    See if we can come up with an appropriate configuration for selecting and fitting calibration stars with low source density  "
Answer: 41730.0

User story: "Rather than just populating the monthly report with milestones which are due that month, I should be able to generate and circulate a summary of all upcoming milestones through the duration of construction."
Answer: 270.0

User story: "Create a consumer for the mock SAL experiment in https://github.com/lsst-sqre/kafka-efd-demo to verify that the messages are formatted correctly and to help [~<USER> diagnose decoding issues seen with Kafka Connect for InfluxDB."
Answer: 9864.0

User story: "Do the following:   * Update display_firefly to work with the firefly_client updates for Jupyter lab   * Update the Pip install of firefly_client   * Update firefly_client fork on the lsst side   * Test the whole think so that it is working together correctly"
Answer: 66499.0

User story: "-The daily build of pipelines.lsst.io includes a section for {{lsst.display.firefly}}, but it is only a stub. We wrote a user guide previously in DM-10601 which at that time was hosted on a temporary site. The {{index.rst}} file needs to be moved into the right subdirectory.-    As part of DM-16782, the module documentation for {{lsst.display.firefly}} was moved to the right location to appear on pipelines.lsst.io. This ticket is to expand the user guide to document the new functionality that has been added in recent months. The user guide will contain some pages that apply to the LSST Science Platform case, and some other pages that cover our other supported use case of a user running the stack and Firefly locally on their own desktop or laptop.    -If feasible, the work in this ticket will enable {{automodapi}}, as has been done for {{lsst.display.ds9}}. This likely will require updates to docstrings.-    "
Answer: 96818.0

User story: "Details of the analysis are here:    [^aodmerra15species.pdf]"
Answer: 345.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 mock SAL Kafka producer (DM-16692) use random numbers to emulate the topics using the SAL Avro schemas.    The InfluxDB Sink connector must be configured to consume those topics.   "
Answer: 10046.0

User story: In DM-18103 we revisit the SQuaSH InfluxDB data model.     You can use this notebook to try different strategies mapping {{lsst.verify}} data to InfluxDB. You can also use it to "manually" synchronize the SQuaSH production database with an InfluxDB instance. 
Answer: 135066.0

User story: "Restrict which nodes Hub and Firefly can start on."
Answer: 84904.0

User story: "Move deployment framework from homebrew to terraform."
Answer: 85128.0

User story: From DMTR-91, pull request 1, following improvements shall be done:        * "*The* following personnel ....."   * change "\{\it ..." to "\textit\{...." and put test case name.
Answer: 27386.0

User story: "The base tests provided by {{obs_base}} require test data to run on.  Because of this, we will need to pick at least one on sky image per instrument to run the tests."
Answer: 49207.0

User story: "What was lsst-pdac will have a new name and will be its own set of namespaces within the NCSA k8s commons."
Answer: 59399.0

User story: "There are base tests that can be subclassed and will provide good coverage of basic functionality of the obs_lsst package.  The {{obs_test}} package has an [example|https://github.com/lsst/obs_test/blob/master/tests/test_obs_test.py] for how this would be done.  There will need to be one test for each of the instruments serviced by {{obs_lsst}}."
Answer: 28862.0

User story: "There is very little code in {{ci_lsst}}.  I think we should merge that code into {{obs_lsst}} proper.  This is somewhat counter to how some other packages do this, but since the script is very specific to {{obs_lsst}}, I think that may be the most helpful thing to do."
Answer: 8681.0

User story: "This is to create a git-lfs repository to hold the test data necessary for running the test script provided by RHL in [ci_lsst|https://github.com/lsst-dm/ci_lsst]."
Answer: 4474.0

User story: "During the generation of LSST asteroid discovery and data rates likely to be submitted to the IAU Minor Planet Center, discrepancies in the results for different asteroid orbit distribution models (S3M / S3M JPL / MPCORB) and sample sizes have been detected. <USER>has offered her assitance in tracking down the origin of those discrepancies.     "
Answer: 223255.0

User story: "Once Pytrax is running in a local environment, it has to be validated and compared to the current LSST MOPS linking algorithm in terms of efficiency.         DELIVERABLES:    1) Validation of Minor Planet Center results with local Pytrax configuration    2) Comparison with current LSST MOPS in terms of linking efficiency for a standard set of detections (e.g. Veres)"
Answer: 223327.0

User story: "Monthly test to catch issues early"
Answer: 227701.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "test to make sure the system still work as it used to after the hardware merged into the k8s commons. "
Answer: 116639.0

User story: "Submission of an abstract to the 2019 IAA Planetary Defense Conference (PDC) describing the LSST moving object processing system.    In accordance with the LSST deputy director and the organizing committee of the PDC, an abstract is submitted detailing the current layout and future capabilities of LSST MOPS in light of the LSST's potentially significant future contribution to asteroid discovery and planetary defense.          DELIVERABLES:    Abstract          "
Answer: 15.0

User story: The IAU Minor Planet Center (MPC) has developed a new linking algortihm (HelioLinC,  Holman, M.J., et a. 2018. _The Astronomical Journal_, _156_(3), p.135.) that promises to be an efficient alternative to the classical moving object processing system (MOPS) linking.    HelioLinC is currently under development as part of the "Pytrax" package (M. Lackner, 2018).     In order to evaluate the potential of HelioLinC to reduce complexity and increase efficiency in the LSST-MOPS ecosystem, the package needs to be locally installed and tested against the classical MOPS (epyc.astro.washington.edu).    Since the package was custom built for the MPC the installation requires code modification that have to be performed together with the code author M. Lackner via teleconferencing.    DELIVERABLES:    1) Create a conda enviroment to install and run Pytrax on the local machine epyc    2) Test the installation using standard tests collected in a Jupyter notebook provided by the MPC          
Answer: 201.0

User story: "Finalize the LSST-MOU text, incorporating comments from the MPC. Deliver a final version that is ready to be signed by all parties."
Answer: 338712.0

User story: "Keep the Notebook Aspect working with current-released version of JL and other components."
Answer: 126634.0

User story: "After running the test plan documented in DMTR-91 (LVV-P1), some test cases have been updated.    Therefore the LDM-533 need to be updated."
Answer: 61900.0

User story: "Considering the comments collected until now, DM model need to be updated."
Answer: 8949.0

User story: "Test the build and release process.  This includes making all the relevant branches and mocking a feature branch that needs to be included (i.e. more than one release candidate)."
Answer: 1731.0

User story: "This milestone will be demonstrated by executing test plan LVV-P16.    Successful execution of this test plan will mark the completion of milestone LDM-503-07."
Answer: 61885.0

User story: "The LVV-T368 test case, step #2, has a typo (a missing {{~/}} prefix to the string {{notebooks}}). Please fix it."
Answer: 6713.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: "Key points include:   * Generating figures of images *and* objects/sources from a recent ap_pipe run on the HiTS dataset   * Making light curves for a few illustrative objects of interest   * Doing a preliminary comparison of results with the HiTS data release   * Amazing flowcharts and poster design adventures"
Answer: 51379.0

User story: "In a convenient test environment (e.g., a notebook), test the major configuration options of {{lsst.pipe.tasks.imageDifference.ImageDifferenceTask}}.    I suggest starting with:    * {{ImageDifferenceConfig.subtract}}  * {{ImageDifferenceConfig.decorrelate}}  * {{ImageDifferenceConfig.doSpatiallyVarying}}    but ultimately we should test all of the various options (unless they are trivial or of obviously no value).    The immediate deliverables for this are:    * A table describing each option — what it does (if that's not obvious from the documentation), how it was tested, and whether it works;  * If something is found to be broken, file a Jira ticket describing the problem so we can fix it later.    For bonus points, think about how to turn these tests into an automated test suite, in line with the other tests in the {{pipe_tasks/tests}} directory — but we should file another ticket before investing serious effort on that.    "
Answer: 109455.0

User story: "JupyterLab allows creating dask clusters.  Putting users in their own namespace allows for putting limits on the size of those clusters.  Test whether this works from the LSP at LDF."
Answer: 2.0

User story: "This will create symmetry with teardown and, I hope, get rid of the problem where logout that is not followed by closing the window re-runs init() which then recreates the resources, leading to confusion on later logins."
Answer: 1395.0

User story: "Create a gke deployment of the helm chart [~<USER> modified in DM-16533 plus establish route53 records, prometheus metrics collect and a grafana dashboard. "
Answer: 11738.0

User story: "add support for XOR in the WHERE clause. t    This will require extending our IR to support NOT in more locations, no that we can express XOR in disjunctive normal form, where {{a XOR b}} becomes {{(NOT a AND b) OR (a AND NOT b}}. I think it means adding NOT to {{BoolFactor}}, but this will require some research & verification."
Answer: 45.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 the near future, once I get the TAP service that is deployed at NCSA up to at least some level of stability, I need to provide a reference notebook that uses pyvo to access the data and allows people to run queries.    I've got the notebooks for the demos, but I think also adding in some of the other queries on Fritz's list of example queries is a good idea.  (as they become supported, most use qserv_ funcs that as of today aren't supported)    This also means bringing in pyvo into the container build, which shouldn't be a problem."
Answer: 23093.0

User story: "Sometimes when running a TAP query through the CADC frontend, I get the following error that has bubbled up from Presto:    SQLException: Query failed (#20181204_195142_00054_3t528): Unknown transaction ID: 8fbec9c7-e6d3-48cd-a3e6-6f79acdffdb8. Possibly expired? Commands ignored until end of transaction block FailureException: Unknown transaction ID: 8fbec9c7-e6d3-48cd-a3e6-6f79acdffdb8. Possibly expired? Commands ignored until end of transaction block    This is not good.  Things can get stuck and the connection doesn't seem to get reaped as done.  Really I need to root cause this and figure out what the model is for querying this, since we don't really need transactions to just do a bunch of selects.  There's some code in the CADC query runner that handles autoCommit and such, so that's the first place I'd look."
Answer: 23102.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: "Create a prototype page which would allow to browse TAP schema and submit queries to the selected TAP service."
Answer: 23319.0

User story: "We can simplify configuration if we just expose the flag specifying authentication type (CILogon vs Github) and then choose the appropriate class based on that."
Answer: 36.0

User story: "Job     [https://ci.lsst.codes/blue/organizations/jenkins/release%2Fbuild-publish/detail/build-publish/161/pipeline]    failed in the archive stage"
Answer: 312.0

User story: "This ticket will add the fgcmcal-tract mode to fgcmcal to allow small-scale processing of a single tract."
Answer: 387630.0

User story: The photometric calibration output from fgcmcal is of the "jointcal-photoCalib" type even though a compatible "fgcmcal-photoCalib" dataset is defined in obs-base.  The primary difference between the two is the template, as "fgcmcal-photoCalib" does not require a tract.  This ticket will add the appropriate template to obs_subaru and update fgcmcal to output the new dataset type (without a fake tract).
Answer: 50347.0

User story: Currently, fgcm runs without any reference stars for the fit, solving everything internally for a relative calibration.  Reference stars can be loaded to create an absolute calibration for the final output.    For the new "fgcmcal-tract" mode, we need to be able to use reference stars in the fit.  We will also be able to use these reference stars for absolute calibration in the case that a small number of calspec/WD stars with known SEDs are available.    This ticket will add the ability to use reference stars in the fit, and allow additional absolute calibration terms.
Answer: 255603.0

User story: "Currently, only the star-flat term (determined from multiple exposures) is allowed to be spatially variable in fgcm.  All other throughput terms (from the atmospheric model and the final gray correction) are only computed per-ccd.  This ticket adds the option to compute the ccd gray correction with a 2d chebyshev polynomial of configurable order."
Answer: 73971.0

User story: "DM-15895 investigated the source of the bimodality in the HSC S18a fgcm run when comparing HSC r-band to Gaia G band.  Most of the relative offset between different regions of the footprint was due to differing throughput of the HSC r and r2 filters.  This ticket will add additional fit terms to fgcm to allow for these sorts of throughput offsets (which also applies to the HSC i/i2 filters)."
Answer: 22463.0