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: "Install CCHeaderService on summit  This ticket had been created automatically Primavera ID: None"
Answer: 101864.0

User story: "Install OODS in support of ComCam on summit  This ticket had been created automatically Primavera ID: None"
Answer: 101861.0

User story: "Install CCArchiver container on summit  This ticket had been created automatically Primavera ID: None"
Answer: 101861.0

User story: "Deploy for DBB Buffer Mngrs v1.1 Gen2 for BOT images (endpoint only)  This ticket had been created automatically Primavera ID: None"
Answer: 246810.0

User story: "Deploy for DBB Buffer Mngrs v1.1 Gen2 for summit ComCam (handoff and endpoint)  This ticket had been created automatically Primavera ID: None"
Answer: 246808.0

User story: "Gather requirements for LDF monitoring  This ticket had been created automatically Primavera ID: None"
Answer: 245781.0

User story: "Implement sending logging messages to LDF monitoring support for Forwarder Services  This ticket had been created automatically Primavera ID: None"
Answer: 255635.0

User story: "Deploy on the NCSA teststand, run tests, fix any issues  This ticket had been created automatically Primavera ID: None"
Answer: 152585.0

User story: "Determine mid-level implementation details  This ticket had been created automatically Primavera ID: None"
Answer: 51072.0

User story: "Write new code for endpoint buffer mngr and remove no longer needed code in the handoff buffer mngr.  This ticket had been created automatically Primavera ID: None"
Answer: 134385.0

User story: "Write/update documentation for deployment and staff users (and make sure internal code documentation meets LSST guidelines)  This ticket had been created automatically Primavera ID: None"
Answer: 134387.0

User story: "Prepare list of new activities which need to be completed during the next cycle.  This ticket had been created automatically Primavera ID: None"
Answer: 121925.0

User story: "Baseline the plan and send to the Project Controls Specialist  This ticket had been created automatically Primavera ID: None"
Answer: 123043.0

User story: "Review Plan As Imported Into Both Jira Systems  This ticket had been created automatically Primavera ID: None"
Answer: 123042.0

User story: "Vlad to Import Plan Into Both Jira Systems  This ticket had been created automatically Primavera ID: None"
Answer: 121925.0

User story: "Review Final Schedule With Leads  This ticket had been created automatically Primavera ID: None"
Answer: 123043.0

User story: "Move Activities Into Appropriate WBS  This ticket had been created automatically Primavera ID: None"
Answer: 121925.0

User story: "Adjust resources based on complete proposed plan  This ticket had been created automatically Primavera ID: None"
Answer: 121942.0

User story: "Meet with management team to review proposed plan for completeness prior to resource leveling activity  This ticket had been created automatically Primavera ID: None"
Answer: 123043.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: "Management Team Reviews Plan  This ticket had been created automatically Primavera ID: None"
Answer: 123043.0

User story: "This step encompasses everything after loading the initial plan into Primavera, e.g., scheduling the plan, refining allocations, re-prioritizing and re-scheduling to level resources.  This ticket had been created automatically Primavera ID: None"
Answer: 121943.0

User story: "Next cycle plan is imported into Primavera and reviewed for accuracy   This ticket had been created automatically Primavera ID: None"
Answer: 121926.0

User story: "Meeting to review defined high-level epics and dependencies, new and carryover, to ensure completeness, as well as to refine epics, storeis, descriptions, deliverable(s), level of effort, resource assignments, and dependencies.   This ticket had been created automatically Primavera ID: None"
Answer: 121943.0

User story: " Assess current resource levels based on current work  This ticket had been created automatically Primavera ID: None"
Answer: 121943.0

User story: "Review milestones, upcoming priorities, and thrusts from the project. Prepare list of tasks which are on course to carry over into next cycle.  This ticket had been created automatically Primavera ID: None"
Answer: 121926.0

User story: "Ensure All Systems Are In Sync leading into reviewing current work and planning new work  This ticket had been created automatically Primavera ID: None"
Answer: 121927.0

User story: "Document build and deployment of Catchup Archiver  This ticket had been created automatically Primavera ID: None"
Answer: 101637.0

User story: "Implement a skeleton of the ATArchiver that responds to the SAL commands to enable, disable, standby, exitControl, etc.   A good starting point is the base cases for the ATArchiver and CCArchiver.  This ticket had been created automatically Primavera ID: None"
Answer: 101637.0

User story: "Update the current XML definition with any additional info that is required  This ticket had been created automatically Primavera ID: None"
Answer: 101638.0

User story: "Technical Reporting for June 2020  This ticket had been created automatically Primavera ID: None"
Answer: 123128.0

User story: "Technical Reporting for May 2020  This ticket had been created automatically Primavera ID: None"
Answer: 121932.0

User story: "Technical Reporting for April 2020  This ticket had been created automatically Primavera ID: None"
Answer: 121932.0

User story: "Financial Reporting for June 2020  This ticket had been created automatically Primavera ID: None"
Answer: 123049.0

User story: "Financial Reporting for May 2020  This ticket had been created automatically Primavera ID: None"
Answer: 121932.0

User story: "Financial Reporting for April 2020  This ticket had been created automatically Primavera ID: None"
Answer: 121933.0

