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: "Now that we've done the big JHU rewrite, fix up our standalone tools to take advantage of it too."
Answer: 1657.0

User story: "A couple of typos remained in the mapper file after the work in DM-20524.  This issue is to fix these to be able to use them in DC2 processing for DESC."
Answer: 98074.0

User story: "As a pilot for incorporating static type checking to SQuaRE's products, let's add type checking to Documenteer as part of its 0.6 overhaul.    This ticket is to add mypy type checking to Documenteer through the pytest-mypy plugin. The goal is to have tests pass with a minimum of work. Future tickets can incidentally add explicit typing to Documenteer's APIs."
Answer: 25852.0

User story: "One of the scripts in ts_standardscripts gets current TAI from ts_ATMCS. Modify it to call salobj.current_tai.    Update unit tests to use asynctest in ts_standardscripts and ts_externalscripts.    Stop using salobj.test_utils.    Fix flake8 warnings."
Answer: 5934.0

User story: "Several classes do not have destructors and all rely on many bare pointers. This is a follow up on the comments provided by [~<USER> in https://github.com/lsst-ts/ts_m1m3support/pull/3. "
Answer: 129728.0

User story: "It turns out the work I did on decam for DM-20763 was not complete: I only tested that one dataId could be retrieved from the ingested raw data, but there are two ccds in that file in two different HDUs and the second one is not actually getting ingested. The gen2 CameraMapper path for a decam raw looks like {{decam%(visit)07d.fits.fz[%(hdu)d]}}, so the hdu number is baked in there.  As far as I can tell, gen3 doesn't have any way to encode hdu number. Maybe this has to be a further specialization in the RawFormatter. File paths that go into butler.ingest have to actually exist, so we will have to do something to the raw paths that we pass into `butler.ingest`.    The gen2 butler registry has an `hdu` field that encodes which hdu to get that raw from. It doesn't look like there's an equivalent `hdu` field anywhere in the gen3 registry: could we add an extra `hdu` field to the `posix_datastore_records` table? That's my best guess as to where it should live."
Answer: 60439.0

User story: "Reaper is not waiting for its image data to be pulled, and is this not finding the images to reap."
Answer: 85.0

User story: "Create a DSM CSC deployment container with a Dockerfile."
Answer: 48847.0

User story: "The changes I made in DM-22027 correct some documentation errors that are relevant for v19. It would be good if those changes were reflected in the version of the docs that are shown online at pipelines.lsst.io.    I don't know if it's possible to update the docs separately from the release, or if we need to issue a point release to do this."
Answer: 77458.0

User story: "Task to finalize deployment of T&S components at NCSA"
Answer: 49937.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 options form is created at the beginning of a user session and is cached while the session is valid.  If that's 24 hours, that's way too long, so we need to invalidate the cache and rebuild on, say, each auth_refresh (which is 15 minutes or so)."
Answer: 1341.0

User story: "One of the things we figured we may want to do with the ATAOS is to be able to apply offsets on the current look up tables. This task is to include a command on ATAOS to enable that capability."
Answer: 87412.0

User story: "[kafka-connect-manager 0.4.0] fails posting the {{influxdb-sink}} connector configuration if {{topics=[]}}."
Answer: 8461.0

User story: "To incorporate Doxygen documentation into pipelines.lsst.io, it's become clear that a stack-wide Doxygen build is required, rather than piecing together individual Doxygen builds that are made by {{scons doc}}. At the moment, [create_xlinkdocs.sh|https://github.com/lsst-sqre/ci-scripts/blob/18d0f21ab6dc6db27927e42589153eaebc3427fd/create_xlinkdocs.sh] and [makeDocs|https://github.com/lsst/lsstDoxygen/blob/master/bin/makeDocs] work together to do a stack-wide Doxygen build as part of the {{run_rebuild}} Jenkins job. The products of this Doxygen build aren't available to the {{documenteer}} Jenkins job.    It seems that the best route forward is to replace the legacy tooling with an integrated build solution in {{documenteer}} itself, so that both the Doxygen and Sphinx builds are controlled from one command and one code-base.    The purpose of this ticket is to add this functionality to documenteer, based on the prior art in {{create_xlinkdocs.sh}} and {{makeDocs}}.    An outcome of this work is that a monolithic Doxygen {{xml}} output will be available to Breathe to incorporate C++ API documentation directly into pipelines.lsst.io.    This work will not attempt to build HTML output from Doxygen, nor compile Doxygen pages ({{.dox}}) as those are considered legacy output and contents."
Answer: 31672.0

User story: "There is no documentation for the various acknowledgements SAL supports. This task is to document them in the ts_sal documentation."
Answer: 63272.0

User story: "Correct the acknowledgments in the TMA software. "
Answer: 103703.0

User story: "This ticket creates an example notebook on how to use EFD data to analyze issues that arise during operations (e.g. motor slippage). A user provides a timestamp and plots are created looking at the pertinent information for each axis.     "
Answer: 83470.0

