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 update the scripts CalSysTakeNarrowbandData and CalSysTakeData in ts_externalscripts for dds salobj (ts_salobj v4.1) and schema-based configuration (ts_scriptqueue v2.1).    Notes:  * ts_standardscripts already has an updated version of CalSysTakeData. I strongly recommend that you start from that, instead of what's in ts_externalscripts, and try to figure out the differences (if any). If there are no differences then please consider deleting the version in ts_externalscripts!  * I suggest you update the scripts for ts_scriptqueue v2.1, which means the schema is returned using a property named {{schema}}. There are updates coming that will make trivial further changes (truly trivial and I'm happy to do the work), but I think we'd really like to have a version of ts_externalscripts that works with ts_scriptqueue v2.1 before we make those changes.  * For the scripts you keep please add {{from calsys_take... import *}} to {{auxtel/\_\_init.py\_\_}}  * Please fix flake8 errors.    Resources:  * https://community.lsst.org/t/changes-in-salobj-4-the-dds-version/3701/2  * https://community.lsst.org/t/changes-to-sal-script-schemas-and-dds/3709/2  * DM-20089 shows the same update for some scripts in ts_standardscripts, including CalSysTakeData  * I am happy to help as wanted."
Answer: 57630.0

User story: "When looking at a header created yesterday from AuxTel the first two blank keyword comments  are shifted one character to the right:    {code}  $ fitsheader tests/data/ticket20143.fits  | grep '\-\-'           ---- Date, night and basic image information ----                                 ---- Telescope info, location, observer ----                                     ---- Pointing info, etc. ----                                                     ---- Image-identifying used to build OBS-ID ----                                  ---- Information from Camera                                                      ---- Geometry from Camera ----                                                    ---- Filter/grating information ----                                              ---- Exposure-related information ----                                            ---- Header information ----                                                      ---- Checksums ----                       {code}  "
Answer: 1215.0

User story: "Write the base class for Watcher alarrm rules. These rules will be loaded by the Watcher model DM-20148."
Answer: 71925.0

User story: "Write the Watcher model: the component that reads alarm rules, listens to the events needed by those rules, and manages the alarms."
Answer: 97862.0

User story: "Write the Watcher CSC, a shell that communicates with the model."
Answer: 80697.0

User story: "Write documentation for the Watcher, including how to configure the watcher and how to add rules."
Answer: 80701.0

User story: "Write SAL XML files for the Watcher in ts_xml"
Answer: 19793.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: "Continue investigating persistence frameworks that could be used to store C++ and Python objects instead of the C++-centric {{afw::table::io}}. The results will be added to DMTN-120 as part of DM-20142."
Answer: 429053.0

User story: The HeaderService is now writing FITS headers to raw data that include header cards using 8 blank characters as the special comment keyword.  This is completely within the standard but the reader code in afw.fits is confused and stores them as keyword {{""}} and value {{None}}.  This confuses things when output files are written.    Fix the reader. It may be simpler to move these blank keyword comments into {{COMMENT}} fields in PropertyList.  Since the order is lost once comments are read there is nothing to be gained from retaining the distinction between the two types of comments.
Answer: 103.0

User story: "Write a tech note ([DMTN-120|https://dmtn-120.lsst.io/]) that describes how we are making the {{Exposure}} code more flexible and to propose alternative persistence frameworks to {{afw::table}}. The text will be written by [~<USER> and myself, as appropriate."
Answer: 193003.0

User story: "Address security alerts in LTD Keeper as of 2019-07-13:   * Upgrade flask to version 0.12.3 or later   * Upgrade requests to version 2.20.0 or later"
Answer: 352.0

User story: "In DM-20122 we determined that LTD Keeper can provide a presigned POST URL to build upload clients. This prevents clients from needing to maintain their own S3 credentials.    This ticket enables LTD Keeper to generate those presigned URLs as part of a new \{\{{{[POST /products/(slug)/builds/|https://ltd-keeper.lsst.io/products.html#post--products-(slug)-builds-]}} endpoint.}}    {{To prevent this update from breaking older clients, we may want to use accept headers to version the endpoint. This will set a useful precedent for future breaking API changes in LTD Keeper's REST API.}}"
Answer: 36345.0

User story: "In DM-20122 we determined that presigned POST URLs are a good fit for giving upload clients the ability to upload a build without having to maintain their own AWS/S3 credentials. This ticket adds that capability to the LTD Conveyor application. Other tickets will add the ability for LTD Keeper to generate the presigned URLs."
Answer: 35940.0

User story: "DM-19841 introduced temporary code that expanded the masks of {{ccd=9^33}} in the process of building coadds. [~<USER> has discovered that these mask expansions are not sufficient, and [need to be expanded further|https://jira.lsstcorp.org/browse/DM-19841?focusedCommentId=198664&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-198664]."
Answer: 135.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: "Paraphrased bug report from Andy Goulding (parentheticals are [~<USER>'s musings):  {quote}Some of the mask pixels around bright objects (probably BRIGHT_OBJECT, or maybe DETECTED) are having that plane cleared when they overlap with another mask plane, which mostly appears as narrow rectangles or stripes (INEXACT_PSF or SENSOR EDGE?).   This was particularly obvious in the Deep and UltraDeep fields.  {quote}  This sounds like a fairly straightforward case of something assigning to the mask plane when it should be OR'ing into it.  What's confusing (at least to me) is that I thought the candidates for the plane being cleared (BRIGHT_OBJECT, DETECTED) are all set after all of the candidates for the plane that's apparently clearing them (INEXACT_PSF, SENSOR_EDGE).    [~price], [~<USER>, [~<USER>, do you have any guesses off the top of your heads about what could be going on here?  (i.e. maybe you know something about the order of operations that I've guessed wrong about).    If we can't spot the effect in processed data we have in hand (e.g. an RC2 run) easily, I'm sure we can get more details from Andy as to exactly which mask planes are interacting poorly."
Answer: 289.0

