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: "Tanaka-san found a field in VVDS with bad stellar photometric matching to panstarrs. He found that {{compareWarp}} was clipping stars, despite the filter that rescues artifact candidates from the chopping block if they completely overlap a source detected in the PSF-Matched sigma-clipped template.    {code}          self.detect.nSigmaToGrow = 2          self.detectTemplate.nSigmaToGrow = 2.0  {code}    These current defaults assumed that footprints of the detections in the PSF-matched template are larger than those in the warps. Incorrect.     Fiddling with configs fixed the problem in the VVDS field: dataId={'tract': 10181, 'patch': '2,4', 'filter': 'HSC-G', 'visit': 82508}). I'm currently running a few configuration options through a full RC2 to determine with there are any unexpected side effects and metrics.     So far changing to {{detect.nSigmaToGrow = 1}} looks promising.     "
Answer: 143397.0

User story: "official releases build 23 failed:    [https://ci.lsst.codes/blue/organizations/jenkins/release%2Fofficial-release/detail/official-release/23/pipeline]    the reason seems to be that externals packages are tagged from the tip of master instead of that from 18.0.0 existing tag."
Answer: 11149.0

User story: "Use fake sources to assess the completeness of the pipeline processing."
Answer: 63563.0

User story: "Deleted test cases are not included in the VCD, but they shall not be there.    Also, I found a couple of issues in the summary counting, that decrease the coverage."
Answer: 119334.0

User story: "It appears at [line 255|https://github.com/lsst/ip_isr/blob/4e3c610941f9a3dc4c7bc1469fe72bcc4d0858d2/python/lsst/ip/isr/isrTask.py#L255] and at [line 437|https://github.com/lsst/ip_isr/blob/4e3c610941f9a3dc4c7bc1469fe72bcc4d0858d2/python/lsst/ip/isr/isrTask.py#L437] of {{isrTask.py}}."
Answer: 200.0

User story: "Update units and descriptions for the following CSCs. Per Tiago's request.        * ATAOS   * ATMonochromator   * ATSpectrograph   * ATTCS   * DIMM   * Environment   * Electrometer"
Answer: 12598.0

User story: "As a proof-of-concept for documenting ad hoc command line utilities, create documentation pages for the scripts that ship with [https://github.com/lsst/verify.] This will use the {{sphinx-argparse}} extension being added to documenteer (DM-20767)    See [https://sqr-032.lsst.io|https://sqr-032.lsst.io/] for more details about documenting scripts for the LSST stack (DM-20511)."
Answer: 18883.0

User story: "Add [sphinx-argparse|https://github.com/ribozz/sphinx-argparse] to the {{documenteer[pipelines]}} dependency list to enable auto documentation of {{argparse}}-based scripts."
Answer: 11725.0

User story: "Update the MTM2 xml for description and unit. The related tests in ts_xml will be done by Rob. There is the document provided by Harris for the description. The unit will be based on my best guess if needed."
Answer: 1467.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "In DM-20736 I updated sphinx-rtd-theme to 0.4.3, but didn't update the \{\{layout.html}} theme file to match. The result is that syntax highlighting does not show up, among other issues. This ticket is to use the new layout.html theme file while incorporating the updates made to put the version switcher in the sidebar."
Answer: 82.0

User story: "Add the following package as a docker container based on develop-env image. [https://github.com/<USER>cwfs]"
Answer: 33785.0

User story: "The Ppdb has a non-Null constraint on RA/DEC. However, depending on the algorithm used to compute a source centroid (and translate into RA/DEC using the WCS), NaN values can result.    This ticket will tests for NaN values in the DiaSource table, drop those objects, and throw a warning to the log with the offending DiaSource id."
Answer: 18510.0

User story: "For things like qserv monitoring and logs, and other operational or admin things, it'd be nice to have a capability to put this under.  Then we can make an ingress rule that allows only for those admin type people to access it.  This will simplify a lot of simple services since they can rely on the auth proxy to handle that for them."
Answer: 103612.0

