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: "In DM-20849 I added a {{current_tai}} function to ts_salobj. However, it works by calling {{time.time()}} and converting it to TAI using {{tai_from_utc}}. This is likely to be slightly off very near a leap second transition. (Fortunately we are not expecting one anytime soon, so there is time to deal with this).    The proposed long-term solution is to call Linux function {{clock_gettime(CLOCK_TAI, ...)}}. There are a few subtleties:  * By default this will return UTC, not TAI. Only on systems with a an NTP or PTP daemon configured to set the current TAI-UTC will this actually return TAI. We need to decide how to handle this. At present very few of our current CSCs have ptp or ntp configured such that CLOCK_TAI returns the correct value. This will, of course, change -- at least for deployed software. I am less sure if we can make it happen for our development environments.  * Even if TAI-UTC is not zero it may still be incorrect. That is harder to handle and I do not propose to try to detect it in salobj. It can easily be checked in the Watcher or by an EFD monitor.  * Some operating systems do not have CLOCK_TAI, including macOS. However, we think all our deployment or development systems support CLOCK_TAI.    Options include:  * Silently return UTC (as SAL does). I hate silent failures, but it makes for simple code and is a appropriate choice if our systems are almost always correctly configured (even our development environments).  * Raise an exception. This seems far too drastic.  * Return TAI (correct the time using AstroPy). This is rather complex, but I believe it necessary if we adopt this code now, because few CSCs have ptp or ntp correctly configured.    I think salobj should also provide a way to test CLOCK_TAI, e.g. return TAI-UTC. CSCs could do this as they start up and log a message if ptp is mis-configured.    I am inclined to do two things:  1) Silently return UTC  2) As a CSC starts up test the value to see if it matches UTC, and if it does, log a warning about clock error.    Another option is to use ts_sal directly, but this has several issues:  * At present ts_sal only makes the functions available as part of a SALPY library, and in particular as part of the SAL object. It is not safe to construct a SAL object in code that uses OpenSplice dds (it leads to segfaults). In any case we will want a smaller more focused library.  * We still have to perform the checking mentioned above. ts_sal's getCurrentTime function silently returns UTC not TAI unless something such as an ntp or ptp daemon is properly configured."
Answer: 386023.0

User story: "New rpms for ts_xml 4.1.1  and ts_sal 3.10.0 are available and ready to be tested and integrated with ATCamera and ATArchiver."
Answer: 2507.0

User story: "The linear stage, when given a value outside the range (meaning larger than 75mm) accepts the command and returns a 303, however, the stage doesn't move. It also doesn't appear to take values after a 77mm is sent as a command.     "
Answer: 24033.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: "ci_hsc_gen3 loads calibrations into the Registry database via raw SQL dumps.  This is fragile to schema changes and assumes SQLite.    My tentative plan is to replace these with Butler/Registry API calls fed with either YAML data or Python literals (e.g. lists of dictionaries)."
Answer: 40220.0

User story: "Reprocess the HSC RC2 dataset, as defined in DM-11345, using Stack w_2019_34.     pipe_drivers / pipe_tasks  # {{makeSkyMap.py}}  # {{singleFrameDriver.py}}   # {{jointcal}}   # {{skyCorrection.py}}   # {{coaddDriver.py}}    # {{multiBandDriver.py}}.     pipe_analysis   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    qa_explorer  # matchVisits.py     validate_drp   # matchedVisitMetrics.py   # validateDrp.py   # reportPerformance.py    Upload the validate_drp metrics (json files) to SQuaSH:   # dispatch_verify.py  "
Answer: 34733.0

User story: "Work with TMG to come up with initial dashboard for monitoring incident and request tickets."
Answer: 3042.0

User story: "Discuss TMG suport nd processes for other projects, and begin to map out needs for LSST."
Answer: 3043.0

User story: "Looking into how Rucio can be deployed, including security concerns. Work with ICI to configure and test."
Answer: 417367.0

User story: "Instantiate an instance of the LSP for Commissioning use, based on requirements from  DM-21076."
Answer: 165602.0

User story: "Work with designated commissioning team staff to understand who will need access, if separate resources are needed, and any other specialized data and configurations.    The scope is the initial instance of the LSP for commissioning activities in Tucson; however we will keep in mind the future needs when commissioning activities begin in Chile."
Answer: 156802.0

User story: "Add TSTN (and OPSTN and SITCOMTN) to the www.lsst.io landing page."
Answer: 123.0

User story: "Concerning: *DMS-REQ-0004 (Priority: 1b):  Nightly Data Accessible Within 24 hrs*     The value of a parameter should not form part of a requirement title. This requirement should be updated to state something like     *DMS-REQ-0004 (Priority: 1b):  Nightly Data Accessible  Within Specified Time*  (aka DMS-REQ-089) , with the specified time, L1PublicT (24h) defined as a parameter of the requirement  "
Answer: 106851.0

User story: "Analyze the results of MultiProFit task output running on some COSMOS/HSC patches, including runtimes and comparisons to meas_modelfit."
Answer: 115597.0

