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: "Add unit test framework to [OpenOrb|https://github.com/oorb/oorb] (our adopted orbit integration engine).    This includes:    * A make target so running 'make test' will execute all unit and integration tests   * A few example unit tests (for versioning functionality)   * Running the python/test.py integration test    Unit test framework will use pytest. The idea is that all code (including command line utilities) will be tested via pytest drivers (to maintain uniformity).    The work will be on [https://github.com/<USER>oorb/tree/build-system-rework,] and will be PR-ed upstream upon completion."
Answer: 35977.0

User story: "Remove timestamp from the generate tex file. This information is redundant (already available in github) and has the undesired effect to update the document source even if there are no changes in jira."
Answer: 11180.0

User story: "Modernize the build system for [OpenOrb|https://github.com/oorb/oorb] (our adopted orbit integration engine).    This includes:    * Fix makefiles so parallel builds work   * Fix makefiles to correctly track and respect dependencies   * Compute and record version information in all binaries   * Update related documentation    The versions will be inferred from git. The makefile work is non-trivial because Fortran 90+ (with modules) and make interact poorly.    The work is ongoing at [https://github.com/<USER>oorb/tree/build-system-rework,] and will be PR-ed upstream upon completion."
Answer: 35981.0

User story: "Review laser tracker protocol interface docs, update text and diagrams to include new terminology (Laser Tracker CSC instead of Laser Tracker Controller, remove references to labview, etc). Our vendor, New River Kinematics, is proposing an API for communication between our CSC and their part of the code. Review this API and prepare feedback for meeting next week"
Answer: 31585.0

User story: "learn about how to package the CSC with docker, according to the grand LSE-150 plan. This has been ongoing for a while but will be a success when I have a docker container that runs the component and has all the required dependencies."
Answer: 31597.0

User story: "This task is for reviewing the TMA FAT documents.  Andrew Serio is leading this effort and tasked me to review a couple of documents, so this task tracks the time necessary to do so."
Answer: 5459.0

User story: "Update LDM-639 content from Jira"
Answer: 40039.0

User story: "Need to work some more on the release scenarios and talk to some people about things like alert possibilities .."
Answer: 67770.0

User story: "Following a discussion on community we have decided to adjust the calculation of detector_exposure_id and exposure_id to remove additional 0-padding between exposure ID and detector (3 digits for lsstCam rather than 4) and to have a maximum sequence number of 99,999 rather than 999,999. It would be good if we could get this done before v17.0."
Answer: 10564.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: "Loi has introduced jest as Javascript testing framework for Firefly.    We need to    - Update SUIT to use jest for javascript testing   - Move LSST specific java tests (LSSTDbServTest.java and LSSTImgServ.java) to suit."
Answer: 37245.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 Jan 2019 monthly report (/)  - Circulate upcoming milestone list to dm-cams (/)  - Audit and update https://confluence.lsstcorp.org/display/DM/DM+PMCS+Update+Requests (/)"
Answer: 20133.0

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

User story: "Meet with staff to incrementally refine initial list of activities into final activity plan."
Answer: 86331.0

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

User story: "Prepare list of project needs, milestones, activities, current status, staff availability, etc., as input into planning process.    Joel, Kaylyn, Margaret"
Answer: 36085.0

User story: "Need to purge topic when receiving the dreaded:    Error in DomainParticipant.create_topic: Creation failed: invalid handle"
Answer: 86461.0

User story: "Initial M2 Software setup @ Summit"
Answer: 5713.0

User story: "Move {{obs_lsstSim}} to the legacy area."
Answer: 551754.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: "At present the ATMCS CSC enables all axes when the summary state is Enabled. Unfortunately this includes the M3 rotator and also both instrument rotators. We should turn off power to drive motors that we are not using, unless the actuators go into an extremely low power mode when they aren't doing anything. Otherwise we generate unnecessary heat in the enclosure, which harms image quality due to roiling the air.    I propose the following solution:  1) Only enable the M3 rotator drive when executing the setInstrumentPort command.  2) The Nasmyth rotator drives are trickier because we might want to move one for engineering purposes regardless of the position of M3. So I suggest that we normally disable any rotator drive that M3 is not pointing at (that would be one or both rotators, depending on the instrument port). However, we also add new commands that lets us move either rotator for engineering purposes (not a command that the pointing component would ever send). If we can safely move a drive and then disable it and it will stay then it can be a pair of move commands (one per port) accept a position. The command enables that drive, moves the drive, and disables the drive (engaging the brake). I would also suggest that the command be prohibited for the current port IF tracking is enabled. (No need to prohibit it if the M3 is pointing to the other port, as there is no conflict). Full error handling will take a bit of work since we should also prohibit enabling tracking while executing the command, or moving M3 to that port while tracking...    I also propose that we prohibit moving M3 while tracking is enabled."
Answer: 188800.0

User story: "Reported to the Chronograf developers:    https://github.com/influxdata/chronograf/issues/5066"
Answer: 1401.0

