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: -See [https://confluence.lsstcorp.org/display/DM/Dataset+and+Collection+Table+Reorganization|https://confluence.lsstcorp.org/display/DM/Dataset+and+Collection+Table+Reorganization;]; this should move the schema from something like the "Partition datasets (only)" to the final design  on that page.-    Superseded by [https://confluence.lsstcorp.org/display/DM/Architectural+Prototype+for+the+New+Gen3+Registry] (which is not that different). Goal of this ticket is now to make runs a type of collection; this involves:   * requiring registration for new tagged collections as well as runs;   * giving the (recursive) tagged collection associated with a processing run a different name than the run-collection. This will probably be the responsibility of {{pipetask}} rather than Butler.    This will add the general framework that will let us add more types of collections later (calibration collections and maybe virtual collections), but we won't actually do that here.
Answer: 222486.0

User story: "{{lsst-sqre/jenkins-dm-jobs}} needs to be more generally accessible by DM devs.  The easiest way to accomplish this is to move it out of the {{lsst-sqre}} github org."
Answer: 44.0

User story: "To support FITS-TAB WCS a few of the AST FitsTable methods need to be added to astshim."
Answer: 24522.0

User story: We need to make sure the type of exposure (e.g. "science", "bias", "flat") is extracted from metadata and put into the registry's exposure table in ingest.  I think this is what's called OBSTYPE in FITS, and I'm not sure if ObservationInfo already includes it and we drop it on the floor in ingest, or if we need to add it to astro_metadata_translator (either way, I'm sure that's on [~<USER>'s radar).    In any case, this is becoming particular important as we prototype Gen3 CPP pipelines, which we of course want to run only on raws with specific types.
Answer: 434.0

User story: "Create the docker runtime environment for running the OODS."
Answer: 28821.0

User story: The ATHeaderService has been "dockerized" and can be run a service from inside a container. However, the container version has not been tested outside docker at the NCSA test stand and need to be deployed and test communication with other CSCs on the same network.
Answer: 9860.0

User story: "service.describe() doesn't work because it apparently goes to /tables, which needs to be explicitly added to the jupyterlabutils part of the getting the catalog."
Answer: 5868.0

User story: "So, tokens expire in the notebook all the time, and aren't refreshed.  This causes no end of confusion, and it's hard to tell when someone's token is busted.  Create a notebook to help debugging of token issues."
Answer: 5891.0

User story: "Make acronyms table inline with other LSST table"
Answer: 49344.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: "Fritz, Gregory, and I have all seen that /availability throws a 503.  Here's the stack trace, looks like its trying to look up some java class and not finding it:         2019-10-18 17:39:58.231 TAP ObsCore [http-nio-8080-exec-8] ERROR AvailabilityServlet  - BUG    java.lang.NullPointerException    at java.lang.Class.forName0(Native Method)    at java.lang.Class.forName(Class.java:264)    at ca.nrc.cadc.vosi.AvailabilityServlet.doGet(AvailabilityServlet.java:126)    at javax.servlet.http.HttpServlet.service(HttpServlet.java:635)    at javax.servlet.http.HttpServlet.service(HttpServlet.java:742)    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)    at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198)    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:496)    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140)    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81)    at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:650)    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342)    at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:803)    at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)    at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:790)    at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1468)    at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)    at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)    at java.lang.Thread.run(Thread.java:748)"
Answer: 16071.0

User story: "The goal is to run integration tests on a Qserv instance, with no other data, and to update Qserv component to the very same version used in PDAC 'shmux-orchestrated' Qserv.    Qserv components will be also updated to latest version."
Answer: 131038.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 ability to gather current sets of orbital elements and covariances of known Solar System objects is essential to identify moving objects in LSST images. The python interface below queries the Small Body Database API to receive this information. Since the Minor Planet Center does not currently provide orbit covariances, these routines will be used to validate moving object identification.      https://github.com/lsst-dm/pysbdb"
Answer: 78700.0

User story: "Based on existing reprocessed DC2 data and the ticket branch of DM-16234, execute   writeObjectTable.py transformObjectCatalog.py consolidateObjectTable.py to create Object parquet file "
Answer: 70255.0