User story: "Refactor message topology for Camera  This ticket had been created automatically Primavera ID: None"
Answer: 141501.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 we use configured queue names in RabbitMQ to communicate with services.  Investigate the possibility of creating names on the fly, which are exchanged during service startup negotiation.  This ticket had been created automatically Primavera ID: None"
Answer: 141501.0

User story: "Test bbcp/scp transfer time and fix issues if there is still delay  This ticket had been created automatically Primavera ID: None"
Answer: 141501.0

User story: "Write additional unit tests and stress test fits file creation  This ticket had been created automatically Primavera ID: None"
Answer: 141502.0

User story: "Document build and deployment of Forwarders  This ticket had been created automatically Primavera ID: None"
Answer: 71809.0

User story: "Run initial tests and generate purposeful violation for qualsys  This ticket had been created automatically Primavera ID: None"
Answer: 242852.0

User story: "Security to enable periodic scans of Kubernetes  This ticket had been created automatically Primavera ID: None"
Answer: 242852.0

User story: "Add additional logging to stdout when file logging is specified. We log in both places to make it easier to debug (files), and so logs can be gathered by services monitoring containers (stdout).  This ticket had been created automatically Primavera ID: None"
Answer: 124905.0

User story: "Add CC OODS and AT OODS definitions to ts_xml  This ticket had been created automatically Primavera ID: None"
Answer: 41054.0

User story: Currently the when the OODS rejects a file, it lands in the "root" directory of the where the bad files are stored.  (ie, cc_badfiles).  It should go in a dated directory below that (cc_badfiles/2020-03-18)  This ticket had been created automatically Primavera ID: None
Answer: 16732.0

User story: "Write documentation Share documentation and ensure everyone reads it. Announce a deadline for when login ndoes will need to be used instead of cerb/bastion.  This ticket had been created automatically Primavera ID: None"
Answer: 51569.0

User story: "Research LSST pipeline prereqs and implement  This ticket had been created automatically Primavera ID: None"
Answer: 62846.0

User story: "Install necessary packages. Determine how much X11 support we want to provide. * just x forwarding of applications? * Provide full desktop? (xfce?)  This ticket had been created automatically Primavera ID: None"
Answer: 175583.0

User story: "Install kubectl and copy kubeconfig files for users to new host. In iptables, open 6443 to kubh nodes from login nodes.  This ticket had been created automatically Primavera ID: None"
Answer: 51033.0

User story: "Install basic slurm packages needed for job submission. Put slurm.conf file onto login nodes.  This ticket had been created automatically Primavera ID: None"
Answer: 83248.0

User story: "Will need to research this, but should just be a matter of installing necessary packages.  This ticket had been created automatically Primavera ID: None"
Answer: 175583.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 Systems side work for this is done.  Awaiting pfsense updates after security vetting is complete.  This ticket had been created automatically Primavera ID: None"
Answer: 101451.0

User story: "GSSAPIStoreCredentialsOnRekey yes' is already set in the sshd config. Was there more to it than this? @clausen  This ticket had been created automatically Primavera ID: None"
Answer: 101521.0

User story: "sshd config. Possibly pam? I'll need to do some research for best practices.  This ticket had been created automatically Primavera ID: None"
Answer: 214206.0

User story: "Install necessary packages. Configure sshd. Make firewall changes to allow ssh connections.  This ticket had been created automatically Primavera ID: None"
Answer: 198196.0

User story: "Ensure necessary packages installed. Configure ssh client config.  This ticket had been created automatically Primavera ID: None"
Answer: 23780.0

User story: "Research and move home folder creation services to a dedicated VM and implement  This ticket had been created automatically Primavera ID: None"
Answer: 186777.0

User story: "Add additional logging to stdout when file logging is specified.  We log in both places to make it easier to debug (files), and so logs can be gathered by services monitoring containers (stdout).  This ticket had been created automatically Primavera ID: None"
Answer: 124902.0

User story: "When forwarders are added to the redis data base, they should be added to a set, rather than a list.  Additionally, the set entry should expire.  Redis doesn't support this directly, so investigate methods of doing this.  (Possible via a LUA script in Redis)  This ticket had been created automatically Primavera ID: None"
Answer: 124905.0

User story: "Change retrieval of a forwarder from a redis set, not a list  This ticket had been created automatically Primavera ID: None"
Answer: 124902.0

User story: "Changes for automatic queue creation  This ticket had been created automatically Primavera ID: None"
Answer: 124903.0

User story: "Document build and deployment of Archivers  This ticket had been created automatically Primavera ID: None"
Answer: 124905.0

User story: "Planning for the June 2020 PM. Plan for PM will be linked to the maintenance story for the month  This ticket had been created automatically Primavera ID: None"
Answer: 126216.0

User story: "Planning for the May 2020 PM. Plan for PM will be linked to the maintenance story for the month  This ticket had been created automatically Primavera ID: None"
Answer: 106156.0

User story: "Planning for the April 2020 PM. Plan for PM will be linked to the maintenance story for the month  This ticket had been created automatically Primavera ID: None"
Answer: 106156.0

