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: "As a component of the Environment Awareness System EAS ([https://confluence.lsstcorp.org/pages/viewpage.action?pageId=73574873),|https://confluence.lsstcorp.org/pages/viewpage.action?pageId=73574873)] it's necessary to develop a dome environment conditioning system, to control the temperature during daytime."
Answer: 19376.0

User story: "Prepare and coordinate weekly meetings on dome control software with EIE contractor."
Answer: 19320.0

User story: "{{lsstdm/headerservice:4.1.1-6.0.0-salobj_5.15.0-hs_2.3.0}}  {{lsstts/headerservice:v2.3.0_salobj_v5.15.0_idl_v1.2.2_xml_v6.0.0}}"
Answer: 1186.0

User story: "While working with [~<USER> to add some LSB fakes to images a few small issues came up. Improving these would make the fakes code easier to use."
Answer: 30277.0

User story: Implement {{qgraph}} and {{run}} using click (in the {{pipetask2}} command, which will eventually replace {{pipetask)}}    Add the "chained" subcommands feature, write a Community post about it describing the differences from the existing {{pipetask}} command, request feedback.
Answer: 82227.0

User story: "Do version upgrades of Roundtable applications uncovered by the work to check whether versions are up to date."
Answer: 9964.0

User story: "Please, add {{docker-compose}} to the Jenkins nodes so we can experiment using it to manage the build of deployment containers. "
Answer: 95317.0