User story: "Minikube is buggy and doesn't allow to setup several k8s nodes. kind should solve these issues."
Answer: 80772.0

User story: "It's been requested to provide a container for the HeaderService. The primary usage of this should be to provide an estable version to spun new instances for development. At the moment the baseline is to use puppet to deploy this services at NCSA and Tucson. This could become useful when/if we decide to move CSCs into containers."
Answer: 2411.0

User story: "     For ATHeaderService The keywords {{RASTART/END}} and {{DECSTART/END}} must be calculated from the above AZ/EL keywords by the HS"
Answer: 37311.0

User story: "I'll have to make some updates do the docker and compose files to accomplish this task. I'll create this task to capture the work. "
Answer: 19814.0

User story: "In order to test auth, all of our lower case j's need to be dotted.  This means fixing our returned IVOA capabilities from the TAP service to use the right urls, with https instead of http, since this matters for auth things.  (For example, not doing basic auth over http, but maybe allowing it over https)    Should be a simple change.  Discovered this as a part of doing the auth work.  It detects the hostname automatically, but not the http/https, or at least it doesn't work because it is behind so many levels of proxy."
Answer: 20.0

User story: "Currently there are no unit tests for {{mea_extensions_scarlet}}. Tests should be implemented to ensure that changes in the stack do not break this package."
Answer: 61608.0

User story: "The old unit tests need to be modified and new tests need to be created for scarlet v0.5. A separate ticket will be created for unit tests in the {{meas_extensions_scarlet}}."
Answer: 16474.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "To properly test the TMA software in Tucson a PXI like system will be installed using a standard desktop PC. Review the spec for such a machine and issue a req for it"
Answer: 138531.0

User story: "Review the latest set of deployment documents for the TMA"
Answer: 201702.0

User story: "Manage the preparation of the new EFD hardware (24 dell servers) so that they can be upgraded before shipping to Chile. Test proposed upgrades on a sample machine and then issue a req for same"
Answer: 133946.0

User story: "This is an investigation, design, and planning ticket for the larger DM-18720 epic.    The basic problem is that clients for LSST the Docs generally shouldn't have S3 credentials. They are both extra things for clients to track, and they can potentially give clients more access to S3 than they need. We want to move to a model with LTD Keeper is the only application with credentials to LTD's S3 bucket. The question then, is how LTD Keeper should provide access for clients to upload new builds into the S3 bucket. The main options are:   # LTD Keeper creates a temporary S3 credential for the client, and then ensures that the credential is deleted/rotated.   # LTD Keeper generates presigned URLs that the client can upload to.   # The client uploads files to LTD Keeper, and LTD Keeper forwards those objects to S3."
Answer: 1475.0

User story: "For this task I'll convert the GenericCamera CSC to use ConfigurableCSC. I'll also add some tests."
Answer: 40830.0

User story: "Perform an analysis of the current SAL testing being performed now and suggest an itemized list of unit tests that could be implemented to increase our coverage with maximum impact that would increase our effectiveness in identifying bugs prior to cutting an official SAL release.    This ticket is assigned to Russell, but this is meant to be a ticket where anyone, specifically [~<USER>, [~<USER> and [~<USER> can suggest tests.    Upon compiling the list then we can rank them and evaluate how we move forward."
Answer: 22328.0

User story: "Add Deprecated APIs information the Release Note (as per action of DMCCB 2019-05-01)"
Answer: 54502.0

User story: "Update the tunable laser csc to new salobj version 4."
Answer: 423333.0

User story: "At DMLT meeting in early June I was told to prepare LDM-635 for RFC. This mainly requires I fix the sort order of the requirements."
Answer: 4395.0

User story: "Containerize the LinearStage CSC into a docker file. "
Answer: 60518.0

User story: "The header service failed yesterday whilst operating because a deferred import to Astropy could not be completed. The header service should do all required imports at launch time so that we can detect problems early."
Answer: 4524.0

User story: "Generic Camera software knowledge transfer with Chris on one of the EAS cameras:   * ZWO ASI 1600mm Pro (mono CMOS sensor)"
Answer: 60960.0

User story: "TMA Software Workshop in Spain with vendor."
Answer: 8981.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "DM policy is not to defer imports, the HeaderService should follow this, the import of astropy is an issue that need fixing."
Answer: 824.0

User story: "Validate the performance of the new implementation of pytrax. [Github repo|https://github.com/pytrax/]  commit [6b46741|https://github.com/pytrax/pytrax/commit/6b46741999635bbe991df9859178db94c907a45c] ."
Answer: 155278.0