User story: "The {{kafka-connect-manager}} Helm chart needs to get the influxdb credentials from an existing secret delivered by the {{vault-secrets-operator}} in the EFD deployment managed by Argo CD.  "
Answer: 8710.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: After adding the -pedatic cxx flag to the compilation of ts_m1m3support code the following warning appears:    {noformat}  Building file: ../src/LSST/M1M3/SS/FirmwareUpdate/FirmwareUpdate.cpp  Invoking: GCC C++ Compiler  g++ -std=c++11 -pedantic -I"../../../boost_1_65_1" -I"../../../ts_opensplice/OpenSpliceDDS/V6.9/HDE/x86_64.linux/include" -I"../../../ts_opensplice/OpenSpliceDDS/V6.9/HDE/x86_64.linux/include/sys" -I"../../../ts_opensplice/OpenSpliceDDS/V6.9/HDE/x86_64.linux/include/dcps/C++/SACPP" -I"../../../ts_sal/test/MTM1M3/cpp/src" -I"../../../ts_sal/test/MTM1M3/cpp" -I"../../../ts_sal/test/MTMount/cpp/src" -I"../../../ts_sal/lsstsal/include" -I"../../../ts_sal/test/MTMount/cpp" -I"../../../ts_sal/test" -I../../../ts_sal/test/include -I"../src/LSST/M1M3/SS/DigitalInputOutput" -I"../src/LSST/M1M3/SS/FirmwareUpdate" -I"../src/LSST/M1M3/SS/Accelerometer" -I"../src/LSST/M1M3/SS/AutomaticOperationsController" -I"../src/LSST/M1M3/SS/BusLists" -I"../src/LSST/M1M3/SS/CommandFactory" -I"../src/LSST/M1M3/SS/Displacement" -I"../src/LSST/M1M3/SS/Inclinometer" -I"../src/LSST/M1M3/SS/ForceController" -I"../src/LSST/M1M3/SS/Commands" -I"../src/LSST/M1M3/SS/Context" -I"../src/LSST/M1M3/SS/Controller" -I"../src/LSST/M1M3/SS/Domain" -I"../src/LSST/M1M3/SS/FPGA" -I"../src/LSST/M1M3/SS/Gyro" -I"../src/LSST/M1M3/SS/ILC" -I"../src/LSST/M1M3/SS/Include" -I"../src/LSST/M1M3/SS/Logging" -I"../src/LSST/M1M3/SS/Modbus" -I"../src/LSST/M1M3/SS/Model" -I"../src/LSST/M1M3/SS/PID" -I"../src/LSST/M1M3/SS/PositionController" -I"../src/LSST/M1M3/SS/PowerController" -I"../src/LSST/M1M3/SS/Publisher" -I"../src/LSST/M1M3/SS/SafetyController" -I"../src/LSST/M1M3/SS/Settings" -I"../src/LSST/M1M3/SS/StateFactory" -I"../src/LSST/M1M3/SS/States" -I"../src/LSST/M1M3/SS/Subscriber" -I"../src/LSST/M1M3/SS/Threads" -I"../src/LSST/M1M3/SS/Utility" -O3 -Wall -c -fmessage-length=0 -MMD -MP -MF"src/LSST/M1M3/SS/FirmwareUpdate/FirmwareUpdate.d" -MT"src/LSST/M1M3/SS/FirmwareUpdate/FirmwareUpdate.o" -o "src/LSST/M1M3/SS/FirmwareUpdate/FirmwareUpdate.o" "../src/LSST/M1M3/SS/FirmwareUpdate/FirmwareUpdate.cpp"  ../src/LSST/M1M3/SS/FirmwareUpdate/FirmwareUpdate.cpp: In member function ‘bool LSST::M1M3::SS::FirmwareUpdate::CreateAppData()’:  ../src/LSST/M1M3/SS/FirmwareUpdate/FirmwareUpdate.cpp:102:31: warning: overflow in implicit constant conversion [-Woverflow]           appData.push_back(0xFF);                                 ^  ../src/LSST/M1M3/SS/FirmwareUpdate/FirmwareUpdate.cpp:103:31: warning: overflow in implicit constant conversion [-Woverflow]           appData.push_back(0xFF);                                 ^  ../src/LSST/M1M3/SS/FirmwareUpdate/FirmwareUpdate.cpp:104:31: warning: overflow in implicit constant conversion [-Woverflow]           appData.push_back(0xFF);                                 ^  Finished building: ../src/LSST/M1M3/SS/FirmwareUpdate/FirmwareUpdate.cpp  {noformat}  
Answer: 131203.0

User story: "Add the ComCam Archiver XML definitions"
Answer: 3737.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: The current "TELEMETRY" message from the forwarder sends a status code, obsid, and description when the file is completely written to where the archive controller does it work.   It would be better to send a filename, instead of a description field.  Also, the MSG_TYPE should change to IMAGE_RETRIEVAL_FOR_ARCHIVING.  The message should be:            {code:java}MSG_TYPE: IMAGE_RETRIEVAL_FOR_ARCHIVING  OBSID: <the obsid>  FILENAME: <the filename>  STATUS_CODE: <status code> (0 = success, >0 error code for type of failure)  DESCRIPTION: <English text describing success or reason for failure>{code}       Additionally, the message sent to the archive controller that the file was transferred successfully also needs OBSID.       
Answer: 4315.0

User story: "There are action items that came out of the CCW Review. This is to capture the time spent reviewing these action items, setting up any necessary meeting to push these actions forward, and priority planning to figure out what our scientists want first. "
Answer: 1433.0

User story: "The three python scripts in daf_butler use the old style approach of parsing arguments directly.  This is now deprecated and we should instead move all the code to the python module and have one line in the scripts themselves.    This allows for:    1. Unit testing of more of the code  2. Inclusion of scripts in sphinx documentation."
Answer: 30220.0