User story: The development environment build is made up of three builds:         1 - [BaseDevImage|https://tssw-ci.lsst.org/job/BaseDevImage/]    2 - [SalObjContainer|https://tssw-ci.lsst.org/job/SalObjContainer/]    3 - [DevelopEnvironment|https://tssw-ci.lsst.org/job/DevelopEnvironment/]         Build 2 and 3 have options to build using either "master" or "develop" branch on all packages.          Currently, the Daily RPM build start the the development environment build with the "develop" option. I would like to have the build also started with the "master" flag, to make sure we are monitoring both.      
Answer: 10126.0

User story: "Add/Replace LFO event with the proper S3 object and URL.    Implement header service publication to an S3 bucket and broadcast message accordingly    This ticket had been created automatically  Primavera ID: None"
Answer: 100611.0

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

User story: "Refactor message topology for Camera  This ticket had been created automatically Primavera ID: None"
Answer: 41808.0

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: 133796.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: 133797.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: "Write additional unit tests and stress test fits file creation  This ticket had been created automatically Primavera ID: None"
Answer: 133798.0

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

User story: "Implement changes as required by updates of the Telescope & Site CSCs  This ticket had been created automatically Primavera ID: None"
Answer: 40504.0

User story: "Implement changes as required by updates to the CCamera's XML definition  This ticket had been created automatically Primavera ID: None"
Answer: 63312.0

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

User story: "API needs to understand job status so that eventually completion is reported back to external trigger (for now can be a log).  This ticket had been created automatically Primavera ID: None"
Answer: 120656.0

User story: "make job a pipeline task operating on a specified file/ID with results available in repo  This ticket had been created automatically Primavera ID: None"
Answer: 122513.0

User story: "Express a python API that can spawn jobs (hello world) based on an incoming instruction (file/prompt).    This ticket had been created automatically Primavera ID: None"
Answer: 120656.0

User story: "Become familiar with the relavent existing and not yet existing systems that surround prompt processing (eg. OCPS, OODS)  This ticket had been created automatically Primavera ID: None"
Answer: 113705.0

User story: "Investigate addtion of graphical interface for Data Transfer Monitoring pages.  As a first thought this is intended to examine whehter a Chronograph can provide analytic summary displays for file transfer/ingest monitoring.  This ticket had been created automatically Primavera ID: None"
Answer: 115133.0

User story: "Add number of failed ingests, highlight nights with failed ingest, etc.   This ticket had been created automatically Primavera ID: None"
Answer: 115134.0

User story: "Scan ingest logs to determine cause of ingest errors.  Include in file tracking (with tabulation)  This ticket had been created automatically Primavera ID: None"
Answer: 115129.0

User story: "When appropriate (Auxtel and ComCam) query EFD for Image File Creation and add as first column of File tracking webpage  This ticket had been created automatically Primavera ID: None"
Answer: 115145.0

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

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

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

User story: "Financial Reporting for August 2020  This ticket had been created automatically Primavera ID: None"
Answer: 132328.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: "Financial Reporting for July 2020  This ticket had been created automatically Primavera ID: None"
Answer: 63465.0

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

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

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

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

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

User story: "Move Activities Into Appropriate WBS  This ticket had been created automatically Primavera ID: None"
Answer: 135554.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: 135555.0

User story: "Management Team Reviews Plan  This ticket had been created automatically Primavera ID: None"
Answer: 135590.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: 135555.0

User story: "Next cycle plan is imported into Primavera and reviewed for accuracy   This ticket had been created automatically Primavera ID: None"
Answer: 135456.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: 132311.0

User story: " Assess current resource levels based on current work  This ticket had been created automatically Primavera ID: None"
Answer: 132327.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: 132312.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: 132311.0

User story: "Adjust resources based on complete proposed plan  This ticket had been created automatically Primavera ID: None"
Answer: 135556.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: 136868.0

User story: "Test and deploy  NFS monitoring  This ticket had been created automatically Primavera ID: None"
Answer: 113916.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: "build new slurm cluster  This ticket had been created automatically Primavera ID: None"
Answer: 76367.0

User story: "migrate to new Slurm scheduler  This ticket had been created automatically Primavera ID: None"
Answer: 112357.0

User story: "Currently, the removal of excess or expired archives is manual. A lifecycle routine is needed to remove old archives and dead files.  This ticket had been created automatically Primavera ID: None"
Answer: 134160.0

User story: "Currently, the DR software reads the directories to archive from the configuration file, but no routine is in place to remove those areas that the admins do not want to archive. This story point implements that request.  This ticket had been created automatically Primavera ID: None"
Answer: 134160.0

User story: "point consolidates the code after dead code removal to reduce the memory footprint (extra configuration steps) as well as to streamline the code.  This ticket had been created automatically Primavera ID: None"
Answer: 134169.0

User story: "Throughout the implementation of DR, different approach avenues were used and discarded. This removes the extra unneeded code.  This ticket had been created automatically Primavera ID: None"
Answer: 134169.0

User story: "handle different filesystems in a modular fashion. This story point implements that request; Lustre; GPFS; POSIX (scp), AVS S3/Deep Archive  This ticket had been created automatically Primavera ID: None"
Answer: 134169.0

User story: "Planning for the September 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: 134230.0

User story: "Planning for the August 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: 103705.0

User story: "Planning for the July 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: 42978.0

User story: A set of new  version need to update for roles on the NTS:    {{sal2::ospl_version: "6.9.0"}}  {{sal2::ts_idl_version: "1.2.2_4.1.1_6.0.0"}}  {{sal2::ts_salobj_version: "5.15.0"}}
Answer: 1431.0

User story: "Create Jenkinsfile.deploy which builds a dockerfile and pushes it to dockerhub and the nexus docker registry."
Answer: 34729.0

User story: "Document the configurations needed to know for task DM-25306 . A checklist of important details to document.    This task can be marked as completed if the documentation allows you to start up the HMI.     The Instructions are here [https://ts-tma.lsst.io/v/feature-tickets-DM-25520/virtual_machines.html#eui-engineering-user-interface]"
Answer: 60749.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 problems are causing warnings in doc builds.  (There are more in the geom and afw test utilities, but those appear to still be in doxygen form.)   * [https://github.com/lsst/obs_base/blob/master/python/lsst/obs/base/butler_tests.py#L82] needs quoting around the code (or {{**}} is misinterpreted)   * [https://github.com/lsst/obs_base/blob/master/python/lsst/obs/base/camera_tests.py#L52-L57] indented an extra space   * [https://github.com/lsst/obs_base/blob/master/python/lsst/obs/base/tests.py#L80] indented an extra space"
Answer: 13433.0

User story: "The doxygen output has not lived at this location for a long time.  The proper URL should be {{https://doxygen.lsst.codes/doxygen/}}"
Answer: 14238.0

User story: "Update containers to use:         ts_salobj 5.15.0 and ts_idl 1.2.2_4.1.1._6.0.0"
Answer: 5349.0

User story: "Before we can deprecate validate_drp, we have to have the metric measurements produced in the nightly.  This means replacing validate_drp with a step to do the processing, a step to produce the measurements, and a step to send the measurements to squash (DM-25507).  This must wait until the test datasets are gen3 compatible."
Answer: 128091.0

User story: "Write the tooling needed to report the metrics computed in this new framework to SQuaSH. "
Answer: 30017.0

User story: "After talking to Michael about the possibility of using docker-compose to improve the way we manage the final container build, we agreed on starting a new repo to start fresh on this task.    I will move to this new package some work I did in DM-25324 and start exploring this venue.     This initial work will be mainly to establish the basic container build and try to integrate it in Jenkins. It is also a step in helping us manage the versioning of deployment components at the different locations. "
Answer: 34559.0

User story: "Metric AD1 implemented in the validate_drp framework should be ported to the new framework.    "
Answer: 38784.0

User story: "Metric AD1 implemented in the validate_drp framework should be ported to the new framework.    "
Answer: 38785.0

User story: "Metric AF2 implemented in the validate_drp framework should be ported to the new framework.    "
Answer: 38787.0

User story: "Metric AF1 implemented in the validate_drp framework should be ported to the new framework.    "
Answer: 38788.0

User story: "Metric PA2 implemented in the validate_drp framework should be ported to the new framework. "
Answer: 18443.0

User story: "Metric PF1  implemented in the validate_drp framework should be ported to the new framework. "
Answer: 18444.0

User story: "Renaming sciencemonkey to mobu"
Answer: 4175.0

User story: "The HTML build process of the SAL is being deprecated.  The generated documentation is taking a different format.  As such, the build scripts will need to be updated."
Answer: 38586.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "The XML 6.1 release is focused on updating the CSC entries in SALSubsystems.xml.  As this is a multiple person effort, the updates will need to be managed and reviewed carefully.  The unit tests will also need to be updated and coordinated carefully.    These updates all offer opportunities to optimize the build scripts, by using various field values (RuntimeLanguages, Generics) to target specific build steps, rather than just building everything.    This task covers this work."
Answer: 40253.0

User story: "The camera will escape delimiter characters in content of the additionalValues message attributes. The HS should be able to handle the escaped characters when parsing content."
Answer: 5532.0

User story: "Upload 02.06 of auxtel dome vendor software and create a tag.     "
Answer: 13850.0

User story: "Take the ESS code that reads the sensors and integrate it into the ESS CSC code."
Answer: 19645.0

User story: "Use the Python bindings for libgphoto2 and the GenericCamera CSC to command the all sky camera."
Answer: 64844.0

User story: "Go to the Recinto, pick up the all sky camera and Raspberry Pi and install it all at home."
Answer: 15038.0

User story: "The [Amazon S3 sink connector|https://docs.confluent.io/current/connect/kafka-connect-s3/index.html] is released under the Confluent Community License.    It presents all features required to use with the {{kafka-aggregator}} like time-based partitioners, schema evolution, and support to write Parquet format on AWS S3 and Non-AWS storage providers.      With the refactoring of {{kafka-connect-manager}} in DM-25488 in this ticket we'll the configuration class for the Amazon S3 Sink connector and the CLI interface to configure this connector.   "
Answer: 64771.0

User story: "In this ticket we plan on refreshing {{kafka-connect-manager}} in preparation to DM-25489. Some of the things we want to do:    - Modernize the Python package using tox with the following environments: {{lint}}, {{typing}}, {{py}}   - Update dependencies  - Add typing annotations  - Review documentation site  - Use GitHub Actions for CI, docs and PyPi release.   "
Answer: 59154.0

User story: Let's stop using the wildcard cert, and move to letsencrypt + cert-manager for everything.  This probably just means adding annotations to our ingress resources and a flag to say "this instance is letsencrypt-managed."
Answer: 120045.0

User story: "Use {{kafka-connect-manager}} to create the {{s3-sink}} connector and test it with the {{kafka-aggregator}}. "
Answer: 70631.0

User story: "* Add a deployment for the kafka-aggregator worker and producer  * Add a job for the kafka-aggreatator example initialization  "
Answer: 15999.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 aggregration example can be used to evaluate the performance of the kafka-aggregator if it is extended in such a way that we can control the number of source topics to be processed, the number of fields in each topic, the number of messages produced and the frequency in which the messages are produced.     Given the frequency and number of fields, the goal is to evaluate how many topics a Faust worker can process with a relatively small lag and using a typical Kafka deployment (3 broker nodes) like the Sandbox EFD deployment."
Answer: 5881.0

User story: "Implement kafka-aggregator documention site https://kafka-aggregator.lsst.io"
Answer: 34649.0

User story: "Use of Qserv dependency tarballs in Qserv container builds results in broken paths being baked into the containers (we end up with tarball build-time paths instead of Qserv container build-time paths for components such as mariadb).    Short-term fix is to disable use of tarballs in the Qserv container builds (these builds are already scheduled for demolition, and finding and implementing all the necessary path fixups is deemed not worth the effort at this time.)"
Answer: 606.0

User story: "The {{SEQNAME}} is defined in both the:  * primary_hdu.header  * primary_sensor_hdu.header    However it should only be present on the {{primary_sensor_hdu.header}}    Also add FILTER=r to the ComCam template."
Answer: 6794.0

User story: "I believe the {{ups}} directory in {{dax_imgserv}} is actually unused, as the package is installed using {{pip}} and {{setup.py}} rather than {{eups}}.  The real dependencies appear to be in {{requirements.txt}} and the {{Dockerfile}}.    The presence of this misleading information is confusing automatic dependency tooling for the product tree.  Accordingly, it would help if it were removed.  Other unused files (like {{SConstruct}}?) could be removed at the same time."
Answer: 6871.0

User story: "During our integration meeting we discussed that it would be helpful to have more behaviors added to the M2 simulator ([https://github.com/lsst-ts/ts_m2).] The obvious thing would be to implement the LUT. That means, the simulator will read the LUTs, listen to the telescope position and simulate applying the LUTs values to the different axis. This will allow us to study how M2 will behave during slews and help us identify any missing feature.     There are some relevant examples here: [https://github.com/lsst-sitcom/M2_summit_2003] "
Answer: 25163.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 default path template for raw images for obs_lsst instruments is {{raw/%(run)s/%(raftName)s/%(expId)013d-%(raftName)s-%(detectorName)s-det%(detector)03d.fits}}.  This is overridden for LATISS to be {{raw/%(dayObs)s/%(expId)013d-det%(detector)03d.fits}}.    Problems include the presence of {{run}}, which is not usually defined, and the single additional {{raftName}} level of directory hierarchy, which causes large numbers of images to end up in the same directory and related images to be in separate directories.  The LATISS template is better, but following that template for LSSTCam would still lead to hundreds of thousands of files in the same directory.    The action requested here is to come up with a better path that avoids having more than a few thousand entries at any level of the directory hierarchy.  Having it be conducive to subsetting/caching and replication would also be desirable.    I suggest that for ComCam and LSSTCam that both the {{dayObs}} and {{expId}} should be separate parts of the directory hierarchy, in that order.  With that division, {{raftName}} likely does not need to be part of the path.  Gen3 places {{filter}} in the path, but that may make it slightly more difficult to usefully subset the repo for caching purposes, so I would normally avoid that if it weren't for future compatibility."
Answer: 37165.0

User story: "In order to be able to use the ESS CSC as a generic CSC for all kinds of sensors, the existing ESS code needs to be inspected so an API can be extracted. This issue is for doing the inspection and for forming an API proposal."
Answer: 16468.0

User story: "Example of the template that should be updated:   * [https://wiki.ncsa.illinois.edu/display/LSST/New+Account+Email+Templates#NewAccountEmailTemplates-LSSTCluster]    It should make reference to [https://developer.lsst.io/services/lsst-login.html] .    Once updated language is agreed upon, this change is actually update in the older *{{lsst-pup}}* Puppet class:   * {{developer::account_provisioning}}"
Answer: 7151.0

User story: "In DM-25171 I broke the sphinx build. Fix it."
Answer: 38.0

User story: "Write a how-to document for using Vault and Vault Secrets Operator on Roundtable. Use DMTN-112 as a reference, though this doc will focus on being a how-to rather than a general-purpose architectural document."
Answer: 9875.0

User story: "We currently use {{raw/INSTRUMENT_NAME}} and {{calibs/INSTRUMENT_NAME}} as default collections for ingest.  We feel that we should flip those round to be {{INSTRUMENT_NAME/???}}. Whilst doing this also add an {{Instrument.getCollectionName}} method that will put that logic in a single place."
Answer: 2248.0

User story: "The conda mirror jobs are mostly obsolete now, we should cleanup the mirror and mirroring jobs."
Answer: 32442.0

User story: "This is to update the cookie cutter template to incorporate changes desired from a call-for-comments made (primarily) to the CAP meeting attendees."
Answer: 12691.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 deployment scripts use version 2.1.0 of dm_csc_base.  This has to be updated to version 2.1.1"
Answer: 1512.0

User story: "Rho Statistics are metrics to validate the PSF modelling. In particular, it quantifies how PSF modelling errors propagate into shear-shear correlation functions which are the scientifically interesting quantities. Rho Statistics were implemented in DM-23539. This ticket is to dispatch these metrics to the SQuaSHboard to regularly track the performance of PSF modelling and how it evolves through the stack development."
Answer: 133949.0

User story: "Currently we define components for StorageClasses to be the components that a dataset can be disassembled into or reassembled from.  This is fine for things like masks and wcs but gen2 supports read-only components such as BBox that allow you to efficiently query information about a specific dataset without having to fetch the entire dataset.    Getting this to work is fairly straight forward if there is no disassembly. If we do disassemble then I need to think about how we forward the BBox request to the correct component."
Answer: 21506.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 Rubin Obs DM team are actively collaborating with the LSST:UK LSB working group to develop LSB sky subtraction and source fidelity metrics. This ticket injects several fake source catalogues produced by the LSST:UK LSB WG into the stack, and analyses their outputs.     Resources:   * [Insert Fakes LSST Community link|https://community.lsst.org/t/new-tasks-for-fake-source-insertion/3722]  * [Insert Fakes source code|https://github.com/lsst/pipe_tasks/blob/master/python/lsst/pipe/tasks/insertFakes.py]    A number of input catalogues were provided, namely: {{model_faceon.fits}}, {{model_edgeon.fits}}, {{model_icl.fits}} and {{model_fornax_tab.fits}}. On closer analysis, a number of issues were discovered with these data, necessitating some modifications. Specifically, the requested pointings did not fall within tract 9813, one of our RC2 contuinally processed regions (see the tract figure attached below). To allow us to use these input data, we repositioned each object to move it into the centre of tract 9813. In addition, RA/Dec values were translated into radians, the column {{sourceType}} was added indicating that these sources are {{galaxy}} type, and Sersic indices were clipped to the range 0.3 < n < 6.2.     The modified Fornax dataset was processed using {{insertFakes}}, and then processed with detection turned on using {{multiBandDriver}}. To produce a final output object table, we finished processing using {{writeObjectTable.py}}, {{transformObjectCatalog.py}} and {{consolidateObjectTable.py}}. A trimmed version of this object table is attached to this ticket below.     All working is shown in the attached Jupyter Notebook, available in {{.ipynb}} or {{.pdf}} format below. We also include two example images below showcasing the insertion of a typical Sersic source in all five bands: one prior to final sky subtraction ({{deepCoadd}}) and one after final sky subtraction ({{deepCoadd_calexp}}).     All outputs are available via the LSP in this directory: {{/home/<USER>fakes_lsstuk/outputs/fornaxmod}}"
Answer: 32295.0

User story: "The layout of spawner and especially reflector classes is weird and confusing.  Some of that's on us and some of it is on KubeSpawner.  Make it less weird and confusing."
Answer: 8402.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: "Remove the history of trajectory after issuing the *stop* command in the tracking. The Simulink model uses the *LsstCmdSet* object to get the time, position, and velocity of tracking target. If the user issues the *stop* command before the finish of slew, the rotator stops without the update of *LsstCmdSet*. This means if the user issues the *trackStart* command, the rotator will transition to the *SlewingAndTracking* sub-state and try to track the unfinished target based on *LsstCmdSet*.    In the following figure, there are two targets: (1) position=1.2 deg, velocity=0.01 deg/sec, and (2) position=3.0 deg, velocity=-0.01 deg/sec. The final *track* command is at time=6.05 second. Issue the *stop* command at time=7 second and *trackStart* command at time=9 second. We can see the rotator tries to finish the second target after it is back to the *SlewingAndTracking* sub-state.   !trackStopBeforeSlewDone.png|thumbnail!    To solve this problem, we need to update the *LsstCmdSet* object to set the position to be the rotator's position or position command, and the velocity to be 0 after the stop completes (*Flags_stopComplete* ==1.0) as the following:   !trackWithStopAnd3rdTargetOfPosNowAndRewiteCmdPosAndVel.png|thumbnail!    There are four possible options to do this:   (1) Update the *LsstCmdSet* object in *ts_rotator_controller* once *Flags_stopComplete*==1.0.   (2) Let *ts_rotator* update the *LsstCmdSet* object by sending the new *track* command once *Flags_stopComplete*==1.0. However, we prefer to use the command acknowledgement to know the *stop* command is finished or not in a latter time.   (3) Add a *reset* command or something similar in *ts_rotator* and *ts_rotator_controller* to let the rotator controller updates the position and velocity of *LsstCmdSet*.   (4) Update the Simulink model to add a latch to determine when to use the new *track* command. This will add the complexity to the Simulink model because it is not designed in that way originally. It may not be easy to debug in a latter time. However, this will not affect the *ts_rotator* and *ts_rotator_controller* at all.    I do not prefer the option 1 because there will be multiple places to write the data into the global variable of *LsstCmdSet*. Originally, it is updated by *ts_rotator* only. Or more accurately, the *ts_rotator* issues the *track* command to update the *LsstCmdSet* in *commanding.c* in *ts_rotator_controller*. If the option 1 is chosen, I need to let the *actuator.c* to be able to update the *LsstCmdSet* object. Think more deeply, for the option 3, it is the same thing. The only benefit for option 3 is that the CSC user knows the *LsstCmdSet* is changed. But if the CSC user does not care about this, maybe the option 1, 2, or 4 is better. If we consider the coherence of code, maybe the option 1 or 4 is the best solution."
Answer: 22442.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: "profile::allow_ssh_within_cluster includes the following params (and more):   String[1] $ssh_private_key,   String[1] $ssh_public_key,   Array[ String, 1 ] $userlist,   I need to update it so that the userlist array can be empty, to allow for the possibility that there are no users who should have managed keys. And in that case, I'd rather be able to specify empty String values for the String params (rather than, say, 'foo')."
Answer: 8325.0

User story: "We just had an issue with the latex_lsstdoc template (added in DM-25331) when the user entered a linefeed as part of the document title. Since that title is used as the GitHub description, we unexpectedly got an error from the GitHub API.    This ticket is to fix that specific problem and also check if there are other places where user input validation and cleaning could be applied."
Answer: 181.0

User story: "We currently set up a few environment variables up by hand when running the pipelines.  This is somewhat error prone, so I'd like to convert to using eups to handle that more automatically.  This could also include adding proper Python modules."
Answer: 8844.0

User story: "[~<USER> reports that when he does a (gen2) butler.get on a raw LSSTCam/BOT file then the fix_header corrections are applied but when he gets {{raw_md}} they are not applied."
Answer: 5774.0

User story: "Examining the package versions we store in butler repository when running pipelines, it is clear that we are not including the details of our conda environment.  We need to add code that will read the conda env and include all the versions (possibly overwriting version information determined from the current technique). This will have the advantage of giving us details of {{boost}} and related packages that are not visible to python.    One wrinkle is that I do not yet see an obvious way to get this information without having {{base}} run {{conda list -e}}."
Answer: 106553.0

User story: "Implement a simple example visit level measurement."
Answer: 1254.0

User story: "Data ingested (see DM-24396 ) look fine when directly queried from Qserv, but the timestamp field  {code:java}  obsstart{code}  in  {code:java}  desc_dc2_run12p_v4e.ccdvisit{code}  when queried from TAP only a single character ('2') is returned; the datatype is identified as bytes1.   A typical value as returned by Qserv directly is  {code:java}  2025-11-27 01:55:42  {code}"
Answer: 31644.0

User story: aiokafka 0.6.0 resolves a significant issue that has affected the stability of our Kafka consumers, namely that the UnknownMemberId exception as being raised, rather than aiokafka retrying.    Related services are:   * templatebot   * lsst-templatebot-aide   * ltd-events   * sqrbot-jr (it doesn't operate a consumer, but should be updated nonetheless)   * ook         If this ticket succeeds, we may not need to implement DM-23996 (an app to create a drumbeat Kafka topic that restarts consumers based on a "dead-man-switch" concept.
Answer: 1717.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: "Due to work on MTDomeTrajectory the command, telemetry and event XML files for the Dome have been updated. Adopt the DCS and mock controller to these changes."
Answer: 4903.0

User story: "In DM-25338 we implemented time-based and size-based retention policies at the broker level for the EFD topics. Data retention for metrics and Control Center topics is controlled by [a different configuration|https://docs.confluent.io/current/control-center/installation/configure-control-center.html]        "
Answer: 2.0

User story: "In DM-25327 I forgot to check the sphinx build in daf_butler before merging. This broke the weekly."
Answer: 215.0

User story: "Make something to help populating secret values into vault for new environments, either prompting things from the user or generating random values."
Answer: 25361.0

User story: "Currently obs_base formatters are all in the top level python/lsst/obs/base directory with long names. As we get more of them it makes sense to move them into a formatters directory as is done in daf_butler.  Similarly in daf_butler we use names like {{lsst.daf.butler.formatters.yamlFormatter.YamlFormatter}} and this has a lot of repetition. Following a discussion on Slack [~<USER> agreed that the formatter in the file name could be removed without resulting in confusion since we always use the full names in configs.    Therefore in this ticket I will:    # Move obs_base formatters to a formatters directory and use the new name scheme.  # Shorten the names of the formatter python files to drop Formatter in daf_butler.    Note this will break existing repositories but the fix is simple and other backwards compatibility breakage this week means that we can make this change without any additional impact."
Answer: 483.0

User story: "Rather than checking in the built chart artifacts, use https://github.com/helm/chart-releaser-action to generate a charts repository on commit. This will make it far easier to use automated tools like renovatebot to update Docker tags inside charts."
Answer: 28056.0

User story: "There is some duplication that I think we can reduce by factoring things out into base classes that can be inherited in multiple place.  I also thing we may find we can push things up into {{MetricTask}}."
Answer: 9742.0

User story: "Add the code for writing and reading alert packets into Kafka to lsst.alert.stream, since that package is distributed on PyPI already. This code will be used by community broker authors."
Answer: 1210.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "i am trying to find tools that will allow us to peak into postgresql performance with the same level of details as oracle 10046 trace data.    i came across bcc and bpftrace and they look promising but the recommended kernel version is 4.9. currently we are on 3.1.    would it be possible upgrade to 4.9? i'm indifferent as to whether that also involved upgrading to centos 8.    just to be clear, i don't have any experience with these tools but they look very much like what i am looking for and I would like to evaluate them against postgresql activity if at all possible."
Answer: 28233.0

User story: "begin conversion of the existing pipetask command in ctrl_mpexec to the click framework, based on or similar to the butler command.    Implement the build subcommand. My goal is to rewrite/refactor as little of the existing implementation code as possible. There is room for improvements (e.g. don't propagate an 'args' container), but it would be better to fix this after the argparse framework is removed so we don't have to work with parallel implementations."
Answer: 48781.0

User story: "Chair the Science Organizing Committee for this year's remote Project and Community Workshop."
Answer: 106325.0

User story: "NPCF:   lsst-adm01   lsst-repos01   lsst-git01   lsst-pup-npcf    NCSA 3003:   lsst-adm-ncsa   lsst-pup-ncsa"
Answer: 25368.0

User story: "The following verify-worker nodes have been transitioned out of Slurm and will be removed from the config during the June 25 PM:   verify-worker[37-40] -> HTCondor DAC   verify-worker[43-44] -> HTCondor Test   verify-worker[55-60] -> k8s"
Answer: 20067.0

User story: "Prepare and test newer servers in NCSA 3003 (using lsst-pup-ncsa) along with NPCF servers (using lsst-pup-npcf). Currently we know the following needs to be prepared and tested:   * Upgrade to CentOS 7.8   * Update other YUM repo pakrat snapshots to ~2020-06-10   * Remove devtoolset-3 packages from Qserv (qserv-test01)   * Update duo YUM repo (duosecurity) to point to lsst-repos01   * Make sure OS update script will allow NOT rebooting, even if kernel is updated"
Answer: 17364.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: While running ci_hsc_gen3 against the PostgreSQL server, I've been seeing the following error message (Usually > 100 times per ci_hsc_gen3 run when it happens):  {noformat}  sqlalchemy.pool.impl.QueuePool ERROR: Exception during reset or similar  Traceback (most recent call last):    File "/software/lsstsw/stack_20200515/python/miniconda3-4.7.12/envs/lsst-scipipe/lib/python3.7/site-packages/sqlalchemy/pool/base.py", line 693, in _finalize_fairy      fairy._reset(pool)    File "/software/lsstsw/stack_20200515/python/miniconda3-4.7.12/envs/lsst-scipipe/lib/python3.7/site-packages/sqlalchemy/pool/base.py", line 880, in _reset      pool._dialect.do_rollback(self)    File "/software/lsstsw/stack_20200515/python/miniconda3-4.7.12/envs/lsst-scipipe/lib/python3.7/site-packages/sqlalchemy/engine/default.py", line 540, in do_rollback      dbapi_connection.rollback()  psycopg2.OperationalError: SSL SYSCALL error: EOF detected  {noformat}  I've only seen the following once:  {noformat}  sqlalchemy.pool.impl.QueuePool ERROR: Exception during reset or similar  Traceback (most recent call last):    File "/software/lsstsw/stack_20200515/python/miniconda3-4.7.12/envs/lsst-scipipe/lib/python3.7/site-packages/sqlalchemy/pool/base.py", line 693, in _finalize_fairy      fairy._reset(pool)    File "/software/lsstsw/stack_20200515/python/miniconda3-4.7.12/envs/lsst-scipipe/lib/python3.7/site-packages/sqlalchemy/pool/base.py", line 880, in _reset      pool._dialect.do_rollback(self)    File "/software/lsstsw/stack_20200515/python/miniconda3-4.7.12/envs/lsst-scipipe/lib/python3.7/site-packages/sqlalchemy/engine/default.py", line 540, in do_rollback      dbapi_connection.rollback()  psycopg2.OperationalError: SSL error: decryption failed or bad record mac  {noformat}    This doesn't seem to actually affect the run.  This doesn't happen 100% of the runs.  It only seems to happen when ci_hsc_gen3 runs pipetask (i.e., never butler commands).  Here are counts from a few runs (from grep of stdout/stderr):  {noformat}  1591627439/cihsc_w_2020_23_1591627439_postgres.out:149  1591633412/cihsc_w_2020_23_1591633412_postgres.out:136  1591819226/cihsc_w_2020_23_1591819226_postgres.out:0  1591886082/cihsc_w_2020_23_1591886082_postgres.out:140  1591888106/cihsc_w_2020_23_1591888106_postgres.out:0  1591889656/cihsc_w_2020_23_1591889656_postgres.out:136  {noformat}    Google searches of the error messages makes it sound like a multiprocessing code issue (e.g., https://virtualandy.wordpress.com/2019/09/04/a-fix-for-operationalerror-psycopg2-operationalerror-ssl-error-decryption-failed-or-bad-record-mac/).   I had found result that talked about TCP keepalive so I tried  pool_pre_ping=True in the create_engine call, but that didn't seem to make any difference.
Answer: 11594.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "In DM-25325 support was added for YAML serialization but the serialization still requires a file name to be given.    It would be helpful for butler gen3 s3 datastore to support a serialization to from bytes by updating the PackagesFormatter (created in DM-25327)."
Answer: 1726.0

User story: "Current simulator FPGA code wasn't touched from 2018. After what appears as changes into simulator cRIO modules, the code wasn't updated and most likely the new incarnation of the simulator wasn't run. The purpose of this task is to make sure the simulator can at least answer ILCs (Modbus) requests."
Answer: 10195.0

User story: "Write a trampoline class (https://pybind11.readthedocs.io/en/stable/advanced/classes.html#overriding-virtual-functions-in-python) so that we can subclass Psf directly in python."
Answer: 16307.0

User story: "Due to disruptions caused by the coronavirus pandemic and the delay in producing sample alerts for the proposing teams, we issued a  delay in the due date for community broker proposals by not less than six months, with a commitment to provide further updates on the status of the call on or before June 15.    This ticket covers the work needed to interact with the SAC to provide guidance on the use of sample alerts in the proposals and any updates due to the evolving  coronavirus pandemic    "
Answer: 49125.0

User story: "Create CentOS SD image with SAL for Raspberry Pi 4 for future use."
Answer: 2834.0

User story: "AS discussed in DM-24803 we need a way to manage schema versions defined in daf_butler. This needs some additional decisions though:  - do we want one global schema version or per-component  - datastore seems to be special case  - dimensions is also very special  - how do we detect schema change  - etc."
Answer: 20601.0

User story: "For schema stability we need a place where we can store identifying information for schema itself and various configuration-related info as well. That will server as a sort of metadata for the rest of the schema and data in registry. To be usable from many releases it itself needs to be super-stable but we also should be be able to store all sorts of metadata in it, exact structure of that is not possible predict today. I think the most generic solution for that is a simple key-value store with arbitrary keys and values encoded as strings. All other structures can be mapped to key/value using reasonable rules, though some care is certainly needed to avoid name collision."
Answer: 2914.0

User story: "This task covers the work to update the build scripts after the SAL is updated with the new RPM naming format.         The Java/Maven name format was also updated.  The build scripts will also need to be updated."
Answer: 13251.0

User story: "Update the M2 xml based on the latest LTS-162. This will also add some interfaces needed to support the level-3 integration test (integration test in software/ simulator level to check the communication of components)."
Answer: 9070.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 Dome temperatures are expressed in Celsius but the AstroPy unit for temperature is deg_C. Please fix."
Answer: 19.0

User story: "Following discussion with [~<USER>, this ticket is for the reprocessing of the RC2 dataset with the 20.0.0 release candidate. [~<USER> or [~<USER> will add the release candidate details to this ticket . "
Answer: 12541.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Update the code in ts_ATDomeTrajectory based on lessons learned from ts_MTDomeTrajectory.    The main change is to support more sophisticated algorithms by sending the next target event to the algorithm.    Additional changes wanted:  * Eliminate use of astropy angles; we aren't gaining any benefit and they add clutter.  * Use {{handle_summary_state}} instead of {{report_summary_state}}."
Answer: 31041.0

User story: "After YAML support was added to base Packages in DM-25325 we started to get failures in standalone builds of {{base}} the first time scons was typed. It seems that the YAML constructor assumes that {{Packages}} full name is {{base.packages.Packages}} rather than {{lsst.base.packages.Packages}}.  This causes the {{isinstance}} test to fail. Running the tests a second time fixes the problem for reasons we aren't entirely sure about.    The fundamental problem seems to be that we are using namespace packages in {{base}} and do not have a {{\_\_init\_\_.py}}. Adding one fixes the problem."
Answer: 215.0

User story: "Security would like NFS v4 mounts to be used for new nodes, when possible, including the pgsql nodes. Let's revisit trying to get an NFS v4 mount set up here.    We can also use test11 as a test node in order to not interfere with work on pgsql04."
Answer: 20170.0

User story: "Help [~<USER> to monitor Kafka during loading tests of the EFD on the NCSA test stand.     This is a temporary setup since we don't have the Confluent license to run the Control Center.     We are investigating open-source alternatives, the Yahoo CMAK tool for managing Kafka seems like a good option: [https://github.com/yahoo/CMAK]   "
Answer: 2.0