User story: There are at least three options of timestamps that we can use to map the {{lsst.verify}} run time to InfluxDB.    * CI pipeline run time  * Verification Job time  * InfluxDB creation time     We are currently using the "Verification Job time" which turns not to be the right choice because we are running a different verification job for each {{dataID}}. As consequence, results that should have the same timestamp get inserted in InfluxDB at different times. A better choice for the InfluxDB timestamp seems to be the CI pipeline run time.  
Answer: 73549.0

User story: "When running   {code}  constructBias.py /datasets/ts8/repo-004 --calib /project/<USER>calibrations/ --output /project/<USER>test_output_dir --id imageType='BIAS' run=9120 --batch-type none --config isr.doCrosstalk=False --clobber-config  {code}  the following error appears:     {code}  AttributeError: lsst.pipe.drivers.constructCalibs.BiasConfig has no attribute doLinearize  {code}       Fix: change {{config.load}} to {{config.isr.load}} in bias.py, flat.py, dark.py (in obs_lsst/config/). "
Answer: 1701.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: pipelines.lsst.io is built by linking the \{\{doc}} directories of individual packages into the build of the {{pipelines_lsst_io}} repository. Right now any package that is set up by EUPS and has a {{doc/manifest.yaml}} file is linked. But this can accidentally include "external" dependencies of the Science Pipelines that aren't actually distributed with the Science Pipelines. This ticket is to is to make the linking code ensure that the package is explicitly listed in the table file before including it.
Answer: 6959.0

User story: "This is for a trip to IPAC to help with their kubernetes deployment of firefly and the portal.  I want to learn more about their architecture, their needs for multicast, and help out with their deployment story.  Mostly just for tracking some story points, as I'll be there for 2 days (and a couple of days of travel)."
Answer: 37559.0

User story: "Update supported browser list. We usually do this every 12 to 18 months.    Typically we try to support the current browser version plus 2 back or any browser version in the last year.    Update support browser list:    * Safari 9 => 10  (current: 12)   * Chrome 62 => 67  (current: 71)   * Firefly 56 => 60 (current: 65)   * Edge  14 => 16 (current: 18)    Upgrading the supported list provides the following:   * Allows for more confidence in the testing of our products.   * Allows for more stable version of library since they are limited in testing of old browsers   * Give opportunity to use newer HTML/CSS features such as Grid layout   * Requires less polyfills and code transforms. This allows more native code and smaller load sizes."
Answer: 38884.0

User story: "In DM-17461 we implemented a command to configure the {{influxdb-sink}} connector and deployed it initially as a k8s Job.    However, we need it working as a daemon to:    1) try creating the connector until the {{cp-kafka-connet}} REST API is ready  2) monitor the connector status and reset the connector if status is FAILED.    See https://docs.confluent.io/3.0.0/connect/userguide.html#connect-administration    This also makes the deployment easier, we can use the {{kubernetes_deployment}} resource from the Terraform k8s provider instead of the {{kubernetes_job}} resource which is not implemented in the official provider yet.  "
Answer: 9032.0

User story: "The LSP now includes the Firefly extension for Jupyterlab. This extension has been integrated with the Firefly backend to {{afwDisplay}} and simplifies the startup of the Firefly viewer. This ticket is for updates to the Firefly notebook curated by SQuaRE that take into account the new capabilities provided by the extension. Some cleanup of Markdown will also be proposed."
Answer: 47474.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: Developer Guida has to be updated with the result of DMCCB$3 discussion on "Board Recommended" usage.         When DMCCB approves a "Flagged" RFC, its status has to be set to "Board Recommended".    The RFC status is set to "Adopted" once triggering issues have been opened.    RFCs to approve baselined documents do not require triggering issues, therefore their status can be set immediately to "Adopted"
Answer: 21832.0

User story: "In order to verify the implementation of DM-17684, a Github/Jenkins/Eups test environment is required."
Answer: 79293.0

User story: "It should be fairly straightforward to implement autograd into scarlet (DM-17748), however automatic gradients alone can only accomplish so much. The problem of calculating step sizes still remains and many accelerated methods that automatically calculate step sizes do not seem to work out of the box with proximal operators. This ticket is to investigate the Adam algorithm (Kingma and Ba 2015) to see if there is a way to make it robust in cases where we take proximal gradients, such as our optimization in scarlet."
Answer: 375995.0

User story: "Thanks to the help of Erin Sheldon and his former student Lorena Mezini we discovered a few fatal flaws in scarlet that need to be corrected in order to generate lensing quality models. The main flaws are due to the way we fit positions and the way we do PSF convolutions. Both of these can be corrected by using a higher order sinc interpolation as opposed to a linear product of matrices, however taking the gradient of these functions is non-trivial.    This is exactly the problem that tensor flow (and pytorch in python) seek to solve, and do so much faster than we can calculate our gradients by hand. So this ticket will be to implement the pytorch autograd function in scarlet to calculate the derivatives."
Answer: 110047.0

User story: "I removed a bug that I introduced to develop. It prevented scons from being able to run. I plan on meeting for a day with [~<USER> to be able to hack out this feature. "
Answer: 17673.0

User story: "Update existing filesystem documentation."
Answer: 1.0

User story: "Understand future production filesystems needs, e.g., as needed by enclaves specified in LDM-129."
Answer: 1.0

