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: Please checkout this script {{01_sfm_wide.sh}} at GitHub [https://github.com/lsst-dm/s20-hsc-pdr2-reprocessing/blob/master/01_sfm/01_sfm_wide.sh]    01_sfm_wide.sh has 724 commands. Please run them, keep track of them, check if any fails, and if any fails due to *infrastructure* reasons please rerun the failed ones.    The environment to be used is at [https://github.com/lsst-dm/s20-hsc-pdr2-reprocessing/blob/master/01_sfm/01_env.sh]    You can do {{source 01_env.sh}} after a fresh login (and nothing else)    Some CCDs will likely fail because the current pipeline/config/data just can't process them; those reproducible failures are okay and expected. If you see error messages and not sure whether they are pipeline errors or infrastructure errors please ask.    Each command submits one slurm job. Each job runs on 1 node and each takes around ~3-4 hours.    Please keep a record of the slurm IDs from your job submissions. In the end of this ticket we want a list of the slurm job IDs of all *successful* jobs. All of them should be "COMPLETED" according to sacct. You can check using {{sacct -j SLURM_ID}} on {{lsst-dev01}}.    Each job will have two log files. Please copy the logs of the successful jobs to /datasets/hsc/repo/rerun/DM-23243/logs/sfm/wide   There should be 724 * 2 = 1448 of log files in total.    Ultimately the logs and slurm job IDs of the (infrastructure-) failed jobs can be discarded (or better just kept as your internal records) once they are re-submitted and data are overwritten.    In the singleFrameDriver.py commands, the job names (as in the --job argument) are "Ax1wi" followed by a number. You can prepend or append any string to this name if that makes your bookkeeping easier. I don't know how well the NCSA infrastructure today can handle 724 jobs in the queue at a time; you might want to submit them in batches –  these details of submission strategies are up to you. Depending on how stable the slurm cluster is you may need some efforts in bookkeeping.
Answer: 10213.0

User story: "https://keeper.lsst.codes  https://cd.roundtable.lsst.codes  https://monitoring.roundtable.lsst.codes/login  https://www.lsst.io"
Answer: 184.0

User story: "When DM-23292 is merged we need to add the grating definitions to obs_lsst just as we define LATISS filters."
Answer: 376308.0

User story: "Generate document to describe the communications protocol between low level and high level dome control software components, as mentioned in DM-23059."
Answer: 16218.0

User story: "This task will check the SAL published event and telemetry in M2 control system. From the previous tests, I only know the telemetry data is not zero. However, I am not sure the values are reasonable or not. I also noticed the published data of summary state event is always 0. Therefore, this task will try to make sure the published data is reasonable."
Answer: 16124.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: "Harris provided the function of script used in M2 control system to assign the actuator steps or forces. This task will evaluate the use of script and test it on the M2 simulator."
Answer: 11615.0

User story: "Just four small commits, but filing so I'm not merging straight to master."
Answer: 37.0

User story: "SSL Labs is now reporting a B grade. Update the configuration to re-attain an A grade."
Answer: 7004.0

User story: "{{butler.get('defects', visit=2020012700579))}}    gives {{OperationalError: no such column: calibDate}}    when defects are ingested."
Answer: 5010.0

User story: When in Tucson, the disperser was written with the FILTER2 key (note the 2), and this was concatenated (using a "+") with FILTER on ingest, so that we had a compound filter.    Now that we're on-sky, we're writing that as GRATING (which is good) but {{exp.getFilter()}} seems to only return the physical filter which is only the first part (though we know the registry is out of date), but moreover, doing       {noformat}  translate_header.py -p lsst.obs.lsst.translators /project/shared/auxTel/_parent/raw/2020-01-28/2020012800335-det000.fits -d{noformat}  shows that the filter is just {{blank_bk7_wg05}} rather than {{blank_bk7_wg05+ronchi90lpmm}} as I'd have expected.          
Answer: 7167.0

User story: "Initially pull in changes from upstream AuxTel branch, then make changes with Jérémy."
Answer: 1174.0

User story: "Making a ticket so it lands on a ticket and merges as normal for DM."
Answer: 3.0

User story: "{code}  $ imageDifference.py DATA/ --rerun ci_hsc:gen2cmp_2020-01-31 -c doSelectSources=False --id visit=903334 ccd=22 filter=HSC-R |& tee -a imgDiff_gen2_hsc_2020-01-31.log       /ssd/<USER>devel/active/DM-22541_ip_diffim/python/lsst/ip/diffim/imagePsfMatch.py:785: FutureWarning: Call to deprecated method getImageF(). (Zero-argument overload is deprecated; use one that takes an ``interpStyle`` instead. To be removed after 20.0.0.)                                                       bkgd = self.background.fitBackground(mi).getImageF()                                                                                                      /ssd/<USER>devel/active/DM-22541_pipe_tasks_gen3_run/python/lsst/pipe/tasks/imageDifference.py:843: FutureWarning: Call to deprecated method makeSourceCatalog. (Replaced by SourceDetectionTask.run(). Will be removed after v20.)                                                                                   doSmooth=not self.config.doPreConvolve     {code}"
Answer: 54864.0

User story: "[https://dmtn-112.lsst.io/]"
Answer: 18838.0

User story: "Change DNS to point all clients at the new Vault deployment, and then after a reasonable burn-in period, garbage-collect the resources for the old Vault configuration (Kubernetes cluster, KMS key, storage, GCP project)."
Answer: 18871.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: "Copy the Vault database and KMS key from the existing Vault project to the new one and then test that the new Vault returns the same keys by changing the address to which some services point (and possibly other testing as indicated)."
Answer: 7369.0

User story: "Deploy Vault in Roundtable with Argo CD and the official Helm chart. See DM-23233 for previous investigation and desired parameters."
Answer: 6086.0

User story: "Task to cover time taking the LinkedIn Learning Jenkins course(s)."
Answer: 4184.0

User story: "Gregory reported that at some point lab containers stopped pointing at lsst-demo's firefly and started pointing to the in cluster one.  We didn't change anything to do this, so it's a bug."
Answer: 5969.0

User story: "the arguments to from_geodetic are reversed:   {{location = EarthLocation.from_geodetic(lat*u.deg, lon*u.deg, height*u.m)}}    and {{RA/DEC/END}} should use {{DATE_END}} and the moment it uses {{DATA_BEG}} instead."
Answer: 97.0

User story: "The HeaderService was designed with the condition that a {{startIntegration}} event from Camera would always be followed by and {{endOfTelemetry}} event. However, this condition has changed and the HeaderService now needs to keep track of the metadata for more than once image at time."
Answer: 18813.0

User story: "Currently there are no tests for the efd helper client.  Add these so they are run by travis before release."
Answer: 5890.0

User story: "Create a presentation for the LSST System Science Team (SST) on deblending in the stack. It has been requested that this presentation includes a general introduction to blending in the science pipelines as well as an update on the latest developments."
Answer: 5869.0

User story: "Documentation is now available here:    http://qserv.lsst.io    https://qserv-operator.lsst.io"
Answer: 145670.0

User story: "installTransmissionCurves /datasets/hsc/repo using w_2020_04  "
Answer: 1333.0

User story: "Profile and optimize the runtime of jointcal         Note: Original scope of this ticket was too broad.  Updated to capture just the profiling work and proposed runtimes improvements. "
Answer: 354147.0

User story: "Create a branch of the DPDD that incorporates DRP leaderships current best guesses at what we will actually do.  This is primarily the removal of multifit and galaxy Monte Carlo sampling, along with what we expect to replace them; it will not attempt to address more fine-grained issues with particular columns, as I believe others have already made progress addressing those elsewhere."
Answer: 239371.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 MQTT topic names are all in Spanish which may be confusing for non-Spanish speaking people. It was decided to keep the Spanish topic names since mechanics generally are Chilean so it will be easier for them to identify the hardware components when they are referred to in Spanish. In addition English Descriptions will be added for those who don't understand Spanish well enough. The Descriptions will be direct translations of the Spanish words into English without an attempt to form proper sentences."
Answer: 97719.0

User story: "Coordinate & execute the S20 HSC-PDR2 reprocessing run for the Algorithms Workshop"
Answer: 150970.0

User story: "In order to spawn workflows, we need work to the LSST Manager objects and to the RBAC setups for our clusters."
Answer: 25823.0

User story: "S20 HSC PDR2 reprocessing. The main objective is to have the needed data for the Rubin Observatory Algorithms Workshop.       https://confluence.lsstcorp.org/display/DM/S20+HSC+PDR2+Reprocessing    This ticket contains child tickets for related tasks. "
Answer: 209166.0

User story: "Update the ATHeaderService to have a dynamically set timeout that is adjusted by the requested exposure time. For example timeout=requested_exptime+N (in seconds)."
Answer: 219.0

User story: "When using the develop-env:salobj4_b55_5 image on Jenkins in a Jenkinsfile. LSST_DDS_IP returns 0 which breaks the build, however running the image locally does not produce the same result.   Please see the following link that shows the console output where this happened. [https://tssw-ci.lsst.org/job/LSST_Telescope-and-Site/job/ts_salobjATHexapod/view/change-requests/job/PR-8/lastFailedBuild/console]"
Answer: 10671.0

User story: "Add per-row median overscan subtraction as an isr config option. Use special casing for handing ints."
Answer: 21451.0

User story: "build xml files for MTAlignmeent commands, events, telemetry"
Answer: 47345.0

User story: "New version of header service needs a container to run on the summit asap."
Answer: 3.0

User story: "Understand current Vault and Kubernetes integration and write up options."
Answer: 4172.0

User story: "In DM-23171 I changed how visit is calculated such that it respects the GROUPID header.  This has led to some confusion because we have been using gen2 butlers as if visit_id and exposure ID were the same thing, and to make things worse exposure_id is not available and obsid is not declared to be a unique header so can't be used on its own to retrieve data.    In this ticket I will:    * Add expId as the exposure_id  * Declare that obsid and not visit is the unique constraint.  * change file templates that use visit to instead use obsid.    "
Answer: 2829.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 flag(s) for fitting two-component models in MultiProFitConfig so they can be configured in MultiProFitTask for use in e.g. DM-23169."
Answer: 132467.0

User story: "Update OODS 1.0.0-rc2 version to use d_2020_01_29 of the stack"
Answer: 2364.0

User story: "Include <USER>as author in lsst-texmf author database to allow co-authorship for LSST / Vera C. Rubin Observatory construction papers."
Answer: 1153.0

User story: "Now that the Object table schema of the output parquet does not depend on what filters the input data include (DM-23074), we can do checks of the schema in ci_hsc and the schema should be the same in the HSC-RC2 outputs.     My plan in this ticket is to add a cross-check of the schema (column names only) between the Object parquet generated in ci_hsc and the yaml ddl in cat.      It will be nice that the DAX team can use the yaml file in cat as the expected schema. So far nothing checks the schema of the pipeline outputs and this ticket will start adding that.  Science Pipelines can still change the schema from time to time, but that's okay, because a failed ci_hsc should prompt the developers to update the cat yaml file.     I plan to leave the data type checking for later (after the end-of-Feb DMLT).  "
Answer: 24410.0

User story: "Currently translate_header has a dumphdr option to list the file header. This is the actual header and there is no option to provide a fixed up header after astro_metadata_translator has patched things up.    Add a new option to allow the fixed header to be seen. It's possible that we could do this with the mode switch and make mode=fixed dump the fixed header and dumphdr could alias to mode=header."
Answer: 4510.0

User story: "[~<USER> tells me that they started using ENGTEST for real yesterday so I should stop converting OBJECT to ENGTEST from that date.    Also consider fixing the RA/DEC scaling before it is fixed tonight."
Answer: 4128.0

User story: "In DM-18126 we added nextVisit to ScriptQueue but [~<USER> pointed out that the {{+}} separator for the supplemental group numbers was the same separator that ISO8601 uses for time zones so this might be confusing.   Please replace with a {{#}} to indicate the supplemental number."
Answer: 79.0

User story: Create draft from Jira for the:    Vera C. Rubin Network Verification Document         using subsystem "DM" and component "Network".
Answer: 41734.0

User story: "Cassandra development branch ({{u/andy-slac/cassandra}}) for dax_ppdb and l1dbproto needs an update after dax_ppdb was renamed to dax_apdb. "
Answer: 1069.0

User story: "A butler pointing at a registry fails to see newly ingested data.  This is a major nuisance when observing as you are always interested in the data that you have just taken, and thus have to restart the butler after every exposure."
Answer: 867.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "After initial orbit determination & orbit determination, orbit covariances have to be sampled and propagated to understand sky plane uncertainties of solar system objects. Monte Carlo sampling is demonstrated.  "
Answer: 197.0

User story: "After initial orbit determination & orbit determination, orbit covariances have to be sampled and propagated to understand sky plane uncertainties of solar system objects. Sigma point sampling is demonstrated."
Answer: 197.0

User story: "Now that DM-23171 add exposure_group to the translator, we can add it to the exposure metadata."
Answer: 83450.0

User story: "The current thinking of the cat package is to house the declarative yaml schemas in the [felis|https://github.com/lsst-dm/felis] format.  Those felis files are (or will be) used to instantiate TAP_SCHEMA tables, Qserv tables, etc.     Currently the cat repo has some old files and sql scripts that are no longer in use. This ticket is to clean them up.  This will remove unnecessary dependencies, and facilitate including the cat package in different builds (Sci Pi or Qserv) for validation. "
Answer: 2986.0

User story: "Describe the detailed content of the interface between low level and high level dome control software components, as mentioned in DM-23059"
Answer: 9883.0

User story: "In order to simplify the listing of headers from multiple files, add a tabular option to translate_header.    I think the default will be that for one file we use the verbose listing and for multiple files we use the tabular form."
Answer: 1255.0

User story: "Centos 8 seems stable; rebase our LSP/nublado components on it"
Answer: 11432.0

User story: "The ingress controller, SSL certificate and DNS configuration for the EFD deployment on the k8s cluster at the NCSA test stand will be managed by NCSA.     We need to create another parent app in Argo CD for the NCSA test stand deployment to accommodate the differences in that environment mainly the fact that we don't need to deploy {{nginx-ingress}} as part of the EFD deployment."
Answer: 3585.0

User story: "We need a user with a viewer role for displaying dashboards at the Summit control room. That was requested by <USER>and discussed in the `#com-efd` Slack channel.    Since we are using GitHub OAuth we need that user to be created on GitHub and also an associated e-mail account. "
Answer: 2.0

User story: "The {{local-path-provisioner}} implements a {{local-path}} storage class for provisioning persistent volumes of {{hostPath}} type in Kubernetes. That worked fine on a single node running k3s.     In this ticket, we'll run tests to make sure it works as expected in a (multi-node) k8s cluster."
Answer: 10436.0

User story: "Add storage of local photometric and astromentric calibration to multiBand.py. This is likely to go in as a plugin for MeasureMergedCoaddSourcesTask."
Answer: 23319.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 changing of {{...Nl}} to {{...nonLinearity}} is an API change which breaks things, including but not limited to {{makeBrighterFatterKernel}} due to a lack of tests (_i.e._ it's not really [~<USER>'s fault.    Also, the API change where that method doesn't {{return dataset}} and now just does {{return}} is breaking too (also due to lack of tests).    It is deliberately ambiguous whether this ticket is for fixing the breakages, or doing that and adding tests."
Answer: 61795.0

User story: "The (intermediate) SAL XML file for the HVAQ Telemetry has been created and will be updated as soon as we receive the missing information from DatControl. This story is for creating the Commands XML file."
Answer: 11962.0

User story: "The ADAM algorithm in scarlet requires accurate weights maps (inverse variance) for optimal convergence. Currently {{meas_extensions_scarlet}} used the inverse variance from each {{MultibandExposure}} as the weight for a blend, then masked the image with the footprint and any masked pixels. But the stack already interpolates pixels for cosmic rays, saturated pixels, etc and updates the variance accordingly, so masking out those pixels in the relevant bands was making the task more difficult on the deblender than necessary. This ticket is to implement the proper weight maps for scarlet."
Answer: 9611.0

User story: "After we get UWS stuff in there, we can get the helm chart working with the TAP + postgres.  This means we won't need mock qserv or the query monkey, but there may also be other changes.    Either way we'll probably need to add it to argo, or at least be able to."
Answer: 28865.0

User story: "Add in the uws parts and the async stuff, just like how we did for the other TAP."
Answer: 120.0

User story: "The _select_top_n_ function in the EFD client library must support indexed components just as _select_time_series_ does."
Answer: 4122.0

User story: "CatchupArchiver processes the images that were dropped by the Archiver/Prompt Processing during telescope operation. This ticket captures the works starting from attaining requirements, exploring technologies, drafting the design to implementing the final catchupArchiver Commandable SAL Component(CSC). "
Answer: 371685.0

User story: "Currently there is no test to verify that the IDL Type is present, nor if it contains a valid value if it is."
Answer: 241.0

User story: "DM-23162 / RFC-650 updated the Flake8 exceptions list (W504 -> W503). This ticket propagates that change into the {{stack_package}} template in lsst/templates."
Answer: 13.0

User story: "Problems were reported on Slack #stack-club, [here|https://lsstc.slack.com/archives/C9YRAS4HM/p1579842619007000] and [here|https://lsstc.slack.com/archives/C9YRAS4HM/p1571424285032300].    While we've got unit tests for Registry helper code operating on a read-only database, we don't have them for Butler, and it's possible we just need to pass a flag down to the helper code telling it to make a read-only connection."
Answer: 6160.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: "Since the OCS subsystem is no longer in existence, the exemptions granted in the XML unit tests should be removed."
Answer: 1193.0

User story: When deploying some of the EFD Helm charts to the NCSA test stand k8s cluster I've got an {{Deployment.extensions "" not found}} error because of    {noformat}  apiVersion: extensions/v1beta1  kind: Deployment  {noformat}    The v1.16 k8s (version running at NCSA) stoped serving deprecated API versions like {{extensions/v1beta1}}  in favor of newer and more stable API versions:    https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/    For {{Deployment}} migrate to use the apps/v1 API, available since v1.9.
Answer: 6971.0

User story: "VCD generation code needs to be updated after Jira Test Cases updated workflow, and the summary table needs to be expanded."
Answer: 198800.0

User story: To support the GROUPID header for grouping related exposures in LSSTCam data we need to add a new translation to astro_metadata_translator.     The proposal is to call this "exposure_group" and for most instruments to default it to be a string form of the "exposure_id". For LSSTCam and LATISS it will be the value of the GROUPID header.
Answer: 5949.0

User story: "Fit some DC2 patches with MultiProFit and investigate the best way to analyze the results (match & compare to inputs)."
Answer: 106554.0

User story: "Please correct the spelling on the test name."
Answer: 167357.0

User story: "The attribute in the title is missing a description. This can be seen by removing the exemptions on DM-20971 in all the tests and running pytest. Once this issue is fixed, we can remove the exemption."
Answer: 42.0

User story: "The error code and message are hard-coded in a string in the M2 control system. This part should be moved into the LabVIEW native error file for the extension and maintenance. In addition, there is no scroll bar for the list of error in the M2 control system. This needs to be fixed as well."
Answer: 15771.0

User story: When a description tag is empty (no blank spaces): <Description></Description>, the test is not handling the fact the description.text is None in this case. The test throws this exception:       {code:java}  for description in root.findall(f"./{saltype}/item/Description"):  > assert description.text.replace(" ", "") is not None  E AttributeError: 'NoneType' object has no attribute 'replace'{code}     Also, the test does not handle the case where the description might be blank spaces. In this case the test passes, but there's no actual content in the description.    I found this when I was testing to see if we could lift DM-20971 from all the tests. It showed that the Hexapod XML still had one missing description, but the test failed it an unexpected manner.
Answer: 7249.0

User story: "Following the adoption of RFC-650, change the developer guide to put binary operators at start of the next line when having to break a line."
Answer: 291.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "The XML topic and attribute names should only contain letters, underscores and maybe numbers.  Create a test to validate this is true."
Answer: 2652.0

User story: "The systemd service scripts for dm_ATArchiver which are installed as part of the RPM build are out of date;  this ticket will update the environment."
Answer: 21494.0

User story: "Start the outline of the construction paper DM outline .."
Answer: 16813.0

User story: "On Friday the 17th, The Camera Hexapod faulted into a so-far unrecoverable state. This task outlines the effort in helping to debug this problem."
Answer: 12878.0

User story: "Evaluate changes  required to update M1M3 controller and EUI for use with the  SAL 4.x releases"
Answer: 17496.0

User story: "LATISS data are arriving from the mountain but there are problems with headers that are causing ingest failures. Specifically the OBJECT header was forgotten about and is not present at all, and the airmass headers are undefined even when the RA/Dec headers are not.    Issue warnings and work around the problems."
Answer: 540.0

User story: "Write section on configuring your docstrings for tstn-005."
Answer: 17329.0

User story: "- Update the milestones repository with data extracted from PMCS (/)   - Update milestone dates loaded into Jira (/)   - Update skeleton December 2019 monthly report (/)"
Answer: 39982.0

User story: "In DM-17954, a bunch of updates were made to the December 2019 baseline to reflect changes to DM milestones.    Check over these and make sure they look right (in particular, check when Science Pipelines Fall 2019 release happens, since that looked suspicious)."
Answer: 352607.0

User story: "Update the README file in the cpb package to link to the online documentation."
Answer: 2443.0

User story: "Make a post on community.lsst.org in the DM Notifications category, describing the ip_diffim functionality which we do not plan to make available in Gen3 in the foreseeable future. Ask whether any members of the community have a pressing need for those features to be available in Gen3."
Answer: 30031.0

User story: "As of the currently available limited ci_hsc gen3 repo we have a very limited number of template images, however a production environment gen3 collection may contain many templates, covering large sky areas.         As a follow up of the initial gen3 support DM-22541 in {{ImageDifferenceTask}}, check whether the number of template inputs can potentially be huge in a production environment or not because of gen3 automatic filtering on patch spatial information and science image coordinate matching.         If all available template images are potentially loaded as task input, add support for deferred loading of the template coadd images to avoid unnecessary I/O and save resources. Load only at a later stage, if input belongs to a relevant skymap patch. If the coadd images loaded as inputs are pre-filtered at the middleware level then we perhaps do not need to implement any cautious approach in {{ImageDifferenceTask}}.     "
Answer: 43112.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: "Update the OODS to use _mapper named as lsst.obs.lsst.latiss.LatissMapper.  It's currently specified as lsst.obs.lsst.auxTel.AuxTelMapper, which gets remapped to LatissMapper."
Answer: 48649.0

User story: "This ticket encompasses the time spent in Dec 2019 and Jan 2020 on a hiring committee for LSST DM AP."
Answer: 54891.0

User story: "The recipe requires some improvements."
Answer: 4217.0

User story: "Provide an API, callable from JupyterLab notebooks, or the Hub, or as an external endpoint, to allow spawning of Argo Workflows based on Nublado Lab Images (plus Nublado environment)."
Answer: 12768.0

User story: "Implement RFC-657 by updating the schema in ts_xml to allow the Author tag to be omitted from topics."
Answer: 402.0

User story: from [~<USER> on Slack  {quote}  The comment just above this method says "Get an unordered map", but it returns a binary-tree map instead:  [https://github.com/lsst/afw/blob/6637c4fb6fa5813268496d76dcd9e97cbd417bcc/include/lsst/afw/cameraGeom/DetectorCollection.h#L62]  {quote}    We should just fix the docs; we probably have code that now depends on these being ordered, and it's not unreasonable for them to be ordered.
Answer: 50.0

User story: "Testing the Camera Hexapod for the week of the 13th to the 17th. Completed on the 17th. Also helped Roberto and Mario finish hardware tests."
Answer: 57.0

User story: "In DM-23024 I changed FileDataset to support a list of DatasetRef and updated obs_base ingest to work with that.  What I did not do is update RawFileData to allow it to be populated with something that can be converted to a FileDataset with multiple DatasetRef.    The plan in this ticket is to create a new class that contains the dataId, obsInfo, and region and change RawFileData to accept a list of those."
Answer: 2108.0

User story: "Read documents LTS-307, LTS-159, LTS-103 as if I had a test on it. "
Answer: 56315.0

User story: "The first effort in working towards the replacement of the tma_management software. Unidentified scope. "
Answer: 31785.0

User story: "Stayed on the summit Mon - Fri    Covered misc tasks related to the TMA (a few meetings, coordinating action items, reading an LSE document). Supported Eric in operating the CCW. Mainly clearing of an E stop that prevented work on the Rotator. "
Answer: 101.0

User story: "Reprocess the HSC RC2 dataset with Stack w_2020_03"
Answer: 44400.0

User story: "Write a minimal MTMount CSC to support the camera cable wrap (CCW). Extra credit for supporting the existing MTMount XML API.    Also think about how we can operate in partial emulation mode: having the CSC talk to the real CCW controller and emulate the remaining hardware components (elevation, azimuth, locking pins, counterweights...).    I will estimate story points after I implement DM-23118 and DM-23119, both of which are necessary precursors."
Answer: 84740.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 MTMount CSC handles communication from the EUI as well as SAL/DDS. Write the component that manages the two channels (EUI and SAL) and forwards data to the client that talks to the low-level TMA controller.    This also requires writing a server that the EUI can connect to."
Answer: 34424.0

User story: "Write an initial emulator for Tekniker's low-level TMA controller. Requirements:  * TCP/IP must be correct  * CCW commands should be properly emulated  * A client for the CSC side that talks to the emulator (needed to unit test the emulator, as well as by the eventual CSC).  * Other commands can be emulated on a best-effort basis. It'd be ideal if the EUI could usefully talk to this (via the CSC), even if the displayed values were not reasonable.    Much of the work involved is reading the C++ code and understanding what Tekniker has done."
Answer: 94658.0

User story: "TCP/IP connection between M2 control and cell systems is easy to break."
Answer: 8301.0

User story: "At the moment the ATHeaderService is reading the vendor configuration from the yaml configuration file. However, the correct approach would be to read it from events from {{ATCamera.wrebSettingsApplied}}"
Answer: 396986.0

User story: Historically, {{afwMath.BackgroundControl}}'s constructor accepted the parameter {{style}}, to set the the interpolation style, and {{undersampleStyle}}, to set the behaviour when there are two few grid points for interpolation.    This, to interpolate with an Akima spline, and to reduce the interpolation order when there aren't enough grid points, you'd do something like:    {code}  bctrl = BackgroundControl("AKIMA_SPLINE", ..., undersampleStyle="REDUCE_INTERP_ORDER")  background = makeBackground(image, bctrl)  background.getImageF()  {code}    On DM-17566, the {{style}} argument (but *not* the {{undersampleStyle}} argument) was deprecated, and, instead, the user is encouraged to instead call:    {code}  background.getImageF(style, undersampleStyle="THROW_EXCEPTION")  {code}    The confusion arises when the user does something like this:    {code}  bctrl = BackgroundControl(undersampleStyle="REDUCE_INTERP_ORDER", ...)  background = makeBackground(image, bctrl)  background.getImageF("AKIMA_SPLINE")  {code}    I contend that the reasonable user would be expecting this to use a {{REDUCE_INTERP_ORDER}} undersample style, as set in the {{BackgroundControl}}, but instead the {{getImageF}} default of {{THROW_EXCEPTION}} is used.    This seems wrong to me.
Answer: 139462.0

User story: "RFC-632 renamed {{getAmpInfoCatalog}} to {{getAmplifiers}} but the plotting code in cameraGeom.utils that used it didn't notice.  Please fix this.  "
Answer: 23.0

User story: "This ticket is to deploy documentation for lsst-efd-client onto LSST the Docs. Domain will be {{efd-client.lsst.io}}."
Answer: 5932.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 metadata output in gen3 always write to the same filename, which prevents multiple calls to the same task in a pipeline.  If this respected the task label in the pipeline, or if the output name (like the lsst.pipe.base.connectionTypes.Output.name field) was settable, this would resolve this."
Answer: 5801.0

User story: "See DM-18175 for the original intent of that task."
Answer: 79581.0

User story: "Similar to the salobj conda package job, the next step is to create a job to create a conda package of the IDL files and the ts_idl repo.  See DM-18175 for details on the salobj conda package job for guidance on creating this job.     "
Answer: 37502.0

User story: "In looking for ways to speed up the generation of the RPMs, I found that Jenkins pipelines can run stages in parallel.  See if this functionality can work.    https://jenkins.io/blog/2017/09/25/declarative-1/"
Answer: 64797.0

User story: "I went through the exercise of trying to use the ObjectTable for some QA last week. I had to add a lot of columns we use regularly like per-band CalibFlux, and per-band PixelFlags.     In addition to these, I'm going to add the columns that pipe_analysis uses as well.  ObjectTable is going to bitrot if its too skinny to be used in practice.     ideally, it'd be something that [~<USER> could base the example qa-drilldown site on.       "
Answer: 42911.0

User story: "test_functors.py in pipe_tasks relies on a dataset with fixed columns creating problems if new columns/values are needed for newly created functors. This ticket will modify the unittesting to be more similar (and reuse some of the code from) the test_parquet.py suite, creating the dataframes/parquet tables as needed within each test allowing control over a) the columns created b) the values input which in turn will allow for testing of a specific funtor's algorithm/calculation.     "
Answer: 29803.0

User story: "I missed a couple changes on DM-16234. Wasn't aware that matchVisits was being used at the time."
Answer: 8173.0

User story: "After multiple workshops and better understanding of daq api, this ticket captures the work for implementing the codes to daq v4 and testing it."
Answer: 72306.0

User story: "With the changes implemented in lsstsw documented in DM-16839, when a specific environment definition (reference) is used from scipipe-conda-env, the command run-rebuild is able to show the changes made in the environment locally since it has been created using bin/deploy.    This functionality is not available, in case the default environment is deployed, lsst-scipipe, running bin/deploy without any reference.    I think it is desirable that this functionality to be available also when the default environment is used. In order to permit this, the sha-1 of the environment has to be added to the environment name."
Answer: 66339.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 encountered a few [processing failures|https://lsstc.slack.com/archives/C2JPXB4HG/p1562915140263300] in the HSC S19A production around the edges of the field:  {code}  RuntimeError: AST: Error at line 53 in file src/FitsChan.cc.astFindFits(FitsChan): Cannot encode floating point value nan into a FITS header card for keyword 'BGMEAN'.  {code}    The problem occurs in {{deblendCoaddSources}}, and brings {{multibandDriver}} down.    The coadd image ({{tract=9812 patch=5,3 filter=NB0921}}) is completely {{NAN}}. In this case, the only contribution to the image is {{visit=67792 ccd=103}}.    Make this fail nicely."
Answer: 81.0

User story: "Read up on Dome software design and specifications."
Answer: 45942.0

User story: "Create a patch release in the Documenteer 0.5 line that eliminates any use of pytest-runner. This is intended to avoid difficulties getting Documenteer built on Conda.    pytest-runner is already being removed from the Documenteer 0.6 release via DM-22957."
Answer: 19.0

User story: "Investigate using [Doxylink|https://sphinxcontrib-doxylink.readthedocs.io/en/stable/] to link to an HTML Doxygen build of the C++ API reference compiled alongside the main Sphinx site.    This work would build upon DM-22698, which gave Documenteer the ability to run a Sphinx build. In this scenario, Documenteer would build the Sphinx site, and then embed it as a sub-site (subdirectory) of the Sphinx-generated documentation. Doxylink would let us link between from reStructuredText to Doxygen using a custom role. For example:    {code}  :lsstcc:`lsst::afw::table::Schema`  {code}    Of course, links from Doxygen to the Sphinx site would not be straightforward (in princple, they could be added manually, though that would be prone to fail if URLs change)."
Answer: 62541.0

User story: "Ticket for inspecting and merging the changes."
Answer: 1140.0

User story: "The main telescope Hexapod should check limits for position and offset commands and reject the command if out of bounds."
Answer: 10251.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 filter list from DM-23075 must be added to obs_lsst to allow ingest of LATISS data by butler."
Answer: 338.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Per [discussion at the DM-CCB|https://confluence.lsstcorp.org/pages/viewpage.action?pageId=125240021], {{SourceDetectionTask.makeSourceCatalog}} is to be removed in Pipelines release 21.0.0. Please add the appropriate deprecation notices to release 20.0.0."
Answer: 3064.0

User story: "Implement the docstrings for the {{lsst-efd-client}} classes and functions."
Answer: 28555.0

User story: "Prototype out by hand and get working a postgres TAP service with pgsphere.         This has proven to be a bit harder than I thought:   # There aren't many containers out there with postgres and pgsphere.  Postgres is everywhere.  But pgsphere doesn't even seem to have a nice rpm of a recent build, which means I'd have to build it myself.   # CADC has a container, but it uses a private yum repo that has their pgsphere fixes   # ESA made one, although the source isn't able to be found on github, and it uses different table names than the CADC one expects.    Then I need to get everything together and just try it out on docker."
Answer: 12840.0

User story: "This implements the DimensionTableRecords and DimensionTableManager classes described in the [prototype document|https://confluence.lsstcorp.org/display/DM/Architectural+Prototype+for+the+New+Gen3+Registry]."
Answer: 41303.0

User story: "This implements the OpaqueTableRecords and OpaqueTableManager classes described in the [prototype document|https://confluence.lsstcorp.org/display/DM/Architectural+Prototype+for+the+New+Gen3+Registry]."
Answer: 11457.0

User story: "Currently, sky objects are implemented on the coadds (see ticket DM-4840). For various QA reasons it would be beneificial to have sky objects for single frame imaging also. This ticket adds sky objects at the single frame visit level. Such sources are termed 'sky sources', to distinguish them from the currently existing sky objects output by the stack and in keeping with processing nomenclature standards.     A community post highlighting this change is located here: https://community.lsst.org/t/sky-sources-added-to-single-frame-processing/4137"
Answer: 162632.0

User story: "Currently, the behavior is to throw an exception if interpolation outside the curve boundaries is attempted.  It seems like a better default, would be to clamp to zero outside the boundary.  I can imagine this would not be the case for all possible curves, so I will try to make this configurable."
Answer: 339.0

User story: "Per discussion on DM-22814, {{lsst.meas.algorithms.SubtractBackgroundTask.fitBackground()}} with the {{algorithm}} kwarg needs to be marked as deprecated before the release of 20.0.0."
Answer: 142586.0

User story: "This ticket adds a LATISS config file. Contains currently installed filters/gratings as well as network configuration."
Answer: 2217.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 schema of the Object table in the output parquet files depend on what filters are included in the input dataset. For example the Object table in a parquet file from the ci_hsc dataset has fewer columns than one from the HSC-RC2 dataset, because the former contains 2 filters and the latter contains 5.  It is not ideal that the schema is not fixed.  We would like the output schema to be deterministic and independent of the input dataset for the same camera (or obs package).  Perhaps a config parameter in the obs package would be suitable.    It's okay to only consider obs_subaru for now."
Answer: 12902.0

User story: "Default type in PTC task is wrong, should be overridden."
Answer: 1343.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 don't have any master calibs since early 2018, so we need to build some. We may as well use this opportunity to test using many fewer flats, so that the photometric solution isn't constantly perturbed. We will have four "seasons" (separation at MJDs 57420, 57606, 58050), with one flat in each filter for each season. We will continue to build biases, darks, fringes and sky frames as frequently as possible, as these are additive effects that shouldn't affect the photometric solution.
Answer: 44886.0

User story: "This is the ~monthly ap_pipe rerun of the HiTS 2015 dataset (all 3 fields). This time we should see if setting {{nImagesMax}} in the best seeing selector will work with the new slurm template generation. To be clear, this rerun should include generating new templates as well as running ap_pipe.    Optional bonus level and/or spinoff ticket: adopt the templates generated as part of this rerun as the new default in the ap_verify datasets."
Answer: 31808.0

User story: "Exercise ticket to learn workflow"
Answer: 43.0

User story: "Reprocess the HSC RC2 dataset with Stack w_2020_02"
Answer: 28654.0

User story: "[~<USER> et al. have requested that {{fgcmcal}} be run on NB0387 which has proved to be difficult to calibrate in the past.  As of DM-22955, the spatially varying narrow-band filters are now in {{obs_subaru}}, making it possible for {{fgcmcal}} to be run on these data.  In addition, [~<USER> has run {{singleFrameDriver}} on some NB0387 data from PDR2 over COSMOS, which is on {{lsst-dev}} at {{/datasets/hsc/repo/rerun/private/<USER>PDR2/w_2020_01/}} (see https://lsstc.slack.com/archives/C2JPXB4HG/p1578945289050000).      This ticket will report on the progress from a test run on COSMOS with NB0387 (from PDR2) + g + r + i + z + y (from RC2), and will also encompass any updates to {{fgcm}} and {{fgcmcal}} that are necessary to make this work."
Answer: 30216.0

User story: "Another instance of the EFD needs to be deployed at the NCSA test stand (see [https://sqr-031.lsst.io/])    The machine {{lsst-l1-cl-efd}} (141.124.238.172) was reserved for that initially. It satisfies the basic requirements to run a test stand deployment on Kubes (k3s) i.e. 16 cores, 45 GB memory, 1.8TB disk.    However, we run into firewall issues that prevented k3s to work.      It was decided that this deployment should be done in a new k8s cluster at the NCSA test stand.     "
Answer: 29526.0

User story: "RFC-576 established that we would propagate all input headers to the output files. This feature is desired for the next HSC production run."
Answer: 1399.0

User story: "Generate document to describe the communications interface between low and upper components of the new architecture of the dome control software"
Answer: 10143.0

User story: "Create XML SAL bindings for the MQTT telemetry subset."
Answer: 18651.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: "Fix the bugs found in the M2 cell system. This task is the phase 1.    Founded bugs:   # The log file can not be generated after rebooting the cRIO. (Done)   # The state can not transit after rebooting the cRIO.   # TCP/IP connection is easy to break. (Partially done.)"
Answer: 11020.0

User story: "Since DM-17566 landed, we're generating a bunch of FutureWarnings from inside DM code. Please suppress them."
Answer: 12613.0

User story: "The documentation for lsst.utils.tests has a number of minor formatting issues:    - https://pipelines.lsst.io/v/d_2020_01_13/py-api/lsst.utils.deprecate_pybind11.html#deprecate-pybind11  - https://pipelines.lsst.io/v/d_2020_01_13/py-api/lsst.utils.continueClass.html#lsst.utils.continueClass  - https://pipelines.lsst.io/v/d_2020_01_13/py-api/lsst.utils.tests.ExecutablesTestCase.html#lsst.utils.tests.ExecutablesTestCase.assertListEqual    Please fix them."
Answer: 4092.0

User story: "Per email from aws:    ??EC2 has detected degradation of the underlying hardware hosting your Amazon EC2 instance (instance-ID: i-858d4a03) associated with your AWS account (AWS Account ID: 039289279626) in the us-east-1 region. Due to this degradation your instance could already be unreachable. We will stop your instance after 2020-01-17.??"
Answer: 5680.0

User story: "While {{fgcmcal}} is a product, it doesn't have a {{component}} in jira.  Please add one."
Answer: 3.0

User story: The {{coaddAnalysis.py}} script distinguishes between "unforced" (i.e. the {{\*_meas}} dataset type) and "forced" (i.e the {{\*_forced_src}} dataset type). The latter table does not include some of the flag columns that are useful for sample sub-selection. The desired columns are thus copied to the "forced" catalog within the script.   Most of these columns should be coming from the {{\*_ref}} dataset, as it is those that are appropriate for the forced catalogs.  Some of those that should be coming from {{\*_ref}} are coming from {{\*_meas}} and thus can have the wrong value (it's quite rare but, for example, for two random patches, the {{detect_isPatchInner}} is different for 1 and 6 sources).  However, we want the various "calib\*" columns to come from the {{\*_meas}} catalog as these reflect what actually occurred during SFM per band (which is always what we want for the calib* columns rather than assigning the specific value associated with the forced filter to all other filters).  Here we should make the column copying more explicit and in accordance with the above desiderata.     
Answer: 76064.0