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: "From @<USER>in #ts-software Slack:         please update your CSCs to be compatible with ts_salobj 6. You can easily retain version 5 compatibility at the same time. The version history is here: [https://ts-salobj.lsst.io/v/PR-141/version_history.html]. Basically ts_salobj 6 removes all the things in 5 that were deprecated (most or all of which should be printing deprecation warnings). Some highlights:  • use {{BaseCsc.amain}} instead of {{main}} to start your CSCs (in your bin script).  • The {{initial_simulation_mode}} CSC constructor argument is no longer accepted. Use {{simulation_mode}} instead.  • The {{fault}} method now requires an error code.  • Do not set the summary_state attribute in CSCs; it is read-only. Most code I have seen that does this is going into fault state; call the {{fault}} method for that.  Also for later, when you no longer need ts_salobj 5 compatibility: version 6 offers simplified support for simulation mode. See the manual (how to write a CSC, simulation section) and recent changes to ts_ATDome to see how it works. Meanwhile you will see a deprecation warning when you start CSCs that support simulation."
Answer: 58732.0

User story: "Please could I have access to the shared gen 3 repo for testing gen3 code at scale. My username is sr525."
Answer: 846.0

User story: "We have yet to enable a flake8 travis job and branch protections for this repo.  As such, our code is becoming very flake8 un-compliant.  This ticket is to make all of {{pipe_analysis}} flake8 compliant while allowing for the [Rubin Style Guide exceptions to PEP 8 |https://developer.lsst.io/python/style.html?highlight=flake8#exceptions-to-pep-8], and then turn on the flake8 travis job and branch protections so that no further violations will be able to sneak their way in."
Answer: 16226.0

User story: "Photodiode data from the BOT comes as a .txt file. This needs to be made usable by the PTC task, but we don't need to properly engineer the solution right now, as this ticket is just for Gen2, and in support of BOT work.    This ticket is to get it working in some form. A further ticket will be filed to sort out what will surely be teething problems with how the rendezvous is done with the images it corresponds to, and makes it all work in Gen3, etc..."
Answer: 27315.0

User story: "There is a bug in the scarlet testing framework that causes it to update the table of merged branches each time. This update will remove the duplicates."
Answer: 12963.0

User story: "Update to the latest master on <USER>scarlet."
Answer: 45753.0

User story: "Open Distro for Elasticsearch supports OpenID Connect and the incremental change over the existing support for Chronograf is small. Add support and use this for Elasticsearch authentication instead of the dual-layer Gafaelfawr auth request handler plus password authentication."
Answer: 36128.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, {{butler convert}} only does the write curated calibrations step when there is a gen2 calibrations registry in the repo.  The origin of this logic is unclear, and in regular usage people will expect the curated calibrations to come over when doing a {{butler convert}}.  "
Answer: 718.0

User story: "During development of a {{pipelinetask}} it may happen that the developer will erroneously define an incorrect {{datasetType}} (with incorrect {{dimensions}}, or {{storageClass}}, etc.). At this point it is impossible to recover without blowing away the registry or sqlite hacking because any fix to the entry will raise a {{ValueError: Supplied dataset type inconsistent with registry definition}} error.      We should not allow the ability to delete datasets if a dataset type is associated with them that is being deleted. This would imply that the dataset type has been used. Instead a user should first delete the relevant collection/dataset before deleting the dataset type."
Answer: 31618.0

User story: "[~<USER> has a new set of sensor positions derived from the updated engineering diagram.  He will push them to a branch and I will run {{obs_lsst}} through CI and review the PR."
Answer: 407.0

User story: "it should describe how to control subsystem log levels, similar to pipetask:  {code:java}-L LEVEL|COMPONENT=LEVEL, --loglevel LEVEL|COMPONENT=LEVEL                          logging level; supported levels are                          [trace|debug|info|warn|error|fatal]   {code}       It has also come up recently (e.g. in DM-26645) that the default log level for the `butler` and `pipetask` commands should be changed to INFO, from WARNING as it currently is now. "
Answer: 18873.0

User story: "This task is to create the Dockerfile which can be used to create three different images. These images are;    CentOS7 + LabVIEW 2018 + Caraya + VIPM  CentOS8 + LabVIEW 2020 + Caraya + VIPM  CentOS8 + LabVIEW 2020 + Caraya + VIPM    This Dockerfile will help speed to process of deploying LabVIEW related projects and is related to the CTIO LabVIEW deployment strategy.    *Acceptence Criteria*   - The Docker file is capable of creating the 3 images that are described above by using 3 different CLI's"
Answer: 50598.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: An instrument name needs to be provided by pipetask (as an explicit argument, or via the Pipeline object) in order to load obs_* package overrides, and generally should also be provided as part of the -d argument that constraints data IDs, and it is confusing to users that providing an instrument in one place does not satisfy the other.    For now, I think we should focus on passing the instrument from the Pipeline or explicit argument to the data ID constraint, because it's impossible in general to extract an instrument from the latter even if it ought to be possible for most exceptions.  I think this is as simple as taking the original -d argument and rewriting it as "instrument='{instrument}' AND ({original})".  If there's already an instrument in the original, it should be a harmless.
Answer: 19517.0