User story: Look at current usage for "production" filesystem at the LDF.
Answer: 5.0

User story: "          https://confluence.lsstcorp.org/display/DM/Data+sets+used+for+DM+Verification+and+Validation"
Answer: 436664.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: With w_2019_04 lsst_distrib and master obs_lsst at the time, "RangeError" is seems in makeCoaddTempExp in several tracts of imsim DESC Run 1.2i data. An example to reproduce is:  {noformat}makeCoaddTempExp.py  /datasets/DC2/repo/ --rerun w_2019_04/sfm:private/username/yours -c doApplyUberCal=False --id tract=4432 patch=4,5 filter=g   --selectId visit=183892  {noformat}  which gives:  {noformat}makeCoaddTempExp INFO: Processing calexp 1 of 1 for this Warp: id=DataId(initialdata={'visit': 183892, 'filter': 'g', 'raftName': 'R34', 'detectorName': 'S12', 'detector': 158, 'tract': 4432}, tag=set())  makeCoaddTempExp.warpAndPsfMatch.psfMatch INFO: compute Psf-matching kernel  makeCoaddTempExp.warpAndPsfMatch INFO: Cannot PSF-Match:     File "src/WarpedPsf.cc", line 72, in lsst::geom::Box2I lsst::meas::algorithms::{anonymous}::computeBBoxFromTransform(lsst::geom::Box2I, const lsst::geom::AffineTransform&)      Unexpectedly large transform passed to WarpedPsf {0}  lsst::pex::exceptions::RangeError: 'Unexpectedly large transform passed to WarpedPsf'    makeCoaddTempExp INFO: directWarp has 349480 good pixels (2.0%)  makeCoaddTempExp INFO: psfMatchedWarp has 0 good pixels (0.0%)  makeCoaddTempExp INFO: Persisting deepCoadd_directWarp  {noformat}  FWIW, this wasn't seen in last year's processing using {{w_2018_49}}.
Answer: 8914.0

User story: "Final testing and planning for Feb. PM"
Answer: 22857.0

User story: "Implement temporal search box content for TAP search.   The box includes the following components for temporal search,      - Entries to enter 'from' and 'to' time - the time could be entered in date/time format (eg. yyyy-mm-ddhh:mm:ss) or MJD numbers. A React date/time picking component is to be discovered and used to assist entering the data/time value.       - text message displays the time value in the format different from that in the entries. (i.e. if the time value in the entry is in date/time format, the text message will show the value in MJD, and vice versa).        "
Answer: 31701.0

User story: "This story  mostly involves engaging the CILogon/Auth team on federated login, and working to resolve some configuration issues, as well as documenting what goes in a token    * We need to verify which claims that are returned by CILogon, and which claims to rely on  * We need to verify those claims are standardized for all identity providers, including NCSA as the identity provider  * jwt_authorizer needs to be modified to honor those claims, if necessary  * documentation needs to be written and information communicated to the portal/notebook implementers, if necessary  * help out, if requested, with coming up with a process to handle configuration and deployment of LSST-Specific features for CILogon oauth2 clients    Some of this is done, but it needs to be concrete so we don't have issues in the future"
Answer: 29153.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: "Clean up the code in these various repos, try to get them into github.com/lsst and some code reviews once done.         For oauth2_proxy, do some cleanup work and issues some PRs to the upstream repo, github.com/pusher/oauth2_proxy."
Answer: 23327.0

User story: "Implement a token issuer (aka reissuer aka token proxy). This involves setting up private keys, and probably reusing the existing jwt_authorizer code as the repo for this"
Answer: 29161.0

User story: "With the release of new versions of pycodestyle and flake8 that support max-doc-length, we can update our eups packages to allow packages to use max-doc-length in their setup.cfg files."
Answer: 4347.0

User story: "Write a python 3 interface to the Andor sCMOS Zyla camera for early AOS and Guider testing."
Answer: 321786.0

User story: "Upgrade react and related components from 16.2 to 16.8    * don't upgrade redux   * upgrade any other react components.   * only do webpack and babel         Implemented:    * upgraded React.js to version 16.8  * converted AdvancedADQL to use react hooks which is a big feature of this release    The converted file make use of the new useState and useRef hooks, as well as demonstrate how updated props can be compared directly in the render function.  It serves as a test for the upgrade as well as demonstration of how new features are used.    Here is a complete changelog for react:  https://github.com/facebook/react/blob/master/CHANGELOG.md#1680-february-6-2019    This blog highlight some of the changes in v16, up to v16.7.  https://hackernoon.com/react-16-0-16-3-new-features-for-every-day-use-f397da374acf    Summary of the blog:    * Returning multiple elements from components with fragments (16.2)   <React.Fragment>   …   </React.Fragment>   or   <>   …   </>  * Returning strings and numbers from components  * Cancelling setState() to avoid rerendering  * Avoiding prop drilling with the official context API (16.3)  * Updating state based on props with getDerivedStateFromProps() (16.3)  * Re-rendering function components on props change with React.memo() (16.6)  * Easier access to context in class components with contextType (16.6)"
Answer: 49098.0