User story: "Run the new MultiProFit task (DM-20728) on COSMOS/HSC (UDeep) data - a patch or two - to verify that it works and for further analysis."
Answer: 16000.0

User story: "Please add a `make_idl_files.py all` option such that idl files will be generated on what is located in subsystems.xml. This helps facilitate the building of conda packages for ts_idl. "
Answer: 141.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 propose to use `aioinflux` a new Python client for InfluxDB which has several advantages over `influxdb-python`. See https://aioinflux.readthedocs.io/en/stable/usage.html#    In this notebook, we configure the client to access data from the DM-EFD deployment at the AuxTel lab and show simple analysis using Pandas dataframes."
Answer: 3273.0

User story: "To provide a framework for writing tests of the spectrograph without having it physically plugged in, we need a way to mock the connection/library. {{unittest.Mock}} provides a simple system for this. Once that's written, I can later leverage it to build the spectrograph simulator."
Answer: 8797.0

User story: "We are trying to remove usage of pex_policy but there are still some places where it is used. Some of these come from {{pexConfig.makePolicy}}. Analyzing the code it looks like it would be fairly straightforward to replace those with calls to {{pexConfig.makePropertySet}}."
Answer: 17270.0

User story: "pex_config has confusing copyright messages and depends on packages it doesn't really need. This ticket is to clean it up a bit to make it more obvious what the issues are relating to making the package usable externally."
Answer: 7297.0

User story: "Write up the design for how we would do traditional crowded-field detection and photometry in DRP if it is accepted as in scope for construction."
Answer: 119632.0

User story: "/datasets/DC2/repo has the (old) DC2Run1.2i data.     The Princeton team would like monthly reprocessing of at least one tract, before  DM-17421 defines a better subset. "
Answer: 46066.0

User story: "<USER>was having issues with re-running pipeline on output collection:  https://lsstc.slack.com/archives/C2JPT1KB7/p1566508300359600  {noformat}  If I change the output collection with -o something, the first attempt fails with QuantumGraph is empty (even with @hsinfang’s updated -i arg above), while the second attempt fails with Output dataset icSrc_schema already exists.  {noformat}    I do not expect to be written if QuantumGraph is empty , need to check what is happening."
Answer: 30255.0

User story: "It seems that a cli parameter, once associated with an environment variable, can't be associated with a different one.     "
Answer: 1214.0

User story: "The implementation of RFC-617's DM-20548 effectively breaks {{meas_mosaic}} and the RFC calls for its deprecation. Please perform the necessary steps to remove it from {{lsst_distrib}} and move it from the lsst GitHub organization to that of lsst-dm (as a legacy repo?)"
Answer: 430.0

User story: The {{fgcmcal}} "Forward Global Calibration Method" calibration is adding a new dataset type and product in the form of the usual {{photoCalib}} object (called {{fgcm_tract_photoCalib}} but currently only defined in {{obs_subaru}}, see DM-16704).  The scripts in {{pipe_analysis}} require updating to allow for the option of applying {{fgcm}} photometric calibrations in lieu of the {{jointcal}} ones.
Answer: 262221.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: "Some changes needed to support 20812 changes to the butler datastores."
Answer: 5476.0

User story: "Answer questions related to Gen3 processing based on my previous experiences running Gen3 pipelines.    This is mostly to collect questions. Based on the feedbacks here I may create additional tickets as appropriate. "
Answer: 151150.0

User story: "DM-20732 (soon to be merged) changes the XML to publish new values (essentially forwarded from the ATPng CSC) and publishes telemetry as arrays. The simulator needs to be updated to reflect this functionality."
Answer: 19789.0

User story: "AT Spectrograph CSC needs to have the instrument port, to which the instrument is installed, as part of the configuration. This then needs to be reported such that the AT header service can capture the value."
Answer: 993.0

User story: "Capture work from CAP-329    Based on discussions on June 19, 2019 several header updates were agreed upon. This ticket incorporates those decisions into the header service.      https://jira.lsstcorp.org/browse/CAP-329"
Answer: 7264.0

User story: Bunch of logging messages from qserv uses explicit "QI=12345" (or "QI=12345:123") to identify query ID. It would be better to replace it with a logging context if possible.
Answer: 23128.0

User story: "The SAL Kafka producer (DM-20911) creates topics and upload their schemas to Kafka. As a consequence, we don't have the initialization step where we uploaded the schemas to the Kafka schema registry and configured the InfluxDB Sink connector. Given that we don't know the topics in advance, we need an application that runs as k8s cronjob that from time to time re-configures the InfluxDB Sink connector based on the current list of topics. The time interval fo the connector reconfiguration should be larger than the SAL Kafka Producer initialization.     In this ticket we also will extract the existing code to manage the connectors from   {{kafkaefd-demo}} and migrate to the new application {{kafka-connect-manager}}.   "
Answer: 21635.0