User story: "As reported in DM-25694, 6145 exposures (out of 20,679) failed with fatal errors during single frame processing of DECam galactic bulge data (in i- and g-band). Of these, 166 were RuntimeErrors, e.g.      {code:java}  slurm_pccd/job254037-04.out:processCcd FATAL: Failed on dataId={'visit': 205429, 'date': '2013-05-11', 'filter': 'g', 'hdu': 36, 'ccdnum': 3, 'object': 'B2'}: RuntimeError: Unable to measure aperture correction for required algorithm 'base_GaussianFlux': only 1 sources, but require at least 2.{code}  and  {code:java}  slurm_pccd/job254037-05.out:processCcd FATAL: Failed on dataId={'visit': 216990, 'date': '2013-06-24', 'filter': 'i', 'hdu': 13, 'ccdnum': 39, 'object': 'B2'}: RuntimeError: Unable to measure aperture correction for required algorithm 'base_PsfFlux': only 0 sources, but require at least 2.{code}    I need to identify the cause, or causes, of this error and suggest a solution. Implementation of the solution is expected to be made on a new ticket."
Answer: 28562.0

User story: "As reported in DM-25694, 6145 exposures (out of 20,679) failed with fatal errors during single frame processing of DECam galactic bulge data (in i- and g-band). Of these, 386 were RuntimeErrors, e.g.  {code:java}  slurm_pccd/job254037-05.out:processCcd FATAL: Failed on dataId={'visit': 216048, 'date': '2013-06-22', 'filter': 'i', 'hdu': 34, 'ccdnum': 1, 'object': 'B2'}: RuntimeError: No objects passed our cuts for consideration as psf stars{code}    I need to identify the cause, or causes, of this error and suggest a solution. Implementation of the solution is expected to be made on a new ticket."
Answer: 28569.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 reported in DM-25694, 6145 exposures (out of 20,679) failed with fatal errors during single frame processing of DECam galactic bulge data (in i- and g-band). Of these, 131 were TaskErrors, e.g.  {code:java}  slurm_pccd/job254037-02.out:processCcd FATAL: Failed on dataId={'visit': 427318, 'date': '2015-04-02', 'filter': 'g', 'hdu': 35, 'ccdnum': 2, 'object': 'B1'}: TaskError: All pixels masked. Cannot estimate background{code}    I need to identify the cause, or causes, of this error and suggest a solution. Implementation of the solution is expected to be made on a new ticket."
Answer: 18519.0

User story: "As reported in DM-25694, 6145 exposures (out of 20,679) failed with fatal errors during single frame processing of DECam galactic bulge data (in i- and g-band). Of these, 2211 were LengthErrors, e.g.  {code:java}  slurm_pccd/job254037-01.out:processCcd FATAL: Failed on dataId={'visit': 223903, 'date': '2013-08-06', 'filter': 'i', 'hdu': 52, 'ccdnum': 48, 'object': 'B1'}: LengthError:{code}  and  {code:java}  slurm_pccd/job254037-00.out:processCcd FATAL: Failed on dataId={'visit': 209536, 'date': '2013-06-07', 'filter': 'g', 'hdu': 19, 'ccdnum': 21, 'object': 'B1'}: LengthError:{code}  I need to identify the cause, or causes, of this error and suggest a solution. Implementation of the solution is expected to be made on a new ticket."
Answer: 31576.0

User story: "Make the ts_athexapod package compatible with ts_salobj 6 while retaining compatibility with version 5."
Answer: 234.0

User story: "As reported in DM-25694, 6145 exposures (out of 20,679) failed with fatal errors during single frame processing of DECam galactic bulge data (in i- and g-band). Of these, 3108 were IndexErrors, e.g.  {code:java}  slurm_pccd/job254037-01.out:processCcd FATAL: Failed on dataId={'visit': 223903, 'date': '2013-08-06', 'filter': 'i', 'hdu': 54, 'ccdnum': 53, 'object': 'B1'}: IndexError: No viable PSF candidates survive{code}  I need to identify the cause, or causes, of this error and suggest a solution. Implementation of the solution is expected to be made on a new ticket."
Answer: 31578.0

User story: "Cycle 12 will have the experimental versions of salobj 6.0.0  and sal 5.0.0.    This version implements partitions for each individual components, subdivided in a partition for command reading/writing and data reading/writing. "
Answer: 16926.0

User story: "The ScriptQueue's {{showScript}} command fails after logging a traceback if the specified script does not exist. Instead it should fail gracefully with a simple error message and no logged traceback.    This is also a problem for the {{move}} and {{requeue}} commands."
Answer: 1242.0

User story: "There is unused code in MySqlConfig that is showing up in a segmentation fault. While it is difficult to explain how the code could cause a segmentation fault removing it is certainly beneficial. See DM-26575."
Answer: 362.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 ts_salobj the read topics (ReadTopic, RemoteEvent, REmoteTelemetry, and ControlllerCommand) use a default queue_len of 100. Use DDS_READ_QUEUE_LEN instead.    Also remove deprecated max_history argument from ControllerCommand's constructor."
Answer: 12002.0

User story: "Makes M1M3 SS sends (every second) logevent_heartbeat. This is software/SAL heartbeat, unrelated to GIS (Global Interlock System) heartbeat. The current incarnation of the M1M3 SS CsC C++ code doesn't send those software heartbeats. CsC triggers hardware/interlock heartbeats, send over wires hooked to cRIO DIOs."
Answer: 9469.0