User story: Add package "tables" to scipipe_conda_env
Answer: 73462.0

User story: "User expression is now passed to pre-flight as a plain string (even though that expression is parsed and checked for syntax in advance). This makes it difficult to do smart things with it like deducing table names from link names or converting it to true sqlalchemy construct.    I want to try to pass parsed tree to preflight and build sqlalchemy selection from that instead."
Answer: 8736.0

User story: "On the Feb. 11th-20th 2019, Nick Mondrik from Harvard University will be using the TunableLaser, Electrometer and Linear Stages to do characterization of the laser testing. This task is for providing software support for his efforts."
Answer: 14678.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: "Continuation of https://jira.lsstcorp.org/browse/DM-17693    ------------------------------------------------------------------    This task covers   * time to research and learn about Docker.   * create a Docker image configured for testing.   ** miniconda or scl/ius for Python3 support   ** Robot-Framework   ** XML parser   ** dependencies"
Answer: 3229.0

User story: "Remove all the use of Antlr2 in qserv, including tokens, the build system, and the eups package file."
Answer: 44290.0

User story: This task is to create the subsystem "Confluence Template" that the T&S team will use. This template is planned to be used by the team to contain an overview of a single CSC. For example, some of the items on the template will specify who the product owner is, what the release strategy is and where the links to the Jenkins automated test builds are if they exist.     This task will also go over the time spent working with James and getting his CSC into one of these templates so that we can go through a test run with the template as well an example for a future Tech talk when I go over the teams documentation. 
Answer: 32993.0

User story: "Put a glossary file in lsst-texmf  and let everyone know its there if they want to use glossary.    Provide script to give CSV for back loading to Magic Draw (include the acronyms ?)    Provide Script to modify tex files  and markup the found glossary items - for manual run by authors. (Does that include acronyms ?) ..     "
Answer: 144005.0

User story: "A new version of ts_sal, ts_xml and ts_opensplice has been tagged, this is v3.8.41, and the HeaderService need to be tested against this new version. In addition a new build and install need to be tested against this."
Answer: 21179.0

User story: In order for the "deprecated" package incorporated via RFC-557 to be usable by developers, it must be available in their stack environments (lsstsw-built, eups distrib installed, and shared).  Please arrange for this to happen, presumably by updating {{lsstsw}} and {{newinstall.sh}} to use the new conda environment YAML configuration.
Answer: 74585.0

User story: "While we wait for rpms to be created, we need to create binaries that can be installed across CSCs on the L1 Test Stand"
Answer: 90262.0

User story: "Continue SAL mentoring"
Answer: 20124.0

User story: "Build and deploy SAL runtime as a set of RPM's (per CSC)  "
Answer: 20128.0

User story: "Review the final versions of the TMA FAT verification test reports"
Answer: 20127.0

User story: "The release of pycodestyle 2.5.0 has caused flake8 to be unhappy with the current {{master}} of afw. Please fix it.    Unhappy flake8/Travis: https://travis-ci.org/lsst/afw/builds/488690857  pycodestyle release notes: https://pypi.org/project/pycodestyle/2.5.0/  Relevant Slack discussion: https://lsstc.slack.com/archives/C2JP8GGVC/p1549313396138300"
Answer: 346.0

User story: "The PVC for NFS volumes is really just clutter.  Define a volume with type nfs directly, and point at the NFS server."
Answer: 86.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: "Instead of listening for the mount position from the ATMount, make ATAOS listen for the pointing component. "
Answer: 19943.0

User story: "The scarlet docs currently fail building. There was probably a breaking API change at some point that needs to be fixed, and they also need to be updated with an example of using S matrix normalization to model point sources."
Answer: 2660.0

User story: "Currently TS8 data are handled as a single raft definition shared for all rafts from a single manufacturer. There is a ts8itl and ts8e2v specialization.  In this ticket we will change the organization such that each raft exists as a real raft named RTM-nnn after the actual raft name. Then each raft YAML file defines its own sensors in the normal way and the e2v/itl specialization can be removed.  There will be a single definition of TS8 that allows you to retrieve data by actual raft name or sensor name without risk of confusion."
Answer: 5871.0

User story: "Write the ATSpectrograph CSC using salobj. The main goal of this task is to create a CSC that is capable of running in simulation model. Stretch goal is to have it integrated with the hardware. But, since I'm not entirely familiar with the hardware, it may need a follow-up ticket to complete that. "
Answer: 20083.0

User story: "Write down environment CSC that will capture data from the weather station and publish it to SAL. "
Answer: 10346.0

User story: "Oracle works much better with lowercase field names, and case-sensitivity is in general inconsistent in SQL databases.    We should do this after unifying Dimension names and link names on DM-17023, since that will eliminate the only current use of differently-conventioned names to refer to (essentially) the same concepts, and make a good chunk of the Registry table names lowercase already."
Answer: 117433.0