User story: "report"
Answer: 152483.0

User story: "Prepare a tutorial session in the Kavli Petabytes to Science workshop at Boston    [https://petabytestoscience.github.io/workshop-iii]"
Answer: 25827.0

User story: "Test and troubleshoot the newly made AMIs.          For example whether condor jobs run, whether annex workers join the pool, whether necessary software run as expected, etc. "
Answer: 36072.0

User story: "Based on the w_2019_38 stack (before the backward incompatible change in the Gen3 registry and the missing RC2 repo generation code), integrate the steps and test execution. Use tract=9615, the HSC-RC2 tract as in the June/July milestone run. Troubleshoot issues. "
Answer: 139448.0

User story: "As discussed on slack, https://lsstc.slack.com/archives/C2JPXB4HG/p1571320209017600 it would be useful to use fgcmcal to propagate candidate psf flags, per band, to the final output star catalog.  This will either be the fraction of input visits for which a star had the candidate psf flag set, or the number of input visits with the flag set and the total number of visits with the given star.  This information can then be used downstream for a more uniform selection of psf stars and a reserve list that is not used."
Answer: 25934.0

User story: "With DM-21048 it is possible to read in raw data even when the filter is not listed in the obs package, although a warning is given.  This can be annoying because currently a warning is given for each amplifier, although it is unnecessary to set/check the filter when reading in amps, it only needs to be done (and is done!) when assembling the ccd.    It appears as though the place to put the change is in https://github.com/lsst/obs_lsst/blob/aeaebe9ad92137ac7a57e2bd580746e2cbffe16f/python/lsst/obs/lsst/lsstCamMapper.py#L393 where the call to {{self._standardizeExposure}} should have {{filter=False}}."
Answer: 1542.0

User story: "Learn to be Robs replacement for M1M3 as he leaves before it will be complete."
Answer: 9125.0

User story: "This ticket is to capture the work of writing an RFC as a conclusion of DM-16544."
Answer: 11388.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "h1. Objectives   * learn about the catalog and its data model   * identify (and download if necessary) catalog data   * evaluate data and apply corrections/transformations if needed   * figure out schemas of the catalog's tables:    * prepare configuration files needed by the _partitioner_ tool   * partition input data into _chunks_ for the partitioned tables   * configure a new catalog in Qserv and test-ingest а small batch of the LSST Object-alike rows into it. Then QA results    h1. Infrastructure    Store intermediate (input, processed, configurations) data at the *GPFS* folder:  {code:java} /datasets/<USER>gaia_dr2/{code}  Perform all data formatting and pre-processing using the following resources:   * the interactive machine {{lsst-dev}} for small processing   * the LSST Verification Cluster (managed by *SLURM*)    Use LSST Stack and the _partitioning_ tool from:  {code:java}% exec scl enable devtoolset-6 rh-git29 bash  % source /lsst/software/lsstsw/stack/loadLSST.bash  % cd /datasets/<USER>hsc_rc2/cd partition/  % setup -r .  % which sph-partition  /datasets/<USER>hsc_rc2/partition/bin/sph-partition{code}  Perform the actual loading directly from the machines of the *Qserv* cluster  h1. Documentation   * GAIA DR2 catalog info: from: [https://www.cosmos.esa.int/web/gaia/data-release-2]   * Data Model: [https://gea.esac.esa.int/archive/documentation/GDR2/Gaia_archive/chap_datamodel/]   * An example of using the low-level *Ingest* framework: [https://confluence.lsstcorp.org/display/DM/Live+demo%3A+test+ingest+of+a+subset+of+one+track+of+the+HSC+Object+catalog]                         "
Answer: 67729.0

User story: "In connection to DM-21702, it seems that the main reason of the exploding number of sources in the science convolution case is a lower variance level in the difference images.   * Check the operations that result this lower value.   * Check what operations are performed in the decorrelation step."
Answer: 48941.0