User story: "In case of {{rsync}} base transfers, the list of the files that are ready to be ingested is inferred by parsing {{rync}}'s logs. Writing this log files is not an atomic operation so there is a good chance that manager's search plugin may start parsing a log file which has not been fully transferred yet. The file will be erroneously flagged as already parsed and any files added to that after that will be effectively ignored.    The goal is two-fold. Firstly, implement some heuristic which will allow the search plugin to determine if a log file has been fully transferred. Secondly, add a safeguard which will detect and log occurrences of such events."
Answer: 8852.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: Steps to reproduce using w_2020_35    With an empty bucket at s3://hfc-w35/    I created a butler.yaml like this  {noformat}  datastore:    cls: lsst.daf.butler.datastores.s3Datastore.S3Datastore    root: s3://hfc-w35/  registry:    db: sqlite:////scratch/<USER>trash/butler35/gen3.sqlite3  {noformat}    Then I could create the butler repo with   {noformat}  butler create s3://hfc-w35/ --seed-config butler.yaml --override  {noformat}    In a python prompt this failed     {noformat}  from lsst.daf.butler import Butler  Butler("butler.yaml")  {noformat}    {noformat}  Traceback (most recent call last):    File "<stdin>", line 1, in <module>    File "/software/lsstsw/stack_20200515/stack/miniconda3-4.7.12-46b24e8/Linux64/daf_butler/19.0.0-148-g38150800+de92faa26f/python/lsst/daf/butler/_butler.py", line 219, in __init__      butlerRoot=butlerRoot)    File "/software/lsstsw/stack_20200515/stack/miniconda3-4.7.12-46b24e8/Linux64/daf_butler/19.0.0-148-g38150800+de92faa26f/python/lsst/daf/butler/core/datastore.py", line 289, in fromConfig      return cls(config=config, bridgeManager=bridgeManager, butlerRoot=butlerRoot)    File "/software/lsstsw/stack_20200515/stack/miniconda3-4.7.12-46b24e8/Linux64/daf_butler/19.0.0-148-g38150800+de92faa26f/python/lsst/daf/butler/datastores/s3Datastore.py", line 122, in __init__      super().__init__(config, bridgeManager, butlerRoot)    File "/software/lsstsw/stack_20200515/stack/miniconda3-4.7.12-46b24e8/Linux64/daf_butler/19.0.0-148-g38150800+de92faa26f/python/lsst/daf/butler/datastores/remoteFileDatastore.py", line 77, in __init__      if not self.root.exists():    File "/software/lsstsw/stack_20200515/stack/miniconda3-4.7.12-46b24e8/Linux64/daf_butler/19.0.0-148-g38150800+de92faa26f/python/lsst/daf/butler/core/_butlerUri.py", line 1115, in exists      exists, _ = s3CheckFileExists(self, client=self.client)    File "/software/lsstsw/stack_20200515/stack/miniconda3-4.7.12-46b24e8/Linux64/daf_butler/19.0.0-148-g38150800+de92faa26f/python/lsst/daf/butler/core/s3utils.py", line 133, in s3CheckFileExists      obj = client.head_object(Bucket=bucket, Key=filepath)    File "/software/lsstsw/stack_20200515/python/miniconda3-4.7.12/envs/lsst-scipipe/lib/python3.7/site-packages/botocore/client.py", line 316, in _api_call      return self._make_api_call(operation_name, kwargs)    File "/software/lsstsw/stack_20200515/python/miniconda3-4.7.12/envs/lsst-scipipe/lib/python3.7/site-packages/botocore/client.py", line 626, in _make_api_call      raise error_class(parsed_response, operation_name)  botocore.exceptions.ClientError: An error occurred (302) when calling the HeadObject operation: Found  {noformat}  
Answer: 251.0

User story: "Review the updated trajectory document of TMA. This is a follow-up task of DM-26091. The updated document is [^TrajectoriesDoc.pdf], which replies the questions in [^TeWei_200730.docx]."
Answer: 12823.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: "Empty files are not handled optimally by the endpoint manager. Firstly, all empty files, except the one which was discovered as first are treated as duplicates and deleted.  Secondly, the manager still tries to ingest the empty file to the database system which results in rather obscure errors coming from the ingest software being recorded in the database. The goal is to make the manager properly save all empty files in the storage area for future reference and provide a clear message in such a case."
Answer: 1077.0

User story: "Task to fix any issue found in the deployment of cycle 11. "
Answer: 1567.0

User story: "Generating terabytes of data can take some time and there are high odds of the process being interrupted. The status should be stored on disk in such a way that it can be easily used to continue with a system restart."
Answer: 23105.0

User story: Implement Tiago's new partition naming scheme:  prefix + "." + SAL_component_name + "." + suffix  where:  • prefix is given by env var LSST_DDS_PARTITION_PREFIX  • suffix is ".cmd" for command_ topics and ".data" for all other topics, including ackcmd    If env var LSST_DDS_PARTITION_PREFIX is not defined then fall back to the old env var LSST_DDS_DOMAIN, with a warning.
Answer: 18614.0

User story: Implement Tiago's new partition naming scheme:  prefix + "." + SAL_component_name + "." + suffix  where:  • prefix is given by env var LSST_DDS_PARTITION_PREFIX  • suffix is ".cmd" for command_ topics and ".data" for all other topics, including ackcmd    If env var LSST_DDS_PARTITION_PREFIX is not defined then fall back to the old env var LSST_DDS_DOMAIN, with a warning.    The idea is that each Remote and Controller should have just one subscriber and one publisher, and that the durability service for a Controller will not read topics that a controller writes: events, telemetry, and the "ackcmd" topic.  
Answer: 13570.0