User story: "I'm using {{ap_verify_ci_hits2015}} to test my gen2->gen3 repo converter code, and I ran into a problem due to the use of the gaia dr1 refcat, which uses htm depth=8. Gen3 repos all have to use depth=7 for the moment. The easiest solution is to just extract the necessary pixels from the new gaia dr2 refcat and replace the old one in ap_verify_hits. That also gains us an upgraded reference catalog.    This should be an easy change to {{scripts/gaia_HiTS_2015.py}} and then a bit of processing on lsst-dev."
Answer: 41784.0

User story: "The code should be formatted in agreement with https://developer.lsst.io/cpp/style.html, and therefore the Google Style Guide (https://google.github.io/styleguide/cppguide.html). This will make it easier to work with this codebase."
Answer: 4194.0

User story: "Somewhere along the line, argocd started doing automated syncs.  I think this may have happened during the refactor, when I tried to set the prune mode to be true, not knowing it would set automated to true as well.  So going to try removing those parts of the yaml and test it out on -int."
Answer: 110.0

User story: "Reprocess the HSC RC2 dataset"
Answer: 18581.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 project has simulated throughputs for the optical components of the system.  These are currently stored in https://github.com/lsst/throughputs.  We will, eventually, be able to replace these by measured values.  It seems prudent for this information to be taken into account in the commissioning/calibration phases of construction by the DM team.  As far as I know, this is not currently written down as part of the plan, so taking option one or two below will result in a change in plan (though I don't think it is an increase in scope).    How do we plan to do that transition?  Options seem to be:  1. Ignore {{lsst_throughputs}} and do our own thing.  2. Take ownership of {{lsst_throughputs}} and develop an ecosystem around it (possibly porting pre-existing code from the syseng team).  3. Stick with existing plan and do nothing with the per component throughputs, simulated or measured."
Answer: 403520.0

User story: "Some things never worked (specifying the file as a config option), other may never have worked, and certainly don't now.    Make it so that new kernels can be used, and their use is logged clearly. Now that the new style kernels carry their gains with them, make sure that when using new-style kernels, a self-consistent gain is used."
Answer: 23737.0

User story: To deal with the various obs_package gen3 support tickets, I'm going to try to make a more generic version of the {{gen2to3.py}} conversion script. This will serve as a useful stopgap for using test datasets, while the official "create a gen3 repo from scratch" code is sorted out.
Answer: 122440.0

User story: "End-to-end Solar System Processing of Test Data-set (roughly 1000 objects over 3 months of LSST observations). Input: Test Data-set, HelioLinC linking, IOD filtering, (OD filtering).    Output: Example of clusters of SSO observations that can be submitted to the MPC.     "
Answer: 171258.0

User story: "Generate a test data set of LSST observations of roughly 400 known Solar System Objects from various categories such as near-Earth asteroids, Main Belt asteroids, Comets, Centaurs, Jupiter Trojans and Trans-Neptunian objects. This will serve as input to the Jupyter notebook level implementations of Classical MOPS and HelioLinC."
Answer: 86594.0

User story: "Python implementation / wrappers for orbital dynamics routines used in LSST Solar System Processing."
Answer: 171281.0

User story: "Jupyter notebook level implementation of the classical MOPS algorithm (Kubica et al. 2007) to compare completeness and performance with a similar implementation of HelioLinC algorithm (Holman et al. 2018)."
Answer: 110881.0

User story: "Since we no longer have special low-latency crosstalk-corrected images for Alert Production, we have only raw images that are destined for AP as well as other uses such as summit visualization, the OODS, and the Data Backbone.  Write a new tech note or modify DMTN-111 to describe how this should be handled."
Answer: 124640.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: "So the TAP async service is broken.  It puts everything in the bucket, but the domain name for the results (async-results.lsst.rocks) has been lost to me.  The domain I think is gone, or has been expired.  This should move anyway to under .codes, so async-results.lsst.codes.  Right now this isn't configurable through the layers, so I'll also be adding that.  By bubbling this all the way up to the TAP chart level this makes this a real useful feature."
Answer: 2733.0

User story: "In order to persist DcrModels using the Gen 3 butler, I need to define a new subfilter dimension in daf_base. I may also need to write a short script similar to make_skymap to be run before DcrAssembleCoaddTask to define the subfilters and update the local registry."
Answer: 66036.0

User story: "CAP-396 requires torr unit support in Astropy. File a one line pull request with Astropy."
Answer: 2601.0

User story: "In RFC-647 it was agreed to add pytest-subtests to the conda env.    Since this dependency only affects the testing environment and not the runtime environment it can be done standalone without affecting any existing stack installations so does not have to be deferred until a major env refresh."
Answer: 90830.0

User story: This task is to create 2 "How To" documents on a newly creates "TMA" Technote. Right now Te-Wei needs this for the afternoon. Will be working on this now. 
Answer: 485.0