User story: "Make the ad-hoc data transfer monitoring for AuxtTel/LATISS work for ComCam data (from the summit test stand)  This ticket had been created automatically Primavera ID: None"
Answer: 114848.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: "Make the ad-hoc data transfer monitoring for AuxTel/LATISS work for BOT data.  This ticket had been created automatically Primavera ID: None"
Answer: 114849.0

User story: "Additional puppetization/deployment to allow for an  LFA within the teststand.  This ticket had been created automatically Primavera ID: None"
Answer: 4154.0

User story: "Updates of puppet deployments within the NCSA Test Stand to address evolution of system.  This ticket had been created automatically Primavera ID: None"
Answer: 94280.0

User story: "Expand the framework's functionality to include options for variations of time for the full backup option on long term media, such as tape  This ticket had been created automatically Primavera ID: None"
Answer: 151993.0

User story: "Expand the framework's functionality to include options for variations of size for the full backup option   This ticket had been created automatically Primavera ID: None"
Answer: 151993.0

User story: "Expand the framework's functionality to include options for variations of time for the full backup option   This ticket had been created automatically Primavera ID: None"
Answer: 151993.0

User story: "Learnings have occured, rewriting a number of algorithms for speed   This ticket had been created automatically Primavera ID: None"
Answer: 151993.0

User story: "Improve resilency against crashes   This ticket had been created automatically Primavera ID: None"
Answer: 151993.0

User story: "Improve logging, outputs to prometheus to influx for direct monitoring and alerting  This ticket had been created automatically Primavera ID: None"
Answer: 151994.0

User story: "Containers need to restart after a reboot, which they currently do not.   This ticket had been created automatically Primavera ID: None"
Answer: 124907.0

User story: "Build docker container for Catchup Archiver  This ticket had been created automatically Primavera ID: None"
Answer: 106130.0

User story: "Change the deployment scripts to specify logging to file system outside of the container; should be done after implementation of secondary logging.  This ticket had been created automatically Primavera ID: None"
Answer: 124908.0

User story: ﻿<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">  <HTML><HEAD>  <META content="text/html; charset=unicode" http-equiv=Content-Type>  <META name=GENERATOR content="MSHTML 11.00.10570.1001"></HEAD>  <BODY>  <P><FONT face=Calibri>Dependent on Release Update 19.7 being provided by Oracle   (April 30th, 2020)</FONT></P>  <P>Patch 2nd Oracle cluster to April 2020 Release Update</P></BODY></HTML>    This ticket had been created automatically Primavera ID: None
Answer: 114751.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: ﻿<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">  <HTML><HEAD>  <META content="text/html; charset=unicode" http-equiv=Content-Type>  <META name=GENERATOR content="MSHTML 11.00.10570.1001"></HEAD>  <BODY>  <P><FONT face=Calibri>Dependent on Release Update 19.7 being provided by Oracle   (April 30th, 2020)</FONT></P>  <P>Patch 1st Oracle cluster to April 2020 Release Update. Includes combing   through the readme for any changes to previous procedure, setting things up on   all the nodes, running autopatch, checking for any errors in various logs and   ensuring clusterware and database are operating as expected.</P></BODY></HTML>    This ticket had been created automatically Primavera ID: None
Answer: 114751.0

User story: "Understand limitations, benefits and trade off using kubernetes resource management framework to manage the resources for different deployments within the cluster and pod prioritization.  This ticket had been created automatically Primavera ID: None"
Answer: 145083.0

User story: "Update all OODS instances to support Gen3 Butler  This ticket had been created automatically Primavera ID: None"
Answer: 131582.0

User story: "DM-24055 made a significant improvement in defect reading speed. Now the profiler is showing that there are some reasonable gains that can be made by adjusting table creation to use columns rather than per row assignment."
Answer: 1250.0

User story: "SPIE paper"
Answer: 50356.0

User story: "In Auxtel’s files, a comment that starts “FITS (Flexible Image” is repeated twice in the header, along with SIMPLE and EXTEND"
Answer: 258688.0

User story: "SEQNUM in the fitsfile is currently written as double. It should be written as integer."
Answer: 9624.0

User story: "Reading defects is taking a very long time. Some of the larger defects files from DECam take over 2 seconds to read in. The bulk of this is in afw Table processing. It seems I was doing it wrong and it can be significantly optimized by preselecting keys."
Answer: 224.0

User story: "We had to put some ugly code in ts_standardscripts in order for it to work with the version of ATMCS trackTarget command in ts_xml 4.8 and the next version. Remove that when we no longer need ts_xml 4.8."
Answer: 100481.0

User story: "Take the parquet files at  {{/datasets/hsc/repo/rerun/RC/w_2020_11/DM-23889/obj/deepCoadd-results/merged/*/*parq}} as inputs, go through the workflow and ingest into Qserv.    "
Answer: 46087.0

User story: "The Fiber Spectrograph does not yet try to upload the images it takes to the LFA. Update the code to make that happen."
Answer: 14572.0

User story: "[~<USER> gave me credentials for NCSA's S3 LFA service. Try to use these credentials from home to figure out what will be needed for our CSCs."
Answer: 15689.0

User story: "Add unit tests for the mock devices and the mock controller to ts_MTMount."
Answer: 15707.0