User story: "DM-25748 finished the bulk of the testing and code to create randoms for fakes in AP. Next step is to finish tests for the runQuantum method and test an initial run of the ap_pipe pipeline with fakes inserted."
Answer: 39966.0

User story: "Test Python asyncio socket behavior when one end of a connection hangs up and update https://confluence.lsstcorp.org/pages/viewpage.action?pageId=140284619 accordingly."
Answer: 84.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-26476 we discuss a need for an observation reason to be added to gen3 registry. This requires that we add the concept to ObservationInfo. This will be a string that can have any value.    Provide a default implementation that returns a reason of "science" for observation_type of science, and "calibration" for all other cases. Then provide obs_lsst implementation that looks for TESTTYPE header and overrides it with that value. We do not yet know the name of the header that will be used for LSSTCam and ComCam.    Adding reason suggests that using "science" for observation_type might be too generic since that was previously trying to serve both roles. Code already relies on "science" for observation type though so it will be difficult to switch those to using reason instead.
Answer: 5437.0

User story: "Upgrade the Vault software and Helm chart"
Answer: 40258.0

User story: Add basic escalation support to the watcher: set the escalated, escalateTo and timestampEscalate flags in alarm events. Don't do anything with the information, just set it.    This is a necessary precursor to full alarm escalation: CRITICAL alarms that are not acknowledged quickly enough are "escalated" by calling or texting somebody. Just having the {{escalated}} field set is sufficient to support writing escalated alarms to a Slack channel, using tools we already have.
Answer: 26162.0

User story: "Change the --simulate argument in BaseCsc.amain to be true/false if there are only two valid simulation modes."
Answer: 119.0

User story: "Ingest two partitioned tables {{allwise_p3as_psd}} and {{allwise_p3as_mep}} of catalog {{WISE}} into the cluster using the new Ingest system. This effort is similar to the one of [DM-26390]. Note that input data of the catalog need to be repartitioned to the more efficient scheme:  * {{stripes}}: *340*  * {{sub-stripes}}: *3*  * {{overlap}}: *0.01667*    Put scripts and configurations used during the ingest into the dedicated Git package: https://github.com/lsst-dm/qserv-ncsa-wise"
Answer: 13584.0

User story: "In DM-26179 I put together a first cut at a process for converting {{validate_data_hsc}} from gen2 to gen3.  I used the {{SConstruct}} file in {{ci_hsc_gen3}} as a starting point, but because of a few stops and starts, I think the final process is significantly more complicated than it needs to be.    I'd like to explore here how to do this in as few steps as possible."
Answer: 25955.0

User story: Continue testing DDS deployments with the NCSA test stand.   Explore the impact of seperating subsystems into dds "partitions"
Answer: 20018.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: "Presentation on last Thursday co-work (Aug 27) about the next developments on SQuaSH. It covers things we plan on complete still this cycle and material to help discussion/planning for future cycles. In particular we propose adopting Kafka in SQuaSH which replaces some of the actual components of the SQuaSH API (Redis, Celery) by EFD components (Kafka broker, zookeeper, InfluxDB Sink, S3 Sink and JDBC Sink connectors). Sharing EFD components simplifies the maintenance of both systems EFD and SQuaSH."
Answer: 3.0

User story: "This task has essentially become the following    - procure a LabVIEW windows 10 machine with a full LabVIEW 2018 SP1 license    - Learn about the RBF and development workflow of the TMA ATS"
Answer: 14592.0

User story: "The ATArchiver and CCArchiver are now BaseCSCs.  Update the dm_iip_deploy versions to use those releases."
Answer: 11646.0

User story: "Release packages that need ts_salobj 6:    Packages that use the new simulation support:  * ts_ATDome    Other packages:  * ts_watcher: uses a new feature of BaseCscTestCase"
Answer: 45650.0

User story: "Currently the data generator needs to be manually supplied with the number of Objects to create. This should instead be automatically computed from a density model defined in the specification file."
Answer: 56043.0

User story: "Just noticed that we aren't using the cert-manager stuff on the star wars environments, so I'm going to update the secrets and the cert-manager parts to make sure they all work in the new magic way."
Answer: 38719.0

User story: "The purpose of this ticket is to update LTD Conveyor with many of SQuaRE current best practices to make it easier to maintain the LSST the Docs command line. Namely, this includes GitHub Actions, tox, pre-commit based linting, and possibly mypy as well."
Answer: 5555.0

User story: "This is a continuation of DM-24925.  It covers various improvements and refinements to the merged Jenkinsfile.    Also, I need to update [https://tssw-ci.lsst.org/view/SAL_XML/job/Parallel_Release/] and [https://tssw-ci.lsst.org/view/SAL_XML/job/RPM_Push_daily/] to use this now unified script."
Answer: 20014.0

User story: "So we've been having a problem where the read keys have been disappearing.  This is to check in the fix.  The issue is that the lifetime used by the vault-secrets-operator was 24h.  So the expiration time of the read token would be shortened to 24h.  But it would be renewed so we wouldn't notice unless the environment was down for more than 24h, and then the key expires."
Answer: 16.0