User story: [~<USER> correctly pointed out that the <confifugrable> tag in the ts_xml branch needs a test. This task it to implement a simple "yes" or "no" text requirement for the tag. 
Answer: 3071.0

User story: "The InfluxDB Helm chart also add secrets in the {{value.yaml}} and so we cannot check in this file in a repo. In addition, it creates a Kubernetes secret with the username and password. We don't want that in our Argo CD workflow. Instead, we want to use an {{existingSecret}} created by the `vault-secrets-operator`. Thus we are adding this variable to the InfluxDB stable Helm chart."
Answer: 45712.0

User story: "Add protection when loading data:    https://github.com/lsst-ts/ts_m1m3support/blob/b69aaf788c278cbef6f6da31524ac8176ee8f2be/Controller/src/LSST/M1M3/SS/Accelerometer/Accelerometer.cpp#L36-L60     This can happen in other components of m1m3support code too."
Answer: 138003.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: "Use the new Database class (DM-22508) as the backend for Registry, with a lot of pragmatism about how much to change.  The goal will be to make this as transparent to Butler users as possible (I don't yet see a reason why it can't be completely transparent), and stick to:   * Making Registry a concrete class, basically just merging Registry's docs with SqlRegistry's implementations.   * Using Database instances to create engines and connections for Registry (and connecting RegistryConfig's connectionString logic with Database's).   * Using Database to emit all DDL (this probably means moving schema.yaml content to Python).    At this point, we'll just brazenly steal the (protected) connection object out of the `Database` instance to let most existing SqlRegistry method implementations remain unchanged.  That will get fixed later as we port Manager objects over from the u/<USER>prototyping branch.    This should take care of all of the code duplication that currently exists (core/schema.py and registry/ddl.py, registries/* and registry/databases/*)."
Answer: 44309.0

User story: "The MQTT based generated list of HVAC parameters, was verified for completeness by comparing with the Windows server list and, now then proceed with the final generation of XML telemetry, alarms and commands files."
Answer: 74657.0

User story: "When deploying {{kapacitor}} with Argo CD, the {{vault-secrets-operator}} creates a k8s secret with the InfluxDB username and password. The  {{kapacitor}} Helm chart on {{stable}} does not accept an existing secret and implies that we include the secret value in the {{values.yaml}} which is not possible using GitOps.    That seems like a good contribution to the {{kapacitor}} Helm chart.     In this ticket we'll PR this change upstream and also add the {{kapacitor}} Helm chart temporarily to the {{lsst-sqre/charts}} repo in order to use it right away.    "
Answer: 96617.0

User story: [~<USER> points out that version 2.0 of the alert schema contains a number of entries like:    {code}  {"name": "diaObject", "type": ["lsst.diaObject", "null"], "default": null}  {code}    However, the order of the {{type}} field should be reversed, per the [Avro spec|https://avro.apache.org/docs/current/spec.html#Unions]:    {quote}  Note that when a default value is specified for a record field whose type is a union, the type of the default value must match the first element of the union. Thus, for unions containing "null", the "null" is usually listed first, since the default value of such unions is typically null.  {quote}    
Answer: 98342.0

User story: "It turns out that the rafts tested in ts8 have actually been installed in the LSST camera.  Add read noise, gain, full well value to the camera and copy over QE curves the real camera from the ts8 camera: [mapping is here|https://confluence.slac.stanford.edu/pages/viewpage.action?spaceKey=LSSTCAM&title=Raft+Delivery+and+Acceptance+Testing+Status]."
Answer: 130005.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: "* Move GAIA data from /qserv to /qserv/qserv-prod and /qserv/qserv-dev   * Test inside qserv-dev namespace it is working   * Set up qserv-prod instance"
Answer: 94670.0

User story: "unit tests for MTAlignment Model, and the mock controller underneath. "
Answer: 338191.0

User story: "add support for commands to model"
Answer: 61632.0

User story: "build a skeleton model for the alignment CSC"
Answer: 15596.0

User story: "now we have a skeleton, flesh out the documentation a bit and add support for more of the API"
Answer: 7179.0

User story: Most of our new pipeline tasks' functionality can be tested by writing unit tests against {{run}} or more specific methods (in theory, these tests should be identical to those from the Gen 2 era). However, such tests do not verify:   * whether a task's {{Connections}} are correctly written and whether they match the inputs and outputs of the {{run}} method   * any logic in a custom {{runQuantum}} method   * configuration logic, such as optional or alternative inputs or outputs    Since the Gen 3 API is unfamiliar to us, these aspects of a {{PipelineTask}} are the ones that are most likely to have bugs.    Currently, the only way to test these features is in large-scale runs on Gen 3 repositories (e.g., HSC). Such tests, while valuable, can only exercise a small subset of conditions (e.g., configs), can be expensive to debug (e.g., due to cascading failures), and do not protect against regressions (no CI). A {{pytest}}-compatible framework that lets us test those parts of a {{PipelineTask}} that lie _outside_ {{run}} will let us catch problems much faster.    As part of DM-21875, I created a prototype [test framework for direct Butler I/O|https://github.com/lsst/verify/blob/b3f960befa179cee8050cdf380fd16c8a2acbafd/tests/butler_utils.py] and used it to verify that datasets could be stored to and retrieved from a dummy, obs-agnostic repository. I believe the same approach can be used to test {{PipelineTask}} functionality without the need to simulate a "realistic" Butler or depend on {{obs}} packages.    Desired features:   * a natural way for the test author to provide mock data IDs for the repository. The appropriate IDs will depend on the task being tested. It should be possible to simplify this from the prototype code, since most of the complexity of the Gen 3 Dimensions system is not needed for most tests; an exception may be {{ImageDifferenceTask}}'s mix of detector-level and patch-level inputs.   * a simple activator that calls {{runQuantum}} without modifications other than mocking {{run}}   * a way to test that the desired inputs get passed to {{run}}, including self-consistent use of config flags -and templates-. This will probably involve mocking {{run}} and may involve mock datasets, which are more technically challenging.   * a way to verify the output of a (real) {{run}} call against a configured connections object   * -analogous support for {{\_\_init\_\_}} inputs and outputs, which I'm less familiar with-
Answer: 136894.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: Per [~<USER>, the nfs exported path "/lsst/project" has changed to "/user/staff/project" .
Answer: 65.0

User story: "This ticket is to provide updates to the cwfs notebooks. It will also add some notebooks that are used to mine EFD data."
Answer: 91733.0

User story: "We seem to have grown a new issue type. Let's make sure people don't use it."
Answer: 59039.0

User story: "Fix the logging service on -int and make sure it works for qserv and is keeping up with the log stream."
Answer: 11364.0

User story: "In testing and validating Gauss's method for IOD we found that the initial guess of the orbit could be off by as much as ~10,000 km (idealized inputs with no astrometric error). Gauss's method is fundamentally not closed-form and uses an approximation to compute a potential target's state vector.  To improve the initial orbit, some astrodynamics textbooks suggest iterating over the initial orbit (for example, using the guess of the state to compute the 'exact' equations for the Lagrange coefficients). We selected Howard Curtis' algorithm for iterative improvement and need to test if it will work as an additional component of IOD. "
Answer: 93591.0

User story: "Due to the deprecation of obs_sdss and the stack demo in RFC-645, we should create a simple replacement demo script based on one of the supported obs packages. This would just need to have enough data to run a single image and confirm that the results are generally sensible."
Answer: 352905.0

User story: "In DM-22550 a bunch of files had the wrong filter. This could be fixed by the current scheme of per-file fixups but during that I realized that LSST_NUM is missing for the entirety of November. Providing a fixup file seems like the wrong answer to fix a month of data.    This ticket experiments with adding programmatic fixups as well as the existing scheme. The downside of programmatic fixups is that we might end up with every header having date strings parsed twice -- once to see if a date of interest is in play for header fix up, and again when the fixed header is translated."
Answer: 1836.0

User story: "simple tcp server that will emulate the T2SA application for testing"
Answer: 17134.0

User story: "Attend the MPC User Group meeting (U. Arizona, Dec 10th)    Review the current status of MPC system upgrades, and their state as it concerns the LSST    Update the RFC-620 risk assessment based on the findings."
Answer: 93685.0

User story: "Present the LSST SSP expectations and status at LPL NEO Workshop on Dec 9th, U. Arizona."
Answer: 14.0

User story: "Update SQR-016 to tag manually lsst repository when release candidates and official releases are done."
Answer: 27387.0

User story: "This is a special repository and needs to be tagged manually instead after the release branch is created."
Answer: 27389.0

User story: "Make GenericCamera package pip installable."
Answer: 17533.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 yum repository for SAL artifacts needs to be created on the new nexus server. The yum repo should be able to receive release (master) and develop artifacts."
Answer: 59806.0

User story: Perform light testing cover of the LSST "verify" Slurm cluster and HTCondor "Test" cluster in advance of the planned maintenance on Thu, Dec 12, using some Gen2 Scripts of RC2.
Answer: 1420.0

User story: "Obtain basic runtime benchmarks for alert production pipeline.  For example:  runtime (walltime), memory usage, I/O (sizing inputs/outputs), # alerts... can be as simple as getting a sense of what is (and is not available) from runs in DM-22560 with an eye for what might be quickly automated, where additions might be needed to facilitate, or ideas about other metrics."
Answer: 14307.0

User story: "Initial attempt to run alert production pipeline (AP) over test set similar to testing that developers are using (although this can be at a smaller scale).  "
Answer: 14306.0

User story: "Verify that the SUIT Portal application has been integrated with the WebDAV-based workspace interface."
Answer: 224625.0

User story: In DM-22366 it was reported that there is a filter in LATISS called "disperser" but it's actually meant to be called "diffuser".  This ticket is therefore to:    * Add metadata correction files to map disperser to diffuser  * Add filter to the obs_lsst filter definitions  * Add explicit LATISS filter list distinct from lsstCam in obs_lsst
Answer: 9911.0

User story: "Everyone gets everything he wants.  I wanted a mission, and for my sins, they gave me one.    LSST needs MultiNamespaceKubeSpawner and it looks like I'm the person who cares enough to spearhead the PR."
Answer: 115370.0

User story: "Please include the ts_simactuators package in any future T&S Docker images, at least those images that include any packages that have a simulation mode that involves actuators. This includes ts_ATDome, ts_ATMCSSimulator, ts_rotator and ts_hexapod."
Answer: 290311.0

User story: "The test documentation procedure in confluence:    [https://confluence.lsstcorp.org/display/DM/DM+Test+Documents+Procedure]    shall be updated in order to clarify how to handle large files involved in a test campaign:   * notebook preparation and executed files   * csv files   * large images"
Answer: 20148.0

User story: "The xml code for ComCam HeaderService (CCHeaderService) needs to be revised to be compatible with ComCam"
Answer: 11683.0

User story: "We like to set up a new K8s using existing machines at the NCSA Test Stand."
Answer: 72333.0

User story: "Add {{ImageDifferenceTaskConnections}} and {{runQuantum()}} if necessary to make {{ImageDifferenceTask}} executable under gen3.   * Prepare the inputs of run() in gen3 terminology.   * Under gen3 calexp template need not be supported, but keep functionality under gen2 if possible for maximum backward compatibility."
Answer: 145563.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 script generateAcronyms.py should be updated in order to include only acronyms in the acronyms table, when executed with the -t option (generate acronyms table)"
Answer: 5692.0

User story: "This ticket contains work to generate multiband catalogs and plots to analyze the performance of the current LSST deblender and {{meas_extensions_scarlet}}. A lot of the work involved tracking down inconsistencies in matching the simulated catalogs to the real sources, and formatting the resulting catalogs to display the plots."
Answer: 70433.0

User story: "As a good way to wrap up the Epic I gave a presentation to the DESC Blending Working Group on my work testing HSC with injected images using the current deblender vs scarlet. Most of this work was generating plots that were required for us to evaluate scarlet internally in DM, it just so happened that the BWG meeting occurred before presenting it to the DRP group."
Answer: 13003.0

User story: "We'd like to update documenteer so that it's compatible with Sphinx 2.0 (up to the modern 2.2). This is necessary so that we can use the latest versions of Breathe, which now require Sphinx 2.0.    One known issue with the Sphinx runner; the API there changed.    Another potential issue is documented in https://github.com/lsst-sqre/documenteer/issues/47"
Answer: 13077.0

User story: "So when installing the nublado helm chart I noticed some new issues.  The home for the hub persistent volume claim was failing to create using argocd (more on that later), due to the annotations.  So I think originally these were in the wrong spot, and better checking had improved it to make it an error.    Now when diagnosing the error, I found that I should quote the annotation, as when running create vs apply, there is different behavior.  Helm will seem to do a create as well, so best to just quote the GID."
Answer: 8.0

User story: The "processingStatus" event that had been sent by the Forwarder was incorrect since that message was intended for prompt processing.  The event to send is "imageRetrievalForArchiving", and this needs to be updated.
Answer: 45941.0

User story: "This is continuation of DM-22451"
Answer: 9741.0

User story: "Now that {{v19_0_0}} is released, we can port the new content added to the release branch ({{19.0.x}}) back to {{master}}."
Answer: 238.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: "Documenteer has a {{lsst-pipelinetasks}} directive that works analogously to {{lsst-cmdlinetasks}}. However, it is not mentioned in either the [module topic documentation|https://developer.lsst.io/stack/module-homepage-topic-type.html] nor in the [package templates|https://raw.githubusercontent.com/lsst/templates/master/project_templates/stack_package/example/doc/lsst.example/index.rst]. As a result, tasks that get converted to {{PipelineTask}} will drop off the module documentation.    Add a {{lsst-pipelinetasks}} section to the template (possibly before {{lsst-cmdlinetasks}}, which is still relevant until the migration is complete) and update the developer guide to match. Updating the {{index.rst}} files of individual packages is out of scope for this issue."
Answer: 46067.0

User story: "The obvious intent of the {{lsst.afw.table.GroupView}} iterator is to iterate over the {{ids}} attribute, but this is broken at the moment."
Answer: 55.0

User story: "So when setting up the argocd for LSP, I was hoping to have all the values.yaml files for each component organized by environment (so like, lsst-lsp-int/portal.yaml, lsst-lsp-int/nublado.yaml, etc).  But it seems like that is hard to do in argocd, for reasons about where it draws the values files from.  When linking it in via a URL (even to the same repo) it didn't get the alert.  So that won't work.  So I think I'm going to do what Jonathan and Angelo suggested in adding another layer of apps and have each one have all the values for all the environments.  So for example, this would be portal/values-google.yaml portal/values-int.yaml, etc.We'll see how that goes."
Answer: 7170.0

User story: "Failure to build dax_ppdb when doing the official release of 19.0:    [https://ci.lsst.codes/blue/organizations/jenkins/release%2Fofficial-release/detail/official-release/31/pipeline/]"
Answer: 6027.0

User story: "In order to implement the changes ratified in the [settingsApplied|https://confluence.lsstcorp.org/display/LSSTCOM/Commissioning+Activities+2019-05-14+Meeting+notes#CommissioningActivities2019-05-14Meetingnotes-settingsApplied] discussion, the similarly named CSC specific event needs to be renamed or removed. Please see the generic event attributes to make that decision."
Answer: 4286.0

User story: "Move the Database ABC from the [prototype|https://confluence.lsstcorp.org/display/DM/Architectural+Prototype+for+the+New+Gen3+Registry] to a permanent home in daf_butler, and add concrete implementations for SQLite, Oracle, and PostgreSQL, with unit tests.     "
Answer: 15169.0

User story: "{{ImageDifferenceTask}} will be migrated to support Gen3 middleware while remaining Gen2 executable. The goal is to create a minimal wrapper while keeping as much as possible unchanged in the code.    The first step is to create a {{run()}} method that already takes all inputs from memory and there is no butler reference in the code from here."
Answer: 30498.0

User story: "Update AuxTel manual to use new IPs for creating tunnels."
Answer: 306188.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: "Deploy SUIT 1.1.1 to stable.  This also means updating stable's portal to using the helm chart and the argocd infrastructure."
Answer: 33.0

User story: "To bridge Doxygen-generated C++ reference documentation into pipelines.lsst.io, a Sphinx-based site, we know we want to use Breathe. However, we don't know the best way to build out the API reference site. We don't want a monolithic page with all APIs, instead, we want one-page-per-API, like we do the Python docs.    One approach to building out this page hierarchy is with [exhale|https://github.com/svenevs/exhale], an additional Sphinx extension that builds generates doxygen-like namespace browsing of a C++ API. This ticket is to demo that approach and see if it's an appropriate solution for the LSST Science Pipelines documentation."
Answer: 77572.0

User story: "To bridge Doxygen-generated C++ reference documentation into pipelines.lsst.io, a Sphinx-based site, we know we want to use Breathe. However, we don't know the best way to build out the API reference site. We don't want a monolithic page with all APIs, instead, we want one-page-per-API, like we do the Python docs.         One approach to building out this page hierarchy is {{breathe-apidoc}}, a CLI tool that's part of Breathe. This ticket is to demo that approach and see if it's an appropriate solution for the LSST Science Pipelines documentation."
Answer: 77552.0

User story: "Other modes of clobbering are more complicated and require careful thought.  This one should be easy, and would make a lot of developers' lives easier.  We should just do it."
Answer: 8362.0

User story: "Make new release of LSE-61 with LCR-1933 and LCR-1664 included."
Answer: 31.0

User story: The example in the documentation for Butler.export doesn't appear in HTML because the heading is "Example", not "Examples".
Answer: 338.0

User story: "Ingest the newer set of Object tables Parquet files of HSC-RC2 into Qserv.     Useful reference information:  https://confluence.lsstcorp.org/display/DM/Live+demo%3A+test+ingest+of+a+subset+of+one+track+of+the+HSC+Object+catalog  DM-21810"
Answer: 79123.0

User story: "Following discussion with Merlin, please write an overview of your proposed design for handling calibration products in Gen3 and circulate it (on community.lsst.org) for discussion. Solicit comments from all the relevant folks."
Answer: 51839.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> discovered that two things go wrong when the datastore runs out of disk space:    1. The file partially written by the datastore does not get deleted.  2. If a directory was created by the put it tries to delete the directory but can't because the file is still there.    Item 1 should be fixed since we do not want partially written files left over in the datastore when a put fails.  Item 2 should be removed since it is possible that some other process is actively writing to the datastore and using that directory. The implication is that we should never try to remove directories if a transaction fails, solely files that are only under our control.  "
Answer: 8407.0

User story: "There are two types of deployments, the source, and aggregator EFDs. Plus, we need to manage these deployments in multiple environments: summit, tucson-teststand, ncsa-teststand, ldf and gke.    That's has implications on concepts like environment in Argo CD and suggest to adopt a naming convention for the Helm chart values file and for the service names."
Answer: 2815.0

User story: "As part of DM-21886 we can better future proof subtasks within ap_association by creating a new task to load from the Apdb and lightly restructure other association tasks to take preloaded data instead of loading from the Apdb as needed."
Answer: 11526.0

User story: "THis is the first copy of the LATISS user manual. The original commit will be copied over from a latex document. This is tstn-006.     "
Answer: 49010.0

User story: "I know you’ve been looking at the landing page. Can you put something equivalent to this:    {code}  Check [here](https://github.com/lsst-dm/lsp-landing-page/blob/master/motd/integration.md)  for a complete list of messages.  {code}    into the framing material of the page so that I don’t have to replicate it in each new MOTD text?  No rush at all on this."
Answer: 21453.0

User story: "Currently there are uses of python {{future}} in {{fgcmcal}} and {{fgcm}}.  Remove these!"
Answer: 53306.0

User story: "{{fgcmcal}} does not currently build documentation that will go on https://pipelines.lsst.io . Add this directory and template files."
Answer: 191609.0

User story: The "obsid" (which internally in the Forwarder is called "image_id") needs to be sent back in a message to the ATArchiver in addition to the rest of the information that is sent.
Answer: 2689.0

User story: "Latest version of rabbitmq-c 0.10.0 is out and it might solve our issue where Forwarder doesn't respond to connections after 11 days of uptime without errors."
Answer: 2641.0

User story: "We're ready to start taking more control of the SUI / portal deployment for -int and -stable.  We will start with the helm chart that is checked in here:    [https://github.com/lsst-sqre/charts/tree/master/firefly]    and works on Google.  We will modify it as necessary to make it work for -int."
Answer: 1357.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 goal of this extension is to render C++ documentation (generated by Doxygen and Breathe) equivalently to how we already render Python API documentation in pipelines.lsst.io using the automodapi directive.    automodapi creates a contents table of all the functions and classes available in a Python module namespace. It also generates rst pages (in an {{/py-api/}} directory) with placeholders for standard Sphinx autoapi directives for individual Python functions and classes.    What this does is ensure that each function and class has its own page.    This is different from Breath's default behaviour with its {{doxygennamespace}} directive, which inserts all documentation for a given namespace into one page.    This extension will be implemented in [https://github.com/lsst-sqre/documenteer|https://github.com/lsst-sqre/doxygen]"
Answer: 125889.0

User story: "Review test cases proposed for the S19 science pipelines acceptance test campaign"
Answer: 190663.0

User story: "The efd-prod cluster at GKE is not being used and we can save some money. This is to disable the Nagios checks for that instance."
Answer: 30185.0

User story: "Create the test plan and report for the 2019 Fall science pipelines release acceptance test campaign.     "
Answer: 65084.0

User story: "Carry out acceptance testing of the Fall 2019 Pipelines Release"
Answer: 131003.0

User story: Use the new Firefly build script feature in release-2019.3.2 to create a Portal application ("suit" package) release as agreed with [~<USER>.    Fine-tune messages if there is a problem constructing the LSST TAP service URL.
Answer: 3020.0

User story: "Update the TSTN-004 document with procedures for E-stop resetting, dome resetting, hexapod resetting etc."
Answer: 9.0

User story: "Put Lauren's astrometry sprint work on a Princeton WBS. "
Answer: 131222.0

User story: "Generate a document on software modules deliverables by EIE dome contractor, that integrates a Dome Control System and, serves as a reference to validate the deliverables and also, serves to evaluate the feasibility to develop certain software components by the LSST software developers."
Answer: 8451.0

User story: "Based on the data maturity assessment and initial reports from the POC, identify areas of low hanging fruit and high importance to improve on data quality "
Answer: 154342.0

User story: "Documenting of the processes used during the POC and then evaluating where the process can be improved, and write up an initial repeatable process scaling the scope of the potential tool     "
Answer: 123797.0

User story: Once data has been entered and we have been shown the tool, we will be given two weeks to "play" in the tool to evaluate how to use it, and ask additional questions about the use of the tool 
Answer: 123799.0

User story: "From DMLT/Commissioning Team feedback formulate full outline/draft of OPS Rehearsal 2 with LDM-643 "
Answer: 24936.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: "Vendor will enter data into the tool and we will then have a half day to one day workshop with them to evaluate how the data is entered and what data outputs we have"
Answer: 60838.0

User story: "Touch base on how the data integration into the tool is going "
Answer: 60839.0

User story: "Touch base meeting with the vendor to discuss additional needs of data "
Answer: 60839.0

User story: "Mapping Data across data sources to assist ITFM vendor in integrating into tool"
Answer: 60841.0

User story: "Evaluating potential ITFM vendors and who meets the needs of our organization and goals for doing budgeting, planning and future forecasting "
Answer: 1.0

User story: "Provide preliminary outline within LDM-643 including options given current project status.  Present to DMLT and solicit feedback"
Answer: 5.0

User story: "Collect all documents needed for the vendor proof of concept to model the tape archive at NCSA"
Answer: 3.0

User story: "Ensuring that the contract is in place so if we move forward with a purchase after vendor POC, and NDA signed"
Answer: 3.0

User story: "Negotiate the contract with the consulting company for data maturity assessment and vendor POC advisory "
Answer: 3.0

User story: "Probably including everything in PDR2 that covers the COSMOS field. Refer to DMTN-091 regarding the definition of datasets, medium scale, etc."
Answer: 174185.0

User story: "Add minipage in DMTR summary table for comments"
Answer: 25772.0

User story: "Testers are rendered in DMTRs only after the tests have been executed.    This information is important to ensure that the test is ready to start, therefore it should be visible before."
Answer: 25820.0

User story: "Improve CSC startup by not starting the heartbeat pulse until after the CSC is ready to receive commands. Make sure that the initial summary state is delayed until then, as well (but I think it already is).    Improve close methods on Domain, SalInfo and Controller so if close is called multiple times the later calls wait for closing to finish. This avoids nasty messages from asyncio in unit tests. Also improve SalInfo.close by giving time for the read loop to terminate.    Reduce duplication in ReadTopic.close by making a new private method to cancel callbacks."
Answer: 5524.0

User story: "Since test specifications are not used, it is required to be able to see the traceability to the requirements in the DMTR directly"
Answer: 25904.0

User story: "Simon and I prepared this list that was sent to Russ Savage and Deniz Kusefoglu at InfluxData.    https://gist.github.com/<USER>641757913ff0a15441deccf271ae2962"
Answer: 4.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: "Argo CD is being adopted by the team to manage our Kubernetes deployments (see SQR-035)    Argo CD is  a declarative, GitOps continuous delivery tool for Kubernetes. In this ticket, we'll use Argo CD to manage the EFD deployment on multiple environments. The goal is to keep all the deployment configuration on Git and use Git to control the deployment changes. Helm is going to be our main resource for deploying Kubernetes applications.    As for the secrets, we'll use the {{vault-secrets-operator}} to retrieve secrets from Git. "
Answer: 31784.0

User story: "In DM-22234 I knew that obs_base used {{from past}} but it seems that I lost track of fixing it. Do the fix (again) here."
Answer: 406.0

User story: Outline a plan to fill in concerning IT - and get the budget under control.    This will also cover the action from DMLT "ensure that a standardized deployment mechanism is documented and required across subsystems."    This document will point at a deployment spec which shall be the standard.
Answer: 221770.0

User story: "This ticket covers the formal deployment of sqrbot-jr and templatebot on Roundtable/Argo CD. This ticket is enabled by DM-22099 and DM-22100 (and DM-22408)."
Answer: 1557.0

User story: "The previous developer used to generate makefiles with and IDE (Eclipse) that I can replicate. Even when little more work this could be achieved, an improvement could me to have a more general setup.    It is expected that this issue takes time."
Answer: 60637.0

User story: "When loading XML setting files there is no check if the file is correctly loaded. This caused me to debug the code for a good amount of time, because it was causing a segmentation fault. I propose to add some error handling everywhere this files are loaded so that end users can easily notice this kind of issues, of example if files are corrupted or moved to another location."
Answer: 4263.0

User story: "Just to change makefiles from OpenSplice version from 6.4.1 to 6.9 to match the current version of ts_sal@v4.0"
Answer: 4267.0

User story: "As summary."
Answer: 3959.0