User story: "This is a continuation of DM-17366.  That task ended up only comprising getting the Ptg Component to build.  This task covers time needed to get the vendor-supplied automated tests running in the TSSW CI environment."
Answer: 21569.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "The new flake8 version warns about F632 (using {{is}} rather than {{==}}) and this triggered a few flake8 failures over the weekend when the weekly tags were added.    The full list I can find:    {code}  qserv/admin/bin/qserv-parallel-cmd.py:191:12: F632 use ==/!= to compare str, bytes, and int literals  meas_modelfit/python/lsst/meas/modelfit/display/cModelDisplay.py:34:8: F632 use ==/!= to compare str, bytes, and int literals  meas_modelfit/python/lsst/meas/modelfit/display/cModelDisplay.py:36:10: F632 use ==/!= to compare str, bytes, and int literals  daf_persistence/python/lsst/daf/persistence/butler.py:917:12: F632 use ==/!= to compare str, bytes, and int literals  display_firefly/python/lsst/display/firefly/firefly.py:406:12: F632 use ==/!= to compare str, bytes, and int literals  synpipe/bin.src/compFakeGalaxy.py:184:8: F632 use ==/!= to compare str, bytes, and int literals  synpipe/bin.src/tractFindVisits.py:25:8: F632 use ==/!= to compare str, bytes, and int literals  synpipe/bin/compFakeGalaxy.py:184:8: F632 use ==/!= to compare str, bytes, and int literals  synpipe/bin/tractFindVisits.py:25:8: F632 use ==/!= to compare str, bytes, and int literals  synpipe/python/lsst/synpipe/positionGalSimFakes.py:74:12: F632 use ==/!= to compare str, bytes, and int literals  ./synpipe/python/lsst/synpipe/positionGalSimFakes.py:133:20: F632 use ==/!= to compare str, bytes, and int literals  synpipe/python/lsst/synpipe/makeFakeGalaxy.py:32:8: F632 use ==/!= to compare str, bytes, and int literals  synpipe/python/lsst/synpipe/makeFakeGalaxy.py:41:8: F632 use ==/!= to compare str, bytes, and int literals  synpipe/python/lsst/synpipe/makeFakeGalaxy.py:52:8: F632 use ==/!= to compare str, bytes, and int literals  synpipe/python/lsst/synpipe/makeFakeGalaxy.py:71:8: F632 use ==/!= to compare str, bytes, and int literals  obs_lsstSim/python/lsst/obs/lsstSim/processCalibLsstSim.py:121:16: F632 use ==/!= to compare str, bytes, and int literals  obs_lsstSim/python/lsst/obs/lsstSim/processCalibLsstSim.py:123:40: F632 use ==/!= to compare str, bytes, and int literals  obs_lsstSim/python/lsst/obs/lsstSim/processCalibLsstSim.py:128:36: F632 use ==/!= to compare str, bytes, and int literals  obs_lsstSim/python/lsst/obs/lsstSim/processCalibLsstSim.py:198:16: F632 use ==/!= to compare str, bytes, and int literals  obs_lsstSim/python/lsst/obs/lsstSim/processCalibLsstSim.py:200:18: F632 use ==/!= to compare str, bytes, and int literals  {code}  "
Answer: 4520.0

User story: "Add support for IVOA SODA v1.0 common shapes (CIRCLE, RANGE, POLYGON)."
Answer: 99525.0

User story: "Try deploying a second czar node at PDAC and collect information on services/applications that would fail and need to be separated out for successful multi-master setup."
Answer: 377097.0

User story: "Test new secondary index application on full Qserv deployment at PDAC or IN2P3."
Answer: 492796.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: "Discuss and document basic requirements for working on Qserv ingest improvements. Document the effort at:  * https://confluence.lsstcorp.org/display/DM/Evaluate+Ingest+Improvement+Requirements+for+Qserv"
Answer: 27466.0

User story: "Perform PPDB scaling test in Google Cloud with other database technologies like postgres and using node configuration not available at NCSA."
Answer: 73708.0

User story: "This ticket is to implement the shapes for image cutout, mandated by SODA 1.0,  as already marked ToDo in ImgServ SODA code base. The approach is to use the geometry functions in the priority 1) lsst/afw 2) astropy."
Answer: 99653.0

User story: "This is to track the demo preparation work that's mostly completed at this point.    The scope of the demo is to demonstrate in ImgServ the  support for    SODA and VO framework (in Python 3):                    Generic DAL layer                    Generic SODA layer                    DAX SODA-specific layer (BRECT, LSST stack: afw, butler)    The demo will demonstrate the standard DALI operations in working order, namely:                   /availability                   /capabilities                  /examples                   /sync           and more...     "
Answer: 57599.0

User story: "When writing unit tests it is sometimes useful to check that a log message was created. Python provides {{TestCase.assertLogs}} for this purpose but this does not work with {{lsst.log}}. It would be useful to allow unit tests to temporarily forward {{lsst.log}} messages to Python {{logging}} so that they could be tested.    This would have to ensure that DM-15201 does not cause a logging loop.    Ideally C++ log4cxx messages could be forwarded but it seems much easier to focus on Python {{lsst.log}} messages."
Answer: 5396.0