User story: "After ATArchiver and CCArchiver have been updated to become BaseCSCs, the SALSubsystems.xml needs to be  updated to reflect that."
Answer: 15724.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "At present supporting simulation modes in CSCs requires overriding 3 methods: BaseCsc.implement_simulation_mode, BaseCsc.add_arguments, and BaseCsc.add_kwargs_from_args. Simplify this as follows:    Add a valid_simulation_modes argument to BaseCsc. Default it to None for backwards compatibility. If not None then do the following:  * Test the {{simulation_mode}} argument in the {{BaseCsc}} constructor.  * Make {{BaseCsc.handle_simulation_mode}} a no-op.  * Add a {{--simulate}} argument to {{BaseCsc.amain}}'s argument parser, if there is more than one valid simulation mode.    This will greatly reduce the amount of extra work needed by CSC authors to add a simulation mode.    Also convert at least one other package to use this new technique, to check the design."
Answer: 2201.0

User story: "Deploy DBB handoff buffer managers using timing data for Auxtel and Comcam on NCSA test stand and verify they are working. This includes writing deployment-specific documentation for those in charge of operating the service."
Answer: 28771.0

User story: "After success with replacing pyqtgraphs with PySide2/QtCharts, it makes sense to replace pyqtgraphs scatter plotting of the M1M3 with native PySide2 solution.    That shall give much better visualization options, enables zooming/submenu on actuators, etc."
Answer: 15936.0

User story: "There are new versions of the Helm charts. Upgrade and test on Roundtable and the Rubin Science Platform."
Answer: 5667.0

User story: "Support the LSST full-array mode (FAM) in AOS modules in phase 1. The SE team will provide the needed parameters such as the off-axis correction, sensitivity matrix, etc. This task is to update the *ts_wep*, *ts_ofc*, and *ts_phosim* to support the following evaluation of convergence. In the mean time, the SE team will check the calculated wavefront error by *cwfs* with the *ZEMAX* test data. The field points on 21 rafts will be checked and evaluated. After this cwfs test is done, the related test data will be added into *ts_wep*.    Bo verified the cwfs with ZEMAX in the following: [fam.ipynb|https://github.com/<USER>cwfs/blob/master/examples/fam.ipynb].    The sensitivity matrix file is [^senM_189_19_50.yaml]. The field numbers start from lower left, then go up: [^senM_189_200812.pdf].       This task is the phase 1."
Answer: 29724.0

User story: "The conda job for ts_MTDomeTrajectory is failing. Looks like missing dependencies. https://tssw-ci.lsst.org/job/MTDomeTrajectory%20Conda%20package/"
Answer: 1066.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 the pipetask command line for running inside compute jobs appears in the BPS config file, the pipetask command line for generating the QuantumGraph does not.  Mostly this was just due to the complexity of the pipetask command line at the time (loop over all the -t/-c/-C).  Now with the pipeline yaml file, the QuantumGraph generation command line is a lot simpler and would be good to have in the BPS config file.  This better route is being chosen instead of changing the hard-coded command line as pipetask command options change when switching to click.    Since it is not clear how much the non-yaml style command line will actually be used, this ticket will not include effort for putting a command line pattern for the non-yaml command line that will use BPS pipetask yaml definitions to generate the command line (i.e., no behind the scenes looping over portions of a pattern).  Just leave the non-yaml command line as hard-coded now."
Answer: 38492.0

User story: Support the shared enum in LabVIEW. Based on Dave, the bug described in DM-26270 can not be fixed in his side. Therefore, the ts_SALLabVIEW may need to be updated to support this.    To do this, maybe I will need to pass "const" and "enum : xxxx" in the IDL file.    This ticket will try to fix the *space/tab* and *private* in the IDL file.
Answer: 8355.0

User story: "RC2 tract 9813 run with fakes, fork from RC2 with w_2020_34"
Answer: 6898.0

User story: "There are a few references to atdometrajectory in the ts_mtdometrajectory package (presumably holdovers from starting the package by copying ts_atdometrajectory). Fix them."
Answer: 190.0

User story: "Now that DM-26391 is complete, we have a fairly accurate picture of the state of the CSC Conda jobs.  The next step is to get those jobs running regularly so we get the feedback on the status of the jobs.    We also want the wrap the Conda jobs into the daily workflow.  This will require a lot of coordination and logic."
Answer: 21751.0

User story: "Currently, there is no direct way to convert numpy arrays of ra/dec to and from x/y with a {{SkyWcs}}, which leads to inefficiencies when computing {{SpherePoint}} for large numbers of positions.  Some of this would be fixed with DM-19235 which I believe is tricky because of the memory ordering.    As it turns out, AST supports using numpy arrays without any memory finagling, for example in {{suprême}}: https://github.com/LSSTDESC/supreme/blob/75a2008d203e28b3d42738374823f1f5e42d9db1/supreme/utils.py#L157    This ticket will add {{wcs.xyToRaDec}} and {{wcs.raDecToXY}} (or some suitable name) to {{wcsContinued.py}} to allow general access to these very fast ways of interfacing with the AST code.  I don't believe the names {{skyToPixel}} and {{pixelToSky}} can be used because pure-python methods can't do the overloading (plus these don't return or take quite the same type of data structures)."
Answer: 21266.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 the gen2 system adding {{--show history}} will give a listing of what overrides were applied to the config and where.  This no longer works with the gen3 command line tool {{pipetask}}.  It would be nice to get this working as it is very difficult to find out how overrides are being applied without it."
Answer: 61712.0

User story: "For MTEEC, EAS and ESS the PATH and PYTHONPATH need to be set correctly for the conda package job to properly work. This ticket is for that."
Answer: 1368.0