User story: "Test the SAL Kafka producer developed in DM-20911 with the following CSCs running at the   AuxTel lab:    {{ATCamera}}, {{ATHeaderService}}, {{ATArchiver}}, {{ATMonochromator}}, {{ATSpectrograph}}, {{Electrometer}}, {{Test}}, {{ScriptQueue}}, {{Script,}} {{ATPtg}}, {{ATMCS}}, {{ATDome}}, {{ATDomeTrajectory}}, {{ATPneumatics}}      "
Answer: 40576.0

User story: "- Update the milestones repository with data extracted from PMCS (/)  - Update LDM-503, LDM-564, images repository (/)  - Update milestone dates loaded into Jira (/)  - Update skeleton July 2019 monthly report (/)  - Circulate upcoming milestone list to dm-cams  - Audit and update https://confluence.lsstcorp.org/display/DM/DM+PMCS+Update+Requests"
Answer: 79462.0

User story: "Current forwarder code fetches a single ccd at 0.11 second. Generalize current forwarder code to fetch a raft."
Answer: 97875.0

User story: "Put nublado on lab kub3s; use GH OAuth."
Answer: 29133.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: "DIMM CSC needs to be upgraded to SalObj 4 and also become a configurable CSC."
Answer: 140385.0

User story: "Environment CSC (e.g. Weather Station) need to be upgraded to a Configurable CSC and to salobj 4. "
Answer: 71449.0

User story: "walk through ts_xml 4.1.1. build"
Answer: 22873.0

User story: "This task covers the time to release v4.0.0 of SAL, update the tests accordingly, as well as work with [~<USER> to train him on the SAL release process."
Answer: 22912.0

User story: "This task covers the time to release v4.1.1 of the XMLs, as well as work with [~<USER> to train him to cover this work when I am unavailable."
Answer: 14325.0

User story: "Dear Gabriele and Michelle,    Is the new Jira-based version of LDM 503-8b ready to look at?    Thanks,  Michael"
Answer: 2832.0

User story: "Task in preparation for the next AuxTel on-sky testing. Need to organize notebooks with tasks to raster around a position and to offset for acquiring a target. "
Answer: 11289.0

User story: "One of the tasks in preparation of the next on-sky tests with AuxTel is to get the ATTCS class and scripts in the standard script repository.          Write Startup and Shutdown scripts."
Answer: 28499.0

User story: "[~<USER> has transferred the new Run2.1.1i agn-test simulation data over to lsst-dev at   {{/project/shared/data/desc_dc2/run2.1.1i-agn-test/}}    There should be 257 visits(45896 sensor visits).    I plan to run the 3 driver tasks: singleFrameDriver.py   coaddDriver.py  and  multiBandDriver.py    and the necessary makeSkyMap.py     Meanwhile we'd like to capture missing information and document them at https://confluence.lsstcorp.org/display/DM/Notes+on+reprocessing+datasets+in+Gen+2   I'll be dumping every little steps in the comments of this ticket.  If anything surprises you or you feel missing in the existing documents, please let me know.     "
Answer: 38789.0

User story: "Get the Labview Real Time software installed onto two machines so that we can run them to simulate the PXI controllers for the TMA"
Answer: 99406.0

User story: "Make a helm chart for deploying nublado."
Answer: 11567.0

User story: "When trying to run the S3 datastore tests, with boto3 and moto installed, they fail unless some values are present in a {{~/.aws/credentials}} file. This is not a friendly way to run the tests for people who haven't got S3 configured on their system.    Please update the tests so that they either pass the fake credentials into the relevant test routines, or else the tests set {{$AWS_ACCESS_KEY_ID}} and {{$AWS_SECRET_ACCESS_KEY}} in {{setUp}} or {{setUpClass}}."
Answer: 1705.0

User story: "Fix the M2 configuration editor by MATLAB, which has the broken GUI with missing button, text, and configuration files.         PS. Use the story point of [DM-20998|https://jira.lsstcorp.org/browse/DM-20998]."
Answer: 5786.0

User story: "We need to add documentation for the expression syntax understood by exprParser."
Answer: 22835.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-10000 implemented some useful code to rebuild and display meas_modelfit's CModel results, but this is no longer working correctly."
Answer: 1199.0

User story: "We need to find ways to add more information to commands being rejected by salobj powered CSCs, specially when the CSC is in fault state.     I think a good solution would be to add an attribute to the BaseCSC class that the user fill out whenever the CSC goes to fault state. Then, when rejecting a command, salobj can add that string to the ack so the user know what happened without the need to go to errorCode. "
Answer: 201893.0

User story: "Changes in {{lsst-sqre/terraform-efd}} have broken {{lsst-sqre/terraform-efd-k3s}} and the later needs to be updated."
Answer: 594958.0

User story: "The new S3Datastore duplicates a lot of logic from PosixDatastore. This is fine in the short term but we need to try to refactor a bit to prevent bugs appearing when a fix is made in one datastore but not the other."
Answer: 11907.0

User story: "Many members of community broker teams are not LSST project members and so do not receive information communicated via usual project channels (slack, community).  An LSST 'information for brokers' webpage similar to the [LSST Information for Scientists|https://www.lsst.org/content/lsst-information-scientists] page could be a good way to communicate with the wider community"
Answer: 136908.0