User story: "We are moving towards a secure and production like cluster, we need to define some standards for the deployments"
Answer: 131282.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 "root" user for the tssw aws account has an email address of <EMAIL> and I am not aware of the password.  This has long been an irritation as aws support emails responses go to that address.  Another problem is that unless a permission change is made as "root", aws iam billing policy is deactivated, which is preventing usage monitoring/alerting from being enabled.
Answer: 141.0

User story: "Attend the DAQ workshop at NCSA remotely at 2/12 - 2/13 from 8 am in Tucson time. The confluence page is at: [https://confluence.lsstcorp.org/display/SYSENG/DAQ+2.5+API+Workshop+and+COB+installation+at+NCSA+Test+Stand]     "
Answer: 17240.0

User story: "Review the SHWFS FAT (factory acceptance test) document and presentation by the vendor and feedback the problems to Jacques. This task will also review the document of LSE-150."
Answer: 24382.0

User story: "Do the unit test of WEP interface between the algorithm and control system (MTAOS). This is to make sure the behaviors of WEP interface fulfills the need of control system. This task will do the related documentation contains the class diagram."
Answer: 15461.0

User story: "Discuss and define the WEP interface between the algorithm and control system with Chris."
Answer: 15465.0

User story: "Do the unit test of OFC interface between the algorithm and control system (MTAOS). This is to make sure the behaviors of OFC interface fulfills the need of control system. This task will do the related documentation contains the class diagram."
Answer: 8413.0

User story: "CILogon needs an ordered list of username claim name possibilities."
Answer: 4280.0

User story: "Enable travis flake8 checks in {{log}} so that branch protection can be enabled properly."
Answer: 8.0

User story: "Profiling on DM-17496 revealed that the slow speed of preflight was not due to the big {{selectDimensions}} query, but rather follow-up data ID manipulations.    Improvements were also done and reviewed DM-17496, but I'm moving them here because they weren't actually relevant for that ticket, and the work that is relevant isn't done yet."
Answer: 470.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: "Improve ATDome XML as per discussions with [~<USER> and Paul.    Command changes:   * Add a {{homeAzimuth}} command.   * For the {{moveShutterDropoutDoor}} and {{moveShutterMainDoor}} commands replace the field with a boolean named {{open}}; the TCP/IP interface doesn't support partially opening or closing a door.   * Rename the {{stopAllAxis}} command to {{stopMotion}}.   * Remove the {{stopShutter}} and {{stopAzimuth}} commands; the TCP/IP interface only supports stopping all motion.    Event changes:   * Modify {{settingsAppliedDomeController}} as follows:   ** Rename {{xActivated}} to {{xEnabled}} for all fields because this indicates whether detecting the condition is enabled, not whether the condition is detected.   ** Remove the {{learnManual}} field; the TCP/IP interface does not provide the information.   ** Add a {{homeAzimuth}} field to report the configured position of the home switch; this may be useful in conjunction with the {{homeAzimuth}} command and is output by the TCP/IP interface.  * Add a {{homing}} field to {{azimuthState}}. It could be made part of the {{state}} field but then we would need to treat the enums as bits for a bit mask and the XML doesn't seem to have good support for that.   * Modify {{settingsAppliedDomeTcp}} as follows:   ** Change portRange field to port.   ** Change ip to host and allow to be longer (to enable domain lookup).  ** Remove {{writeTimeout}}; the CSC doesn't use it.   * Remove the following events, as we will not be outputting them:   ** {{internalCommand}}   ** {{loopTimeOutOfRange}}   ** {{rejectedCommand}}   ** {{internalStatus}}   ** {{detailedState}} (and associated enum) because there is nothing to report beyond summaryState.   * Rename the allAxisInPosition event to allAxesInPosition.    Telemetry changes:   * Remove the following telemetry topics, as they are not output:   ** {{loopTime}}   ** {{timestamp}} telemetry topic; it is not output.  * Modify the position topic by renaming the dropout door fields from dropoutOpening... to dropoutDoorOpening... for consistency with the main door.    Enum changes:   * Remove the {{ShutterDoorState_NotInMotionState}} enum value; it cannot be output.   * Remove the {{AzimuthState_InMotionState}} enum value; it cannot be output.   * Remove the {{AzimuthState_StoppingMotionState}} enum value; it cannot be reliably output.   * Remove the redundant trailing {{State}} from {{AzimuthState_}} and {{ShutterDoorState_}} enums. For instance {{AzimuthState_NotInMotionState}} becomes {{AzimuthState_NotInMotion}} and {{ShutterDoorState_ClosedState}} becomes {{ShutterDoorState_Closed}}.  "
Answer: 6176.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: "Improve the ATPneumatics XML as per disussion with [~<USER>    * Ditch the Position events because they are fully duplicated by the limit switch events.  * Add Invalid mirror cover state to handle the case that both an open and a closed switch are active for the same cover.  * Ditch the overlap of the “state” enums with summary state and shorten the names to remove redundancy and stutter, so that the MirrorCoverState enums become:  {code}  <Enumeration>MirrorCovers_Closed,MirrorCovers_Opened,MirrorCovers_InMotionState, MirrorCovers_Invalid</Enumeration>  {code}  and the mirror vents state enum becomes:  {code}  <Enumeration>CellVents_Opened,CellVents_Closed,CellVents_InMotion</Enumeration>  {code}  * Delete the {{resetEStopTriggered}} event, rename the {{eStopTriggered}} event to {{eStopTrigger}} and set the {{triggered}} field appropriately.  * Add two new events for reporting m1 and m2 commanded air pressure (each with a single field), unless folks have a very strong desire to add fields to the existing m1AirPressure and m2AirPressure telemetry instead.  * Flesh out the Description and Units fields (including the units for pressure, which are Pa)."
Answer: 10284.0