User story: "A few ts_sal unit tests are now failing, as expected, because telemetry topics are now volatile and so have no historical (late joiner) data. Update the tests on the version 5 ticket branch."
Answer: 33.0

User story: "The TestResults schema is not rendering properly the Jira issues associated with a test execution."
Answer: 3190.0

User story: "Update the gen3 registry to use the observation reason added in DM-26550.  "
Answer: 44612.0

User story: "From [~<USER> - [~<USER> discussion this morning: update the {{suit}} package's build scripts to     # use the new Firefly online help system, building the help from the suit-specific fork [lsst/suit-help|https://github.com/lsst/suit-help] of the core online help text at [Caltech-IPAC/firefly-help|https://github.com/Caltech-IPAC/firefly-help], and   # place the generated pages into the .war file output of the build, and therefore into the resulting Docker image, for service from Tomcat under a sub-endpoint of the {{suit}} / Portal Aspect application.    This feature should be backported to the rc-2.0 branch of {{suit}}."
Answer: 39733.0

User story: "Make telemetry volatile in ts_salobj v6 pre-release and update documentation to say it is only compatible with ts_sal 5."
Answer: 2349.0

User story: "The [README|https://github.com/lsst/lsst_dm_stack_demo/blob/2015897ec0869a7c5f8027018755049171008ebc/README] says:    {code}  output; choose a result set appropriate for your system. The ./bin/compare  script can then be used to check if your results are within the expected  numerical tolerances::        $ python bin/compare.py detected-sources.txt      Ok.  {code}    However, {{bin/compare.py}} doesn't exist; I see a {{bin/compare}} and a {{bin.src/compare.py}}."
Answer: 61193.0

User story: "Whitelight is failing some tests when run in the latest develop environment. Get tests passing and the CSC updated for SalObj v5+"
Answer: 29407.0

User story: "Work is being done in DM-26371 that will affect the internals of the QuantumGraph.  ctrl_bps code will need to be modified to work with it.  This may mean that the Science DAG conversion is no longer helpful and can be removed.  There is expected to be more API available, so those should be used in the code instead of accessing the graph directly where possible in order to make the ctrl_bps less affected by QuantumGraph changes."
Answer: 55066.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: "Sky objects are pseudo-objects placed within coadded imaging after object detection has taken place. They are randomly placed such that their footprint (currently an 8 pixel radius) does not overlap with any other detected source footprint. As such, these objects are very useful for QA purposes, e.g., sky level tracking.    This ticket adds two simple sky object performance metric tracters: the sigma-clipped mean sky object circular aperture flux value for all sky objects within a given tract; and the standard deviation of this distribution. These values are the same as those generated for the {{pipe_analysis}} skyObjects figure (e.g., [plot-t9615-HSC-I-skyObjects-hist.png|https://lsst.ncsa.illinois.edu/~<USER>w_2020_30_qaPlots/HSC-I/tract-9615/plot-t9615-HSC-I-skyObjects-hist.png]). Once generated, these metrics will ultimately be tracked over time by the [SQuaSH metrics tracking Chronograf|https://chronograf-demo.lsst.codes/sources/2/dashboards] (see [SQR-019|https://sqr-019.lsst.io/])."
Answer: 44567.0

User story: "Implements a Helm chart to deploy the SQuaSH API. Following DM-25963 this Helm chart will produce a k8s deployment with the following:   - the API itself, implemented as a flask app   - redis   - celery   - cloud-sql-proxy         that's to minimize changes in the current deployment. Redis and celery will be removed when we adopt Kafka and Kafka Connect in SQuaSH.    {{cloud-sql-proxy}} is a thin container and it make sense to keep it in the same k8s deployment as the flask app that uses it to connect to Cloud SQL."
Answer: 14140.0

User story: "A first cut at the documentation.    This is primarily to populate the lsst.io sites with the vendor provided documentation.     "
Answer: 26132.0

User story: "Enhance the ScriptQueue commander to allow the user to specify logLevel and other options for the add command. Preferably make these optional arguments that use keywords, e.g. logLevel=40."
Answer: 4255.0