User story: Quantum pickles from ctrl_bps have {{id=None}} in the DatasetRef, fail the condition here   [https://github.com/lsst/ctrl_mpexec/blob/w.2019.29/python/lsst/ctrl/mpexec/singleQuantumExecutor.py#L131]   butler.registry.find doesn't fix it, and then executions such as     {{pipetask -b /project/<USER>gen3repos/w_2019_20/repo/butler.yaml -i G3M19c_000001_025 -o test run -skip-init-writes --qgraph /project/<USER>bps/submit/G3M19c/000001/drp/025/input/cit/quantum017777.pickle}}    failed with a not very helpful message    {noformat}    File "/software/lsstsw/stack_20190330/stack/miniconda3-4.5.12-1172c30/Linux64/ctrl_mpexec/18.0.0-2-g98b9f3b/python/lsst/ctrl/mpexec/singleQuantumExecutor.py", line 69, in execute        self.updateQuantumInputs(quantum)      File "/software/lsstsw/stack_20190330/stack/miniconda3-4.5.12-1172c30/Linux64/ctrl_mpexec/18.0.0-2-g98b9f3b/python/lsst/ctrl/mpexec/singleQuantumExecutor.py", line 133, in updateQuantumInputs        ref._id = storedRef.id    AttributeError: 'NoneType' object has no attribute 'id'  {noformat}     The command is wrong but it would be nice to have more informative error messages. 
Answer: 8040.0

User story: "Run pipe_analysis scripts   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    qa_explorer  # matchVisits.py     and validate_drp   # matchedVisitMetrics.py   # validateDrp.py   # reportPerformance.py    Upload the validate_drp metrics (json files) to SQuaSH:   # dispatch_verify.py    with the w_2019_30 RC2 outputs from DM-20525"
Answer: 18529.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: I should have a new Gaia DR2 LSST reference catalog (with parallax and proper motion!) ready and uploaded to lsst-dev by the end of the week. We should try to use it as part of a processCcd run with HSC data before we can say it is "ready". We may have to make changes to the HSC AstrometryConfig in order to use the this refcat (for example, the position errors are now much smaller than PS1, which may require changing match/fit tolerances).    I don't know what the best approach to testing this would be. Suggestions from the DRP team?
Answer: 93600.0

User story: "This story covers the time necessary to remove the   * ATCalCS   * ATEEC   * ATThermoelectricCooler   * MTCalCS   * Sequencer    CSCs from ts_xml and update the tests appropriately."
Answer: 40027.0

User story: "This story covers the time necessary to cut the v4.0.0 release of ts_xml, and make appropriate updates to the various XML and SAL tests and CI jobs."
Answer: 11517.0

User story: "After chatting to Colin, next step for closing the loop between the DRP output parquet files and ingestion into the DB is an HSC override file for https://github.com/lsst/cat/blob/master/yml/baselineSchema.yaml to match https://github.com/lsst/obs_subaru/blob/master/policy/Object.yaml"
Answer: 214433.0

User story: "Recently, in DMTN-085, the QA Strategy Working Group (QAWG) made specific recommendations to improve the SQuaSH metrics dashboard. SQR-033 presents an overview of the current implementation and a plan to implement what is missing.  "
Answer: 11761.0

User story: "The merge of the new defects work broke validate_drp because there are no defects in the repository, but that step is not skipped.    The fix is to add defects to the {{validation_data_drp}} package."
Answer: 1315.0

User story: "Create a notebook that demonstrates the improvements of scarlet on several HSC blends from the SDSS/HSC deblender."
Answer: 18367.0

User story: "This ticket is to use {{synpipe}} to insert fake sources into images from an appropriate dataset*, persist them to disk, and then run the fake-inserted images through {{ap_pipe}}.     (the HiTS CI dataset would be preferable if synpipe supports non-HSC cameras)"
Answer: 401741.0

User story: "This ticket is to become familiar with the ap_pipe code and to run it yourself on an appropriate dataset, likely https://github.com/lsst/ap_verify_ci_hits2015, either on your own computer or on lsst-dev"
Answer: 44672.0

User story: To fully implement RFC-616, we need a way to get the original FITS WCS from a raw file. As proposed in that RFC, this will be a "raw_header_wcs" datasetType in the butler (gen2 and 3).
Answer: 109678.0

User story: "And make sure it is installed in the right place."
Answer: 93961.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: "Complete CSC level code for FiberSpectrograph version 1    At minimum, this should implementing the commands specified in the XML and outputing the events and telemetry. Most of the generic commands and events are handled automatically by ts_salobj, so focus on the ones specified in the XML for the FiberSpectrograph.    An open question is whether we should also implement a heartbeat that uses the spectrograph status to periodically check the USB connection."
Answer: 92633.0

User story: "Add unit tests for FiberSpectrograph csc"
Answer: 63625.0

User story: "Update the Developer Guide to from documenteer 0.3.0 to 0.5.x. Also try upgrading the theme. And temporarily change the pytest intersphinx URL given the outage of pytest.org reported in https://github.com/pytest-dev/pytest/issues/5641"
Answer: 152.0

User story: "Build up alignment system so we can run a simulated correction loop.         In this version of the simulation we aren't actually moving the mirror, we're just reading the simulated variance of the instrument. So for now I measure each component a semi-random number of times to simulate iterations in the loop. "
Answer: 1090.0

User story: "move to room 202, set everything back up"
Answer: 1121.0

User story: "This ticket is to modify the ATMCS Telemetry XML to use arrays instead of single values. Then we can gather and log high-speed telemetry by publishing 100 values at 1 Hz, and therefore getting 100HZ information on the motors/encoders etc.     Also adding the RADESYS and TRACKSYS attributes to the trackTarget command and events."
Answer: 63436.0

User story: "This ticket is to capture the work of drafting a report to foster communication with [~<USER> about the possible algorithmic details regarding the image difference _fingerprint_ pattern issue.    This ticket is part of the clean-up of DM-17825."
Answer: 28650.0

User story: "The TAP service needs to look at the token and parse it out to determine various things, like read  vs write access, and possibly pass it down to further levels.  One other thing this controls is listing the jobs that a user has.    Without auth, you will get a 403 when deleting a job, which the async wrappers and the delete function on async job do.  This is because the CADC TAP service, after successfully deleting the job, will redirect to the page that lists the jobs.  But since it doesn't parse out the auth token, it gives a 403 when trying to list them.  Once we have the TAP service look at the token, this should be fixed."
Answer: 136851.0

User story: "Write a Task to run MultiProFit in the stack and test on existing COSMOS repos."
Answer: 70348.0

User story: "This task is to study how to rotate the DOF with the camera rotation angle. This task will use the PhoSim to do the evaluation and verification. This task will focus on the OPD-level first. This means only the OFC will be used. The use of WEP will be in the following tasks."
Answer: 20112.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "In the phase 1 [DM-20482|https://jira.lsstcorp.org/browse/DM-20482], I found the port: 55555 is hard-coded by M2 cell code to listen to M2 server. I issued the JIRA ticket ([IHS-2398|https://jira.lsstcorp.org/browse/IHS-2398]) for the help. This task is to check the communication between M2 cell and cRIO after the IT helped to open the port and fix the problems if the communication can not work even the port is unblocked."
Answer: 24243.0

User story: "End of august or early September, Doug wants me to update SAL version on Management PC, Diagnostic computer and ship the hardware to summit. Creating a task for this update and putting it in Backlog. "
Answer: 161185.0

User story: "Attend Puppet Workshop week of 15/July"
Answer: 5778.0

User story: "Adjustments or additional code to handle logging, etc. in this system."
Answer: 351729.0

User story: "How to integrate with the monitoring system"
Answer: 351730.0

User story: "Operator-type user test run ci_hsc reporting problems to developer"
Answer: 524459.0

User story: "Improve code documentation/style"
Answer: 524455.0

User story: "Implement HTCondor version."
Answer: 524457.0

User story: On Slack ([https://lsstc.slack.com/archives/C2JPT1KB7/p1563485540182700), |https://lsstc.slack.com/archives/C2JPT1KB7/p1563485540182700):]    [~<USER> writes:  {quote}{color:#1d1c1d}The other SciPi error I saw was{color}  {code:java}ValueError: Error in inputs to MergeCoaddMeasurements: source IDs do not match {code}  {color:#1d1c1d}But if I try to reproduce it directly, I'm seeing{color}  {code:java}File "/software/lsstsw/stack_20190330/stack/miniconda3-4.5.12-1172c30/Linux64/pipe_tasks/18.0.0-7-g4840a288+1/python/lsst/pipe/tasks/mergeMeasurements.py", line 298, in run      mergedCatalog.reserve(len(orderedCatalogs[0]))   IndexError: list index out of range {code}{quote}  This affects 19/79 quanta.  An example of one that failed is at  {code:java}/project/<USER>bps/submit/G3M19c/000001/drp/025/input/mmt/quantum083381.pickle {code}  That's (tract=9615 patch=77).
Answer: 14459.0

User story: "Bucket for September"
Answer: 109293.0

User story: "Bucket for August work."
Answer: 70608.0

User story: "Bucket for July work."
Answer: 197386.0

User story: "Bucket for September work."
Answer: 221656.0

User story: "Bucket for August work."
Answer: 221657.0

User story: "Bucket for July work."
Answer: 221657.0

User story: "The Lab container now does not know how to get its user from the Hub cookies; clearly we are stomping on something."
Answer: 1436.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: "If a select list item does not have an alias, Qserv will add one to it during query processing. This 'default' alias is simply the quoted sql of that item. For example {{SELECT foo.bar.baz...}} gets turned into {{SELECT foo.bar.baz AS `foo.bar.baz`...}}. (This aliasing is needed specifically for the merge table).     In some cases the alias is longer than the allowed length of 64 characters. We prefer the alias to reflect the original user query, but in this case a shorter alias must be created."
Answer: 9913.0

User story: "DM-20205 introduces a new api for pipeline tasks. This ticket will update the existing pipeline tasks to use this new api."
Answer: 61539.0

User story: "Run test with additional origin's"
Answer: 223552.0

User story: "Monitor Performance and Usability of initial data set, and provide feedback"
Answer: 223556.0

User story: "Initial setup and test with one origin of data."
Answer: 223552.0

User story: "Incorporate Gen3 if it is ready and in a semi-stable mode."
Answer: 222195.0

User story: "Incorporate Rucio when it is Ready"
Answer: 222195.0

User story: "Hand-processing and scripts to verify data transferred against data ingested (monitoring)."
Answer: 108249.0

User story: "Follow-on monitoring to verify initial deployment"
Answer: 353139.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: 112484.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: 49322.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: 7493.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: 99711.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: 50375.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: 3.0

User story: "Participate in the Data Management System Science Team and perform related duties as needed."
Answer: 108298.0

User story: "Participate in the Data Management System Science Team and perform related duties as needed."
Answer: 62106.0

User story: "Attend System Science Team meetings and perform related tasks as necessary."
Answer: 52132.0

User story: "it's failing because of a duplicate `ORDER BY` in the result statement."
Answer: 1351.0

User story: "The Dome Seeing Monitor needs to be added into the XML system. "
Answer: 18596.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Currently the ts_salobj package is only available inside docker images that have been built on top of the lsst stack and eups intended for development for T&S. The HeaderService is successfully running in this development environment. In order to deploy the HeaderService using salobj, it is necessary to create an environment that that does not depend on the lsst stack and eups. A first approach is to document this in a Dockerfile and the creation of a docker image using standard unix commands."
Answer: 11054.0

User story: "Create a conda environment and document detailing how to use said environment."
Answer: 8532.0

User story: "Backport issue DM-20506 to 18.1.x branch"
Answer: 9957.0

User story: "In order to prepare for the 18.1.0 release, branch 18.1.x has to be created to the involved git packages, starting from the 18.0.0 tag"
Answer: 1576.0

User story: "Do release 18.1.0 of science pipelines"
Answer: 38866.0

User story: "Check the LabVIEW dependency for M2 Cell code, which should be the windows version."
Answer: 2937.0

User story: "In theory it should be pretty easy to make group-based decisions about default container size and namespace resource quotas.    Test that theory."
Answer: 404.0

User story: "This command will be able to send startIntegration, endReadout and largeFileObjectAvailable logevents."
Answer: 8631.0

User story: "Work for design of ComCam Archiver."
Answer: 255025.0

User story: "Includes:   * Identify largest risks and possible migrations   * Planning scope of July 2019 PM   * Prepare Test Systems in NCSA 3003 for July 2019 PM   * Create a plan and new Schedule Maintenance Plan"
Answer: 17285.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 June 2019 monthly report (x)  - Circulate upcoming milestone list to dm-cams  - Audit and update https://confluence.lsstcorp.org/display/DM/DM+PMCS+Update+Requests"
Answer: 130811.0

User story: "Implementation of RFC-606."
Answer: 14367.0

User story: "Task to capture the work needed to deploy the containers in Chile with SAL 3.10. "
Answer: 9719.0

User story: "We need to make a wrapper that takes the LSP environment (environment variables like ACCESS_TOKEN, and URLs) and provides a pyvo TAP client to access the catalog."
Answer: 102342.0

User story: "Test kafka writers running from https://cloud.docker.com/u/lsstts/repository/docker/lsstts/kafka and using SAL_VERSION=3.10.0"
Answer: 4157.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: Initial test with Cassandra (DM-19536) showed that Cassandra data model may be usable but performance on a single-node "cluster" with spinning disk as very far from the goal numbers. To produce a reasonable performance numbers I think we need to have more realistic setup with more than one node (or more than 3 if we want to test replication), plenty of memory on each node and locally-attached SSD storage.    I'm not all sure where or when can we get access to this sort of hardware. Cloud options seem to be expensive, and buying this sort of hardware is not in the current purchase plan. So this ticket is blocked for now by hardware (in-)accessibility.    Important point when we are ready to test is for prototype to produce more realistic data for all DIA tables. Cassandra only stores columns that are specified in a query so we'll need realistic payload to measure performance.
Answer: 316861.0

User story: "Document in the release procedure the steps required to add the deprecation information in the release note."
Answer: 211727.0

User story: Right now if a Qserv restrictor function is called for a non-chunked table it results in an Analysis error, but the only way for a client to know a table is not chunked is to try to run the query with a restrictor, and if it fails try it without the restrictor.    We would like to fix this so that the client can make 1 call that Just Works.    Investigate changing to a Qserv "hint" (instead of restrictor), or changing the restrictor behavior to work even if the table is not chunked, and understand the architecture so we can have a discussion about possible fixes/implementations in a co-work meeting.
Answer: 11801.0

User story: "The meas_algorithms functions must be removed from defects.py prior to the release v19.0.0"
Answer: 66019.0

User story: "The deprecated functions in ip_isr must be removed from isrFunctions.py prior to the release v19.0.0"
Answer: 174206.0

User story: "The obs_lsstSim package must be removed from the lsst_obs metapackage and moved to legacy prior to the release v20.0.0"
Answer: 418702.0

User story: {{scipipe/ap_verify}} build [#286|https://ci.lsst.codes/blue/organizations/jenkins/scipipe%2Fap_verify/detail/ap_verify/286/artifacts] was run using the 18.0.0 release branch rather than the {{master}} version of the Stack. For some reason, this version could not load defects ("No registry for lookup"; see attached log).    While the error does not apply to recent Stack builds, we should determine:  * if it was caused by a problem in, e.g., defects handling that could affect future release builds  * if it's a sign that the 18.0.0 release build is broken in some way and needs to be patched
Answer: 626348.0

User story: "Have the top-level endpoint available, without service-specific routes."
Answer: 144.0

User story: "We have deprecated lsst.afw.geom.Point2I and related routines but they are still used all over the place. They need to be removed so that to allow DM-20565 to be unblocked."
Answer: 12766.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 {{afwGeom}} aliases for Point, Extent, and others that are now defined in {{geom}} must be removed prior to the release of v20.0."
Answer: 407211.0

User story: "Do release 20.0.0 of science pipelines"
Answer: 503666.0

User story: "Ensure the following FAQ answers from DM-20291 are integrated into future communications with the broker proposal teams, in LDM-612 and/or the letters soliciting full broker proposals:  Q3, co-locating a broker at NCSA  Q4, the fact that LOI and proposals are not shared publicly  Q5, the number of full-stream brokers supported  Q6, postage stamp handling options"
Answer: 285063.0

User story: "[~<USER> identified in the June '19 False Positive Sprint that the variances were wrong by 10-15% (  https://nbviewer.jupyter.org/github/yalsayyad/dm_notebooks/blob/master/examples/DiaSourceCensusCcdVisitNight-HSC-RC2.ipynb).  This is likely due to pixel covariances introduced by coaddition and warping.  This ticket is to investigate rescaling the variances appropriately with {{ScaleVariance}}."
Answer: 184934.0

User story: "[~<USER> produced some nice visualizations as part of the June False Positive print (e.g., https://github.com/lsst-dm/ap_pipe-notebooks/blob/master/false_positives/DiaSourceCensusCcdVisitNight.ipynb).  This ticket is to extract them from notebooks into a more generalized script or library"
Answer: 378683.0

User story: "[~<USER> suggests from attempting HSC processing that we should try using the calexp background in our HiTS processing as well.  She also adjusted the background order to 2.  This ticket is to do so and compare the results to the current ap_pipe defaults."
Answer: 24854.0

User story: "Right now there is no straightforward way to tell if a DIASource was produced from an (A&L) subtraction where the template seeing is worse than the science seeing.  This ticket is to either add logging or catalog columns to denote this."
Answer: 36283.0

User story: "If a pending RabbitMQ is received before all of the SAL proxy devices have topics registered, a message will attempt to be processed and cause a crash."
Answer: 4263.0

User story: "2nd week of observing the M2 coating."
Answer: 11723.0

User story: "I have accumulated a number of bug-fixes and features in display_matplotlib; please merge them to master.   * Implement DM-16560 (support mask in {{scale}})   * disable {{fastMaskDisplay}} by default   * support passing a matplotlib figure as the {{frame}} variable   * support a dpi argument to the ctor   * add colorbar support that actually works   * pass arguments through to {{savefig}}   * {{add allowPdb}} argument to the wait command   * fix colorbar for asinh stretches"
Answer: 298510.0

User story: "The first week of work spectating over VA and the happenings of the Coating Chamber. "
Answer: 11729.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: "During last week PCWG workshop, a new assessment of MERRA-2 data has emerged :    P.F. Leger and J. Mayer from the PSF task force are showing DECAM images of PSFs potentially sheared by wind.    The test we envisioned is to look into the MERRA-2 table at the wind direction at these dates.     "
Answer: 136445.0

User story: Following the work done on DM-20289, make the switch from the current "unity" scaling for the HSC camera focal plane to the actual physical focal plane units of millimeters (i.e. the representation preferred by the LSST stack). There are a few other packages (see list in components + {{fgcmcal}}, which doesn't seem to be recognized) that will need adjusting. The ultimate test for updates will be to run at least one full tract from the RC2 dataset (i.e. running through {{singleFrameDriver}}, {{skyCorrection}}, {{jointcal}}, {{coaddDriver}}, and {{multibandDriver}}) to make sure the results are consistent with that of the latest weekly reprocessing run.    Merging of this work will also be contingent on acceptance of an RFC to make the switch (this will be the triggered ticket for that RFC once it is written).
Answer: 56058.0

User story: "afw has some deprecated code that is not formally marked with the new {{@deprecated}} scheme. Some of these have been deprecated for many years. For deprecations over a year old, remove them. For others try to use the modern scheme.    This ticket is not fixing the {{afw.geom}} deprecations described in DM-17566."
Answer: 17090.0

User story: "We have been seeing situations where the client in a notebook will lose communication with the dask cluster it is constructed with.  The cell appears to just be hung.  Sometimes it does come back, but not for a long time.  The attached notebook will show this behavior on a weekly 20 build.  Just run the cell with {{len(df)}} a few times to see this behavior."
Answer: 106525.0

User story: "When the configuration key is wrong, the command should be rejected."
Answer: 80349.0

User story: The DMCS currently renames all the commands (such as "ENTER_CONTROL" instead of "enterControl", because of translations made by the old OCSBridge code.  The new OCSBridge doesn't do this, it uses the standard naming convention.  This will fix the DMCS to be in line with the standard naming convention.
Answer: 9800.0

User story: "Once the software is officially delivered to LSST, it will be necessary to update the design and code to conform to SAL constraints and conventions, as defined in [https://confluence.lsstcorp.org/display/SYSENG/SAL+constraints+and+recommendations]    This includes:   * Naming conventions   * Enumeration definition   * Implementation of all standard commands and events."
Answer: 494549.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: To better understand RFC-605, we need to determine if any of our existing obs packages have a flip in their pixel->focal transform. We think they are all defined as looking "down" on the focal plane, but we need to check.    1. Load the cameraGeom for each obs package.  2. Compute determinant of pixel->focal transform.  3. If determinant is negative, there is a flip.  
Answer: 14567.0

User story: "The {{utils}} package has had some methods that have been deprecated for years. Remove them."
Answer: 286.0

User story: "The release note contains already a section with high-level deprecations.    However, there are lots of deprecations on small functions, used only by a few people.    This list has to be added to the release note in a separate section."
Answer: 367.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Following DM-20435, we have a working set of flags used to filter out bad DIASources. See if the problems we saw before with highly variable nonsense totFlux (and also psFlux, apFlux) in the PPDB still appears with the remaining flag-filtered DIAObjects. Think about what we need to do to fix any remaining weirdness. (Some metric we can compute from flux data in the PPDB/diasrc/src to determine if a DIAObject is "really variable" or not? Some flux cut or SNR cut? Some measure of how far the position of the DIASource is from the DIAObject?)
Answer: 117804.0

User story: Following DM-19525, help debug problems with this run, and analyze the results. In particular, understand how it differs from a "standard" ap_pipe rerun with raw data + coadd templates and see if DIASource counts are consistent with those reported in DMTN-021.
Answer: 28690.0

User story: "LDM-503 & LDM-564 are currently under RFC (RFC-608 and RFC-609, respectively). Please make the following fixes:    - Incorporate the description of LDM-503-10a from DM-19208;  - Incorporate the new [deployment diagram|https://github.com/lsst-dm/images/commit/08bb3ad268245aa63b2340f851c5125fbea77511].  "
Answer: 7325.0

User story: "While debugging SAL softwares, we had a hard time migrating our software from current machine to the next. Tiago provided us with the initial docker image and we are gonna build upon that for deployment."
Answer: 106234.0

User story: "This task is to capture the work needed to (re)deploy the CSCs, Jupyter notebooks and EFD containers in Chile for the upcoming on-sky test with the Auxiliary Telescope. "
Answer: 16941.0

User story: "docsteady: include additional personel in test report"
Answer: 8648.0

User story: "Reprocess the HSC RC2 dataset, as defined in DM-11345, using Stack w_2019_30. Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{jointcal}}, {{skyCorrection.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}}. "
Answer: 31914.0

User story: "1.  Add {{deepDiff_diaObject}} datasetType     -- This is still a bit experimental.  It's being used and tested through DESC DC2 and {{dia_pipe}}, so it seems appropriate to just include these datasetTypes here in {{obs_lsst}} and not propagate to {{obs_base}}.  2. Correct deepDiff_diaSrc datasetType templates to use {{%08d}} to format {{visit}}.    Original work done by [~<USER>.   [~<USER> 's work is to do some light reformatting and testing."
Answer: 129610.0

User story: "In an effort to help speed up and streamline the DES optical model in Piff, go through the code and docstrings to develop a mental model of its high-level implementation.  Write that model down."
Answer: 484097.0

User story: "Gaussian quadrature is the most robust way to measure Zernike coefficients from wavefronts, and would also enable direct comparison with values from Bauman++."
Answer: 38065.0

User story: "Review PST Astro2020 paper before upload to arxiv"
Answer: 97484.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: DM-EFD is deployed at the Tucson lab.    Chronograf can be used to navigate through the topics     [https://test-chronograf-efd.lsst.codes/]    along with the monitoring of the k3s ("kubes") cluster and Kafka through the Grafana UI    [https://test-grafana-efd.lsst.codes/]    We want to test this setup with the SAL subsystems running at the Tucson lab {{ATCamera, ATHeaderService, ATArchiver, ATMonochromator, ATSpectrograph}}, and {{Electrometer}}.         
Answer: 8461.0

User story: "In the first implementation, I had both the InfluxDB Sink Connector and SALTransform in one Helm chart called [kaka-efd-apps|[https://github.com/lsst-sqre/charts]].    With SAL Kafka SAL transform is not required anymore and the InfluxDB Sink Connector is now implemented as part of the Kafka connect manager (DM-21042).    In this ticket, we implement a Helm Chart to deploy the Kafka connect manager.   "
Answer: 98684.0

User story: "{{kafka-connect-manager}} is the project that manages the different connectors used in the EFD https://kafka-connect-manager.lsst.io/    It is deployed via the {{kafka-connect-manager}} Helm Chart.     In DM-23575 we add support to the Replicator connector in {{kafka-connect-manager}}. In this ticket, we add the necessary configuration to deploy the Replicator connector using the {{kafka-connect-manager}} Helm chart."
Answer: 372963.0

User story: "We would like to migrate the ATArchiver at the NCSA test stand from the old system {{ lsst-ats01}} to the new one {{lsst-l1-cl-arctl}} which is controller via puppet."
Answer: 168193.0

User story: "Update XML to have consistent units and descriptions, as per required by CAP-235."
Answer: 174004.0

User story: "There is a pending Forwarder change for ComCam. For a better design, I need to find out if cfitsio can support reading of binary array and create fitsfile. In the earlier iteration, we were using files."
Answer: 1476.0

User story: "Do a ci_hsc run with [~<USER>'s test Oracle cluster & a new version of Oracle at lsst-oradb-test.ncsa     This should go before the re-start of the RC2 milestone runs."
Answer: 258.0

User story: The QA Strategy Working Group, in https://dmtn-085.lsst.io, produced three recommendations related to documentation examples and testing:    * QAWG-REC-13: "Provide a central location where examples, scripts and utilities which are not fundamental to pipeline execution are indexed and made discoverable"  * QAWG-REC-14: "The Project should adopt a documented (in the Developer Guide) policy on the maintenance of example code"  * QAWG-REC-15: "The   *Project should prioritize the development of a documentation system which makes it convenient to include code examples and that tests those examples as part of a documentation build"    As a first step towards implementing these recommendations, we need to analyze them and expand them into concrete technical requirements to guide future development. This will be done in a new technote, https://sqr-032.lsst.io.
Answer: 23182.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: Now that we have split "prod" builds, I'd like a way to automatically display experimental builds on `-int`, which argues for a way to generically add experimentals to the menu and prepull selection.
Answer: 336.0

User story: "Write up docs and provide accounts to help T&S upload their own documentation projects to LSST the Docs."
Answer: 4.0

User story: For writing PFS data, we want elements of the {{dataId}} to allow unsigned 64-bit integer values (e.g., object identifiers or hashes). This is not currently possible, because the butler puts the {{dataId}} into a {{PropertySet}} (as "{{additionalData}}"), and {{PropertySet}} does not support unsigned 64-bit integers (signed 64-bit integers are allowed).    I will add u64 support to {{PropertySet}}. This may not be something that LSST cares strongly about (because of Gen3 efforts), but this is something that we would like to see get into a 18.x release so we can base the PFS work off that for the next year or so.
Answer: 19134.0

User story: "This is to update the XML to use proper descriptions and units.    This is related to CAP-236"
Answer: 174377.0

User story: "ATArchiver needs C++ and python libraries. This script will help Felipe deploy ATArchiver with puppet."
Answer: 108106.0

User story: "DM-18396 made changes to the portal deployment entry points as following:   # Main Portal application: (instance-FQDN)/portal/app   # Time series viewer: (instance-FQDN)/portal/app/ts.html   # Slate: (instance-FQDN)/portal/app/slate.html    We need to do  a test to make sure all the notebooks using Firefly for visualization still work with the new deployment in lsp-int. "
Answer: 77512.0

User story: "Community post checklist proposed in SQR-16 need to be reviewed, and the actual meaning of each step clarified.         Section 1.4.2 needs to be updated also: O_LATEST need to be true for the final release. It has to be false in case the final release is a patch based on a previous major/minor release."
Answer: 295147.0

User story: "As per jenkins job :     [https://ci.lsst.codes/blue/organizations/jenkins/release%2Fofficial-release/detail/official-release/20/pipeline]    the lsstsw rebuild is failing on the following test:    obs_cfht.centos-7.devtoolset-6.py3.tests.test_butler.GetRawTestCase.testRaw         After some investigation, it is found that the lsst-build prepare is checking out master for the package    astro_metadata_translator    that has been changed since the weekly 23 has been done, on which 18.0.0 is based.    Further checks show also that other DM External packages are checkout with the master version.    The package autograd, for example, is also cloned, despite it was not part of the weekly 23.         It seems that lsst_build need some extra logic to properly clone and checkout the DM External packages."
Answer: 115.0

User story: "The xml for the HeaderService on ts_xml needs to be update for the upcoming release of ts_xml version 4.0.0"
Answer: 1679.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: "Same as DM-20495, but for the TAP services.  Since two people will be doing the work on two different repos, two tickets."
Answer: 230572.0

User story: "So in looking at -int with the Jenkins failure, Josh thinks that the running out of memory issue might be on another service running on the same node as the Jenkins failure.  He also noticed that the DAX services aren't setting resource limits in kubernetes to help limit and restrict the resource usage, specifically the memory usage.  We should add this.  I'm going to make a duplicate issue for the TAP service part of this."
Answer: 200255.0

User story: "Setup with the typo gives     Unexpected line in  ..../ci_hsc_gen3/ups/ci_hsc_gen3.table:1: setupRequires(ctrl_mpexec)     and  setupRequires(tesetdata_ci_hsc)"
Answer: 1215.0

User story: "DM-19843, DM-20050 and DM-20265 made significant changes to MultiProFit's code and fitting methods. This ticket is to re-run MultiProFit on a large sample of COSMOS galaxies, validate the results and fix any obvious bugs/issues that pop up."
Answer: 159697.0

User story: "The newest xml (version 3.10.2) introduced several changes to the message content sent by ATCamera. The HeaderService needs to be modified for this reason."
Answer: 1855.0

User story: "Update units and description for CSCs FiberSpectrograph, HR, Monochromator."
Answer: 20196.0

User story: "Chronograf was added to the EFD deployment managed by Argo CD, however, GitHub OAuth2 is missing."
Answer: 275009.0

User story: Update the documentation layout for the cbp package using the modern standard which eliminates the unnecessary "cbp" subdirectory and moves "lsst.cbp" up to the top level.    Upload the new documentation.
Answer: 283716.0

User story: "The QA dashboard project needs hvplot installed on the Jupyterlab environment.  "
Answer: 11403.0

User story: "At present, when jenkins build failures are suspected to be caused by a specific kubernetes node, the process for determining the node name is tedious. It requires determining the name of the jenkins agent(s) the build was scheduled upon, then manually describing the running k8s pod(s) to see which node(s) said pod(s) are currently scheduled on.  If the pod(s) have been killed/restarted since the suspect build, this information is essentially lost to the SQRE team (but perhaps could be reverse engineered from kubelet logs?)"
Answer: 1482.0

User story: During the "False Positives Sprint" we ran ap_pipe with default configs on HSC RC2 data. We found that most of the false positives were due to backgrounds not being matched right, which is probably a simple misconfiguration or bug.    Image difference for visit=30490 (HSC-I):  !Screen Shot 2019-07-08 at 12.11.47 PM.png|thumbnail!    looks like the filter-transmission and sky Frame. 
Answer: 178963.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "It looks like there is no communication between the m2 server and m2 cRIO now. Need to construct the communication to let the cRIO to run. There is a risk here that it looks like the m2 laptop can not talk to the cRIO also. Need some time to dig into this. This is the phase 1."
Answer: 16020.0

User story: "Review the documents of M2 to have an initial understanding of status. This is the phase 2."
Answer: 16024.0

User story: "Science Platform Network Decadal Survey 2020 APC White Paper"
Answer: 5617.0

User story: "Initial work to migrate the HeaderService to use salobj."
Answer: 45560.0

User story: "The auxTel uses a CMOS detector for collimating, and it therefore has no overscan.  If you blithely set the overscan region to contain no pixels in the cameraGeometry the ISR code handles it, except that it tries to report statistics.    Please detect the {{None}}.  A workaround is to set {{config.isr.qa.saveStats = False}}, but that disables too much and anyway fixing the code is cleaner."
Answer: 4069.0

User story: "Plot the magnitude difference between input and output magnitudes for fake sources against the distance to the nearest neighbour."
Answer: 68062.0

User story: "The section section of the paper is edited to account for referree's observations :    the atmospheric variability impact on LSST photometry as predicted by MERRA-2 is added in the discussion.      spectral type (A5V) -> main-sequence star (blue)    LSST throughput from Filter Throughputs in   https://www.lsst.org/scientists/keynumbers  [https://github.com/lsst/throughputs/tree/master/approximate_baseline]    ANNUAL :  u variation = 12.59%  g variation = 12.58%  r variation = 12.61%  i variation = 13.03%  z variation = 13.54%  Y3 variation = 13.27%  Y4 variation = 16.70%    NIGHTLY :    u variation = 0.90 %  g variation = 0.90 %  r variation = 0.90 %  i variation = 0.99 %  z variation = 1.20 %  Y3 variation = 1.11 %  Y4 variation = 2.55 %         UNCERTAINTY :    u variation = 2.00 %  g variation = 2.01 %  r variation = 2.06 %  i variation = 2.17 %  z variation = 2.28 %  Y3 variation = 2.22 %  Y4 variation = 2.93 %          "
Answer: 150632.0

User story: "Run pipe_analysis scripts   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    and validate_drp   # matchedVisitMetrics.py   # validateDrp.py   # reportPerformance.py    Upload the validate_drp metrics (json files) to SQuaSH:   # dispatch_verify.py    with the w_2019_26 RC2 outputs from DM-19560"
Answer: 9620.0

User story: "Please, install these two plugins on [https://ts-ci.lsst.codes/] Jenkins server.          [https://plugins.jenkins.io/versionnumber]         and          [https://plugins.jenkins.io/generic-webhook-trigger]     "
Answer: 279716.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: [~<USER> reports an error when running multiband:  {code}  [73] Traceback (most recent call last):  [73]   File "/ana/products.7.7.2/stack/miniconda3-4.5.12-1172c30/Linux64/ctrl_pool/7.0-hsc+1/python/lsst/ctrl/pool/pool.py", line 113, in wrapper  [73]     return func(*args, **kwargs)  [73]   File "/ana/products.7.7.2/stack/miniconda3-4.5.12-1172c30/Linux64/ctrl_pool/7.0-hsc+1/python/lsst/ctrl/pool/pool.py", line 1070, in run  [73]     while not menu[command]():  [73]   File "/ana/products.7.7.2/stack/miniconda3-4.5.12-1172c30/Linux64/ctrl_pool/7.0-hsc+1/python/lsst/ctrl/pool/pool.py", line 240, in wrapper  [73]     return func(*args, **kwargs)  [73]   File "/ana/products.7.7.2/stack/miniconda3-4.5.12-1172c30/Linux64/ctrl_pool/7.0-hsc+1/python/lsst/ctrl/pool/pool.py", line 1088, in reduce  [73]     result = self._processQueue(context, func, [(index, data)], *args, **kwargs)[0]  [73]   File "/ana/products.7.7.2/stack/miniconda3-4.5.12-1172c30/Linux64/ctrl_pool/7.0-hsc+1/python/lsst/ctrl/pool/pool.py", line 547, in _processQueue  [73]     return self._reduceQueue(context, None, func, queue, *args, **kwargs)  [73]   File "/ana/products.7.7.2/stack/miniconda3-4.5.12-1172c30/Linux64/ctrl_pool/7.0-hsc+1/python/lsst/ctrl/pool/pool.py", line 573, in _reduceQueue  [73]     resultList = [func(self._getCache(context, i), data, *args, **kwargs) for i, data in queue]  [73]   File "/ana/products.7.7.2/stack/miniconda3-4.5.12-1172c30/Linux64/ctrl_pool/7.0-hsc+1/python/lsst/ctrl/pool/pool.py", line 573, in <listcomp>  [73]     resultList = [func(self._getCache(context, i), data, *args, **kwargs) for i, data in queue]  [73]   File "/ana/products.7.7.2/stack/miniconda3-4.5.12-1172c30/Linux64/pipe_drivers/7.5-hsc+1/python/lsst/pipe/drivers/multiBandDriver.py", line 428, in runMeasurements  [73]     self.measureCoaddSources.runDataRef(dataRef)  [73]   File "/ana/products.7.7.2/stack/miniconda3-4.5.12-1172c30/Linux64/pipe_tasks/7.0-hsc+1/python/lsst/pipe/tasks/multiBand.py", line 996, in runDataRef  [73]     exposureId=self.getExposureId(patchRef))  [73]   File "/ana/products.7.7.2/stack/miniconda3-4.5.12-1172c30/Linux64/pipe_tasks/7.0-hsc+1/python/lsst/pipe/tasks/multiBand.py", line 1073, in run  [73]     matchResult.matchMeta)  [73]   File "/ana/products.7.7.2/stack/miniconda3-4.5.12-1172c30/Linux64/meas_astrom/7.0-hsc+1/python/lsst/meas/astrom/denormalizeMatches.py", line 65, in denormalizeMatches  [73]     raise RuntimeError("No matches provided.")  [73] RuntimeError: No matches provided.  [73] application called MPI_Abort(MPI_COMM_WORLD, 1) - process 73  {code}
Answer: 10484.0

User story: "The new Watcher XML (DM-20145) has a few errors:  - Use of Explanation instead of Description for topics  - No description for the heartbeat event"
Answer: 7253.0

User story: "Fix log times to use UTC with Z"
Answer: 10245.0

User story: "Add commands to enterControl, start with config key Normal and enable."
Answer: 10250.0