User story: "Build the latest docker image of MTAOS. The environment of `b41` and ts_xml v4.7.0 is used."
Answer: 4376.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: "Make sure that the DCS can connect to and disconnect from the lower level components. Use the mock controller at first and make sure that it later can switch to the real CRIO."
Answer: 5587.0

User story: "Make sure that the upper level DCS can command the lower level components."
Answer: 14249.0

User story: "Start implemeting the CSC that publishes the telemetry into the EFD."
Answer: 118276.0

User story: "Get familiarized with the M2 hexapod thermal sensors hardware."
Answer: 109517.0

User story: "Received the latest DIMM documents and will read them."
Answer: 14185.0

User story: "Catch-all task to cover various activities needed to prepare for the SAL v4.1.x release.  This is a continuation of DM-24012 into the next sprint   * V4.1.1 requires Python 3.7.6, so update the Docker image accordingly.   * Cut release candidate branches and run tests.   * Implement Jenkins parallel stages in the SAL Release job   * Update SAL tests with SAL v4.1.0 changes"
Answer: 25560.0

User story: "Testing is revealing a flaw where one user gets associated with another one's UID (and presumably groups--but not name).  This is probably down in the spawner's guts somewhere.  "
Answer: 67749.0

User story: "Set up backups for Vault."
Answer: 70494.0

User story: "On all nublado environments, also manage vault-secrets-operator with Argo CD. This will require a separate application because it has to be bootstrapped before Argo CD itself (see how this is done with Roundtable)."
Answer: 131912.0

User story: "The metadata checking code that runs during read of curated calibrations from obs_x_data packages incorrectly assumes that CALIBDATE should match the validity start.  It turns out that CALIBDATE is meant to be a label for the calibration and is distinct from validity. Please remove the check that requires them to match."
Answer: 7307.0

User story: "Dockerize ts_m1m3simulator."
Answer: 5632.0

User story: "CCCamera sends endReadout event without finishing/waiting on the image is fully completed. That creates issue where Forwarder thinks image is ready and when tried to fetch the image, it does not exist in the catalog. This ticket uses barrier class to update Forwarder code."
Answer: 11540.0

User story: "Moved desktop computer and electrometer to home for working remotely for an undetermined length of time. Setup desktop and electrometer."
Answer: 5581.0

User story: "Tiago wants a login.  The LSP stuff is argo-cd deployed so what the hell."
Answer: 6030.0

User story: "https://lsstc.slack.com/archives/C2JPT1KB7/p1585184879129400"
Answer: 1036.0

User story: "A high-level interaction class similar to the LATISS class needs to be created for ComCam. This ticket will develop the first iteration of that class in the ts_standardscripts repo."
Answer: 153766.0

User story: "Update sciplat-hub to help out Stelios Voutsinas"
Answer: 7019.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Review the rotator Simulink model by MOOG. This is to have an initial understanding how the code works and have the idea how to modify it. This task will remove the hard-coded paths in the model for the evaluation as well."
Answer: 2777.0

User story: "See [https://lsstc.slack.com/archives/C2JPT1KB7/p1585160382064500]     "
Answer: 17.0

User story: "Catch-all task to cover various activities needed to prepare for the SAL v4.1.x release.   * V4.1.1 requires Python 3.7.6, so update the Docker image accordingly.   * Cut release candidate branches and run tests.   * Implement Jenkins parallel stages in the SAL Release job   * Update SAL tests with SAL v4.1.0 changes"
Answer: 7212.0

User story: "This is to create a workflow on how to develop observing notebooks and move that functionality to scripts and eventually into production code. Seeing as this workflow will require some amount of evolution of repos, the first cut is really a proposal, which will then become a technote."
Answer: 785.0

User story: "Currently, if you can authenticate, you can issue a personal token with any scope you want. This should be restricted to the scopes you have."
Answer: 44097.0

User story: "This work involves developing a pipeline task to automatically detect and mask satellite trails. The main place it will be used is in building the coadds. "
Answer: 5.0

User story: "This task will reorganize the files in ts_rotator_controller and update the related configuration.ac and Makefile.ac. This is to improve the readability and maintainability of repository."
Answer: 12699.0

User story: "More aggressively manage expiration of our image cache."
Answer: 48703.0

User story: After the latency tests at the Summit with M1M3 and M2 data, we switched on using the {{private_sndStamp}} as the InfluxDB timestamp.    We notice, however, that some subsystems still have {{private_sndStamp}} in UTC instead of TAI.    This change was tested with M2 data at the Summit and in particular, the "features" in the data introduced by the internal EFD latency are removed and Chronograf display is consistent with the timestamps produced by SAL.
Answer: 2.0

User story: "Update ts_ATMCSSimulator for a minor change to the XML.    Also take the opportunity to format with black and modernize the CSC unit test to use BaseCscTestCase."
Answer: 323.0