User story: "Somehow a number of changes made on May 16 in the {{deblender-sprint}} branch on {{meas_extensions_scarlet}} did not get merged into DM-19991 with the rest of the deblender sprint tickets. This ticket is to re-implement those changes, which includes    * adding a blank source for point sources that fail to initialize (this is only temporary, since a more permanent solution will be implemented in DM-19790  * fix bug that prevents PSFs that are different sizes in each band from being combined into a multiband PSF (to be implemented in {{afw}} with DM-19789)"
Answer: 90820.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "1) Identify and gather software related wants from out team. Aside from the obvious SAL update, branstorm with Dave and other relevant members what is expected for me to be able to do with the software.    2) After identifying a few items attempt to understand the code BEFORE the visit to spain. This will produce nots and questions    3) Prepare and make these notes public or if useful put them down on confluence or an lsst.io page to begin documentation on this software. Perhaps talk to Andrew Serio since he has a way we should be organizing our documentation.     4) Put all of this preparation in a Confluence page and create some collaborative information."
Answer: 37042.0

User story: "This task is to make further progress on our teams documentation. For this task I will be focusing on the status of our githubs documentation and looking into how we can integrate our pdf.     I will also create content that will give an overview so that developers know the status of our documentation."
Answer: 17511.0

User story: "Previous work on fitting COSMOS HST images used custom scripts to fit cutouts from a pre-existing GalSim catalog (DM-15354). This ticket will implement an option in the MultiProFitTask to take a catalog (e.g. from HSC) and fit HST cutouts without relying on the GalSim catalog, which will make it convenient to generate truth-y tables for isolated sources."
Answer: 34149.0

User story: "Add a Config parameter and implement fitting a single Gaussian with no PSF convolution in the MultiProFit task, ideally minimizing overhead by using as little of MultiProFit's fitutils as possible."
Answer: 38878.0

User story: "How do we offer users the ability to submit Argo Workflow jobs as an alternative to interactive containers?"
Answer: 125248.0

User story: "- Update the milestones repository with data extracted from PMCS (/)   - Update LDM-503, LDM-564, images repository  (/)   - Update milestone dates loaded into Jira  (/)   - Update skeleton July 2019 monthly report (/)   - Audit and update [https://confluence.lsstcorp.org/display/DM/DM+PMCS+Update+Requests] (/)"
Answer: 252.0

User story: "DM-21263 packages the wavelength in output FITS files as a separate data array semantically distinct from the primary data. This ticket changes the output FITS files to store the wavelength using the FITS -TAB standard format as documented in FITS paper III."
Answer: 24548.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: "(original description is no longer accurate; see comments)    -Registry's provenance tables - execution, run, and quantum - can't currently be fully populated without having database updates.  For example:-   * -you can't insert a dataset until after its run has been inserted;-   * -you can't insert a run until you've inserted the execution it inherits its ID from;-   * -you can't insert an execution until after it's completed, because it has an end timestamp field.-    -Work through low-level use cases for these tables and ensure we can actually have all of their values when it's time to insert them, splitting up tables as necessary.-    [~<USER>-,- [~<USER>-: this ticket exists because I'm assuming updates are a problem.  Please let me know if they aren't or if you have any expections/requirements/wisdom on when various provenance records should be inserted relative to the datasets they refer to.-"
Answer: 89648.0

User story: "https://github.com/dask/dask-kubernetes/issues/181    I need to write and PR the RBAC docs."
Answer: 20172.0

User story: "The documentation at [https://pipelines.lsst.io/getting-started/data-setup.html] is no longer correct with the creation of the `testdata_ci_hsc` and `ci_hsc_gen2` packages.  Specifically, the environment variables that point to directories do not contain the files expected by the tutorial."
Answer: 44820.0

User story: "Attend advanced spatialanalyzer training in Los Angeles. This is the third-party application that controls the laser tracker, and contains the spatial model of the components involved in the alignment process (M1m3, M2, Camera) and separately, the calibration alignment (dome, alignment screen) "
Answer: 14331.0

User story: "This is a catch-all ticket for various overdue refactorings necessary for other tickets, including:    - move initialization from moments from fitutils.fit_galaxy() to fitutils.get_init_from_moments()  - implement get_sigma_inverse() and get_var_inverse() in objects.Exposure"
Answer: 24814.0