User story: "NASA Jet Propulsion Laboratory orbit and orbit covariance propagation, the current state-of-the-art in ephemeris generation has been licenced for LSST. As the code is written in Fortran90 and only partly available as source code – the other parts are precompiled libraries – essential routines have been wrapped in python."
Answer: 73642.0

User story: "Resolution to DM-19841 was to add hack in makeCoaddTempExp to update masks on ccd 33 and 9 on the fly. Once S19A is over and the problem is fixed upstream during defect interpolation this Task override should be removed."
Answer: 342119.0

User story: "Currently an ObservationInfo can only be constructed from the metadata of an observation. There are some cases where it would be useful to create an ObservationInfo from either kwargs or else update values in an ObservationInfo after creation (currently they are immutable).    DM-19978 would be simplified if an ObservationInfo could be constructed from known values."
Answer: 3214.0

User story: "For the commissioning papers (and overview paper) we need a scheme for managing author lists in a standardized way.  The overview paper has some infrastructure for this but the scripts need to be modified to separate the author list for a specific paper from the author full name and affiliation.    In theory the name and affiliation information should come from contacts DB. In the interim I will use an intermediary YAML file."
Answer: 5755.0

User story: "A set of instructions, that will become a community post, on how to insert fake sources into single epoch images and coadds."
Answer: 308.0