User story: Update the ts_MTMount code based on my conversation with Alberto 2020-03-23. Changes include:  * Enforce only one command at a time.  * The source field of errors and warnings is a string of the form {{f"\{subsystem_id\}. \{text\}"}}, rather than a simple integer.  * The CSC should not command the azimuth cable wrap; let the azimuth axis take care of it. Remove the azimuth cable wrap from the simulator.  * Use the suggested startup sequence.  * Add the suggested shutdown sequence.  * Corrected the source-ish field for the error and warning replies. I had assumed it was an integer, but it turns out to be a string (that starts with an integer; it's ugly).
Answer: 4456.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Since the structure of each reply received from the mock controller is similar, it is possible to have one assert method for each kind of reply instead of dedicated ones."
Answer: 12.0

User story: "Open ports for use of Dask on HTCondor cluster hosts:   - sub (schedd/workflow) nodes will be the scheduler hosts   - compute (execd) nodes will be the worker hosts"
Answer: 31513.0

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

User story: "The OK reply sent from the mock_controller lacks a space right before the Timeout keyword."
Answer: 20.0

User story: "Trying to run the all sky gaia dask notebook fails in the workflow system because the {{JUPYTERHUB_SERVICE_PREFIX}} environment variable is not set in the workflow environment.  This causes dask to throw an exception when it tries to construct the path to the scheduler dashboard interface.    I have confirmed that variable is set in an interactive JupyterLab running {{w_2020_12}} on stable."
Answer: 8888.0

User story: "Deploy the EFD on the LSP integration cluster to exercise the deployment on the LSP stable cluster.    This thicket reports the work done from March 5 to March 16 worth of 5.6 SP mostly due to problems with the {{local-path-provisioner}} and NFS file locking issues on the LSP integration cluster. "
Answer: 35.0

User story: "Move the 3 desktop machines and laptop from office to house. Setup a table and connect the devices. Verify communication between them and setup to allow continuation of TMA software installation.    Also moved a desk, picture of setup attached.  "
Answer: 4500.0

User story: This task is to complete the ATPneumatics user's manual and developers guide. The "source" of the documentation (e.g. latex, word doc etc) is part of the deliverable. Ideally this should all go in the repo with the code, but should this not be possible other solutions may be considered.
Answer: 162391.0

User story: This task is to complete the ATMCS user's manual and developers guide. The "source" of the documentation (e.g. latex, word doc etc) is part of the deliverable. Ideally this should all go in the repo with the code, but should this not be possible other solutions may be considered.
Answer: 165223.0

User story: "Felis is our standard for representing metadata about tabular data stored in relational databases.  A similar system, TAP_SCHEMA v1.1, encodes similar information.    This issue is to explore how straightforward a direct mapping of TAP_SCHEMA to felis description files is."
Answer: 50.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 gen3 instrument classes have no consistency in naming or module path. This adds to the confusion. Currently we have:    * lsst.obs.subaru.gen3.hsc.instrument.HyperSuprimeCam  * lsst.obs.decam.instrument.DarkEnergyCamera  * lsst.obs.lsst.gen3.instrument.LatissInstrument  * lsst.obs.lsst.gen3.instrument.Ts8Instrument  * lsst.obs.lsst.gen3.instrument.Ts3Instrument  * lsst.obs.lsst.gen3.instrument.UcdCamInstrument  * lsst.obs.lsst.gen3.instrument.PhosimInstrument  * lsst.obs.lsst.gen3.instrument.ImsimInstrument  * lsst.obs.lsst.gen3.instrument.LsstComCamInstrument  * lsst.obs.lsst.gen3.instrument.LsstCamInstrument    corresponding to instrument names of HSC, DECam, LATISS, LSST-TS8, LSST-TS3, LSST-UCDCam, PhoSim, LSST-ImSim, LSST-ComCam, lsstCam.    Instrument names have to be unique in Gen3 since telescope is not part of the data model. This is why TS8 is not TS8. lsstCam should probably be LSSTCam.    This ticket will try to clean things up a bit.    obs_cfht has no gen3 support at this time."
Answer: 4136.0

User story: "Move Python code from labview ts_m1m3supporteui feature/Python branch into develop branch of ts_m1m3supportgui."
Answer: 40.0

User story: "In DM-23778 I updated writeCuratedCalibrations to support QE curves as well as defects. This is generic code that uses the pipe_tasks read_all function to read standardized calibration data from {{obs_x_data}} packages.  Since by definition these calibrations are standardized we should move this code to obs_base and ensure that all gen3 instruments call it if they have defined an _data package.  The relevant dataset types and curated calibrations would only be created/ingested if they exist in the _data package (which by definition means they are standardized).  The instrument subclasses should only be required to define their non-standard curated calibrations."
Answer: 24527.0

User story: "When working on DM-23778 I realized that in obs_base and obs_decam we had defined subfilter to be an int but in obs_lsst and gen3 butler it was defined to be a string.    To be explicit here. obs_base uses:  {code}  %(filter)s%(subfilter)dof%(numSubfilters)d/  {code}    obs_decam uses:    {code}  %(filter)s%(subfilter)d  {code}  but obs_lsst was using:    {code}  %(filter)s%(subfilter)s  {code}    I had to change obs_lsst to an int to prevent the 2to3 conversion code from complaining about the inconsistency but I worry that I changed the wrong end and should have changed obs_base.    Given that the gen3 data model uses a string I feel thes gen2 templates need to be looked at and made consistent with gen3."
Answer: 6233.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'll deploy and test the replicator connector at NCSA. It is configured to read from the Tucson test stand cluster (source) and write to the LSP integration cluster (destination). Both Kafka topics and schemas are replicated.     That's also an opportunity to test the {{kafka-connect-manager}} support to the Replicator connector and to add the deployment configuration to Argo CD.    At the moment, the Summit EFD is not operational due to the Observatory shutdown. When it is back we'll configure the connector on the LSP integration cluster to replicate data from the Summit EFD and, once we verify that, we'll proceed with the deployment of the replicator connector on stable (DM-23974)."
Answer: 10656.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 the help/guidance of [~<USER>, please create ATMCS and ATPneumatics git repos for the code, then upload the current version.    Versions that get deployed on-site (from now on) should be tagged releases. "
Answer: 163984.0

User story: "The AuxTel dome vendor provided software needs a home. I thought Andres Anania made one awhile ago but I can't find any record of its existance.    When created, please let me know so I can provide the vendor push-access."
Answer: 83377.0

User story: "need to add redis_plus_plus (and indirectly, hiredis) to the qserv table file so that installing qserv dependencies with eups will install them."
Answer: 2507.0

User story: "After wrapping up the laser tracker acceptance test in the fallout shelter, I packed up office equipment to take home, and also worked on figuring out all the electronics equipment I will need to work on the PressureSensor CSC. Pretty sure I have everything I need other than a balloon to test it with. "
Answer: 3752.0

User story: "From w_2020_07 to w_2020_08, the schema of the Object table changed significantly (DM-23104).       -Ingest some w_2020_08 parquet files at -  -/project/<USER>analysis-sprint/w_2020_07/deepCoadd-results/merged/9\*/ob\*parq-  (somehow those tables have 601 columns while I expect 600 based on the cat yaml file.  They have an extra column named 'filter'.  Not sure what happened but I don't think it's worth digging)    Ingest a tract or two of the w_2020_08-based HSC Object table from DM-23856   (/datasets/hsc/repo/rerun/DM-23243/OBJECT/DEEP/deepCoadd-results/merged/\*/\*parq )   as an exercise to work out the details for the schema change (so far the schema was made ~manually), and make it easier for the next time before tools read directly from cat. "
Answer: 9970.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: "h1. Objectives  This effort continues what what started with [https://jira.lsstcorp.org/browse/DM-23086 |http://example.com]. All tables which need to be ingested are described in:  * GAIA DR2 catalog info: [https://www.cosmos.esa.int/web/gaia/data-release-2]  * Data Model: [https://gea.esac.esa.int/archive/documentation/GDR2/Gaia_archive/chap_datamodel/]    h1. SSO tables  There are two tables in this group:  * *{{sso_source}}*: https://gea.esac.esa.int/archive/documentation/GDR2/Gaia_archive/chap_datamodel/sec_dm_sso_tables/ssec_dm_sso_source.html  * *{{sso_observation}}*:  https://gea.esac.esa.int/archive/documentation/GDR2/Gaia_archive/chap_datamodel/sec_dm_sso_tables/ssec_dm_sso_observation.html    The former (*{{sso_source}}*) defines a PK key *{{source_id}}* which is referred to from the _dependent_ table *{{sso_observation}}*. What's *IMPORTANT* for the purpose of the current ingest effort is that values of the *{{source_id}}*  do *NOT* overlap with values of a similarly named column of table *{{gaia_source}}*. Hence, the usual _director_/_child_ relationship doesn't apply to the *SSO* tables. Also, given a relatively small size of each table, they should be treated (and loaded into Qserv) as so called _regular_ (fully replicated) tables.  || table || size || #rows ||  | sso_source | 896 K| 14099 |  | sso_observation | 807 M | 1977702 |    h1. *{{light_curves}}*  Documentation:  * https://gea.esac.esa.int/archive/documentation/GDR2/Gaia_archive/chap_datamodel/sec_dm_datalink_tables/ssec_dm_light_curve.html    The table has a *FK* key to table *{{gaia_source}}*. Due to a small size of the table it makes a sense to ingest it as fully-replicated (_regular_) table:  || table || size || #rows ||  | light_curves | 6.8 G | 48255086 |    h1. Other tables  A similar approach was taken for other tables as well. Please, pay attention to specific notes on some tables, especially regarding table schemas. "
Answer: 10043.0

User story: "Dump Summit EFD databases and restore them at NCSA Integration cluster along with the Chronograf dashboards. This needs to be done March 19 before the Observatory  shuts down because of the Covid-19 outbreak."
Answer: 32.0

User story: "Review the use of EOL'd software components by the TMA control software.  In particular NI SoftMotion module."
Answer: 192.0

User story: When reading a {{"raw"}} dataset from the butler, we get an {{Exposure}} back. However, the metadata contained within that {{Exposure}} has not been patched. I believe {{CameraMapper._standardizeExposure}} should call {{fix_header}}.
Answer: 296.0

User story: "Obtain license for the install OpenSliceDDS Enterprise and tools on a dedicated node   in the NCSA test stand cluster."
Answer: 10066.0

User story: "The work is to be completed by our intern at NCSA, Sam Cappon.     We had issues in the past where there is a difference between CCS and Archiver fitsfile creations. This utility can be used to compare the fitsfile."
Answer: 72019.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: "Take a look through the lsst-dm/sample-avro-alert & lsst-dm/alert_stream repos. Understand what's there, and think about whether you understand it and would be able to maintain it. File tickets for any changes that you'd like to make in the short term (and think about longer term evolution, which we should probably discuss in person). Take a look at the ticket backlog on those repos, and see if those tickets seem relevant/obsolete/unclear/etc."
Answer: 18763.0

User story: "During the review of https://jira.lsstcorp.org/browse/DM-23588, [~<USER> produced some additional test code at https://github.com/lsst-dm/sample-avro-alert/pull/10.  This ticket is to review the code, expand it (or its tests) as you view necessary, and merge it to master."
Answer: 20171.0

User story: "There isn't any error handling. The process in best cause core dump when some configuration file is missing, in worst case my understanding is it might end up with wrong configuration. This needs to be fixed."
Answer: 165279.0

User story: "Change M1M3 support logging to allow for logging into a file - the current logging assumes it's logging to stdout, and prints out escapes for color logging."
Answer: 18785.0

User story: "When we  upgraded to scarlet 0.5 in early 2019 we decided that rather than try to place more bandaids on {{meas_deblender}} we would create the new {{meas_extensions_scarlet}} package. In doing so {{meas_deblender}} was left alone, which still included dependencies on {{scarlet}} and {{proxmin}} with code that likely has bit rotted. So this ticket is just to remove all references to {{scarlet}} and {{proxmin}} from {{meas_deblender}} and delete the dependencies, as they be related to an obscure failure in the build system."
Answer: 685.0

User story: "Change M1M3 support to use configured path instead of hardcoded."
Answer: 16016.0

User story: "FPGA object is passed as parameter to multiple classes constructors. Its much better to implement FPGA as Singleton (as it's completely unexpected we will ever run M1M3 support on cRIOs with multiple FPGAs) and use it this way, removing multiple passing of pointer. This will also facilitate transaction from FPGA class to IFPGA, its abstract parent, which can be either real FPGA or simulated FPGA."
Answer: 9076.0

User story: "Create this package, to finish RFC-678."
Answer: 961.0

User story: "[~<USER> found that the current functor for localWcs would not return a valid transform when far from the Wcs center as it uses getCdMatrix/getTANWcs which behave poorly when far from the Wcs origin/do not utilize larger distortions. This ticket will change the plugins and functors to use linearizePixelToSky instead."
Answer: 38393.0

User story: "Switch to standard project documentation formatting and build documentation as part of the project to make it easier to understand the code."
Answer: 5888.0

User story: "The current IOD filtering rejects a number of known-pure clusters. Investigate alternative approaches to avoid this effect."
Answer: 36009.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: "Switch from Dyanconf to pydantic to match the configuration management facilities that we're using for other SQuaRE projects."
Answer: 56287.0

User story: "Refactor jwt_authorizer to follow the roundtable_aiohttp_bot pattern and the safir library instead of being a Flask application. This will make it easier to maintain because it will match the design pattern of other SQuaRE applications."
Answer: 36332.0

User story: "I filed https://github.com/astropy/astropy/issues/10052 to request CLOCK_TAI support in the time module in Python and was told they would likely accept a patch. Provide one."
Answer: 8647.0

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

User story: "sqlite3 on a local Hub isn't the right answer.  Maybe deploy our own RDBMS instance for session DB and similar?"
Answer: 38963.0

User story: "I'm starting to learn some of the middleware code to provide some development support. First task is to take a look at the parser code. Per [~<USER>:     _here is one ticket that I have right now - DM-22173 - this is about adding support for proper date/time in our expression parser and in the Registry, with you Antlr experience it may be interesting to you to look at that. The parser code is in https://github.com/lsst/daf_butler/tree/master/python/lsst/daf/butler/registry/queries/exprParser and it's relatively trivial compared to full SQL language, what we want there is a special literal type for specifying timestamps. There is some info about that in RFC-648 too._"
Answer: 48746.0

User story: "see https://jira.lsstcorp.org/browse/IHS-3604"
Answer: 72.0

User story: "We are still reviewing the use of YAML in stead of using plain semi-colon separated strings for the communication between the upper and lower level components but I am going ahead and will start implementing YAML already since this is the way we will go.    EDIT: YAML has been accepted as the preferred communications protocol."
Answer: 7040.0

User story: "There are many times where we can call makeRepo in cases where a butler repository already exists (or at least the config file exists). It would be useful for makeRepo to be able to complain if that is the case."
Answer: 463.0

User story: "Once we are satisfied that we no longer need clusterproxy/lsstdaskclient, pull them out of JLU."
Answer: 26004.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: For the PFS project, we have issues writing certain {{postISRCCD}} exposures to file using the LSST stack v18.1.0 . For certain visits taken in 2019 on instrument hardware on a testbench, I get the following error:    {code}    File "/tigress/HSC/PFS/stack/20190925/stack/miniconda3-4.5.12-1172c30/Linux64/ip_isr/18.1.0/python/lsst/ip/isr/isrTask.py", line 1434, in runDataRef      sensorRef.put(result.exposure, "postISRCCD")    File "/tigress/HSC/PFS/stack/20190925/stack/miniconda3-4.5.12-1172c30/Linux64/daf_persistence/18.1.0/python/lsst/daf/persistence/butlerSubset.py", line 224, in put      self.butlerSubset.butler.put(obj, datasetType, self.dataId, doBackup=doBackup, **rest)    File "/tigress/HSC/PFS/stack/20190925/stack/miniconda3-4.5.12-1172c30/Linux64/daf_persistence/18.1.0/python/lsst/daf/persistence/butler.py", line 1434, in put      location.getRepository().write(location, obj)    File "/tigress/HSC/PFS/stack/20190925/stack/miniconda3-4.5.12-1172c30/Linux64/daf_persistence/18.1.0/python/lsst/daf/persistence/repository.py", line 185, in write      return butlerLocationStorage.write(butlerLocation, obj)    File "/tigress/HSC/PFS/stack/20190925/stack/miniconda3-4.5.12-1172c30/Linux64/daf_persistence/18.1.0/python/lsst/daf/persistence/posixStorage.py", line 258, in write      writeFormatter(butlerLocation, obj)    File "/tigress/HSC/PFS/stack/20190925/stack/miniconda3-4.5.12-1172c30/Linux64/daf_persistence/18.1.0/python/lsst/daf/persistence/posixStorage.py", line 634, in writeFitsStorage      obj.writeFitsWithOptions(logLoc.locString(), options=additionalData)    File "/tigress/HSC/PFS/stack/20190925/stack/miniconda3-4.5.12-1172c30/Linux64/afw/18.1.0/python/lsst/afw/image/image/fitsIoWithOptions.py", line 127, in exposureWriteFitsWithOptions      self.writeFits(dest, **writeOptionDict)  lsst.pex.exceptions.wrappers.TypeError:     File "src/PropertySet.cc", line 232, in std::vector<T> lsst::daf::base::PropertySet::getArray(const string&) const [with T = std::basic_string<char>; std::string = std::basic_string<char>]      W_XHP2FR {0}  lsst::pex::exceptions::TypeError: 'W_XHP2FR'  {code}    Now, I've found the error is raised when the keyword 'W_XHP2FR' appears twice in the FITS header, _and_ has a value that is empty:    {code}  W_XHP2FR=  / frac power to spreader heater: 0 or 1 NOT CURRENT  [...]  W_XHP2FR=  / frac power to shield: 0 or 1 NOT CURRENT  {code}     The fact that the keyword is duplicate and empty are bugs in the PFS software that have subsequently been fixed. However it is not possible to process historical data that are 'corrupted' this way using v18.1.0 stack. It is also not possible to fix the metadata in the PFS layer before the {{IsrTask}} sees that, as there is no way to intercept the metadata when the {{IsrTask}} reads in the raw exposure.    Is it possible to make {{PropertySet}} robust against such scenarios?
Answer: 568.0

User story: "Create this package, to finish RFC-678."
Answer: 2634.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "As demonstrated in the work on DM-23106, the parallel stage functionality is a real time saver.  Implement this same strategy in the SAL release job, also parallelizing the messaging tests."
Answer: 68835.0

User story: Report on the latency characterization work done during the week of Feb 26 to Mar 4 when we first had [real M1M3 + M2 data streams at the Summit| https://lsstc.slack.com/archives/CM65SGAJE/p1582738049002700].    The first good news is that the EFD runing on a single server with Kubes (k3s) was able to keep up with the M1M3 (50Hz) + M2 (20Hz) data streams.    We noticed however, the presence of "latency spikes" of ~20s every few minutes and decided to find the root cause and improve that.    We deployed the kafka control center to help us to monitor Kafka and from that tool it became clear that there was a lag in the consumer group for the Kafka InfluxDB connector where we observed a repetition pattern of ~1000 messages falling behind (connector lag)  and then getting restored. 1000 messages at 50Hz correspond to the ~20s latency spikes we observe.    To reduce the connector lag we added more partitions to the M1M3 and M2 kafka topics which increased the connector throughput and alleviated the problem reducing significantly those latency spikes. From the Kafka Control Center at the Summit https://control-center-summit-efd.lsst.codes/ we are using 18 partitions for M1M3 and M2 topics now. This way we have messages being consumed in parallel and to increase the throughput when writing to InfluxDB we could also increase the number of connector tasks.  Currently, we are running only one connector task, but we plan on increasing that soon.    That already improved the latency removing the ~20s spikes. The latency is now dominated by the SAL Kafka producer which also shows those spike features of ~2s from time to time.    To further improve latency we can increase even more the number of partitions, increase the number of connector tasks, have multiple connectors for different subsystems if needed, perhaps reproduce in Kafka Connect what we do with the SAL Kafka producers, and if needed increase the size of the Kafka Connect cluster.                
Answer: 8.0

User story: "So, sciencemonkey needs to get the prototype jupyterhub login, spawn, execution flow put in it.  That's the first step!  This means going from Tornado to aiohttp, which is the right thing but probably involves some learning on my part."
Answer: 17286.0

User story: "In order for the unit tests of ts_Dome to pass, an empty _labels.yaml is needed."
Answer: 260.0

User story: "List out the services that are needed for camera operations that are from the BDC for NCSA.  "
Answer: 131583.0