User story: "DM-17495 fixed the deadlocks we saw in SQLite Registries at the expense of adding much more aggressive locking.  That has caused a pretty dramatic slowdown in operations that make a large number of Registry calls without first starting an explicit transaction, at least on GPFS (because this results in many small transactions, and hence many lock/unlock calls in sequence).    A simple workaround for this (which may also be the best we can do long-term for SQLite) is to wrap such calls in an explicit transaction; that needs to be done now for {{gen2convert}} (the only tool we have right now that does not use explicit transactions) to fix a serious regression in ci_hsc performance."
Answer: 515.0

User story: "We work through a first rule based replication example, with Rucio daemons working in coordination with FTS3 service to transfer files, and upon success update records of existing replicas. "
Answer: 126.0

User story: "Publish ascii errors as part of error code event in salobj. Handle serial timeout as fault state. Add simple retry to timeout to allow CSC to potentially continuing functioning."
Answer: 66370.0

User story: "To deblend crowded fields it is useful to model stars as a single point convolved with the PSF. Through experimentation [~<USER> and I discovered that normalizing the A matrix (colors) causes too much variation in the S matrix (morphology) updates. Instead it appears that normalizing the S matrix (and fixing a single pixel) for point sources and allowing the A matrix to encode both SED and intensity information works better.    This ticket is to give users the option to use either A matrix or S matrix normalization for each source."
Answer: 4381.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: "Inside of telemetry method, if a fault value is read in one of the registers, the laser will go into a fault state however, if the fault is not cleared before the next telemetry it will continue to go into a fault state which is not a valid transition.     The solution should check that the CSC is already in a fault state and not go into fault state."
Answer: 24745.0

User story: "This task covers time to discuss with the TSSW team the particular needs of application building and packaging for deployment.  Most of the pieces already exist, but the process needs to be documented and formalized."
Answer: 44782.0

User story: "Work on Gen3 Butler plugin for OODS version 0.1"
Answer: 612642.0

User story: "After discussion with Google experts, they suggested us to look into an alternative way for server discovery to replace the needs of multicast. (Multicast does not work in GKE if the Firefly server pods are on different nodes).     [http://www.smartjava.org/content/service-discovery-docker-and-consul-part-1/]         This will involve modifying Firefly to read the configuration at build time to decide on the library to use for service auto discovery. When it is in k8s environment, other software package may need to be installed. We need to document this in SUIT deployment procedure DM-16670"
Answer: 36669.0