User story: "Make README current again."
Answer: 9.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: scons --butler-config=/scratch/<USER>weekly_ci_hsc_gen3/postgres/output/1598279875/butler-seed.yaml -j 8 --enable-profile    With butler-seed.yaml looking like   {noformat}  registry:     db: postgresql://lsst-pg-devel1.ncsa.illinois.edu:5432/lsstdevdb1     namespace: svclsstdbmgower1  datastore:    composites:      default: true  {noformat}    Leads to:  {noformat}  python -m cProfile -o profile-004-butler.pstats /software/lsstsw/stack_20200515/stack/miniconda3-4.7.12-46b24e8/Linux64/daf_butler/19.0.0-145-g6ed37199+01e3669f2c/bin/butler ingest-raws /scratch/<USER>weekly_ci_hsc_gen3/postgres/git/ci_hsc_gen3/DATA -d /project/shared/data/test_data/testdata_ci_hsc/raw  Error: An error occurred during command execution:  Traceback (most recent call last):    File "/software/lsstsw/stack_20200515/stack/miniconda3-4.7.12-46b24e8/Linux64/daf_butler/19.0.0-145-g6ed37199+01e3669f2c/python/lsst/daf/butler/cli/utils.py", line 444, in cli_handle_exception      return func(*args, **kwargs)    File "/software/lsstsw/stack_20200515/stack/miniconda3-4.7.12-46b24e8/Linux64/obs_base/20.0.0-36-g2de6156+58b4951e8a/python/lsst/obs/base/script/ingestRaws.py", line 75, in ingestRaws      ingester.run(files, run=output_run)    File "/software/lsstsw/stack_20200515/stack/miniconda3-4.7.12-46b24e8/Linux64/obs_base/20.0.0-36-g2de6156+58b4951e8a/python/lsst/obs/base/ingest.py", line 456, in run      self.butler.registry.syncDimensionData("exposure", exposure.record)    File "/software/lsstsw/stack_20200515/stack/miniconda3-4.7.12-46b24e8/Linux64/daf_butler/19.0.0-145-g6ed37199+01e3669f2c/python/lsst/daf/butler/registry/_registry.py", line 953, in syncDimensionData      return storage.sync(record)    File "/software/lsstsw/stack_20200515/stack/miniconda3-4.7.12-46b24e8/Linux64/daf_butler/19.0.0-145-g6ed37199+01e3669f2c/python/lsst/daf/butler/registry/dimensions/table.py", line 157, in sync      compared=compared,    File "/software/lsstsw/stack_20200515/stack/miniconda3-4.7.12-46b24e8/Linux64/daf_butler/19.0.0-145-g6ed37199+01e3669f2c/python/lsst/daf/butler/registry/interfaces/_database.py", line 1097, in sync      f"Conflict ({bad}) in sync after successful insert; this is "  RuntimeError: Conflict (["timespan: Timespan(begin=astropy.time.Time('2013-06-17 13:34:45.775000', scale='tai', format='iso'), end=astropy.time.Time('2013-06-17 13:35:17.947000', scale='tai', format='iso')) != Timespan(begin=astropy.time.Time('2013-06-17T13:34:10.775', scale='utc', format='isot'), end=astropy.time.Time('2013-06-17T13:34:42.947', scale='utc', format='isot'))"]) in sync after successful insert; this is possible if the same table is being updated by a concurrent process that isn't using sync, but it may also be a bug in daf_butler.  {noformat}
Answer: 3270.0

User story: "Contribute to the construction completeness document sitcom-005"
Answer: 64.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: "My MBP has a 250gb disk space, this turn out to be not enough so I switched to using the Dell laptop that was ordered for TMA as my main workstation.     When switching I discovered I was running out of space as I was reaching 25gb. It turn out the disk partitions were done oddly as part of a dual booting (it also had windows). I did not use the Windows side of the laptop as much as I had thought I would.     As a result I have reformatted the laptop to be completely CentOS7 which now gives me 2 terabytes of space to work with which I think will be enough to comfortable continue with all the virtual machines I will be running.     The reformat was fairly easy, I am currently now pulling all the containers and updating the system and installing development tools which I was using. "
Answer: 2884.0

User story: "RC2 reprocessing with w_2020_34 stack"
Answer: 14638.0

User story: "Before modernizing the EAS code, there was simulator code that should be modernized as well. This ticket was created to do that."
Answer: 31.0

User story: "Currently, when running {{processCcdWithFakes.py}}, the task will fail with a {{RuntimeError}} if no fake sources exist for a given dataRef. For example, running this command:  {code:sh}  $ processCcdWithFakes.py INPUT --output OUTPUT --id visit=1228 ccd=5 tract=9813 --config insertFakes.fakeType=FAKEFILE  {code}  will fail with this error:  {code:sh}  processCcdWithFakes FATAL: Failed on dataId={'visit': 1228, 'ccd': 5, 'tract': 9813, 'pointing': 817, 'filter': 'HSC-I'}: RuntimeError: No fakes found for this dataRef.  {code}  if no input fake source exists within CCD 5 of visit 1228.    It would be beneficial for the {{insertFakesTask}} to have the option to generate a {{fakes_calexp}} and a {{fakes_src}} for all requested CCDs, regardless of whether or not each CCD actually contains an injected fake source. This would allow for subsequent coadd processing to generate equivalent coadd imaging using all the same processed input visits/CCDs as a standard non-fake run. This ticket adds that functionality. "
Answer: 1411.0

User story: "The new single frame column 'detect_isPrimary' did not make it into the parquet Source Table list. This tickets adds it in."
Answer: 5134.0

User story: "We don't have a suit build yet, but maybe I can prove the lab extension works with vanilla firefly."
Answer: 30203.0