User story: "The Hub PV needs to be writeable by the jovyan user.  Not an LDF issue since that's a local directory, but it is an external PV at Google."
Answer: 76245.0

User story: "The DSM XML needs to have the following additions to its XML:   * A settingsApplied event now that it is configurable.   * A config file attribute added to DSM_configuration topic"
Answer: 4531.0

User story: "Check the SAL Telemetry in M2 controller. In the previous time, I had rebuilt and re-deployed the M2 cell code in cRIO and there is the connection between M2 controller and cRIO now. However, it looks like there is no SAL telemetry. This task will dig into code to try to fix it."
Answer: 11455.0

User story: "Review the walk-through record of hexapod and rotator software in the following link:    [https://confluence.lsstcorp.org/display/LTS/Software+Code+Walkthrough#/]         PS. Put the story point of [DM-21014|https://jira.lsstcorp.org/browse/DM-21014] here."
Answer: 11458.0

User story: "Attend the LabVIEW core 3 training in CA."
Answer: 27082.0

User story: "Implement the translators for the SDSS DR7 files (and DR9 as a stretch goal)"
Answer: 10186.0

User story: "The daf_persistence DbAuth code is C\+\+ wrapped into Python.  We no longer need it to be accessible from C\+\+, and we need more capabilities to handle a variety of database connection strings."
Answer: 5690.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 .robot file only tests to see if the logger and sender successfully run. It does this by only running the sender when the logger is running.    It however currently does not tests to see if ever event for that subsystem is sent. This task is to do this. There is a looping mechanism that rob has in place to retrieve what the events for a subsystem are I can utilize that work into this."
Answer: 28299.0

User story: "Create the script to generate the .robot file that tests the commander controller communication."
Answer: 31175.0

User story: "A continuation of [] creating the scripts to generate the .robot files that test the single file Java Telemetry programs."
Answer: 31177.0

User story: "Substantial time was taken out of my week meeting renters to rent my home. Visiting the vet to prepare required paperwork for the move. Visiting dealerships to sell my car. Emailing Erin and the rest of HR to get my ticket planned. Calling the airlines to ensure my dogs can board. Meeting with the movers to move all my household goods.     This task capture that time."
Answer: 6733.0

User story: "This task was to learn how robot framework and Jenkins interact with each other. This consists of     - Learning the .robot file syntax and the built in keywords to do various tests.   - The Jenkins manager and how it runs and displays the .robot files online.   - The robotframework_SAL repo and the scripts is contains along with how to run them and what they generate.   - The robotframework_salgenerator repo and the scripts it contains along with how to run them "
Answer: 6768.0

User story: "Add a separate column for  1a requirements"
Answer: 49191.0

User story: "After some investigation by [~<USER> we have learned that the {{lsst/\_\_init__.py}} files do not need to import {{lsstimport}} from the {{base}} package. The library loader flags are no longer relevant for our pybind11 packages.    Furthermore we have learned that the {{lsstcppimport}} _is_ required but is only required by some packages that are using afw C++ interfaces.    We therefore propose the following:    1. Replace lsstimport.py with an empty stub file that does nothing.  2. Force afw to import lsstcppimport.    In a later ticket we will remove the {{lsst/\_\_init__.py}} files from all the LSST python packages. Once that is done {{lsstimport.py}} can be removed from {{base}} package."
Answer: 4134.0

User story: "Write a setup.py for ts_sal so that scripts and python code will be placed on the path. "
Answer: 42989.0