User story: It'd be nice for QuantumGraph generation to recognize when a component dataset like "deepCoadd.wcs" can be obtained from a previous step that produces the full composite (e.g. "deepCoadd").    We can work around this in individual PipelineTasks for now, so this is not a super high priority.  It's also the only kind of composite dataset support I think we should worry about for the forseeable future; everything else is even lower priority.    (I'm also only making this a DAX ticket because I know that's what happens to middleware tickets that don't have teams; this is not a request that [~<USER> be responsible for it).
Answer: 299489.0

User story: "At some point, we should update the jointcal testdata to reflect the latest processCcd output (e.g. using the new Pessimistic matcher) processed with a more modern reference catalog (likely PS1 for photometry, Gaia for astrometry). This should allow us to un-skip several of the existing tests (e.g. DeCAM photometry tests) that are currently skipped because of bad test data, and remove old-style sourceSelector flags, etc. This would also be the time to update testdata_jointcal to the gen3 butler format.    As part of this work, we should investigate in detail the various chi2/ndof values computed by the tests (these were changed as part of DM-17595, without in-depth study). This would be the time to really test assumptions about e.g. no_rank_update or line search astrometry tests not changing the default chi2, when a highly accurate reference catalog is used (Gaia).    I would expect this work to be delayed for a year or so, until all of the above pieces are nicely settled into place."
Answer: 697124.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: "Fight with dockerfiles in attempt to get a working environment with sal, salobj, AND pymodbus, while nominally learning a bit about how docker is supposed to work"
Answer: 41542.0

User story: "Per DM-12558, ip_diffim creates and uses Task objects without going through the regular subtask mechanism. Why? If this is necessary, we should document it and properly account for it on DM-12558. If it's not necessary, we should fix it by using {{makeSubtask}} so we can keep track of the execution time, etc, of these tasks in the regular way."
Answer: 27402.0

User story: "Construct the OFC interface between the algorithm and control system."
Answer: 1446.0

User story: "Gen3 needs regions for visits and visit+detector combinations, which expect to obtain from some kind of bootstrap single-frame processing.  That currently works only when the bootstrap happens in Gen2, and we use gen2convert on a repo with calexps for all visits.  That makes it impossible to bootstrap in Gen3 alone.    To address that, we should have gen2convert and Gen3 ingest pull regions from raws (with extra padding to account for inaccurate WCSs) when calexps are not available."
Answer: 132526.0

User story: When testing this query from the integration tests for firefly, I get an error that I didn't get before:    SELECT * FROM wise_00.allsky_2band_p1bm_frm WHERE   (scisql_s2PtInCPoly(9.5, -1.23, ra1, dec1, ra2, dec2, ra3, dec3, ra4, dec4)=1) AND   (scisql_s2PtInCPoly(9.5, -1.22, ra1, dec1, ra2, dec2, ra3, dec3, ra4, dec4)=1) AND   (scisql_s2PtInCPoly(9.6, -1.23, ra1, dec1, ra2, dec2, ra3, dec3, ra4, dec4)=1) AND   (scisql_s2PtInCPoly(9.6, -1.22, ra1, dec1, ra2, dec2, ra3, dec3, ra4, dec4)=1)    Returned to me is the dreaded "WARN: multiple errors".  When looking through the mysql-lua-proxy log, I get the following information about the errors:    [2019-01-31T21:10:00.216Z] [LWP:2010] ERROR util.Error (core/modules/util/Error.cc:50) - Error [1146] Error applying sql: Error 1146: Table 'qservResult.result_21178' doesn't exist Unable to execute query: ALTER TABLE result_21178 DROP COLUMN jobId0    [2019-01-31T21:10:00.219Z] [LWP:395] INFO mysql-proxy (qserv/mysqlProxy.lua:539) - q1 - ignoring  [2019-01-31T21:10:00.219Z] [LWP:395] INFO mysql-proxy (qserv/mysqlProxy.lua:553) - chunkId: 1234567890, code: 1209, msg: RESULT_ERROR 1470 (Error(s) in result for chunk #1234567890: [1054] Unknown column 'QST_1_.qs_fact' in 'field list') 1548969000, timestamp: 1548970000  [2019-01-31T21:10:00.219Z] [LWP:395] ERROR mysql-proxy (qserv/mysqlProxy.lua:62) - errNo: 4120: errMsg: Unable to return query results:  -- WARN multiple errors         Reproduces 100%.  Full proxy log attached     
Answer: 264008.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 following iptables rule exist in hieradata/03/datacenters/npcf.yaml:  {code:java}    '0340 kubernetes allowed from NCSA 141.142.181.0/24':       ensure: 'present'      proto: 'tcp'      dport: [ '10250', '6443', '6783' ]      action: 'accept'      source: '141.142.181.0/24'  {code}  This should tentatively be changed to:  {code:java}    '0340 kubernetes allowed from NCSA 141.142.182.128/25':       ensure: 'present'      proto: 'tcp'      dport: [ '10250', '6443', '6783' ]      action: 'accept'      source: '141.142.182.128/25'  {code}  It may be possible to restrict this further with more testing. There are also some other weave specific rules that may need changed if using NOT NAT is a possibility. These updates will be made in a separate ticket when I get there."
Answer: 1.0

User story: "Work with DDN on quote for storage for OODS. Whether JBOD or SFA will depend on discussions about network and base design"
Answer: 37200.0

User story: "Work with Dell to get quotes for machines for the two OODS nodes, make sure warranty/support in Chile is understood. Make sure speck requirements from developers are met (mainly memory & network bandwidth) "
Answer: 37200.0

User story: "Need to discuss between NCSA teams and with Chilean folks how the network is going to look at the base when we move in. What options do we have for connectivity, L2 networks/L3 networks & design"
Answer: 37441.0

User story: "Create design for L1 Handoff System"
Answer: 3.0

User story: "A number of components in {{geom}} and {{afw}} are informally documented as deprecated. They should be re-deprecated using the RFC-557 procedure. This includes warning users in the release notes, since old-style deprecation comments weren't particularly visible."
Answer: 464450.0

User story: "Going to split out the deployment scripts into 3: one for dev (google), one for int (NCSA) and one for stable (NCSA)."
Answer: 8665.0

User story: "The focus while developing the algorithm for correcting DCR in coadds and image differencing has been on the quality of the results, and not on efficiency. However, some components that were chosen for ease of initial development are unnecessarily wasteful, and could be sped up considerably with a small amount of effort. For example, the DcrModel that is passed to {{warpImage}} in each iteration is a {{maskedImage}}, but only the image plane is used even though the mask and variance planes are also warped.   This ticket is to switch the DcrModel to use only the image plane throughout."
Answer: 28698.0

User story: "This task covers   * Time to research and learn about enabling SSH to Docker containers.   * Update the salgenerator tests to work with the Docker image   ** This may involve updating the tests to remove all SSH functionality."
Answer: 20175.0

User story: "ADQL BOX doesn't map to scisql box or qserv box.  So we're just going to get rid of it."
Answer: 8663.0

User story: "Process DC2 imsim one tract of data at /datasets/DC2/repo/  Ramp up periodic reprocessing"
Answer: 83418.0