User story: "Following on from DM-20069, make the PTC task work well be adding algorithmic code provided by Pierre^2."
Answer: 569224.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 stack infrastructure work is done already (brought to this ticket, used to live on DM-19709), this ticket is for [~<USER> to use this task outline to actually produce a naive PTC curve.    DM-20070 exists to enhance this task, bringing in the fancy algorithmic techniques provided by Pierre^2.    Naive PTC task:   * Main PTC plot with cubic fit and the linear components displayed for the gain   * Mean vs exp. time (so that relative QE can be compared across runs)   * This will need augmentation later to allow correcting with the photocharge on the monitoring diode   * Read noise from var axis intercept   * Persist all the relevant data products from the above plots as pickled dicts    For later, we will want several modes of operation: [covariance summation, binning, ramp-frames?] and perhaps others, but these probably belong on the enhancement ticket, DM-20070.    Binning as default, and the only supported mode for now.    It is accepted that the linearity model calculation part of this will likely output garbage for now, as the dominant errors will likely be from:        * Shutter variation (commanded vs. delivered)        * Illumination/effective-expTime non-uniformity due to iris shutter itself        * Lamp variability  as all the above will need to be corrected for using photodiode data in order to get good (or likely even useful IMO) results, and this will require a post hoc supplementary analysis for now, as any kind of automated retrieval and processing of this data is clearly overambitious at this stage.   "
Answer: 162965.0

User story: "Ticket is basically done, but wasn't reviewed (as it needed to be closed) and is therefore sitting on the DM-19709 branch.    It's quite a bit of new code, so this is ticketing its review."
Answer: 100746.0

User story: "Update the newly written at_tracking integration test to use salobj 4.0."
Answer: 102426.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 ATHeaderService, which is running on `dm-hs-node-01` at the Tucson test stands needs to be updated to run using version v3.10.0_001 of the ts_sal rpms. In addition several pre-req packages needed to be updated.            {code:java}  pip3 install pyyaml  yum -y install https://centos7.iuscommunity.org/ius-release.rpm  yum -y install python36u python36u-devel python36u-pip  ln -s /usr/bin/python3.6 /usr/bin/python3  install-fitsio.sh  {code}     {code:java}  SAL_VERSION=3.10.0_001  OPSL_VERSION=6.9.0  # Add the lsst-ts repo  wget https://lsst-web.ncsa.illinois.edu/~<USER>packages/lsst-ts.repo  mv -v lsst-ts.repo /etc/yum.repos.d  # These are the ones we've needed for now  yum -y install OpenSpliceDDS-$OPSL_VERSION  yum -y install ATHeaderService-$SAL_VERSION  yum -y install ATCamera-$SAL_VERSION  yum -y install ATArchiver-$SAL_VERSION  yum -y install EFD-$SAL_VERSION  yum -y install Scheduler-$SAL_VERSION  yum -y install ATPtg-$SAL_VERSION  yum -y install ATMCS-$SAL_VERSION  yum -y install ATSpectrograph-$SAL_VERSION  yum -y install ATTCS-$SAL_VERSION  # Needed by ATArchiver  yum -y install CatchupArchiver-$SAL_VERSION  yum -y install MTArchiver-$SAL_VERSION  yum -y install MTCamera-$SAL_VERSION  yum -y install PromptProcessing-$SAL_VERSION  # Get the setup conf  wget https://lsst-web.ncsa.illinois.edu/~<USER>packages/setup_SAL.env -O /opt/lsst/setup_SAL.env  {code}             "
Answer: 3735.0

User story: "Add an auth system to pyvo that follows the IVOA auth guidelines."
Answer: 115564.0

User story: "Ensure that configuration for SSO is ready to go prior to migration."
Answer: 67580.0

User story: Remove old style defects from ap_verify datasets. These include ap_verify_hits2015, ap_verify_ci_hits2015, and ap_verify_testdata. I think that's it?    This split off from DM-19857 and should be done afterwards. It's not essential to have these files removed for us to support the new defects in ap_verify, and "support the new obs_decam defects in ap_verify so we can merge DM-19730" is the real goal of DM-19857.
Answer: 20145.0

User story: "I haven't enforced a consistent style in the MultiProFit code (Python or C++) and I still have a few features to add/update, so now would be a good time to start."
Answer: 5954.0

User story: "Per request of Tony and <USER> copy images created directly by the ACCS to NCSA and put into a gen2 repo."
Answer: 79243.0

User story: "While the data is being copied to a production filesystem, that filesystem wouldn't be mounted as-is on the LSP.   So temporary copies were put in place to /project.   Changes were made to the production filesystem (e.g., new path) so that it would be mounted on the LSP.   Update cron jobs to new location.   Make gen2repo on the production filesystem as before it was only made on temporary location.   Work with K-T to get whatever gen2 repo chaining in place for <USER>updated.    Announce change"
Answer: 79243.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: "Deferring normalization for these objects adds unnecessary complexity, delays error reporting, and [leads to incorrect behavior in DatasetType comparisons|https://confluence.lsstcorp.org/display/DM/Butler+Major+Design+Questions%2C+2019-05-28#ButlerMajorDesignQuestions,2019-05-28-ImmutableDatasetTypes,DataIds,andDatasetRefsimmutable-datasettypes-dataids-and-datasetrefs].    This work has already been started on DM-17023, but I'm spinning it off here to keep that from growing too large."
Answer: 10434.0

User story: "There was a misspelling on salpytools that named a function  DDSSubcriber, it has been changed to to DDSSubscriber. The HeaderService need to be updated to reflect this simple change."
Answer: 59.0

User story: "In reviewing DM-18151 Lauren wanted to see some other plots. This ticket is to make those additional plots."
Answer: 575648.0

User story: "DM-19843 implemented least squares fitting using the analytic Jacobian for Gaussian mixture models in MultiProFit. However, the solution used there - a 1:1 mapping from Gaussian parameter to fit parameter - doesn't work for the Sersic index in multi-Gaussian Sersic approximations, because it changes flux, sigma_x, sigma_y (and hence rho) for every Gaussian, and therefore is a weighted sum of four gradient per component Gaussian, so the Sersic index and any other similar parameters will need to be handled separately."
Answer: 38632.0

User story: "Continue DM-17555, reprocess some DC2 imsim data at /datasets/DC2/repo/"
Answer: 18517.0

User story: "It seems like many messages (both as telemetry and Events) are still present on the Test Stand after many days and still show up when listening to new Event/Telemetry."
Answer: 1293.0

User story: "Node headers by default capped at 8K.  It's configurable, so find a way to pass a larger value down to the proxy."
Answer: 1380.0

User story: "Generators will probably use less memory than adding images to a list. Update the fake source insertion code to use these instead."
Answer: 262404.0

User story: "We are re-architecting oracle_rac stuff in Puppet in several stages and will need to NOT apply changes to oradb[01-03] at first. Maintaining the existing code with an _old appendage and pointing oradb[01-03] at them (and oradb[04-06] still for about a week) will help in this effort, allowing us to merge to production and keep moving forward while scoping our changes appropriately and allowing Puppet to stay running on nodes that can't otherwise change."
Answer: 2.0

User story: "The scarlet docs need to be updated with the new API."
Answer: 20232.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: "Work with Jim and Michelle to bring QuantumGraph generation from the initial 18 hours to a reasonable performance level in Oracle."
Answer: 28.0

User story: "Ingest RC2 data set into Oracle, to initialize repo for RC2 Gen3 runs."
Answer: 29.0

User story: "Analysis of Oracle trace files during ci_hsc runs with Gen3 Pegasus."
Answer: 33.0

User story: "Starting to set up a demo notebook for Quansight, I realize that I can't call a simple functor (e.g., a labeler) on a single-level parquet table (e.g., a {{analysisCoaddTable_forced}}):  {noformat}  ---------------------------------------------------------------------------  TypeError                                 Traceback (most recent call last)  <ipython-input-19-2b4d44d689db> in <module>        1 labeller = StarGalaxyLabeller()  ----> 2 label = labeller(coaddParq)    ~/qa_explorer/python/lsst/qa/explorer/functors.py in __call__(self, parq, dropna, **kwargs)      671       672     def __call__(self, parq, dropna=False, **kwargs):  --> 673         return super().__call__(parq, dropna=False, **kwargs)      674       675     ~/qa_explorer/python/lsst/qa/explorer/functors.py in __call__(self, parq, dropna)      140       141     def __call__(self, parq, dropna=False):  --> 142         df = self._get_cols(parq)      143       144         vals = self._func(df)    ~/qa_explorer/python/lsst/qa/explorer/functors.py in _get_cols(self, parq)      127             columns = self.columns      128   --> 129         df = parq.toDataFrame(columns=columns, droplevels=False)      130         df = self._setLevels(df)      131         return df    TypeError: toDataFrame() got an unexpected keyword argument 'droplevels'  {noformat}  "
Answer: 119496.0

User story: " Coordinate SST review of LDM-522. "
Answer: 149844.0

User story: "Review DM Science documents in the JSR document pack spreadsheet.     Documents in the [Document pack|https://docs.google.com/spreadsheets/d/1XAMoyyCYy8vcVGiVRYckDtxfjkvqMFr459lH6deHwAQ/edit#gid=0] to be reviewed for the JDR/JSR:     LDM-672: DM Release Management Policy (With Gabriele)  DPDD: LSE-163  LSST Science Platform Definition (Vision) Document: LSE-319  MOPS : DMTN-087  Data management and LSST Special Programs: DMTN-065  LSST Data Management Acceptance Test Specification: LDM-639    Comments to Wil:   https://github.com/lsst/wom_presentations/tree/master/STATUS_REVIEW_2019."
Answer: 109935.0

User story: "Use the test dataset created in DM-19864 as a starting point to get Quansight developers familiar with the LSST stack and the data they will be using to generate the dashboard.  Work with them to make sure they understand things; answer their questions, etc.  This will be the initial work under the soon-to-be-completed Quansight contract.    Also, work on making the test dataset available as a butler repo outside the LSP."
Answer: 144206.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: As discussed at DMLT meetings, we need to extract a todo list for YAMLCamera/obs_lsst and the plan/timeline for implementation.    From [DMLT F2F in February 2019|https://confluence.lsstcorp.org/display/DM/DM+Leadership+Team+Virtual+Face-to-Face+Meeting%2C+2019-02-26+to+-28]     "YAMLCamera is a fact of life, but it needs more testing before we rely on it, and there is ongoing development and its schema needs to be formalized.    Four tasks to convert and update obs_decam:  * Conversion to YAMLcamera  * Versioned cameras  * Integration of user generated calibs  * Deal with config overrides in obs_ packages.    The useful end product is a document describing how an obs_ package works.  This is not blocked on other work; Tim, Simon and their T/CAMs can schedule this based on their availability."    The todo list can be listed in this ticket.   
Answer: 42270.0

User story: "The QA working group recommended to adopt the definitions of QA-related terms in the DMTN-085 glossary subsystem-wide  in QAWG-REC-1.  At the DMLT F2F meeting, this recommendation was accepted.     This glossary should be audited for correctness and for clashes with higher LSST glossaries.   "
Answer: 18779.0

User story: "Continue summit work, including ATTCS unit tests, slewing and dome integration tests, hitting e-stop button when we accidentally slew the telescope into a crane, etc.    Returning to Tucson fri/sat"
Answer: 11949.0

User story: "The ATArchiver has seen several code upgrades and modifications recently. Moreover, the assembly method/order has never fully vetted. Therefore we need to confirma that the assembly method of FITS files (segments + header) that the ATArchiver is performing is consistent with the baseline established by (AT)Camera."
Answer: 15319.0

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

User story: We may want to begin tracking files on local file systems with Rucio, and some time later  decide on the preferred protocol for replication to other locations (working with the same "files") . Thus we examine the use of multiple protocol access/operations for files registered in Rucio to check on plausibility of this usage.
Answer: 40380.0

User story: We study the current functionality supported for (zip) archive files in Rucio. In this scenario a potentially large .zip file is "the replica" on disk within the Rucio Storage Element. The constituent "files" are not individually on disk, but will be tracked by Rucio by appropriate registration.
Answer: 41624.0

User story: "We check if Python3 support for Rucio is sufficiently advanced to allow test / initial setups of Rucio services to be based on Python3 by means of a trial installation. "
Answer: 40371.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "In preparation for the 18.0 release, please gather the following information for the release notes:   * list of issue resolved since last release   * Narrative describing the release"
Answer: 36009.0

User story: "Create first release candidate 18.0-rc1"
Answer: 50690.0

User story: "Ensure that the identified weekly build identified to start the 18.0 release process has no scientific regressions and is a good starting point for the first release candidate."
Answer: 11550.0

User story: "DMS-REQ-0362 derives from the OSS ellipticity correlation requirement OSS-REQ-0390.  As the latter requirement was long incorrect, presumably DMS-REQ-0362 is as well and the corrections from LCR-1554 will need to be flowed down to it, and, given the nature of the LCR, additional DMSR requirements may be needed to parallel new ones added at LSR and OSS level."
Answer: 195888.0

User story: "Login node requirements include:    * GPFS Access   * Job Submission   * Slurm   * HT Condor (if/when it is added)   * Kubectl    3 vm's will be created in vsphere that are provisioned by xCAT. The VMs will be 4 cores, 8gb mem, and 30gb storage"
Answer: 151536.0

User story: "To complete the DRP deblender sprint from May the changes must be pushed to master. This ticket includes pushing the required changes to scarlet and updating {{meas_extensions_scarlet}}, {{pipe_tasks}}, and {{pipe_drivers}} with the appropriate changes so that scarlet v0.5 can be run on LSST."
Answer: 31030.0

User story: "I am using the soft that I committed here [https://github.com/lsst-dm/fetch_merra2/tree/master] :      fetchMERRA2.py --site ohp --parameters aod pwv ozone --dir . --date 2018-07-13 2018-01-18 2018-07-11 2018-07-10 2018-07-08 2018-07-09 2018-10-23 2018-07-12 2018-10-22 2018-04-18 2018-04-19 2018-10-24 2018-03-19 2018-10-25 2018-04-20 2018-03-22 2018-03-20 2018-03-21      runAll.py OHP . 20180713 20180118 20180711 20180710 20180708 20180709 20181023 20180712 20181022 20180418 20180419 20181024 20180319 20181025 20180420 20180322 20180320 20180321         to deliver the atmospheric parameters for a set of PCWG/starDICE observations at Haute-Provence Observatory : this is usefull both to test the service and to pursue our investigation of the best strategy for LSST photometric calibration."
Answer: 196831.0

User story: "The steps required to turn a collection of files from some archive into an LSST-style reference catalog need to be written down so that the next catalog is easier to generate. A DM Tech Note seems like the appropriate place for such a description."
Answer: 42623.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 ref cat quanta in the generated quantum graph can be different for processing a CCD in CalibrateTask, depending on whether the data selection query includes a tract. For example,  {code:java}  pipetask -d "visit=1294 and detector=34"  {code}  versus  {code:java}  pipetask -d "visit=1294 and detector=34 and tract=9615"  {code}  with the HSC-RC2 repo, the predictedInputs of CalibrateTask has two ref_cat {{skypix: 222341}} and {{skypix: 222348}} in the former, but has only one ref_cat {{skypix: 222341}} in the latter.    In the latter, CalibrateTask got fewer reference objects and then fails with "RuntimeError: Unable to match sources" in astrometry matchObjectsToSources. w_2019_22 was used in my testing. 
Answer: 56910.0

User story: "{noformat}    Hi Josh,    We realized that after you created the pipeline that scans the repos and creates pipelines for each of them, we ended up with 2 pipelines per repository. For instance:    - LOVE-frontend (our original pipeline)  - LSST telescope & Site / LOVE-frontend (the autogenerated pipeline)    We tried to delete the old pipelines but we don't have permissions. We edited them to remove the references to the repo in order to stop them being triggered but we ended up duplicating them.    In the end, we managed to rename them, could you please delete the old pipelines? The pipelines to remove would be the following:    Pipelines to DELETE        Old LOVE-manager (please delete me)      Old LOVE-frontend (please delete me)      Old LOVE-producer (please delete me)      Old LOVE-manager (please delete me)      Old LOVE-frontend (please delete me)      Old LOVE-integration-tools (please delete me)      Old LOVE-integration-tools (please delete me)    Pipelines to KEEP  The ones we need to keep are the autogenerated:        lsst-ts LOVE-manager      lsst-ts LOVE-frontend      lsst-ts LOVE-producer      lsst-ts LOVE-simulator      lsst-ts LOVE-integration-tools    Thanks in advance.    Cheers,       Sebastián Fehlandt  Ingeniero de Investigación y Desarrollo.  Av. Apoquindo 2827, piso 12, Las Condes, Santiago, Chile  Teléfono: +56 22 584 7277 - Celular: +56 9 78094195  www.inria.cl  {noformat}  "
Answer: 6.0

User story: "Integrate ts_MTAOS with PhoSim for the AOS close loop simulation. This task will update the xml file for the intra- and extra-focal visits."
Answer: 15316.0

User story: "Through the S19 cycle, [~<USER> has performed a number of experiments to understand the range of seeing conditions over which his DCR mitigation approach can be usefully applied without further extension. Summarise these in a brief DMTN that we can (for example) supply to LSST leadership to inform future decisions about survey strategy, requirements for future development of this code, etc."
Answer: 86237.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: "Repeatedly run QuantumGraph Generation with various configurations and daf_butler versions to provide trace info to ChrisS and python profiling info to JimB as they work on speeding up wallclock for this step.   Reports were on slack (most to dm-middleware)."
Answer: 2.0

User story: "As JupyterLab evolves, things break, and sometimes it's us who ends up fixing them."
Answer: 322585.0

User story: "pyvo's build is broken due to an upstream astropy change, and I need to get the build green before any more new development can proceed.         Here's a link to the failure:    [https://travis-ci.org/astropy/pyvo/jobs/539464337]"
Answer: 11442.0

User story: "Add file to git ignore that got missed when merging tickets/DM-19272"
Answer: 5512.0

User story: "I was tasked with coordinating the Release of SAL and XML v3.10.0.  This task is to track that work."
Answer: 17391.0

User story: "* There is a first version to calculate the PTC of ComCam data (repo: /project/shared/comCam/ in lsst-dev01 at NCSA )as part of DM-19709. For this ticket:    ** Use that code and modify it if necessary (e.g, implementing modifications from the PTC code used in DM-18052) to calculate the PTC   ** Analyze the produced PTCs (for different amplifiers/detectors), and determine if it makes sense . "
Answer: 177327.0

User story: "Read the ts_MTAOS code and document to be familiar with it. This task will also to learn the Python asyncio library to have an initial understanding of how to use it. This task also plans to read the code of ts_salobj."
Answer: 5828.0

User story: "Prepare and write up a statement of work describing the job we will hire Quansight to do to implement a prototype QA dashboard.  Iterate with Quansight to make sure it is acceptable."
Answer: 10414.0

User story: "Shadow Tiago, learn about integration, work on auxiliary telescope slewing, develop unit tests for ATTCS"
Answer: 17639.0

User story: "The investigations on DM-19731 did not (as promised there) yield config changes on DM-19638.  Add the config that fell through the cracks."
Answer: 39969.0

User story: "The error is {{AttributeError: 'NoneType' object has no attribute 'getCameraName'}} instead of something more useful."
Answer: 25.0

User story: "  Record fully scheduled, resource-loaded cycle plan in JIRA and Primavera. Transmit to project controls specialist.    Kaylyn, Joel  "
Answer: 47481.0

User story: "Refine task scope, schedule, and staffing based on staff availability, task parameters, and project schedule."
Answer: 37023.0

User story: "Meet with staff to incrementally refine initial list of activities into final task/activity list."
Answer: 37128.0

User story: "Hold initial management-level planning meeting(s). Create proposed list of tasks/activities by WBS and task area.    Joel, Kaylyn, Margaret, Michelle; task area leads"
Answer: 37027.0

User story: "Prepare list of project needs, milestones, activities, current status, staff availability, etc., as input into planning process.    Joel, Kaylyn, Michelle,  Margaret, "
Answer: 10126.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: "Convert some of hslib https://github.com/lsst-dm/HeaderService/blob/master/python/HeaderService/hslib.py for salobj as an example of how to do it."
Answer: 48982.0

User story: Just write down the model carefully, identifying free parameters, labeled cameraGeom systems, and FITS WCS frames like "intermediate world coordinates".  Then take derivatives w.r.t. our desired parameters.  Is the model linear?  Can we make it linear via some transformation, or by fitting for sky-to-pixels instead of pixels-to-sky first?  This may be useful for DM-19734 and DM-19735 as well.
Answer: 25962.0

User story: Identify both "easy" and "difficult" test datasets for testing.  For "difficult" I'd like some CCDs we've failed to fit in the past, even if subsequent config-tuning has gotten them working.  Maybe ask <USER>  At least the "easy" category needs to cover all nQuarter values.  Maybe HSC data for "easy", LSST DC2 data for "difficult"?    [~<USER> has a number of potentially useful datasets identified as part of MatchPessimisticB testing.
Answer: 131258.0

User story: "Prepare agenda, review software and documentation and then attend the TMA software workshop in Spain"
Answer: 19010.0

User story: "In DM-19875 I updated Script and ScriptQueue enums to be shared. This requires a trivial change to ts_sal's test_sal test_enumerations_present method because it changes the Script enum names.    I will implement the ticket, but I leave it to [~<USER> and [~<USER> when to merge it, since it should be coordinated with the next release of ts_xml."
Answer: 17059.0

User story: "In a [GitHub pull request|https://github.com/lsst/daf_butler/pull/160] [~<USER> makes the case that URIs in the Location classes are not working properly.  His fix is not quite right so take the PR and see if it's possible to fix things such that URIs with relative paths are properly handled."
Answer: 13228.0

User story: "attempt runs using the HSC-RC2 repo built in DM-18829"
Answer: 88037.0

User story: "Update FiberSpectrograph code to use sal 3.10. Create and test release 2 version."
Answer: 17297.0

User story: "The topic Alias must match the last part of the EFDB_Name, otherwise the SAL can't properly build the libraries.  Add a test to robotframework_ts_xml to verify this."
Answer: 272989.0

User story: "Give support on the software for the M2"
Answer: 497.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: In {{smoothArray}} multiplying the convolved image by numerator/denominator, was supposed to correct the roll-off produced by padding the input image with zeros.     See the last comment on https://jira.lsstcorp.org/browse/DM-17426?focusedCommentId=196713&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-196713    And conversation on #subaru_hsc:    <USER>[8:42 PM] These lines https://github.com/lsst/pipe_drivers/blob/master/python/lsst/pipe/drivers/background.py#L869    should be fixed (naively) as:    {code}  convolved = gaussian_filter(numpy.where(bad, 0.0, array), sigma, mode="constant", cval=0.0)  -numerator = gaussian_filter(numpy.ones_like(array), sigma, mode="constant", cval=0.0)  +numerator = gaussian_filter(numpy.ones_like(array), sigma, mode="constant", cval=1.0)   denominator = gaussian_filter(numpy.where(bad, 0.0, 1.0), sigma, mode="constant", cval=0.0)   return convolved*numerator/denominator  {code}    Let me explain: we set bad pixels to 0 in computing {{convolved}}. Doing it wrongly lowers the pixels around the bad pixels in {{convolved}} . We compensate this effect with {{*numerator/denominator}}. In computing {{convolved}} , pixels outside the input image are also set to 0 ( {{cval=0.0}} ). It is that these pixels are regarded as a kind of bad pixels, and their effect should have been compensated together with the effect of the bad pixels inside the input image. This is why the {{numerator}} needs the fix above.    But if we compute {{numerator}} according to this fix, all elements of {{numerator}} are 1. Therefore, we can drop it altogether, hence Koike-san's proposal:     {code}  convolved = gaussian_filter(numpy.where(bad, 0.0, array), sigma, mode="constant", cval=0.0)  -numerator = gaussian_filter(numpy.ones_like(array), sigma, mode="constant", cval=0.0)   denominator = gaussian_filter(numpy.where(bad, 0.0, 1.0), sigma, mode="constant", cval=0.0)  -return convolved*numerator/denominator  +return convolved/denominator  {code}
Answer: 417.0

User story: "DiaForcedSourcedTask needs to be converted to accept and use pandas.DataFrames as input"
Answer: 90825.0

User story: "Attend the ComCam MIE Pre-ship Review:    [https://confluence.lsstcorp.org/display/LTS/MIE+Pre-ship+Review]"
Answer: 2862.0

User story: "Okay so we need to cut a release in pyvo for the last version that has all the fixes before I go and probably mess it up.  Always good to save before starting a new level!  Then the bug fixes will progress and get back into development.    This is somewhat new for me, and of course a new project.  So that'll be interesting.  I should theoretically have all the privs I need from the astropy hackathon."
Answer: 4295.0

User story: "Add the extra code developed in DM-19336  to the `findDefectsTask` in cp_pipe (written as part of DM-19709).  "
Answer: 376099.0

User story: "We need to make sure that the HeaderService can work with the newest version (1.0.0 to 1.03) of fitsio properly"
Answer: 4505.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: "Review TSSW Organization and Management Document:    [https://docs.google.com/document/d/1xIn5HlGiaZqLwjmnCdy1Mm4KujjcBXwkdMZqMMyywe8/edit]"
Answer: 10105.0

User story: "Write up some informal documentation on the M1M3 support system and M1M3 thermal system."
Answer: 74926.0

User story: "This task is to document the use of AOS code by the docker-compose with the PhoSim. This task will also prepare the related docker image for Chris to write the organizer script with MTAOS.    This task also reviews the TSSW Organization and Management Document (DM-19898). "
Answer: 18962.0

User story: "This task is to play the Kubernetes API by gcloud sdk to be familiar with it."
Answer: 30681.0

User story: "ERA5 [https://www.ecmwf.int/en/forecasts/datasets/reanalysis-datasets/era5]    is the European counterpart of MERRA-2    [https://confluence.ecmwf.int//pages/viewpage.action?pageId=74764925]    It should be analyzed because of two reasons :    - It is said to be more accurate on small scale than MERRA-2.    - To determine if the periodic wiggles seen in MERRA-2 data are physical."
Answer: 205297.0

User story: "The modeling of the MERRA-2 timeseries using kernel method was good but slow.    I am now testing Long short-term memory (LSTM) method :    [^timeSeries.py]    and the result :    !Capture d’écran 2019-05-28 à 12.04.48.png!"
Answer: 59196.0

User story: "Zipping the bboxes only works if objects are same length, so check that first."
Answer: 835.0

User story: "Ticket for the work being done in Chile with Aux Tel. "
Answer: 22770.0

User story: "This is a proof of concept showing that we can run a bokeh app initially developed for SQuaSH inside a notebook in LSP.    A complete solution implies linking the science pipeline metrics tracked by Chronograf to the corresponding notebook in LSP which is related to the QA WG recommendation 36 (DM-18056)     This work was done by [~<USER> and [~<USER> using the SQuaSH AM1 app as an example:    https://github.com/lsst-sqre/squash-bokeh/tree/master/app/AMx     "
Answer: 7.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: "Quoting [~<USER> on DM-19851:   {quote}By the way, after looking at the quantum SQL a little more closely yesterday, I don't expect (but do hope for) big improvements to execution time until we do one of the following:   * materialize the views used in the SQL   * remove the distinct from the view definition and confirm Oracle properly rewrites the SQL for an efficient plan   * remove references to the views and rewrite the generated SQL to reference the base tables (my preference since it will make further optimizations easier though I understand others wanting to try one of the other approaches first){quote}   Materializing the views is the hardest of these, as it would require much more complex logic in the code that updates the underlying tables.    Removing the DISTINCTs from view definitions is quite easy; I'll do that first on this ticket for some timing tests, and proceed to removing use of the views in the query generation - that's a bit trickier, but certainly still doable.  I *think* some of the DISTINCTs are completely unnecessary (including what may be the most important one, in {{exposure_calibration_label_join}}), and ones that aren't actually shouldn't be appearing in the big query we're running at all - and if they appear in similar queries in the future, I think removing the DISTINICTs from them would only change the query results in a way the result-processing code wouldn't notice."
Answer: 175902.0

User story: "SkyMap uses lots of lsst.afw.geom when it mostly only needs to use lsst.geom.  Replace the afwGeom where appropriate."
Answer: 82.0

User story: "The Header Service reads in the primary and segment hdu from templates that define the content of the headers. The fitsio (Erin Sheldon's) module doesn't not preserve or store this at the moment. We need to make a request to make sure that these can be read, stored and passed on to the output files created by the HeaderServiuce."
Answer: 10137.0

User story: "This task covers the work to finish the export of the ts_xml job into the TSSW Jenkins instance.   * Configure and run the ts_xml job.   * Create a Jenkins user on the LSST GitHub organization to use for Job Credentials."
Answer: 86528.0

User story: "The {{RunIsrConfig}} class was omitted when {{__all__}} was added to {{isrTask.py}}.  This breaks running `RunIsrTask` more than once with the same rerun but different data ids.  Adding the configs fixes this."
Answer: 209.0

User story: "dds salobj is not compatible with SALPY. See the last comment for details of what was wrong."
Answer: 17675.0

User story: "Update the scripts in ts_standardscripts to work with dds ts_salobj and schema+dds ts_scriptqueue"
Answer: 11450.0

User story: "This whole sprint is this. [~<USER> don't forget to fill this out."
Answer: 26174.0

User story: "This sprint will literally be this. [~<USER> Don't forget to fill this out."
Answer: 27330.0