User story: "The new version of salobj that uses the dds library is not providing an informative error message if someone tries to pass an index to a non-indexed component. This task is to improve that.         It would also be good to have some warning issued if an indexed component is instantiated with index=0. It seems like this is ok and means that the listener will listen to all indexed, but we probably want at least a warning. "
Answer: 12632.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 discussing this idea with [~<USER>, we agree that it would be easy and very helpful to add a new method (e.g. {{aget}}) which is an async version of the "get" method. The method would work by either giving the newest value of a topic or wait until a new value is available.
Answer: 13842.0

User story: "As originally proposed in [DMTN-098|https://dmtn-098.lsst.io/], {{MetricTasks}} are responsible for aggregating metrics to any desired level of granularity. This capability has never been used and is unlikely to be needed in the future (SQuaSH's Chronograph UI already supports aggregation implicitly). On the other hand, it makes MetricTasks much harder to write (in particular, they can have much more complicated failure modes) and requires flexibility in inputs that the Gen 3 framework considers undesirable.    Give each MetricTask a well-defined granularity. This will require breaking, and therefore simultaneous, changes to:  * The MetricTask API documentation  * The MetricControllerTask code (should still support MetricTasks that do a many-to-one transformation, though none exist at present)  * The MetricControllerTask API documentation  * discussion of inputs and philosophy in DMTN-098  * MetadataMetricTask and PpdbMetricTask  * all concrete MetricTasks    No changes to {{ap_verify}} should be necessary."
Answer: 33021.0

User story: "Apply for the Github LFS (100 GB) for T&S team. This to hold some large files in linux directory of code by Moog.      The repo ([https://github.com/lsst-ts/M2_Hexapod_Rotator]) we have on github has no this directory because we do not have the enough space to hold it. From the document by Moog, some files in this linux directory have been customized to build the control code in cRIO. Therefore, we need to hold it until we figure out where are those customized files and magic parameters/ numbers.     The price is in the following:      [https://help.github.com/en/articles/upgrading-git-large-file-storage#purchasing-additional-storage-and-bandwidth-for-an-organization]      I propose to hold at least 100 GB for T&S team to use (around 10 dollars per month based on the above link).    Thanks!"
Answer: 33225.0

User story: "The script lsstsw/bin/deploy is installing the latest miniconda available, 4.5.12. This comes with conda version 4.5.12.     In order to be able to use conda-forge 3rd party packages, we need a newer conda.    Conda 4.6.14 will work but probably is preferable to use a more recent one, like 4.7.11."
Answer: 10311.0

User story: "Once the software is officially delivered to LSST, it will be necessary to update the design and code to conform to SAL constraints and conventions, as defined in [https://confluence.lsstcorp.org/display/SYSENG/SAL+constraints+and+recommendations]    This includes:   * Naming conventions   * Enumeration definition   * Implementation of all standard commands and events.    This task will be with [DM-21699|https://jira.lsstcorp.org/browse/DM-21699#]."
Answer: 726232.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "move audit trail out of SYSAUX tablespace.    configure audit policy to track logon information.    configure retention policy for audit trail.    create daily report to summarize logon activity."
Answer: 3202.0

User story: "During the practice talk for the PCW, Zeljko requested the DCR simulations be re-run for very crowded fields."
Answer: 53267.0

User story: "In {{pipe.base.IdValueAction}} has code to parse id strings from the command line, but it's mixed in with {{argparse}} deeply enough that people who need to write custom TaskRunners can't use it.    I pulled this code out into {{cp_pipe/utils.py}} as {{parseCmdlineNumberString()}} but this is somewhat duplicative, and should therefore be removed, with this functionality neatly factored out in {{pipe_base}} so that it, and {{cp_pipe}} can use it."
Answer: 18535.0

User story: "nbreport users would like to include assets alongside the templated notebook, and have those assets copied into place when the report is instantiated. These assets might be Python modules that the notebook imports. Or it might be image files or general data files, or a directory tree full of data files.    nbreport can support this by adding a configuration key to the {{nbreport.yaml}} file format. The copy-on-instantiation feature should replicate any directory structure of these assets relative to the notebook."
Answer: 27233.0

User story: "In discussion on [#dm-middleware|https://lsstc.slack.com/archives/C2JPT1KB7/p1565369360160500] it was suggested that we need to extend our new parser to support range-based selection with a syntax like  {code}  visit IN START..STOP  visit IN START..STOP:STRIDE  {code}  (and for {{NOT IN}} as well). {{STOP}} here is inclusive, similar to existing syntax in CmdLineTask parser.    Opening this ticket to work on a syntax extension and its translation to SQL.  "
Answer: 16424.0

User story: "The current Makefile for the [technote_latex template|https://github.com/lsst/templates/tree/master/project_templates/technote_latex] runs xelatex and BibTeX manually. However, this fails on the first-run experience because there aren't any citations, and BibTeX fails. Using latexmk is a solution because it's smart enough to know whether BibTeX needs to be run in the first place or now."
Answer: 152.0

User story: "With SALPY phasing out, we need to take a good look at what it's going to take to make a salobj version of the components.  I expect that ATArchiver and the ComCam Archiver will be quite similar."
Answer: 30643.0

User story: "Make the ATDome SAL component non-indexed.  This requires using index=0 instead of index=1 in all code that talks to ATDome."
Answer: 5595.0

User story: "Update nbreport's dependencies and compatibility with Jupyter. See https://github.com/lsst-sqre/nbreport/issues/11"
Answer: 130.0

User story: "Attend PCW 2019"
Answer: 17107.0

User story: "Image display + File monitor integration    Used threading to get modules running together after not much success with asyncio approach"
Answer: 69163.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: "Attend LSST 2019 project meetings"
Answer: 56409.0

User story: "Test the new features of SAL V4 and the deployment mechanisms"
Answer: 116921.0

User story: "Remove use of the {{future}} package in {{lsst.verify}}.    Also fix third party packages that were accidentally removed in DM-17205."
Answer: 374.0

User story: Improve SQR-032 based on comments from the team.    [~<USER> writes:    • §5.2: we do have C++ unit tests: https://developer.lsst.io/coding/unit-test-policy.html#testing-frameworks  • §5.3: this particular one ought to be deleted; any others should likely have sample code showing how to use the data file.  • Do you have any suggestions for giving doctest-style examples for inherently time-based or otherwise non-deterministic code (like the notebook sanitization below)?  As one trivial example, how would one document lsst.daf.base.DateTime.now()?  • There are a few typos and grammar issues. §6.4 "to produce examples in", §7.1 "of which ... part of", §8.1 "their", §9.1 "avilable", and probably more.
Answer: 26179.0

User story: "in ts_ATDome the run_atdome.py script uses custom code instead of the standard main CSC method. That is no longer necessary and it makes a bad example so update it."
Answer: 6725.0

User story: "The changes in DM-20154 should result in some code being deprecate-able. {{makeDistortedTanWcs}} and {{computePixelToDistortedPixel}} are the first ones that comes to mind, but there may be others (e.g. in ip_isr). We should use the deprecation decorators so we can remove that code later."
Answer: 129614.0

User story: "Create something to implement:    Keep last 10 experimentals, 15 dailies, 78 weeklies, and all releases.  Remove other tags for lsstsqre/sciplat-lab so that Docker Hub cleans them up."
Answer: 3158.0

User story: "Story covering time at the LSST PCW for 2019."
Answer: 18648.0

User story: "The MERRA-2 servers had changed the queries format.    The script to retrieve the table has been updated and the readme has been edited to provide more extended details on how to setup an access to the data.    [https://github.com/lsst-dm/fetch_merra2]"
Answer: 20479.0

User story: "Per today's discussion, this ticket asks that the {{suit}} package be modified to include a script that encapsulates the full build process for that package, including its dependency on an explicitly specified version of [Caltech-IPAC/firefly|https://github.com/Caltech-IPAC/firefly].    (The equivalent of this already exists in the IPAC Jenkins scripts repo for Firefly/suit builds, so the task here is just to ensure that that information is in the {{suit}} repo itself, to facilitate LSST-driven builds of the package.)    The Firefly version may be specified in the script itself or in a supporting data file.  [~<USER> has a mild preference for the latter, decoupling the build _logic_ from the version numbering.    This is a high-priority task as we wish to converge with LSST on an LSST-maintainable build process by the end of FY19."
Answer: 171187.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "I am drawing close to having a notebook that can be templated to produce a plot based on a CI run.  I'm not sure how to implement the rendering of the notebook with template variable filled in (there will be only one).  Options I see are:  1) Add another menu item like the templated query ID one  2) Add another dropdown that will eventually hold lots of possible notebooks    I will attach the notebook here when I'm happy with it."
Answer: 24274.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: "Attend PCW "
Answer: 518047.0

User story: "implement control logic for chiller always running when bulb is on"
Answer: 54818.0

User story: "Update AT Hexapod for salobj 4 and address any incompatibility that arises"
Answer: 40228.0

User story: "Do a formal release of astro_metadata_translator to PyPI.  This will include determining a formal version number and tagging the repository."
Answer: 4151.0

User story: Please add the Description and Units fields from the XML to the generated IDL files, especially the files such as sal_revCoded_ATCamera.idl that salobj uses.    The hope is to parse the IDL files to generate Avro schemas for the SAL kafka producer, and to be able to include descriptions and units in the schema browser.    Thus it would be a big help to have description and units comments be easily identifiable as such (for example by prefixing them with "description" and "units")
Answer: 54715.0

User story: "The current deployment of the Chronograf UI is still a demo (in the sense that we need to complete DM-18060 work).    However, to avoid confusion and direct (new) users to the Chronograf UI we decided to redirect https://squash.lsst.codes to http://chronograf-demo.lsst.codes."
Answer: 1333.0

User story: "DM-20842 added a location attribute to Formatter. It would be helpful if {{str(Formatter)}} returned the formatter name and location.  Also require the fileDescriptor argument."
Answer: 1468.0

User story: "update ATHexapod for salobj 4 compatibility"
Answer: 519551.0

User story: "Check the M2 MATLAB tool."
Answer: 2805.0

User story: "Invited presentation at [Scarlett deblending workshop|https://indico.ict.inaf.it/event/889/] on the LSP at 7-9 October   "
Answer: 123929.0

User story: "Implement the salobj to Kafka feeder as designed in DM-20910, including documentation and unit tests."
Answer: 41762.0

User story: "Design the salobj to Kafka feeder and negotiate with [~<USER> and [~<USER> about details of the schema. I hope they will be willing to change the Avro schema to match the DDS topics.    Another point to discuss is to consider using the IDL or Python topic data classes, instead of the XML files, to create the Avro schema. However, unless doing such a change requires me to write some code, this is a side issue.    Figure out how to write unit tests for this code.    The product will be a preliminary implementation, not necessarily tested."
Answer: 26192.0

User story: "Following the reviewer's suggestion, all the transmission variations (annual, overnight, 1-sigma RMSE) for both Mauna Kea and CTIO have been translated into Vera Rubin Telescope millimagnitude --> The last paragraph of the last section need to be rewritten."
Answer: 23708.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 seasonal wind trends are complicated to analyzed. The Eastward 2-D field does show a modulation (figure) but with a negative sign. Nonetheless, the vertical profile of the eastward wind (from the 3-D field) has a steady positive component in the tropopause in the winter (lower left panel).         !Capture d’écran 2019-08-05 à 10.03.44.png!"
Answer: 23749.0

User story: The authenticator misbehavior seems to be, according to minrk on the JupyterHub gitter, "bug specifically in SimpleAsyncHTTPClient."    Moving to pycurl should fix it.
Answer: 4294.0

User story: "This is the event at 8/12 - 8/16. The website is at:    [https://project.lsst.org/meetings/lsst2019/]"
Answer: 25878.0

User story: "This task is to continually review the document of hexapod and rotator. Record the questions and get the knowledge transfer from the previous owner.    The ticket for ssh help is [IHS-2490|https://jira.lsstcorp.org/browse/IHS-2490]."
Answer: 14241.0

User story: "Disable dask dashboard"
Answer: 217.0

User story: "This ticket is for compatibility issue when moving to conda 4.7.         Known: Conda 4.7 doesn't like conda clean for some reason, which doesn't play very will with lsstsw."
Answer: 420967.0

User story: "Prepare a 10-minute presentation on the {{verify}} API (both high- and low-level), the philosophy behind it, and how it is used to pass measurements from pipeline code to SQuaSH (should *not* be a how-to). Emphasize connections to the QAWG recommendations."
Answer: 24483.0

User story: "Assign a single scanner per JupyterHub instance and limit its refresh rate."
Answer: 265.0

User story: "The rebuild script [hard codes|https://github.com/lsst/lsstsw/blame/master/bin/rebuild#L40] a path in {{/tmp}} for saving environments and does not clean up after itself.  The script should switch to using {{mktemp}} to make a temporary location that will not collide with other users.    The blocking problem currently is that no one can build a stack on {{lsst-dev}} because the hard coded path is only writeable by one user.    This ticket should also implement the necessary logic to clean up the temporary location."
Answer: 93.0

User story: "Deploy simulators on provisioned ncsa test-integration-stand and run simulators on them. There is no docker, need to take care of things manually."
Answer: 79566.0

User story: "Write a conda recipe for ts_idl. As part of the task write a setup.py for it."
Answer: 86600.0

User story: "Github (at least, maybe other Oauth2 providers) isn't respecting whitelists anymore.  Fix it in our subclass and fix it upstream when I get around to the Tornado 6 work."
Answer: 62.0

User story: "MultiProFit currently print()s logging output directly. This ticket will create a basic Logger class to handle logging (and eventually pass messages to the stack's logging tools)."
Answer: 51876.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 the third parties are packaged and in conda-forge, make a new environment of our third party packages in conda-forge. Attempt to activate that environment and use the {{compilers}} meta package in conda-forge to build the stack, ideally with lsstsw, from scratch."
Answer: 89643.0

User story: "The code sample font size in the theme for pipelines.lsst.io (https://github.com/lsst-sqre/lsst-sphinx-bootstrap-theme) ought to be just a bit smaller so that an 80-character wide code sample can fit."
Answer: 215.0

User story: "Initial determination what types of information we currently have and what types of reporting information would be helpful.  Maybe some very rough prototyping of monitoring. "
Answer: 24.0

User story: "In DM-17295, qserv now doesn't require the qserv_areaspec functions in order to do the scisql region functions.  It should figure those out by itself using the scisql parameters.  So in the CADC TAP service, we can now get rid of the parts that are adding in the qserv_areaspec parts, and we don't have to replace it with anything!  Huzzah!"
Answer: 2841.0

User story: "As I will be traveling for much of September and October, [~<USER> has agreed to learn the SAL/XML release process in order to stand-in during my absence."
Answer: 27208.0

User story: "OAuthenticators do not play well with Tornado 6."
Answer: 7193.0

User story: "Add a index page for every task in {{lsst_distrib}} to https://pipelines.lsst.io.    This is a simpler version of the process-context-based documentation sections designed in https://dmtn-030.lsst.io/#processing-section, but it's something that is doable now with little effort.    This index page could either be linked from the homepage, or from a [Task framework page|https://dmtn-030.lsst.io/#frameworks-section]."
Answer: 13100.0

User story: "Update ATMCS simulator to show position limits once DM-20846 is implemented."
Answer: 61971.0

User story: "Please show the position of each position limit for each axis using a new ATMCS event. Thus the position of the L1 (software) limits for azimuth, altitude, NA1, NA2 and the M3 turret.    Use cases include:  - LOVE can display the position of each axis relative to its limits without having to hard-code values.  - ATPtg can base its limits on the reported L1 limits (instead of having to hard-code values and thus risk going out of date if we tweak the limits)"
Answer: 60564.0

User story: "Jim suggested in [#dm-middleware|https://lsstc.slack.com/archives/C2JPT1KB7/p1564158700036500] that {{pipetask}} can be improved by allowing developers to re-run it on the same output collection. Opening this ticket to understand possible use cases and implement necessaruy options in ctrl_mpexec to support those use cases.  "
Answer: 70780.0

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

User story: "Review the documents of hexapod and rotator in phase 1."
Answer: 3033.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: "Discussing DM-20763 with [~<USER> leads me to think that datastore should guarantee that  {{Formatter}} instances are not reused.  This would allow formatter implementations to cache information with the knowledge that they don't have to worry about the cache being wrong if the file descriptor changes.   To make this more obvious I'm going to investigate changing Formatter so that FileDescriptor is a mandatory constructor argument becoming a read-only property. This will make it impossible for the formatter to be used for any other file and will mean that the argument is removed from the {{read}} and {{write}} methods."
Answer: 7250.0

User story: "[~<USER> and [~<USER> report that most of the WCSs produced by meas_mosaic in hscPipe 6.x (all of those that correspond to sensors with rotations relative to the focal plane) are incorrect - the SIP coefficients are dropped after rotation.  This is seen both in the headers and in the binary table.    After a quick look at the code, I suspect this is only superficial, but still confusing: we rotate a WCS by prepending its mappings with a rotation using AST, which yields a WCS that cannot be represented as TAN-SIP without loss of precision.    First piece of this ticket is to check that hypothesis.  The second (assuming the hypothesis holds) is to come up with a way to reduce that confusion."
Answer: 272973.0

User story: "Following the description on DM-19473 of how these errors ought to be calculated.    Note that an expedient solution, which does not involve redesigning everything, is encouraged."
Answer: 30477.0

User story: "Create a notebook that can be run on the LSP to demonstrate improvements made to scarlet vs the old deblender."
Answer: 21752.0

User story: "Tables of capability over time for each use case would be helpful."
Answer: 2734.0

User story: "LSST IT would like a technote series called {{ittn}}, with the repos hosted at https://github.com/LSST-IT"
Answer: 990.0

User story: "Fork Spectractor to lsst-dm.    Clone sci-pipe conda env on lsst-dev and install dependencies as a user to cloned env.    Make ticket branch on fork from {{profile}} branch (which is the functional {{master}} for Spectractor at the moment) of Spectractor, and start updating code as discussed with Jérémy."
Answer: 407282.0

User story: "In https://sqr-032.lsst.io, we propose that scripts should have documentation pages:    - [Action: scripts are documented in package documentation|https://sqr-032.lsst.io/#action-scripts-are-documented-in-package-documentation]  - [Action: adopt argparse for command-line scripts to enable auto-documentation|https://sqr-032.lsst.io/#action-adopt-argparse-for-command-line-scripts-to-enable-auto-documentation]    This ticket is is to create templates for these pages in https://github.com/lsst/templates, and then document them in the developer guide alongside other topic types."
Answer: 11347.0

User story: "Make reposcanner's work not user-count dependent."
Answer: 11546.0

User story: "FIle Monitor for GenCam"
Answer: 83872.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "I have delivered to DESC PCWG convener N. Regnault a times series of atmospheric transmission above LSST that will be used to quantify the error on SNIa light curves."
Answer: 2352.0

User story: "The gnerateAcronyms should be modified to repeatably scan the glossary list (or write the file and use that)  until all related glossary items are included i.e. until the glossary stops growing.   It is commented currently that you have to run it repeatedly to get the full set as items pull in other glossary terms."
Answer: 44629.0

User story: "[~<USER> requests that we change all the storage class names starting with {{TablePeristable}} to drop that prefix.  The storage class should not be describing how the dataset type should be stored and by definition they are persistable."
Answer: 4005.0

User story: "By request of [~<USER>, try compiling FFTW with {{--enable-openmp}}.    Note that we don't want the DM code to link against the OpenMP version; rather, we just want to make available {{libfftw_omp}} for DESC use."
Answer: 452275.0

User story: "In discussion starting [here|https://lsstc.slack.com/archives/CJ7KBKQQZ/p1557759289148900] it is clear that {{obs_lsst}} camera geometry does not understand how the comcam data (through ts8 I guess) is being ingested/indexed.  Specifically, using master gives something like the following:   !image-2019-07-26-11-00-44-754.png|thumbnail!     I have made some modifications on a branch {{u/<USER>fix_ts8_ordering}} in {{obs_lsst}}.  This now gives the following:   !image-2019-07-26-11-03-30-093.png|thumbnail!     It appears that the master version of {{obs_lsst}} and the way the sensors are indexed on ingestion are at odds."
Answer: 367203.0

User story: "We recently found that the deadman alert on the {{validate_drp}} processing in the nightly was just looking at any data landing in the {{validate_drp}} measurements.  This meant that the if just one failed, there would be no notification."
Answer: 5729.0

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

User story: "To include IOD/OD and ephemeris prediction."
Answer: 121713.0

User story: "Split EFD writer image into one stream per container instead of three"
Answer: 31241.0

User story: "This package was not following python coding standards. Update and add travis check."
Answer: 121.0

User story: "Reprocess all the HITS 2014 & 2015 data that [~<USER> regularly checks, using DCR corrected templates. The results will be used to update DMTN-037 on DM-15340."
Answer: 92143.0