User story: "Update the ScriptQueue commander to handle the stopScripts command (the only command that takes a list of values)."
Answer: 165.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 was not able to find documentation about the EPOCH value of {{daf.base.DateTime.DateSystem}}. From the C++ code, it looks like it means "Julian Epoch Year", like the [astropy time format|https://docs.astropy.org/en/stable/api/astropy.time.TimeJulianEpoch.html#astropy.time.TimeJulianEpoch], but "epoch" is also used elsewhere in the same code to refer to "nanoseconds since the unix epoch", which is quite a different thing.    We need a short docstring on that enum (or elsewhere, if enum docstrings don't work) to make the values explicitly clear.    Also, the private `_getEpoch` could be similarly updated to specify that it is the Julian Epoch Year.
Answer: 94.0

User story: "use image `deps_20200729_0234` whose git SHA is `3130bd0`"
Answer: 4927.0

User story: "The timestamp that was added contains redundant info (private_sndStamp) so it should be removed again."
Answer: 7009.0

User story: "Make the SAL/Kafka producers shut down gracefully for SIGTERM (and SIGINT)."
Answer: 7587.0

User story: Change the user "ARC" (which is used on the test stand) to user "arc" to be consistent with the base.    Add configuration option to change Domain/Id in ospl.xml for testing purposes.    Update version numbers of releases for dm_CCArchiver and dm_csc_base    Set pika and redis versions
Answer: 7286.0

User story: "Logging in to nublado provides an access token to the user that can be used to access services in the API aspect.  This is to provide an extension to nb.lsst.io to provide instructions on how to do that in a specific example case.  I'd like to use access of the TAP service via the TOPCAT tool as my exemplar."
Answer: 10091.0

User story: "During the fakes RC processing [~<USER> found a bug in insertFakes which meant that not all of the sources were being added during processing. This came from some faulty logic introduced in a recent ticket to catch galaxies that had parameters outside of those that galsim can handle. Some of the stars also had their sersic indices set to numbers outside of this range, but this doesn't matter because they are going in as PSFs. However they were being removed before insertion. This resulted in very few stars making it into the images. This ticket is to correct that issue by making the logic check if either the sersic parameters are within the correct range or the object is a star."
Answer: 4109.0

User story: "Release all of my packages waiting for ts_xml 6.2.    At the moment I know of:  * ts_hexapod  * ts_rotator"
Answer: 87948.0

User story: "make the pipetask2 interface similar to the existing pipetask interface: no chained commands, `qgraph` takes `build` options and will execute `build`, similar for `run`, takes `build` and will execute `qgraph` and `run`."
Answer: 5763.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: "If there are masked pixels in the overscan, the \{\{MEDIAN_PER_ROW}} overscan correction code generates a warning:    {code}  python/lsst/ip/isr/overscan.py:344: UserWarning: Warning: converting a masked element to nan.   rowMedian = afwMath.makeStatistics(row, fitType, self.statControl).getValue()  {code}    Please remove this.  I think the simplest fix is \{\{row = row[~row.mask].data[0]}} in collapseArrayMedian, but there may be other occurrences.  A better solution might be to stop using {{np.ma}} in favour of using stack-native code everywhere, which understands {{Mask}} planes.     "
Answer: 10405.0

User story: "Research Kubernetes pod hardening best practices, apply them to Gafaelfawr for a test, and document them in the security reviews for SQuaRE and the Rubin Science Platform. Write a new tech note for detailed recommendations for how to harden clusters and pods."
Answer: 8634.0

User story: "[~<USER> found a problem with licensed OpenSplice 6.10.4 and a version of licensed 6.10.3 as well: when a writer process goes away the salobj reader may be come unresponsive. This especially affects the script queue, since script processes are constantly shutting down. I filed this as case 00020647.    [~<USER> also found a workaround: use  a read mask of dds.DDSStateKind.ANY_INSTANCE_STATE and ignore invalid samples in the Python code. This slows things down a bit, but seems to work with OpenSplice 6.10.4. Update the code accordingly.    We will use that fix until we are sure it's safe to do otherwise.    Add this to prerelease 6 and also release a new version of 5.17 with this fix."
Answer: 1496.0

User story: "The data generation system client needs to run on many nodes with multiple copies per node. The most reliable way to do this is to place the necessary components in a container and start containers as needed. Elements that need to be in the container.   * python3   * dax_data_generator   * numpy, pandas, healpy, pyarrow   * sphgeom   * sph-partition    *   qserv-replica-file-ingest (which may require significant parts of qserv)         It may be beneficial to put the server in a container as well, but only one server instance is need and the container would be very similar as the one used for the client."
Answer: 11525.0

User story: "Write a couple unit tests for ctrl_bps.  First some thought will need to be done to determine which pieces aren't going to immediately change (e.g., the conversion of the QuantumGraph to networkx may all be done inside ctrl_mpexec code now or at least change what conversion needs to be done)."
Answer: 71527.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: "Dimensions.yaml should be locked in and read-only as soon as the schema is created during the makeRepo phase.  At the moment there is nothing stopping a repository from breaking if dimensions.yaml is updated in daf_butler and there is nothing stopping a user editing the config file after repository creation and breaking things.    We propose to remove dimensions.yaml from ButlerConfig and have it as an explicit argument for makeRepo (defaulting to {{pkg://lsst.daf.butler/configs/dimensions.yaml}}) which will then ensure that the dimensions configuration is locked in for that repository.    We will still require that it be possible to migrate a registry to a new dimensions definition but that migration should be by explicit request."
Answer: 86575.0

User story: "There were noticeable delays in jobs starting (jobs not running, nodes idle) during the RC2 single tract run (DM-26271).  Try to track down why that was happening and see if there is a configuration change (or a ctrl_bps code change) that would reduce this delay.   (Details to be added later as comments)"
Answer: 66560.0

User story: "Support activities for the development of low level dome control software development by EIE contractor. The activities include  organization and attendance to technical meetings, review of documentacion, enforce compliance to requirements of software implementations, plan timeline of deliverables, provide technical support and guidance during development."
Answer: 15710.0

User story: "Support activities to develop a dome environment conditioning contract, to control the temperature during daytime. The activities include reviewing proposals, provide technical information to potential contractors, meetings with Rubin Observatory reviewers and contractors."
Answer: 15719.0

User story: "Determine which CSCs need Conda Jenkins jobs, which currently have them and how many are left to work on.  Then coordinate finishing any remaining work."
Answer: 11768.0