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: Running {{matchedVisitMetricsTask}} in {{validate_drp}} yields the following deprecation warning:    {code:python}  /software/lsstsw/stack_20191101/python/miniconda3-4.5.12/envs/lsst-scipipe/lib/python3.7/site-packages/matplotlib/axes/_axes.py:6521: MatplotlibDeprecationWarning:   The 'normed' kwarg was deprecated in Matplotlib 2.1 and will be removed in 3.1. Use 'density' instead.    alternative="'density'", removal="3.1")  {code}    This will be a problem if we update to matplotlib 3.1 (and I don't think this is tested outside of RC2 and related runs).
Answer: 86242.0

User story: "So we just noticed something interesting on stable.    It looks like everything was hanging for people calling the TAP service.  What was really happening was:   # The capabilities endpoint is retrieved at the beginning, to figure out the auth stuff.   # This seems to get stuck waiting forever, but should respond very quickly.   # Trying it on the command line I can see it as well.  It hangs.  But running it again, it works.  50/50.    Now, backtracking through the layers of networking, I noticed that this was the case all the way back into the TAP service pod itself, accessing localhost:8080/tap/capabilities. So this means that probably tomcat (which is serving that website) went out to lunch, and had two threads serving, but only ended up having one that did something.         Just filing this to keep track if it happens again.  This did not happen on int."
Answer: 379252.0

User story: "Demonstrate that the linearity model persisted as per DM-23044 (and generated as per DM-21221) are scientifically adequate. File tickets to address glaring algorithmic flaws."
Answer: 142301.0

User story: "Store the output of DM-21221 in some meaningful form using the Butler, and demonstrate that it can be used in downstream processing."
Answer: 122656.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: "Understand and explore the issue with bright star wings.         Quick summary:   * Started exploratory work (and familiarization with stack functions/data products) by looking at bright stars on both single exposures and coadds, both HSC Wide and DUD fields, etc.   * Looked into current bright star masks for HSC, both the older Arcturus (Coupon et al., 2018) and the more recent/larger ones by Andy Goulding. Had discussions with the latter about their creation. Played around with the masks. In particular, how to use them as a stand-in for using external catalogs to identify and extract bright stars.     * Searched for existing approaches; found they typically rely on stacking large number of bright stars (latest reference being Infante-Sainz et al., 2020, with application to SDSS).   * During analysis sprint, studied radial detection density around bright stars; can be used to determine if future bright star wing models allow for smaller masks.         The conclusion is a plan for a first-step model, namely that of Infante-Sainz 2020, but using stack machinery, which will already increase flexibility (eg by allowing for choice of stacking statistic). See DM-23785 and DM-23786.         With these deployed, we can start studying main sources of variability in the extended PSF: seeing, bright object color, position within focal plane? As well as relationship between number of bright objects used to build model, and its quality.    Combining these should lead to natural next steps for improvement."
Answer: 103846.0

User story: "story points represent the total percentage of the hardware budget remaining. "
Answer: 11496.0

User story: "Total story points represent the percentage of the budget realized for hardware that has been received"
Answer: 11496.0

User story: "Story points will be reflective of the amount of the budget spent on Amazon Web Services "
Answer: 54696.0

User story: "Represents the percent of the budget spent on power and cooling, story points will be updated as power and cooling expenses post"
Answer: 11497.0

User story: "Investigation of calibration errors has shown that improvements can be made by performing local background subtraction on the aperture fluxes.  These will bring the faint stars more in line with the bright stars, and should only improve calibrations (decreasing bias and scatter for bright stars), and this ticket does not imply that these corrections should necessarily be made outside of calibration, or to fluxes other than aperture fluxes used for calibration."
Answer: 15759.0

User story: "In DM-22137 it was discovered that the newer version of scarlet introduces a large (~500 mmag) bias and increased scatter in galaxy photometry that is not present for stellar sources. This ticket is to identify why scarlet is failing for most galaxies while performing so well for stellar sources."
Answer: 6020.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "We have some very nice documentation at https://pipelines.lsst.io/modules/lsst.meas.algorithms/creating-a-reference-catalog.html on how to create a reference catalog.    However, in an effort to make it easy for the user to ingest catalogs spread over multiple files, this page seems to rather bury the lead — which is that the user just needs to run `IngestIndexedReferenceTask` with an appropriate configuration.    This has [caused some confusion|https://lsstc.slack.com/archives/C2KQDG7D0/p1578354181035000]. Please update the docs to make clear exactly what's happening."
Answer: 15799.0

User story: "Create a functor for converting dipole separation in pixels to arcseconds. My result in a generic functor that converts pixel-distance measurements into arcseconds."
Answer: 99525.0

User story: "Photometry functors in the SDM in pipe_tasks currently use a hard coded zero point. This ticket will modify them to use the local zero point stored in the catalog."
Answer: 88168.0

User story: "Make tucson-teststand also use the ArgoCD framework"
Answer: 25571.0

User story: "Staying abreast of upstream developments."
Answer: 70514.0

User story: "Some of the columns needed by pipe_analysis to identify if a source was used in calibration were not being propagated by processCcdWithFakes. This should be rectified by matching to the ic source catalog and including the required columns as is done in calibrate.py."
Answer: 15499.0

User story: "The DM glossary has (what I think is) a slightly confusing discussion of the relationship between Prompt Processing, Alert Production and Solar System Processing. Please clarify it."
Answer: 27.0

User story: "DECam stores multiple detectors in a single file so we need to be able to do an ingest of a single file and associate it with multiple datasetRefs.  This ticket will implement that support.    The baseline design is:    * Change FileDataset to allow a list of DatasetRef per dataset.  * In Butler.ingest add a dataset for each DatasetRef in each FileDataset.  * In Datastore.ingest register a dataset for each DatasetRef but associate with the same file.  * In Datastore.get pass the dataId to formatter.read.  * In Datastore.remove only delete the file if there are no other datasets associated with that file.    I don't think we need to have a special StorageClass listing the particular dimensions if we pass in the full dataId and let the formatter work out what it needs to know, so we don't need a special datasetType. I will find out when I start to implement."
Answer: 8238.0

User story: "create the services to support CCArchiver functionality"
Answer: 77588.0

User story: "Refactor the dm_atarchiver code;  much of this can be reused to create the ComCam code"
Answer: 50394.0

User story: "Jenkins is not telling slack about builds."
Answer: 74.0

User story: "No description provided!  This ticket had been created automatically Primavera ID: None"
Answer: 37326.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 new ts_xml 4.6.0 changed the {{ATSpectrograph_logevent_settingsApplied}} to {{ATSpectrograph_logevent_settingsAppliedValues}} and therefore the ATHeaderService configuration and simulator need to be updated."
Answer: 27615.0

User story: "Follow the procedure that was done for registering the SkyMap, and do the same thing for subfilters. Need to figure out exactly that procedure is!"
Answer: 30395.0

User story: "We moved the location of the Qserv log files, so the corresponding config in the LSP deployment needs to be updated."
Answer: 1176.0

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

User story: "Kafka deployment on the NCSA Test Stand to support AP testing.    This ticket had been created automatically   Primavera ID: None"
Answer: 225890.0

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

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

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

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

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

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

User story: <span style="font-size:13px;color:#000000;font-weight:normal;text-decoration:none;font-family:'Arial';font-style:normal;text-decoration-skip-ink:none;">Run and report issues to Gen3 dev.</span>  This ticket had been created automatically Primavera ID: None
Answer: 216982.0

User story: "In v1.0, hardcoding transfer mechanisms, ingestion calls, etc was acceptable.  Modify code to be more configurable.    This ticket had been created automatically  Primavera ID: None"
Answer: 350886.0

User story: "Performance and verification of CY2020Q1 PM  This ticket had been created automatically Primavera ID: None"
Answer: 70616.0

User story: "Work with admins to get DBB Buffer Mngr v1.0 deployed at the summit and verify it is working.    This ticket had been created automatically  Primavera ID: None"
Answer: 239833.0

User story: "Work with admins to get DBB Buffer Mngr v1.0 deployed at the LDF and verify it is working.    This ticket had been created automatically  Primavera ID: None"
Answer: 208491.0

User story: "Fix minor bugs in the DBB Buffer Mngr v1.0 (src or dest ends) for 1 week after service starts running.    This ticket had been created automatically  Primavera ID: None"
Answer: 239837.0

User story: "Implement Src/Archiver side of DBB Buffer Manager – find and transfer    This ticket had been created automatically   Primavera ID: None"
Answer: 22550.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: "Implement LDF side of DBB Buffer Manager – find and ingest    This ticket had been created automatically   Primavera ID: None"
Answer: 35635.0

User story: "Package software for deployment on summit and LDF production machine.    This ticket had been created automatically   Primavera ID: None"
Answer: 86044.0

User story: "ctrl_pool takes --time passed on the cmdline and computes walltime = time*DataIds/n_procs, which it puts in the slurm scripts.     9 times out of 10 I know what walltime I want, and do a quick time walltime*n_procs/dataIds to decide what --time to pass.  This is because some of our pipe_driver take > 1 hour and some even > 1day, and we expect only 1-3 to be run in serial.         This would be a VERY QUICK addition and would improve my quality of life.           "
Answer: 11633.0

User story: "When people try to log into the /logs endpoint, if they aren't a member of the right group, they just get stuck into a redirect loop.  Since there's no error page, they never think they are missing something.  This is super confusing.  Better to redirect to some kind of error page saying 'not a member of group x' when you have a token, it's not expired, and you aren't a member of the group required, rather than just trying to get them to auth again"
Answer: 152678.0

User story: "So, there's a way to control the debugging level and zones through a web API, but when we turned on auth, apparently now it won't let me turn  on the debug logging.  It took a bit of digging, but I think I understand how this works now, and can get myself back to being able to control the logs, and set up a list of people that can control this in the future (which would probably be a vault secret)."
Answer: 187330.0

User story: "NAOJ report that in the S19A production run with hscPipe 7, about 1% of objects have CModel flux=0 fluxsigma=NaN, without the flag set."
Answer: 7274.0

User story: "Maintenance of the project package for the 0.6 release of Documenteer. Goals:   * Use PEP 518 - ready packing methods (pyproject.toml, setup.cfg, setup.py)   * Update the presentation of the documentation   * More comprehensive user documentation (document existing extensions, scripts, and features)."
Answer: 27523.0

User story: "We're going back to port 4040.  Need a ticket, so I can check in against."
Answer: 22.0

User story: "We recently received spatially varying filter scans for the HSC NB filters.  These will be necessary to run {{fgcmcal}} on HSC NB filters.  The raw files will be formatted to put into {{obs_subaru}} {{filterTraces.py}}"
Answer: 2173.0

User story: "Define DC2.2i tracts to be included in the validation dataset. "
Answer: 32914.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: "Add functionality for greater compatibility with the gen2 run of {{ImageDifferenceTask}}. This is a TODO ticket in the code introduced by DM-22541 .   * Add support of using the calexp source catalog for kernel source selection.   * Add support of using the template source catalog for kernel source selection.   * Add support of using an external catalog for kernel source selection. Complication is the {{refObjLoader}} subtask which takes a gen2 butler currently.   * Add support for using a diasource catalog and performing post-subtraction operations only if this is compatible with gen3."
Answer: 161247.0

User story: "This ticket is introduced as code TODO by DM-22541.         Add support for dcr coadd template loading to {{ImageDifferenceTask}} in gen3 mode. Perhaps instead of GetCoaddAsTemplateConfig.coaddName we want a top level config option e.g. useDcr that controls the inputs in the connection class."
Answer: 150979.0

User story: <span style="font-size:15px;color:#000000;font-weight:normal;text-decoration:none;font-family:'docs-Calibri';font-style:normal;text-decoration-skip-ink:none;">Minor bug fixes and emergent features and incident response for 1 week after deployment.</span>  This ticket had been created automatically Primavera ID: None
Answer: 99198.0

User story: "Rearrange GPFS web data storage location  This ticket had been created automatically Primavera ID: None"
Answer: 238637.0

User story: "security vetting of lsst-web vm  This ticket had been created automatically Primavera ID: None"
Answer: 202887.0

User story: "Put lsst-web vm into production   This ticket had been created automatically Primavera ID: None"
Answer: 233062.0

User story: "Evaluate program need for lsst-web   This ticket had been created automatically Primavera ID: None"
Answer: 89134.0

User story: "Evaluate what is actually hosted on lsst-web   This ticket had been created automatically Primavera ID: None"
Answer: 39923.0

User story: "lsst-web redirect corrections   This ticket had been created automatically Primavera ID: None"
Answer: 233063.0

User story: "Puppet config for lsst-web  This ticket had been created automatically Primavera ID: None"
Answer: 182646.0

User story: "test new lsst-web vm   This ticket had been created automatically Primavera ID: None"
Answer: 162467.0

User story: "Planning for CY2020Q1 PM  This ticket had been created automatically Primavera ID: None"
Answer: 120495.0

User story: "Investigate and test if these mounts can be changed to v4  This ticket had been created automatically Primavera ID: None"
Answer: 41652.0

User story: "Determine where NFS v3 mounts and exports still exist    This ticket had been created automatically Primavera ID: None"
Answer: 41653.0

User story: "Set up VMs for full TICK stack alerting investigation  This ticket had been created automatically Primavera ID: None"
Answer: 80645.0

User story: "Set up and test sample alerts for full TICK stack alerting  This ticket had been created automatically Primavera ID: None"
Answer: 130500.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: "Report and recommendation on Chronograf and Kapacitor   This ticket had been created automatically Primavera ID: None"
Answer: 130500.0

User story: "Benchmark storage capacity at BDC   This ticket had been created automatically Primavera ID: None"
Answer: 122317.0

User story: "Validate storage capacity/configuration at BDC   This ticket had been created automatically Primavera ID: None"
Answer: 122318.0

User story: "Bring storage capacity online/validate at BDC   This ticket had been created automatically Primavera ID: None"
Answer: 122318.0

User story: "client Puppet config (clients) at BDC   This ticket had been created automatically Primavera ID: None"
Answer: 122317.0

User story: "Oversee/instruct disk/array install at BDC   This ticket had been created automatically Primavera ID: None"
Answer: 122318.0

User story: "Remotely support hw installation  This ticket had been created automatically Primavera ID: None"
Answer: 133584.0

User story: "Remotely support sw installation  This ticket had been created automatically Primavera ID: None"
Answer: 133584.0

User story: "Rack new K8 nodes  This ticket had been created automatically Primavera ID: None"
Answer: 39932.0

User story: "Highest priority K8 backlog improvements   This ticket had been created automatically Primavera ID: None"
Answer: 269086.0

User story: "Investigate RSA replacement options.  This ticket had been created automatically Primavera ID: None"
Answer: 37244.0

User story: "Implement changes, getting rid of RSA.  This ticket had been created automatically Primavera ID: None"
Answer: 73353.0

User story: "Report RSA replacement options to ICI admins for a decision    This ticket had been created automatically Primavera ID: None"
Answer: 37241.0

User story: "DR3: Variable Time for full backups  This ticket had been created automatically Primavera ID: None"
Answer: 127960.0

User story: "DR3: Variable Time to save archive on Long-term media  This ticket had been created automatically Primavera ID: None"
Answer: 127960.0

User story: "DR3: Enhance Monitoring and Alerting  This ticket had been created automatically Primavera ID: None"
Answer: 127960.0

User story: "DR3: Variable size of archive  This ticket had been created automatically Primavera ID: None"
Answer: 127960.0

User story: "Benchmark oracle multi tenant   This ticket had been created automatically Primavera ID: None"
Answer: 100664.0

User story: "move multi-tenant arch to production  This ticket had been created automatically Primavera ID: None"
Answer: 100664.0

User story: Multi-tenant Oracle: " Research multi-tenant arch incl. Within NCSA LSST env "  This ticket had been created automatically Primavera ID: None
Answer: 57364.0

User story: "Test setup of multi-tenant arch  This ticket had been created automatically Primavera ID: None"
Answer: 73378.0

User story: "Rack new qserv nodes  This ticket had been created automatically Primavera ID: None"
Answer: 39948.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: "Build and test qserv master nodes  This ticket had been created automatically Primavera ID: None"
Answer: 67539.0

User story: "Bring new storage capacity online (include system changes)   This ticket had been created automatically Primavera ID: None"
Answer: 41650.0

User story: "Benchmark new DDN storage  This ticket had been created automatically Primavera ID: None"
Answer: 41650.0

User story: "Install and validate new DDN storage   This ticket had been created automatically Primavera ID: None"
Answer: 41650.0

User story: "Fix minor bugs in the DBB Buffer Mngr v1.0 (src or dest ends) for 1 week after service starts running.    This ticket had been created automatically  Primavera ID: None"
Answer: 82828.0

User story: <span style="font-size:13px;color:#000000;font-weight:normal;text-decoration:none;font-family:'Arial';font-style:normal;text-decoration-skip-ink:none;">Work with admins to get DBB Buffer Mngr v1.0 deployed at the LDF and verify it is working.</span>  This ticket had been created automatically Primavera ID: None
Answer: 82828.0

User story: "Fix minor bugs in the DBB Buffer Mngr v1.0 (src or dest ends) for 1 week after service starts running.    This ticket had been created automatically  Primavera ID: None"
Answer: 82829.0

User story: "Develop automated methods for verification of data movement and ingestion for instrument operating at summit. Note this assumes a means to probe a record of observations taken.    This ticket had been created automatically   Primavera ID: None"
Answer: 224413.0

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

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

User story: <span style="font-size:13px;color:#000000;font-weight:normal;text-decoration:none;font-family:'Arial';font-style:normal;text-decoration-skip-ink:none;">Review milestones, upcoming priorities, and thrusts from the project.</span>  This ticket had been created automatically Primavera ID: None
Answer: 117775.0

User story: <span style="font-size:13px;color:#000000;font-weight:normal;text-decoration:none;font-family:'Arial';font-style:normal;text-decoration-skip-ink:none;">Prepare list of tasks which are on course to carry over into next cycle.</span>  This ticket had been created automatically Primavera ID: None
Answer: 117775.0

User story: <span style="font-size:13px;color:#000000;font-weight:normal;text-decoration:none;font-family:'Arial';font-style:normal;text-decoration-skip-ink:none;">Presentation of upcoming milestones, priorities, and thrusts for next cycle.</span>  This ticket had been created automatically Primavera ID: None
Answer: 117775.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: <span style="font-size:13px;color:#000000;font-weight:normal;text-decoration:none;font-family:'Arial';font-style:normal;text-decoration-skip-ink:none;">Define high-level epics and dependencies. Discuss with technical groups and management as needed.</span>  This ticket had been created automatically Primavera ID: None
Answer: 117775.0

User story: <span style="font-size:13px;color:#000000;font-weight:normal;text-decoration:none;font-family:'Arial';font-style:normal;text-decoration-skip-ink:none;">Refine epics, stories, descriptions, deliverable(s), level of effort, resource assignments, and dependencies. Load detailed plan into Primavera.</span>  This ticket had been created automatically Primavera ID: None
Answer: 117775.0

User story: <span style="font-size:13px;color:#000000;font-weight:normal;text-decoration:none;font-family:'Arial';font-style:normal;text-decoration-skip-ink:none;">This step encompasses everything after loading the initial plan into Primavera, e.g., scheduling the plan, refining allocations, re-prioritizing and re-scheduling to level resources.</span>  This ticket had been created automatically Primavera ID: None
Answer: 117775.0

User story: <span style="font-size:13px;color:#000000;font-weight:normal;text-decoration:none;font-family:'Arial';font-style:normal;text-decoration-skip-ink:none;">Export plan, including subtasks, from Primavera to Jira.</span>  This ticket had been created automatically Primavera ID: None
Answer: 117776.0

User story: <span style="font-size:13px;color:#000000;font-weight:normal;text-decoration:none;font-family:'Arial';font-style:normal;text-decoration-skip-ink:none;">Export plan, including subtasks, from Primavera to Jira.</span>  This ticket had been created automatically Primavera ID: None
Answer: 127889.0

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

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

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

User story: "Verify that expected data transfer has occurred successfully for AuxTel (summit).    This ticket had been created automatically   Primavera ID: None"
Answer: 102095.0

User story: "Develop semi-automated methods for verification of successful data transfer and ingestion from LATISS (BOT and ComCam should be though about as these will be next).   This is intended for ad-hoc verification until observatory systems can provide a record of observations.    This ticket had been created automatically   Primavera ID: None"
Answer: 260196.0

User story: <span style="font-size:13px;color:#000000;font-weight:normal;text-decoration:none;font-family:'Arial';font-style:normal;text-decoration-skip-ink:none;">Take RC2 processing developed by Menanteau and exercise it (once).</span>  This ticket had been created automatically Primavera ID: None
Answer: 92057.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: <span style="font-size:13px;color:#000000;font-weight:normal;text-decoration:none;font-family:'Arial';font-style:normal;text-decoration-skip-ink:none;">Reprocess RC2 (monthly?)</span>  This ticket had been created automatically Primavera ID: None
Answer: 92058.0

User story: <span style="font-size:13px;color:#000000;font-weight:normal;text-decoration:none;font-family:'Arial';font-style:normal;text-decoration-skip-ink:none;">Use RC2 processing infrastructure to develop methodology for PDR2 processing (Gen2).  Note this should be for a small subset of the PDR2 data (a few patches to a tract)</span>  This ticket had been created automatically Primavera ID: None
Answer: 129511.0

User story: <span style="font-size:13px;color:#000000;font-weight:normal;text-decoration:none;font-family:'Arial';font-style:normal;text-decoration-skip-ink:none;">Use developed PDR2 processing infrastruture to perform a mid-to-full PDR2 processing (Gen2)</span>  This ticket had been created automatically Primavera ID: None
Answer: 92074.0

User story: "Handoff prior knowledge of deployed instances of LSP and familiarize with current state."
Answer: 101799.0

User story: "Digested monitoring/auditing of resources usage."
Answer: 101799.0

User story: "No description provided!    This ticket had been created automatically   Primavera ID: None         Wiki link for detail maintenance plan -    https://wiki.ncsa.illinois.edu/display/LSST/2019-12-12+Scheduled+Maintenance+Plan"
Answer: 18849.0

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

User story: "Create script that executes a basic benchmark AP run and then combine with benchmarking. This should be suitable to provide quick assessment of AP resource usage as pipeline development proceeds.    This ticket had been created automatically   Primavera ID: None"
Answer: 231747.0

User story: "Produce simple scripting around AP test runs that gather runtime benchmarks (e.g. walltime, memory usage, I/O).    This ticket had been created automatically   Primavera ID: None"
Answer: 231746.0

User story: "This requires two things.      First, moving QE curves measured in the ts8 to the appropriate location for the as installed rafts.    Second, updating the camera geometry files with the as built electronic properties.    This issue will implement this for one raft and document the process.  Then, it should then be repeated for the other rafts as they become available."
Answer: 9822.0

User story: "Cosmic rays are leaking through on HSC's {{ccd=33}}, which is half-masked (due to bad amplifiers). For example, see [{{visit = 177512}} (NB0921)|https://www.dropbox.com/s/4zyxpktz179amoa/visit177512.png].  It has also been reproduced with {{visit = 113974}} and {{113976}}.  "
Answer: 1343.0

User story: "The LOVE XML needs a logLevel event in order for INRIA to create a LOVE Controller."
Answer: 25.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's time to refresh the base conda environment to make use of Astropy 4 and the like. We generally do this once a year.    - Do a test build with a bleeding edge conda env.  - File an RFC for the updates."
Answer: 57590.0

User story: "[~<USER> has kindly transferred the DC2 Run2.2i y1-wfd data for tracts 3828 and 3829, including 217 visits, to {{/project/shared/data/desc_dc2/run2.2i/sim/y1-wfd/}}    I'll copy the data to {{/datasets/DC2}} and make a Butler repo at {{/datasets/DC2/repoRun2.2i}} "
Answer: 33255.0

User story: "With a clean slated CentOS machine get the whatever installations is needed to run the TMA EUI software and the docker containers for running the rotator simulator and building SAL libraries."
Answer: 17518.0

User story: "The _domeSeeing_ event and the DSM UI now have more information available from them. The CSC should use the new info from the UI and populated the event."
Answer: 3849.0

User story: "Since JupyterLab proxies ports out of the container, it should be possible to access bokeh apps running from within a JL container."
Answer: 1276.0

User story: "It was discussed that we would like to use Airflow to help automating the ingest process.  Read & learn about Airflow concepts; try examples.  "
Answer: 208773.0

User story: "Image sizes aren't being correctly created from the Options Form anymore."
Answer: 82.0

User story: "Images selected from the dropdown come out as `---custom`.  Fix that."
Answer: 127.0

User story: "Exploratory work analysing the amp-to-amp offset issue, attempting to determine its origin, constructing analysis plots, and testing various fixes. Our results are shown in a talk attached to this ticket, initially presented to the DRP team in December. See also DM-20303. "
Answer: 6.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 the renaming announced at AAS235, the glossary should be updated to include the new names and acronyms"
Answer: 10083.0

User story: "Pull request from outside the project: https://github.com/lsst/pex_config/pull/47 provided by Simon Conseil of Gemini."
Answer: 235.0

User story: "Reprocess the HSC RC2 dataset with Stack w_2020_01"
Answer: 9026.0

User story: "In the course of finishing DM-20163, I realized that the functionality in {{fgcmcal}} to run on a full repo without specifying any {{--id}} on the command line was only being used by the test code, and not in general use (or by the cookbook).  This removal of functionality and clarification of the cookbook and documentation has been split out from DM-20163 since it is logically distinct.  This update will also make it easier to convert {{fgcmcal}} to a {{PipelineTask}}."
Answer: 10555.0

User story: "The HSC team requests some changes to the output FITS headers:    * {{FLUXMAG0}} missing from the {{calexp}} header  * Please do not erase original FITS header keywords in raw data for {{calexp}} (and {{deepCoadd_calexp}}). For example, FRAME_ID, EXP_ID, DATA-TYP, DET-ID, OBJECT, FILTER01, AZIMUTH, ALTITUDE, PROP-ID, DATE-OBS, MJD, etc.  * In the {{deepCoadd_*Warp}}, DATE-OBS, MJD values are wrong.  * Please do not omit the FITS keyword CD1_1, CD2_2, CD1_2, CD2_1 even when its value = 0.  "
Answer: 11449.0

User story: "When pipe_tasks runs its tests it generates a single temporary output directory containing 200MB of files. These are installed. They serve no useful purpose in the installation.    I propose that we clean up the temp directory when the tests complete successfully and leave it around if the tests fail (much like we do with lsst_ci; see DM-22305)."
Answer: 1155.0

User story: "This ticket tracks work targeted for the next HSC release.    hscPipe 8.0:  * DM-20074: Remove SubaruMakeCoaddTempExpTask after S19A AND problem fixed upstream  * DM-21308: Run HSC RC2 coadds with new fgcmcal tract-based calibrations  * DM-20163: Investigate using WCS Jacobian BoundedField in fgcmcal fit  * DM-22822: CRs leaking through on partially-masked CCDs  * DM-22797: Various FITS header fixes  * DM-23062: Preserve input headers  * DM-22958: CModel has unflagged flux=0 fluxSigma=NAN for 1% of sources  * DM-23097: Warp processing failure around field edges  * DM-22955: Add spatially varying HSC HB filters to obs_subaru  * DM-23179: revised color terms for HSC  * DM-23065: Test fgcmcal on NB0387 HSC data   * DM-23083: Update large masks for BF convolution issues    hscPipe 8.1:  * DM-23331: Add default fgcmcal configuration files for HSC processing  * Once FGCM is implemented (DM-23065), disable photometry fits in jointcal  * DM-20841: Investigate reports of incorrect meas_mosaic WCSs after rotation by 90deg  * DM-23352: Add jointcal, skyCorr to forcedPhotCcd"
Answer: 70693.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> has noted that obs_base tests depend on a private butler config test file in DAF_BUTLER_DIR/tests/config.  Those configs are not meant to be used outside of daf_butler since they contain unexpected formatters and storage classes designed specifically for internal daf_butler tests.  obs_base should not be relying on those configurations.  It should be sufficient for obs_base to use a default configuration made by {{Butler.makeRepo}}.    I'm not entirely sure whether I should fix this or whether this should be handled by science pipelines."
Answer: 95236.0

User story: "WARNING: W21: None:2:0: W21: vo.table is designed for VOTable version 1.1, 1.2 and 1.3, but this file is 1.4 [astropy.io.votable.tree] WARNING:astropy:W21: None:2:0: W21: vo.table is designed for VOTable version 1.1, 1.2 and 1.3, but this file is 1.4 WARNING: W41: None:2:0: W41: An XML namespace is specified, but is incorrect. Expected 'http://www.ivoa.net/xml/VOTable/v1.4', got 'http://www.ivoa.net/xml/VOTable/v1.3' [astropy.io.votable.tree] WARNING:astropy:W41: None:2:0: W41: An XML namespace is specified, but is incorrect. Expected 'http://www.ivoa.net/xml/VOTable/v1.4', got '[http://www.ivoa.net/xml/VOTable/v1.3']         This happened after running the notebook in LSP int after patching qserv to point to the one running in kubernetes.  I'm not sure where this has come from."
Answer: 213264.0

User story: "I need to meet with Tiago and discuss exactly the process for building and packagin the AT CSCs.   * What is pulled from Nexus   * Build steps   * Unit testing   * Packaging details (format)"
Answer: 21234.0

User story: "Various Jenkins jobs were pushing to the temporary Nexus3 repo.  Now that the production server, [https://repo-nexus.lsst.org/nexus/], has been created, update the jobs to use this server.    This task covers the work to update the Jobs and run them to ensure they work."
Answer: 5771.0

User story: "The {{warnings.warn}} call in pex_config that warns about a deprecated config item, reports a line number inside pex_config when it should be reporting a line number in user code. Add stacklevel=2 to the call."
Answer: 1228.0

User story: "The test_squash.py is failing for me locally because I have responses installed on my stack but this does not play well with the old EUPS requests package. If I unsetup requests and let the code use my conda requests the tests pass without a problem.    I think [~<USER> has been worrying about our old {{requests}} package for a while now. Since {{requests}} is formally listed in the conda baseline and since no other package in lsst_distrib uses requests,  I think the easiest fix is to remove requests from the table file for verify."
Answer: 1243.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 when qserv rolled out running on kubernetes, this changed the hostname I think from qserv-master01 to a name of a svc running in the cluster.  So now we need to have the chart have the ability to take an arbitrary hostname for qserv's czar on 4040 to connect to, and have that be overridden in the values.yaml of the helm chart."
Answer: 294.0

User story: "Add more information to Dome Seeing Monitor _domeSeeing_ event."
Answer: 353.0

User story: "Take the onramp Simulink course on MathWork website to have the initial understanding of the use of Simulink. This should be helpful to review the model by Moog for the control algorithm. "
Answer: 11315.0

User story: "Fix the M2 control code to be able to feedback the SAL command. It looks like the M2 control code will reject all received SAL command. Need to figure out the reason. This is the phase 1."
Answer: 11320.0

User story: "Organize and clean the code of hexapod GUI. The code delivered by Moog contains everything (middleware, hexapod and rotator GUIs, simulink model, and hexapod and rotator wrappers in PXI) and hard to update the code. This task will separate the hexapod GUI code to a single repository and organize the VIs in the project. This will help for the future's update."
Answer: 24579.0

User story: In a few CCDs in one of the three HiTS fields, despite an otherwise successful rerun with new templates at a resolution of 0.26" (DM-21330 and DM-22729), there are a bunch of false positive sources that look a lot like the problems we used to have with a poorly modeled background.    When Ian and I looked at the template nImages, all regions with data have 20 or 21 constituent visits. This suggests the good seeing selector isn't working as intended (as there are only 21 visits to choose from!). In addition, the variance plane has very low values in the regions with oodles of sources, roughly a factor of 3 lower than surrounding areas. It's unclear if these issues are related. We did a little digging and found no apparently significant codebase or default config changes in pipe_tasks or ip_diffim.    This ticket is to figure out what happened and make a plan to fix it, which may or may not include reworking the good seeing selector so it is more readily parallelized.
Answer: 54638.0

User story: "Organize and clean the code of rotator GUI. The code delivered by Moog contains everything (middleware, hexapod and rotator GUIs, simulink model, and hexapod and rotator wrappers in PXI) and hard to update the code. This task will separate the rotator GUI code to a single repository and organize the VIs in the project. This will help for the future's update."
Answer: 5814.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: "DiaObjects loaded and used in association are no longer trimmed precisely to the CCD boundaries. This means that when DiaForcedSourceTask is run, forced sources are created for DiaObjects that are outside of the observed CCD. This ticket will add a check within the DiaForcedSource measurement step that only appends DiaForcedSources that are in within the image rather than storing extraneous forced sources in the Apdb that have all nan values for their fluxes."
Answer: 9952.0

User story: "{{isrTask}}'s {{runQuantum()}} method should have been updated in DM-22659 but I didn't know how to do it, and [~<USER> kindly said he'd do it if I ticketed and {{TODO:}}ed it."
Answer: 45829.0

User story: "Take the current logging setup for int and stable, and have argocd control it."
Answer: 8792.0

User story: "Review the document of Simulink to have the understanding of model for the debug of rotator track issue."
Answer: 8749.0

User story: "In case of a test plan or test cycle names too long, the summary table may extend beyond the right margin of the page.    This needs to be fixed in the template."
Answer: 409246.0

User story: "The refactoring of the Gen2 conversion tools on DM-17023 broke the scripts we had previously put together for creating a Gen3 data repository containing the HSC RC2 dataset. At the time this wasn't considered worth fixing, because we still hadn't addressed the issues that made RC2 ingest and preflight painfully slow.  That has been partially done (i.e. ingest should now be faster) on DM-21768, so it's time to get that working again.    This ticket is for getting the new Gen2 conversion tools working on RC2.  After that's done, we may want to also make some (hopefully minor) improvements to the yaml import/export mechanism to provide a faster way of re-creating the Gen3 repo from scratch, given that a lot of the slowness in Gen2 conversion is due to limitations in how fast we can discover related datasets in the Gen2 repo."
Answer: 26706.0

User story: "pipe_tasks' {{tests/test_read_CuratedCalibs.py}} contains a copy of {{BaseMapper}} from obs_base's {{tests/test_cameraMapper.py}}. Not only is that ugly, it's also fragile (see DM-22769).    Rearrange things so that pipe_tasks can import {{BaseMapper}} from obs_base directly."
Answer: 1662.0

User story: "Just label the namespaces, and create a separate application to hold user namespaces."
Answer: 18691.0

User story: "Remove instructions to deploy the EFD using Terraform and add instructions to install Argo CD and bootstrap a new EFD deployment using Argo CD."
Answer: 1083.0

User story: "Implement a notebook that demonstrates how data can be queried from within a notebook and analyzed using pandas.  This will not use helpers proposed in DM-21740."
Answer: 12.0

User story: "Not actually prepulling"
Answer: 1476.0

User story: "Need to restrict the command to be only available on the specific state. For example, some commands are only allowed in Enabled state."
Answer: 23358.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 MTAOS does not support the logging file now. I realized this should be helpful to debug in the test with multiple components."
Answer: 22143.0

User story: "Old deployment tools and kubernetes templates can go, to be replaced with a pointer to Helm charts and lsp-deploy values."
Answer: 3167.0

User story: "[~<USER> has requested that ts-ci.lsst.codes be decommissioned in January of 2020."
Answer: 34662.0

User story: "Now that the new Gen3 subtask is created, remove the previously directly used ap_association subtasks from ap_pipe and replace with a DiaPipelineTask initialized as a subtask."
Answer: 18831.0

User story: "Incorporate DMLT feedback into LDM-643 for OPS Rehearsal #2"
Answer: 1.0

User story: I would like propose we minimize the use of environment variables on the python scripts we use to build the libraries in SAL, namely; {{make_idl_files.py}} and {{make_salpy_lib.py}}. In the xml [~<USER> is adding a {{get_sal_interfaces_dir}} method that can replace the use of {{TS_XML_DIR}} for discovery of the sal interfaces location.          This will make the process of packaging xml and sal into conda packages much more reliable. My proposal is to add a backward capable change now and deprecate the use the {{TS_XML_DIR}} on future SAL versions.          This is a code snipped that would accomplish the aforementioned feature:      {code:java}  try:      from lsst.ts import xml  except ImportError:      xml = None    def get_env_dir(name, err_msg):      path = os.environ.get(name) if xml is None else xml.get_sal_interfaces_dir()      if path is None:          raise RuntimeError(err_msg)      path = pathlib.Path(path)      if not path.is_dir():          raise RuntimeError(f"{path} is not a directory")      print(f"${name} = {path}")      return path  {code}        
Answer: 80839.0

User story: "After the last run with the AT there where some bug fixes and configuration changes needed. Most of the work was done on DM-22531. This task is to clean up all the components that where deployed with non-tagged repositories and also to switch up the kafka producers to publish data to the new EFD deployment. "
Answer: 68628.0

User story: This is the ~monthly ap_pipe rerun of the HiTS 2015 dataset (all 3 fields). For the first time, I will use templates with the DECam instrumental pixel scale (0.26"/pixel). The rerun will be in {{/project/<USER>hits2015/rerun/cw_2019_12}} and an accompanying "quick look" analysis notebook will be made.
Answer: 58995.0

User story: "Some DiaCalculation plugins throw numpy warnings while calculating results that are unnecessary. But such clauses in a context manager to catch and ignore these warnings."
Answer: 28962.0

User story: "Add the _settingsApplied_ event to the SALGenerics.xml file."
Answer: 28612.0

User story: Fields for "statusCode" and "description" need to be added to each of the events for ATArchiver and CCArchiver XML
Answer: 1160.0