User story: "Forwarder should be moved to dm_forwarder repo."
Answer: 13290.0

User story: "Missed three plugins needed to completely replicate current ap_assocation behavior.   * HTMIndex - Done   * nDiaSources - Done   * DiaObjectFlagFromSources - Done"
Answer: 4135.0

User story: "To complete RFC-634, we need to put the new Gaia refcat in the correct place, namely {{/datasets/refcats/htm/v1/gaia_dr2_20190808}}, make it readonly, and make the appropriate symlinks (e.g. from {{/datasets/refcats/htm/htm_baseline/gaia}}).    I will need permission to write to the necessary directories to move the files over and create the relevant readme (DM-20267). Who do I contact for that permission?"
Answer: 14385.0

User story: "Make a few simple command-line scripts that exercise the MT Rotator by talking to the Rotator CSC. This is intended to help [~<USER> shake out the MT Rotator at SLAC, especially my new Python CSC."
Answer: 15708.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 the new SAL support for enumerations with values by adding such an enumeration to Test and updating ts_sal tests to test for the existence and value of the enumerations in SALPY."
Answer: 43183.0

User story: "Write MT Hexapod CSC in Python, including a simulation mode that uses the mock MT Hexapod controller written in DM-21777."
Answer: 14639.0

User story: "Write a mock low level MT Hexapod controller. This pretends to be the low level controller provided by Moog, which talks via TCP/IP to a CSC."
Answer: 14647.0

User story: "Merge (major) upstream changes to OpenOrb, resolve any conflicts, and update the eups build scripts to work with the new OpenOrb build system."
Answer: 19.0

User story: "Implement vectorized versions of all operations involved in dataset insertion in Registry."
Answer: 130685.0

User story: "Update the public and internal APIs for dataset insertion in Registry, but only use bulk insert operations where trivial (i.e. not when autoincrement IDs and hence DM-21203 are in play)."
Answer: 135306.0

User story: Move dimension foreign key fields to separate, per-dataset-type tables.  Duplicate primary key fields and optionally (via configuration) duplicate other fields.    This should move the schema to something like the "Partition datasets (only)" design on [https://confluence.lsstcorp.org/display/DM/Dataset+and+Collection+Table+Reorganization|https://confluence.lsstcorp.org/display/DM/Dataset+and+Collection+Table+Reorganization].
Answer: 284663.0

User story: "Move registry code involving datasets (and, as needed, runs and collections) into helper classes as [the prototype|https://confluence.lsstcorp.org/display/DM/Architectural+Prototype+for+the+New+Gen3+Registry].  If possible, defer actually moving from monolithic to split dataset tables to DM-21766."
Answer: 284617.0

User story: "Following the selection of an algorithm in DM-21762, develop an end-to-end implementation of a mock catalog generator, possibly in a Jupyter notebook.    This will serve to:   * validate the design concepts before writing a package   * produce mock catalogs for testing   * measure the end-to-end runtime of the algorithm     "
Answer: 31.0

User story: "The problem this issue concerns is as follows:    > Given orbits (state vectors) for M objects, and times, centers, and fields of view for N visits, find all visits where objects M would appear.    This is a fundamental algorithm for:   * Mock catalog generation   * Population debiasing applications   * Precovery applications (finding which older visits could plausibly contain newly discovered objects)    Existing algorithms take ~weeks on O(100) cores to compute O(100k) orbits. Need to speed this up to O(1hr) on O(20) cores to comfortably fit within the computational budget for precovery.    This ticket is to track the exploration of various options."
Answer: 25.0

User story: "Organize the LSST-centric splinter meeting at 2019 Division of Planetary Sciences meeting in Geneva."
Answer: 52.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: "Prepare two talks for the Geneva DPS:   * Regular program summary of LSST Solar System Processing   * LSST splinter meeting data products talk"
Answer: 82.0

User story: "InfluxDB Sink connector v1.2.3 was released.     It adds DM-21391 but there was also a major refactor of the connector code that needs to be tested.    https://github.com/lensesio/stream-reactor/releases"
Answer: 1528.0

User story: "Re-implement hardware communication for Electrometer CSC phase 1: Electric Boogaloo         Revamp serial communication."
Answer: 233482.0

User story: "Revamp the Electrometer CSC to use salobj 4. CSC needs a rewrite to comply with TSSW python standards."
Answer: 20150.0

User story: "Build the latest OpenSpliceDDS Community Edition to run on the new Raspberry Pi 4 platform. Generate a SAL/DDS SDK image for use by the EAS contractor."
Answer: 20405.0

User story: "Recent weeklies aren't loading extensions and say they need a Lab rebuild.  Investigate and fix if possible."
Answer: 21727.0

User story: "Reivew pull-requests, update tests and push out the RPMs for the XML v4.4.0."
Answer: 16337.0

User story: "Implementation of RFC-635"
Answer: 17537.0

User story: "Deploy Watcher on the Tucson test stand and on the summit this task involves:          1 - writing configuration for the watcher on the lab     2 - updating watcher configuration for the summit with all required rules     3 - build container for the watcher     4 - make compose file to deploy watcher on both locations     5 - Update compose file for salkafka producer to add watcher on the list of CSCs               "
Answer: 24124.0

User story: "Write initial version of Auxiliary Telescope operations manual. "
Answer: 34444.0

User story: "Implement some improvements to ATTCS class with lessons learned on recent Auxiliary Telescope on-sky activities. "
Answer: 27030.0

User story: "There are some things that are uncomfortable to do with the raw outputs of a query to the EFD from within a notebook.  This will implement helper functions/classes to do things like:  * handle connections and credentials  * build queries for specific circumstances  * unpack packed sample series  * resample one time series onto another"
Answer: 166859.0

User story: "DM-20205 made it possible to both mark input/prerequisite datasets as optional on a per-band basis.  We should use that in IsrTask to enable fringe correction and HSC y-band stray light correction in Gen3.    As testdata_ci_hsc is only r and i, we'll need to make some one-off Gen3 repos to test that this works, which may well be most of the work."
Answer: 87637.0

User story: "Change the license associated with pex_config:    * Change LICENSE to state dual license and then refer to BSD and GPL license files.  * Remove GPL short license from all files and refer to LICENSE file.  "
Answer: 34261.0

User story: "Write a call for broker proposals and clear it with the SAC."
Answer: 177105.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 DM dev guide contains useful setup information on how to configure Vim to be consistent with LSST coding standards, but by default, Vim will not use that setup without an appropriate entry in the ~/.vimrc file. A few extra lines in the dev guide are required to explain this. "
Answer: 5812.0

User story: "A _settingsApplied_ and _softwareVersions_ event need to be added to the _SALGenerics.xml_. See the section [Results from Group Discussion|https://confluence.lsstcorp.org/display/LSSTCOM/Commissioning+Activities+2019-05-14+Meeting+notes] for specification of the events and attributes."
Answer: 24722.0

User story: "This is a continued task of phase 1: DM-21464."
Answer: 34748.0

User story: Test the software with the bare rotator in SLAC. The followings are my plan there:    1. To be familiar with the rotator behavior by some simple SAL commands by the original SAL version 3.5.1.    2. Install the SAL 3.10.0 and update middleware code in the mangement PC. In this step, I will need to stop the running middleware (in SAL 3.5.1) and backup the data in "/nfsdemo" directory.    3. Test the rotator hardware behavior by SAL 3.10.0 and do the record. If there is any document of rotator behavior recorded already in SLAC, I will be happy to read. I also want to talk to the users of rotator to see there is any bug found or not. This should be recorded and fixed in the following update.    4. Discuss with the developer of CCS to see how the CCS works with the rotator. Since I might be one of the client of CCS (I am responsible of the active optics), I do want to know how the CCS works.
Answer: 15910.0

User story: "Per RFC-636:    - Copy the existing lsst/afw repository to lsst-dm/afw-archive;  - Remove all merged branches, and all unmerged branches predating 2018, from the lsst/afw repository.    Coordinate the timing with [~<USER> — we want to do this, see if it has resolved the Jira sync problems, and then revert quickly if it hasn't."
Answer: 92734.0

User story: "Collect, record, and verify financial data for the LSST Data Facility. Deliverable consists of a monthly financial report delivered to the Project Controls Specialist."
Answer: 138546.0

User story: "Collect, record, and verify financial data for the LSST Data Facility. Deliverable consists of a monthly financial report delivered to the Project Controls Specialist."
Answer: 79284.0

User story: "Collect, record, and verify financial data for the LSST Data Facility. Deliverable consists of a monthly financial report delivered to the Project Controls Specialist."
Answer: 31597.0

User story: "Link to dm-tea-time actually links to dm-tea-team: https://developer.lsst.io/team/onboarding.html#slack"
Answer: 2720.0

User story: "Verify that the defects file for auxTel produced in DM-18749 are usable and correct by rerunning the `findDefects.py` task with `doDefect=True` and checking that all defects are masked and therefore not found  (this has not been tried before). "
Answer: 198449.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: A pure python package "foo" does not need {{ups/foo.cfg}} if SConstruct specifies {{noCfgFile=True}}, e.g.:  {code}  scripts.BasicSConstruct("ts_foo", disableCc=True, noCfgFile=True)  {code}    Consider whether to take advantage of this and eliminate the unnecessary file. I admit it'll be harder to add C++ code later, but it's already a bit of a chore and not a common change.    I consider this a "nice to have" since the current system works just fine.
Answer: 10213.0

User story: "In preparation for the {{w_2019_42}} we would like to make sure that we can run the previous release {{w_2019_38}}"
Answer: 27039.0

User story: "The setup.cfg file in ts_salobj has gotten a bit stale. Update it."
Answer: 3024.0

User story: "The final piece of the fiber spectrograph software is a document describing its use, caveats, and quirks. This ticket is to write that documentation, while the information is still in my head.    Having something that can integrate with lsst.io would be ideal."
Answer: 23230.0

User story: "This includes (at least):   * {{Amplifier.getHasRawInfo()}}         This ticket should not be merged until after the 19.0 release."
Answer: 295771.0

User story: "[example_project|https://github.com/lsst/templates/tree/master/project_templates/example_project] was useful as a proof-of-concept for the templatekit-based architecture of lsst/templates, but now it serves no real purpose. (If a tutorial project is needed to teach making templates, it shouldn't be part of the production template repository.) Let's simply delete the {{example_project}} so that we don't carry technical debt forward."
Answer: 89.0

User story: "In the AL implementation, the kernel candidates are small image stamps (footprints) around detected sources (on the already warped, pixel by pixel aligned images). The kernel candidate size depends on the kernel basis function pixel size ({{detecionConfig.fpGrowKernelScaling, fpGrowPix}}). Although the kernel candidates are always identified around sources (positions) on the science image, kernel basis function sizes were used inconsistently in case of science image convolution.    In the test runs, this did not make any substantial difference, though it could have caused problems with more extreme config parameter values. The kernel basis function pixel size differ in general if the images are swapped, i.e. switch between convolution and deconvolution cases in {{makeKernelBasisList.py:}} {{makeKernelBasisList().}}"
Answer: 8598.0

User story: The goal in this ticket is to check whether the high number of detection is in any connection with the signal level of the science or the template images i.e. whether any signal level or threshold is "inherited" from the original images. They are on different scales at the moment and image differencing is fitting a flux scaling as well, see DM-21700.
Answer: 60327.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: "Identify a visit in the {{ap_verify}} HiTS 2015 dataset with the 2014B coadds by [~<USER> (/project/<USER>hits2014B/cwcoadds_processed2/) that has the sharpest science image compared to the template.         The goal in this ticket is to check whether the science image convolution fails because the AL solution has known problems in close matching PSF cases (when PSF FWHM difference is < about 1px)."
Answer: 60346.0

User story: {{ip_diffim}} has the bool configuration option {{convolveTemplate}} implemented. With {{convolveTemplate=False}}, it switches the roles of the science and template images and performs the AL convolution of _the science image_ to match _the template_. For cases when the science image is sharper than the template {{convolveTemplate=False}} and {{doDecorrelation=True}} setup should perform as well as the "baseline" case when the template is the sharper one and it is convolved.         The resulting difference image is bad quality, indicated by an order of magnitude (~ 10 times) more sources detected (half positive, half negative approximately).    This ticket covers the work by [~<USER> to investigate the cause of this bug.
Answer: 60382.0

User story: "{{pipe_tasks}} changes made during the deblender sprint were never merged to master, so it still does not support {{meas_extensions_scarlet}}. This ticket is to rebase the branch and merge changes, confirming that it properly runs the latest version of {{meas_extensions_scarlet}}."
Answer: 31289.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 XML for Rotator and Hexapod has some misfeatures I would like to fix if and when we are sure that we are writing our own CSCs. (Actually we could easily fix these even if we keep the vendor's code):   - The Hexapod {{inPosition}} event has no {{inPosition}} field, so there is no way to indicate "not in position". Note that the Rotator {{inPosition}} event is fine. I suggest also adding an array of 6 booleans to indicate if each actuator is in position, perhaps named {{actuatorInPosition}}.   - The Rotator {{tracking}} and {{trackLost}} events have no boolean value so cannot be output properly. They should be combined into a single event with a boolean flag.   - Some telemetry is not output. I will not output them yet, but keep them in mind for the future, should we decide we need them:   -- {{copley_fault_status_register}}; note that similar latching registers are output.   -- {{input_pin_states}}   - Several events are sent only when something (such as tracking, or a problem) starts, but not when it ends. We should send the event when the condition starts and when it ends, with suitable data (e.g. a boolean that is true if the condition is present).   - Most events and telemetry topics have a {{timestamp}} field. That is a waste of space because it duplicates {{private_sndStamp}}.   - The telemetry topic names are capitalized and so do not meet our current standards.    These are at least partly fixed in DM-21694:   - There is no detailed state event, even though that state is crucial for these CSCs. Fixed in DM-21694 by adding the controllerState event.   - The deviceError event has a {{code}} field that is a string, and as implemented by the vendor, that "code" describes a single error so the event is output once for each error condition that is present. In DM-21694 I improved this by adding an {{applicationStatus}} field to the new {{controllerState}} event that has the bit mask. In addition I output {{deviceError}} once for a given set of error conditions, with {{code}} set to a comma-separated list of descriptions of each error so the event only when the error conditions change. I hope we can get rid of the {{deviceError}} event as duplicated information, even though a string can be nice.    This task will also clean up the Jira tickets:    (1) DM-20969 and DM-20971 for the telemetry.    (2) CAP-362 and CAP-369 for the event.
Answer: 132254.0

User story: This ticket will improve the way the Forwarder can detect the failure of the ATArchiver by changing the heartbeat mechanism to monitor service "liveness".
Answer: 4383.0

User story: "Write an MT rotator CSC in Python, including a basic simulation mode.    Note that the simulator is the hard part. I plan to start with a very elementary model (no slewing) in this ticket, then refine it in another ticket."
Answer: 23249.0

User story: "pipelines.lsst.io still references {{calib_psfCandidate}}. Should be updated to {{calib_psf_candidate}} "
Answer: 2764.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: "Some of the current plugins created for DiaObject summary statistics may benefit from more clever pandas usage and conversion to `multi` style plugins. This ticket will either be done at a later date of if during conversion to the plugin system in ap_association, the plugins are found to be too slow."
Answer: 70767.0

User story: "Continue generation of XML files needed to control the HVAC system. The new files consist of the events and commands. For the events, an analysis will be performed on the actions to be taken associated with alarms in the system."
Answer: 46113.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 295286.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 303774.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 236304.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 313838.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 253343.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 34520.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 263538.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 96317.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 235890.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 216040.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 216041.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 216040.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 216041.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 106292.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 221428.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 221428.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 221428.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 221428.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 221428.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 221429.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: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 221429.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 221429.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 221429.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 221429.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 191466.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 191467.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 34520.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 191467.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 191468.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 34520.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 191469.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 34520.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 24498.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 24498.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 24498.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 24498.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 24498.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 24498.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 426572.0

User story: <span style="font-family: Arial; font-size: 13px; font-variant-ligatures: normal; orphans: 2; white-space: pre-wrap; widows: 2; background-color: rgb(255, 255, 255);">assess power capacity [may result in plan to order more/different PDUs]</span>  This ticket had been created automatically Primavera ID: None
Answer: 201467.0

User story: <span style="font-family: Arial; font-size: 13px; font-variant-ligatures: normal; orphans: 2; white-space: pre-wrap; widows: 2; background-color: rgb(255, 255, 255);">plan node location in racks based on rack space and switch ports; may possibly result in plan to order more racks and/or switches</span>  This ticket had been created automatically Primavera ID: None
Answer: 201467.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: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 201467.0

User story: <span style="font-family: Arial; font-size: 13px; font-variant-ligatures: normal; orphans: 2; white-space: pre-wrap; widows: 2; background-color: rgb(255, 255, 255);">plan IP address layout [may result in need to plan to re-IP existing nodes, establish new VLANs, make pfSense firewall changes, etc.]</span>  This ticket had been created automatically Primavera ID: None
Answer: 201467.0

User story: <span style="font-family: Arial; font-size: 13px; font-variant-ligatures: normal; orphans: 2; white-space: pre-wrap; widows: 2; background-color: rgb(255, 255, 255);">update documentation on IP space [i.e., audit netdot and our wiki to make sure understand what is there; special consideration for k8s nodes that moved to a different network - will they stay there?]</span>  This ticket had been created automatically Primavera ID: None
Answer: 201467.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 195995.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 171510.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 171510.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 175822.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 175823.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 175824.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 175824.0

User story: "Populate Primavera with activities resulting from planning meetings.<br>  This ticket had been created automatically Primavera ID: None"
Answer: 126578.0

User story: "Baseline the plan and send to the Project Controls Specialist.<br>  This ticket had been created automatically Primavera ID: None"
Answer: 142663.0

User story: "This step includes all subtasks related to transferring the plan from Primavera to Jira.<br>  This ticket had been created automatically Primavera ID: None"
Answer: 142663.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 102089.0

User story: "This step encompasses everything after loading the initial plan into  Primavera, e.g.,&nbsp; scheduling the plan, reviewing allocations,  prioritizing and scheduling to level resources.  This ticket had been created automatically Primavera ID: None"
Answer: 126581.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 102089.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 102090.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: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 102090.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 83388.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 96588.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 86555.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 51819.0

User story: "Collect, record, and verify technical progress data and narratives for the LSST Data Facility. Deliverable consists of updated JIRA issues and a Technical Progress Report."
Answer: 102088.0

User story: "Collect, record, and verify technical progress data and narratives for the LSST Data Facility. Deliverable consists of updated JIRA issues and a Technical Progress Report."
Answer: 56192.0

User story: "Collect, record, and verify technical progress data and narratives for the LSST Data Facility. Deliverable consists of updated JIRA issues and a Technical Progress Report."
Answer: 15830.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 222996.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 222997.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 222996.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 233329.0

User story: "Closely monitor service following initial deployment until stable.  This ticket had been created automatically Primavera ID: None"
Answer: 233329.0

User story: "Install and test in Tucson environment.  This ticket had been created automatically Primavera ID: None"
Answer: 233329.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 105349.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 105349.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 105349.0

User story: "To prepare for the scarlet mini-sprint we need to pull the latest version from scarlet/master to the LSST fork and test with Jenkins."
Answer: 4590.0

User story: "Cmake will make easier deployment of forwarder."
Answer: 24836.0

User story: "* There is a new version of Strimzi available (0.14.0) and it makes sense to update our deployment.  * We've seen that the Kafka brokers deployed by Strimzi are down. Investigate this and resolve the issue."
Answer: 1122.0

User story: "This task will prepare the docker image of middleware code."
Answer: 4288.0