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: "The partitioner could only handle director tables. Tables like ForcedSource, where partitioning depends on a foreign key to a director table, could not be partitioned/ingested correctly. The partitioner software has been changed to allow this and data generator needs to be changed to take advantage of this. "
Answer: 11627.0

User story: "Research Shared Jenkins Libraries."
Answer: 24694.0

User story: "In order to be able to test the EIE LabVIEW code, a Windows VM with LabVIEW 2018 SP1 is needed. This ticket covers the time spent on that."
Answer: 198.0

User story: Occasionally something goes wrong which leads to a failure that looks something like this:    {code}  Traceback (most recent call last):    File "/software/lsstsw/stack_20200515/python/miniconda3-4.7.12/envs/lsst-scipipe/lib/python3.7/multiprocessing/managers.py", line 811, in _callmethod      conn = self._tls.connection  AttributeError: 'ForkAwareLocal' object has no attribute 'connection'                                                        During handling of the above exception, another exception occurred:                                                          Traceback (most recent call last):    File "/software/lsstsw/stack_20200515/python/miniconda3-4.7.12/envs/lsst-scipipe/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap      self.run()    File "/software/lsstsw/stack_20200515/python/miniconda3-4.7.12/envs/lsst-scipipe/lib/python3.7/multiprocessing/process.py", line 99, in run      self._target(*self._args, **self._kwargs)    File "/home/nate2/repos_lsst/ctrl_mpexec/python/lsst/ctrl/mpexec/mpGraphExecutor.py", line 110, in _executeJob               quantumExecutor.execute(taskDef, quantum, butler)    File "tests/test_executors.py", line 56, in execute      self.quanta.append(quantum)    File "<string>", line 2, in append    File "/software/lsstsw/stack_20200515/python/miniconda3-4.7.12/envs/lsst-scipipe/lib/python3.7/multiprocessing/managers.py", line 815, in _callmethod      self._connect()    File "/software/lsstsw/stack_20200515/python/miniconda3-4.7.12/envs/lsst-scipipe/lib/python3.7/multiprocessing/managers.py", line 802, in _connect      conn = self._Client(self._token.address, authkey=self._authkey)                                                          File "/software/lsstsw/stack_20200515/python/miniconda3-4.7.12/envs/lsst-scipipe/lib/python3.7/multiprocessing/connection.py", line 492, in Client      c = SocketClient(address)    File "/software/lsstsw/stack_20200515/python/miniconda3-4.7.12/envs/lsst-scipipe/lib/python3.7/multiprocessing/connection.py", line 619, in SocketClient      s.connect(address)  FileNotFoundError: [Errno 2] No such file or directory  {code}    This is related to the fast failure mode in the MPGraphExecutor. The fix should be to explicitly close any running jobs before raising.
Answer: 2565.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: "RC2 gen3 run for all tracts. Tracks were submitted separately.    Fringe correction was off:       {code:java}    isr:      class: lsst.ip.isr.IsrTask      config:        doFringe: false  {code}        "
Answer: 5567.0

User story: "Communicate the interim support model to the community "
Answer: 10195.0

User story: "This task covers the time to process the SAL v5.0 release.  This includes updates to the tests and build scripts, performing the git steps (tags, branches, merges) and the miscellany involved in the release."
Answer: 25916.0

User story: "While trialing Sphinx 3.2-based pipelines.lsst.io documentation builds, I found that a few See also docstring sections in {{afw}} and {{ip_isr}} were breaking the Sphinx builds, presumably due to more stringent requirements. The main issue is adding {{()}} to the function names; the See also section can only contain the actual API name."
Answer: 78.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*.    This task is the phase 3."
Answer: 26177.0

User story: "Read DDS messages in a background thread loop in order to reduce the danger that the read queue will overflow."
Answer: 3179.0

User story: "Based on the requirements in SQR-044, write a design document for the token component of the Rubin Science Platform identity management system."
Answer: 15941.0

User story: We ingested 3 HSC databases of Object tables into the new "small" Qserv. We'd like them to be published through the TAP service.     Inside the small Qserv the database names are "hsc_rc2_w_2020_30_04", "hsc_pdr2_2020_08_01", and "hsc_pdr2_2020_09_00".      If possible it'd be great to expose them with more astronomer-friendly names:  * "hsc_rc2_w_2020_30_04" --> "hsc_rc2_w_2020_30"  * "hsc_pdr2_2020_08_01"  -->  "hsc_pdr2_2020_deep"  * "hsc_pdr2_2020_09_00"  --> "hsc_pdr2_2020_wide"  
Answer: 34751.0

User story: Plan and execute the first data exchange "data challenge" with the Minor Planet Center.    Includes:   * Define the details challenge   * Select the week for the challenge   * Coordinate the preparation of necessary datasets and codes   * Liaise with the MPC (regular meetings) in preparation for the DC   * Execute the data challenge
Answer: 40233.0

User story: "Prepare, submit, and do abstracts and presentations for DPS 2020."
Answer: 40228.0

User story: "0.13 changed the Reflector implementation a lot, and our MultiNamespace Spawner depends crucially on that."
Answer: 7359.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: "Modernize ts_MTDomeTrajectory docs.    Also use salobj ReadTopic.get(flush=False) everywhere to avoid deprecation warnings in ts_salobj 6."
Answer: 5872.0

User story: "Add a page for quiet day to dev guide"
Answer: 1469.0

User story: "The tracklet-track findability metric needs to be incorporated into the linkage analysis tool and a new criterion needs to be added to take into account the maximum of 90 minutes between observations for a tracklet to be made. "
Answer: 27536.0

User story: "The slowness is due to some integrity checks that are done to ensure the existing environment corresponds to the pinned version.    I think we may relax this constrain, and if the environment exists, consider it good to use. This is certainly true when we run envonfig in Jenkins.    We may want to add a specific option for checking the environment consistency."
Answer: 31379.0

User story: "Currently there are duplicate IDs in  sdm_schemas/yml/hsc.yaml  and felis doesn't like them."
Answer: 8631.0

User story: pipetask can take many command-line parameters and it can be really annoying to copy and paste them all into a long command line. It would be really helpful if the options could instead be supplied as a configuration file but allow overrides on the command line. This is a common approach taken for complex command lines (for example HandbrakeCLI calls them "presets").    The command line "presets" could be a simple flat YAML file representing a dict where the keys are the long names of options (people could specify array values).    We should do this generically for butler, pipetask, and bps commands using the same infrastructure.  It would be preferably to do this early enough that all the same option validation could happen rather than having to validate in multiple places.
Answer: 5541.0

User story: "See PR [#192|https://github.com/influxdata/helm-charts/pull/192] to the InfluxDB Helm chart.    We need that to configure auth using the JWT tokens issued by Gafaelfawr."
Answer: 7246.0

User story: "When writing some new unit tests downstream, I noticed that a last-minute (but still fully Jenkins-tested!) change on DM-26683 seems to have broken repo export; it looks like we currently have no tests for exporting more than one file.    This ticket will include a fix and port the test from the still-in-progress ticket that discovered the problem."
Answer: 369.0

User story: "ATDomeTrajectory incorrectly claims to support simulation. It does not. Update the docs and remove the {{simulation_mode}} CSC constructor argument."
Answer: 7227.0

User story: "Convert RC2_w_2020_36 to Gen3 with w_2020_37 stack"
Answer: 1568.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 ReadTopic.get defaults to flushing the queue (for for backwards compatibility to a very old version). This can lead to surprising behavior and subtle bugs. I propose to deprecate this behavior in stages. This ticket implements the first stage: issue a deprecation warning if flush=True (the flush argument is omitted, since that is the default behavior). The final stage (later) is to remove the argument."
Answer: 1801.0

User story: "Right now the matcher is using the stock {{photoCalib}} and {{Wcs}} objects for calibration.  This is safe since these will always exist if the calexp does, but sometimes further processing is executed: e.g. jointcal and FGCM which produce different objects.    We would like to be able to configure these to be used when they are available.  This will need to be set up in the pipeline definition if we implement it as templates on the connection class (which is what I will try first)."
Answer: 3007.0

User story: "One of our goals with Documenteer 0.6 is to track the latest versions of Sphinx and Sphinx extensions so that we can start to take advantage of new functionality and bug fixes.    We've already removed the pin on Sphinx itself; the purpose of this ticket is to start removing pins on extensions such as numpydoc, automodapi, and sphinx-click.    Part of this ticket will be to test Documenteer against stack documention, technote, and package documentation builds. And hopefully to develop a way to semi-automate this sort of downstream test suite."
Answer: 8498.0

User story: Basically, an updated "prod" but with JL2.
Answer: 13036.0

User story: "Following adoption of RFC-703, the developer guide should be updated to refer to DMTN-155 as the guiding document for supporting the community during construction"
Answer: 28791.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: 17154.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: 17153.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: A few of the columns added to track scarlet processing are not prefixed with the "deblend" keyword, so it isn't obvious downstream which plugin is responsible for generating these. Part of this ticket is to insert the "deblend" prefix to all of those columns so that everything generated by `meas_extensions_scarlet` begins with the "deblend" keyword.    There are also a few columns that should be added to track quantities and metrics useful for debugging/analyzing the scarlet results:    * deblend_nPeaks: currently "deblend_nChild," the field that keeps track of the number of children in a blend, is only updated after the blend has completed. However, this does not propagate the number of peaks in the footprint of a parent that failed or the number of detected peaks for a footprint (which may or may not have been deblended). So this field will propagate the number of peaks initially in the parent footprint without having to access the footprint data itself.  * deblend_logL: we have discovered that tracking the magnitude of logL can be a very useful way to diagnose a change in scarlet that results in unmodeled (or poorly modeled) flux. Storing this quantity will be a useful regression test of scarlet in difficult blends where the assumptions of the monotonicity operator break down and the model needs to be more flexible.
Answer: 27216.0

User story: "The MultiProFit Parameter class has some inefficiencies like entirely avoidable conditionals in the frequently called get_value and set_value functions; optimizing them could improve performance significantly (particularly for small footprints/galaxies where setup time is comparable or greater than actual model evaluation time)."
Answer: 28296.0

User story: "Hi Chris, I'd like to start using the gen3 postgres registries in {{/project/hsc/gen3repo/README}}          Would appreciate necessary accounts and instructions on how to use them. Thank you. "
Answer: 47.0

User story: "Investigate the timing of the prompt processing system using the evolving prototype as a general benchmark. Identify bottlenecks and consider solutions."
Answer: 19951.0

User story: "Explore ideas and options supporting the possibility of running arbitrary code in the prompt processing system (OCPS)."
Answer: 19955.0

User story: "Configure Selenium testing and add tests for the current token management pages in preparation for refactoring and significantly expanding them."
Answer: 20715.0

User story: "{noformat}  influxdb-demo has a password set  squash has a password set  squash-demo has a password set  api-lsst-codes has a password set  gitlfs-prod has a password set  scipipe-publish-prod has a password set{noformat}  Disable password authentication on these clusters. No one believes we're using it."
Answer: 18877.0

User story: "https://cloud.google.com/kubernetes-engine/docs/security-bulletins#gcp-2020-012"
Answer: 18879.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: "Telegraf-ds provides an opinionated configuration for monitoring Kubernetes nodes and global Kubernetes monitoring. It collect metrics using the following telegraf plugins by default:    * cpu  * disk  * diskio  * docker  * kernel  * kubernetes  * mem  * net  * processes  * swap  * system"
Answer: 124.0

User story: "Test the CTIO Jenkins and Docker image from Nexus. This task will figure out the recipe to put in the Jenkinsfile to do the LabVIEW test."
Answer: 33007.0

User story: "Time spent coordinating, creating agenda, followups, reporting and  holding the weekly TMA Software Integration Meeting    *Acceptance Criteria*   * Agenda Generated and recorded into [https://confluence.lsstcorp.org/display/LTS/Weekly+TMA+Software+Integration+Meetings]   * Meeting held and action items recoded into the same confluence page   * Report sent out to the management"
Answer: 33443.0

User story: "Time spent coordinating, creating agenda, followups, reporting and  holding the weekly TMA Software Integration Meeting    *Acceptance Criteria*   * Agenda Generated and recorded into [https://confluence.lsstcorp.org/display/LTS/Weekly+TMA+Software+Integration+Meetings]   * Meeting held and action items recoded into the same confluence page   * Report sent out to the management"
Answer: 3038.0

User story: "Try to figure out how you actually load the nbextension"
Answer: 2609.0

User story: "Loggers (maybe only with {{\-\long\-log}}) used to initialize PipelineTasks for execution should be set up to always log the task label and quantum data ID.  These are very important identifying pieces of information when combing the logs for failures, and it shouldn't be the responsibility of concrete PipelineTask authors to include them (as it effectively was in CmdLineTask), since the execution framework always knows these values.    This will lead to a lot of duplication initially, because of course many concrete PipelineTasks share code with their CmdLineTask predecessors and hence do explicitly include data IDs, but we can only start removing that once that information is automatically included in Gen3.  "
Answer: 22578.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 recent discussions it was suggested that something like "band", "waveband" (or "energyband" -- following CAOM formalism, although that is "optical" vs "radio") could be less confusing than "abstract filter". It was clear that people weren't entirely sure what "abstract" means and we get some people thinking it means a generic filter name such as "all red filters are called r"  and others who think it's nothing more than a label (so "r" and "r2" and "r3" are all abstract).  Gen3 is trying to use abstract filter to mean "you can probably co-add these and get a useful answer that you expect".    Consider also renaming physical_filter to just filter if we have band. Physical filter always refers to a specific piece of hardware.    If we wish to make this change to registry and butler then we should change it before we declare schema stability.    This ticket can be marked invalid if we decide against it but I need a placeholder.
Answer: 14587.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Since Friday Sep, 11 we started seeing session timeouts in Zookeeper and connection errors from the kafka brokers to Zookeeper. That required a few restarts of Kafka over the weekend before we could investigate the issue.    The relevant message from the Zookeeper logs seems to be:    {noformat}  [2020-09-12 16:34:20,032] INFO Creating new log file: log.7c00000001 (org.apache.zookeeper.server.persistence.FileTxnLog)  [2020-09-12 16:34:21,452] WARN fsync-ing the write ahead log in SyncThread:2 took 1415ms which will adversely effect operation latency. File size is 67108880 bytes. See the ZooKeeper troubleshooting guide (org.apache.zookeeper.server.persistence.FileTxnLog)  {noformat}    which is present even after a restart.    My interpretation is that this fsync operation might exceed the Zookeeper session timeout. The session timeout is controlled by    {noformat}       ZOOKEEPER_TICK_TIME:                    2000  {noformat}    which is 2000ms by default and might be causing the timeouts and connection errors we were seeing. I've set this parameter to 8000ms that is used to set the minSessionTimeout and maxSessionTimeout    {noformat}  INFO Created server with tickTime 8000 minSessionTimeout 16000 maxSessionTimeout 160000 datadir /var/lib/zookeeper/log/version-2 snapdir /var/lib/zookeeper/data/version-2 (org.apache.zookeeper.server.ZooKeeperServer)  {noformat}    and looking at the client, we see that the actual negotiated timeout is now 18000 ms:    {noformat}  INFO Session establishment complete on server cp-helm-charts-cp-zookeeper-headless/10.42.2.213:2181, sessionid = 0x30300d8ba080000, negotiated timeout = 18000  {noformat}    I'll keep monitoring the cluster, but the initial WARNING message is gone after we applied the new configuration.      Reference:    https://zookeeper.apache.org/doc/r3.3.2/zookeeperAdmin.html#sc_configuration    tickTime: the length of a single tick, which is the basic time unit used by ZooKeeper, as measured in milliseconds. It is used to regulate heartbeats, and timeouts. For example, the minimum session timeout will be two ticks."
Answer: 5702.0

User story: "Continue testing and tuning the DDS configuration and QoS settings on the NTS systems. This should be easier now we have implemented QoS.xml to share identical QoS across ts_sal and ts_salobj"
Answer: 20047.0

User story: "Update all the OpenSplice assets (rpms x86_64 and arm64, github repo, Nexus)  with newly minted configuration upgrades gleaned from the NTS campaign"
Answer: 20051.0

User story: "Continuing with the testing of the TSS system at NCSA. This ticket is to capture the work needed for the new cycle build which will deploy the most recent versions of sal and salobj plus execute some testing. "
Answer: 19760.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: Simon is reporting that his task fails with too many open file error:    {noformat}  ERROR: OSError: [Errno 24] Too many open files [multiprocessing.popen_fork]  Traceback (most recent call last):    File "/software/lsstsw/stack_20200515/stack/miniconda3-4.7.12-46b24e8/Linux64/ctrl_mpexec/20.0.0-14-g18fd799+95ed9b6257/bin/pipetask", line 26, in <module>      sys.exit(CmdLineFwk().parseAndRun())    File "/software/lsstsw/stack_20200515/stack/miniconda3-4.7.12-46b24e8/Linux64/ctrl_mpexec/20.0.0-14-g18fd799+95ed9b6257/python/lsst/ctrl/mpexec/cmdLineFwk.py", line 494, in parseAndRun      return self.runPipeline(qgraph, taskFactory, args)    File "/software/lsstsw/stack_20200515/stack/miniconda3-4.7.12-46b24e8/Linux64/ctrl_mpexec/20.0.0-14-g18fd799+95ed9b6257/python/lsst/ctrl/mpexec/cmdLineFwk.py", line 696, in runPipeline      executor.execute(graph, butler)    File "/software/lsstsw/stack_20200515/stack/miniconda3-4.7.12-46b24e8/Linux64/ctrl_mpexec/20.0.0-14-g18fd799+95ed9b6257/python/lsst/ctrl/mpexec/mpGraphExecutor.py", line 232, in execute      self._executeQuantaMP(quantaIter, butler)    File "/software/lsstsw/stack_20200515/stack/miniconda3-4.7.12-46b24e8/Linux64/ctrl_mpexec/20.0.0-14-g18fd799+95ed9b6257/python/lsst/ctrl/mpexec/mpGraphExecutor.py", line 376, in _executeQuantaMP      job.start(butler, self.quantumExecutor)    File "/software/lsstsw/stack_20200515/stack/miniconda3-4.7.12-46b24e8/Linux64/ctrl_mpexec/20.0.0-14-g18fd799+95ed9b6257/python/lsst/ctrl/mpexec/mpGraphExecutor.py", line 87, in start      self.process.start()    File "/software/lsstsw/stack_20200515/python/miniconda3-4.7.12/envs/lsst-scipipe/lib/python3.7/multiprocessing/process.py", line 112, in start      self._popen = self._Popen(self)    File "/software/lsstsw/stack_20200515/python/miniconda3-4.7.12/envs/lsst-scipipe/lib/python3.7/multiprocessing/context.py", line 223, in _Popen      return _default_context.get_context().Process._Popen(process_obj)    File "/software/lsstsw/stack_20200515/python/miniconda3-4.7.12/envs/lsst-scipipe/lib/python3.7/multiprocessing/context.py", line 277, in _Popen      return Popen(process_obj)    File "/software/lsstsw/stack_20200515/python/miniconda3-4.7.12/envs/lsst-scipipe/lib/python3.7/multiprocessing/popen_fork.py", line 20, in __init__      self._launch(process_obj)    File "/software/lsstsw/stack_20200515/python/miniconda3-4.7.12/envs/lsst-scipipe/lib/python3.7/multiprocessing/popen_fork.py", line 69, in _launch      parent_r, child_w = os.pipe()  OSError: [Errno 24] Too many open files  {noformat}    It looks like pipetask does not release resources when child process finishes. Need immediate fix.    Interestingly number of open pipes is much larger than number of quanta/processes, maybe worth understanding why is that too.
Answer: 435.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: "salobj ReadTopic warns if {{max_history > reader_qos.history.depth}}  but does not warn if {{max_history > reader_qos.durability_service.history_depth}}  because {{reader_qos.durability_service.history_depth}} is always reported as 0 in the Community Edition as of 2020-09-14.    Add this additional warning If and when the following are both true:  * OpenSplice fixes this issue.  * OpenSplice allows setting {{durability_service.history_depth < history.depth}}."
Answer: 96.0

User story: "We need a way to freeze configs after they've been instantiated. CmdlineTask does this and [~<USER> reports that this is probably a single line fix to ctrl_mpexec."
Answer: 13470.0

User story: "Update the PTC dataset to be a proper IsrCalib"
Answer: 33448.0

User story: "Something isn't working when reducing more than one image at a time. Find out what's wrong (it's to do with PdfPages) and fix it."
Answer: 4295.0

User story: "The tagging and versioning used by `setuptools_scm` in scarlet is incompatible with non-version tags like the ones used in the stack (eg. weekly tags). There is also an incompatibility since the stack tags `vX.Y.Z` use the same `v` prefix as scarlet now uses (due to the requirement of `setuptools_scm`).    This ticket aims to solve both problems by  1. Converting scarlet version tags to the more common `X.Y.Z` format (without the `v` prefix)  2. Natively creating the `_version.py` file and removing `setuptools_scm` completely from scarlet."
Answer: 1656.0

User story: "[~<USER> reports that yaml serialization is 25 times slower than pickling the same config. Some of this is going to be standard YAML overhead but it maybe that there are some improvements that can be made to the yaml representer in pex_config."
Answer: 43.0

User story: "Describe current JL state graphically."
Answer: 6018.0

User story: "The requirements that I know of so far for this task are to.    - Identify the EIB, do I need to purchase one?   - Specing out a server rack to replace the PXI's in the server room"
Answer: 36587.0

User story: "This task it to complete the Robot Framework tests for the Deployable platforms. This is part of a task that we asked Tekniker allow me to do to learn how the tests are created based of verification documents. Essentially this work is to translate these verification documents into RBF tests."
Answer: 40432.0

User story: "The scheduled prompt processing job should monitor the incoming data repo for the specified data and trigger the processing pipeline when it arrives. Determine whether it is better for this monitor to be part of the HTCondor job or an independent process outside the HTCondor system."
Answer: 21806.0

User story: Update the logic to select the last "executed" test run if available.    Use the milestone id provided in the title, if not provided in the specific field (PMCS Activity) of the test plan.
Answer: 1506.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 IDL Conda Jenkinsfile to trigger the SalObj Conda job and have it use the just-built IDL Conda package.     * Update IDL Conda Jenkinsfile to trigger the CSC Conda jobs.  Work with [<USER>https://confluence.lsstcorp.org/display/~<USER> and [<USER>https://confluence.lsstcorp.org/display/~<USER> to make this clean and easy; don't want N "manual" job triggers.   * Update IDL Conda job, develop builds, to name the build artifact the same each time.  This will stop the Anaconda cloud repo from filling, as the artifact will be overwritten.
Answer: 44517.0

User story: "The {{FitsGenericFormatter}} currently can only ingest {{.fits}} files, but other valid extensions are {{.fits.gz}}, {{.fit}}, {{.fits.fz}}."
Answer: 91.0

User story: "Deprecate needing to pre-pair exposures in PTC task, and calculate an appropriate pair based on header data."
Answer: 7418.0

User story: "This is a continuation of DM-26488.  More work is needed to get the CSC Conda jobs running regularly."
Answer: 40535.0

User story: "After a user reported another instance of loss of CSS rendering on TSSW Jenkins, I decided to perform some maintenance.  I converted all the Jenkins agents (build nodes) into systemd services, such that they will start on boot AND continually attempt to reconnect to master.  Before, the process would crash and the would have to be started up manually.  This does NOT address the CSS rendering issue, but makes recovery faster, now only requiring a restart of the Jenkins master service."
Answer: 137.0

User story: "Many of the bright stars we're observing have very considerable proper motion (and parallax). Take these into account when finding the star positions."
Answer: 221.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: Create a command-line tool for {{Registry.queryDatasets}} as a {{butler}} subcommand.    This method has a large set of optional keyword arguments, and I'm not sure they all need to be included in the command-line interface, especially at first.  I would certainly skip the {{dataId}} argument, as from the command-line it's completely redundant with the {{where}} argument.  The {{dimensions}} argument is probably also less likely to be generally useful.    The other consideration when defining this command-line interface is that we also have many Registry and Butler methods whose primary inputs are the outputs of {{queryDatasets}} - in other words, anything that takes an iterable of {{DatasetRefs}} in Python will probably need a command-line script that first runs {{queryDatasets}} and forwards the {{DatasetRefs}} to the method being wrapped.  That means all of those commands will probably need to have many of the same command-line option, but sometimes the names will need to change to avoid clashes.  For example, {{Registry.associate}} takes a "collection" argument of its own, so we'd probably want to map that to something like {{\-\-output-collection}} while calling the collection(s) passed to {{queryDatasets}} {{\-\-input-collections}}.    Also, you ([~<USER>) are more familiar with the command-line argument names already in use than I am, so please don't take anything I've written above as authoritative; consistency across commands is more important than anything I've written here (as long as consistency doesn't lead to ambiguity, of course).
Answer: 57861.0

User story: "Add a {{butler}} subcommand that wraps the {{Butler.pruneCollection}} method.    I don't think there are any special considerations for translating this interface to the command-line, and it's probably one of the most useful ones for people working regularly with Gen3 repos interactively, so it's probably a good one to put near the top of the list."
Answer: 7486.0

User story: "RepoExport already remembers the dataset IDs it's seen in order to avoid saving the same dataset twice.  It needs to do the same for dimension records.  It would be even better to handle duplicates at import time as well, but that's harder without better database-level insert idempotency, and there are already other tickets on that."
Answer: 8074.0

User story: "We're now ready to finish the integration. Track down and fix any remaining bugs so that Gafaelfawr can provide authentication to Chronograf and InfluxDB."
Answer: 25704.0

User story: "This is ticket for tracking schema changes we intend to release around weekly 38. We are putting the schema changes here so that we can limit the times we need to update version numbers and require ap_verify to be updated within a short period.  Tickets to be integrated are linked to this ticket."
Answer: 22647.0

User story: "Eric Mandel dropped the -latest tag when he released v0.2.  Fix the chart to pin a version by default."
Answer: 1382.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: "Support the use of configuration file in the M2 controller. At this moment, parts of parameters are hard-coded in the code. This task will try to find them and put into the configuration file."
Answer: 30148.0

User story: "treecorr > 4 has some small changes which break validate_drp.         Specifically, varxi in ggcorrelation has been removed.    There is varxim and varxip, described here:    [https://github.com/rmjarvis/TreeCorr/blob/master/treecorr/ggcorrelation.py#L105-L106]         The use is in line 187 python/lsst/validate/drp/calcsrd/tex.py.     Treecorr <4 also does not have varxim or varxip, so this ticket will likely require a merge of a new environment with treecorr > 4 as well.         It appears this is possibly a blocker for moving to python 3.8, due to conda-forge wanting treecorr > 4 for python 3.8 (I am not sure why - I have not checked the recipes at this point).          "
Answer: 27196.0

User story: "Get portal working on NTS."
Answer: 73.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*.    This task is the phase 2."
Answer: 21915.0

User story: "Write the test framework of SAL LabVIEW API. This task begins to construct a framework to test the LabVIEW API for each new SAL update. In the past, we used the component CSC in LabVIEW to test this. Now, we need a framework to test this automatically. The SAL LabVIEW APIs rely on the shared memory, which is not needed for the C++ and JAVA APIs. Therefore, this kind of automatic test framework should be helpful for the maintenance of CSC in LabVIEW. This task is in the phase 2."
Answer: 21594.0

User story: "The ESS 4 channel temperature code has been modified to support N channels, with N configurable. This ticket is for integrating that code into the ESS CSC."
Answer: 40555.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: "Specifically [~<USER> would like to try making events use TRANSIENT_LOCAL durability and telemetry use BEST_EFFORT reliability. But more generally we would like to be able to make such changes by modifying the QoS file, instead of changing code in ts_sal and ts_salobj. So [~<USER> and I have agreed to put all topic QoS in the QoS file with separate profiles: AckcmdProfile, CommandProfile, EventProfile, and Telemetry Profile. The new QoS file is in ts_idl: qos/QoS.xml.    Note that ts_salobj still sets read queue depth programmatically, though the default value of 100 matches the read and write depth in the current QoS file. This might be useful for making a longer read queue for certain systems, such as SAL/kafka producers. But if we don't need it, I can simplify the code by using the value in the QoS file. One problem with setting this programmatically is that there is no simple way for Python to determine what is in the QoS from the file. So if the depth is changed in the QoS file the default has to be changed manually in ts_salobj (and the problem is further complicated if we decide to have different depths for different topic categories)."
Answer: 6234.0

User story: "Update all of the base classes in metric-pipeline-tasks to pass dataIds from the runQuantum method to the run method. This will enable us to extract info such as filter, etc. from the dataIds."
Answer: 9794.0

User story: "This ticket is to verify that `meas_extensions_scarlet` can be run at scale. As such, it will not initially be using the bleeding edge version of scarlet but instead the version from June that was already verified in DM-25744. Once the newer version of scarlet has been integrated into the stack the processing will switch to the newer, improved (and tested) version of scarlet."
Answer: 47549.0

User story: "EIE have proposed a change in the status reporting. This ticket is for implementing the changes in both the Dome CSC and the mock controller and also to update the documentation accordingly."
Answer: 20387.0

User story: "For the ESS software development efforts a Docker image similar to the one used to run the CSC is needed. This ticket is for creating that Docker image."
Answer: 60545.0

User story: "Now that gphoto2 works well from the Docker container, the CSC needs to be improved to work as well. This ticket is to accomplish that."
Answer: 3205.0

User story: "Some patches in HSC do not have data for all bands (eg. tract 9813 patches 0,1 1,8, 8,1). This ticket is to update `meas_extensions_scarlet` to check for missing data and make sure that scarlet only attempts to run on the data that is present."
Answer: 28890.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, images delivered from various sources to the endpoint site are placed in subdirectories corresponding to observation nights when they were taken. However, it is not clear if the images from a single observation night are stored in one or two separate directories (different for images taken before and after 0:00 AM of a local time), what time zone these dates correspond to, and finally if identical conventions are applied across different instruments. Hence, for rsync based transfers, the endpoint manager can't just monitor a directory corresponding to a current date, but also "adjacent" days. Though the endpoint manager is already able to monitor past days, it is not able to look "into the future". The goal is to address this shortcoming.
Answer: 755.0

User story: With {{w_2020_36}} it seems pipetask2 requires {{-j}} otherwise the default isn't very nice.   {noformat}  pipetask2 run -b $CI_HSC_GEN3_DIR/DATA/butler.yaml --output-run  testrun --input HSC/calib,HSC/raw/all,HSC/masks,ref_cats,skymaps,shared/ci_hsc  -t lsst.ip.isr.IsrTask:isr  -d "exposure = 903334 and detector = 22"  --instrument lsst.obs.subaru.HyperSuprimeCam  {noformat}    {noformat}  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-153-ga31d2101+de92faa26f/python/lsst/daf/butler/cli/utils.py", line 443, in cli_handle_exception      return func(*args, **kwargs)    File "/software/lsstsw/stack_20200515/stack/miniconda3-4.7.12-46b24e8/Linux64/ctrl_mpexec/20.0.0-14-g18fd799+95ed9b6257/python/lsst/ctrl/mpexec/cli/script/run.py", line 168, in run      f.runPipeline(qgraphObj, taskFactory, args)    File "/software/lsstsw/stack_20200515/stack/miniconda3-4.7.12-46b24e8/Linux64/ctrl_mpexec/20.0.0-14-g18fd799+95ed9b6257/python/lsst/ctrl/mpexec/cmdLineFwk.py", line 696, in runPipeline      executor.execute(graph, butler)    File "/software/lsstsw/stack_20200515/stack/miniconda3-4.7.12-46b24e8/Linux64/ctrl_mpexec/20.0.0-14-g18fd799+95ed9b6257/python/lsst/ctrl/mpexec/mpGraphExecutor.py", line 231, in execute      if self.numProc > 1:  TypeError: '>' not supported between instances of 'NoneType' and 'int'  {noformat}    Adding a positive number for {{-j}} allows it to run without the error. From the help page it's not obvious this option is required.  1 probably would be a good default. 
Answer: 22705.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: "Rotator can get behind. Try ignoring extra commands.    If this works and is wanted then ts_salobj probably wants an update to handle it more gracefully (so ackcmds come for the commands actually executed, even though the pointing components are ignoring those acks). But I sincerely hope we will not need to do this. The existing queue is sufficient for getting a bit behind and catching back up, and I don't think we want to be running in a mode where the CSC cannot keep up overall. It would be far better to fix the problem -- which could be some combination of:  * Profile the CSC and try to remove bottlenecks.  * Slow down the tracking rate to 10 Hz. This should be plenty.  * Run on faster hardware."
Answer: 3795.0

User story: "Fix Python unit tests to use LSST_DDS_DOMAIN_PREFIX instead of LSST_DDS_DOMAIN"
Answer: 86.0

User story: "We want to know whether using gbdes in the stack in place of jointcal is a good idea, or whether there are aspects of gbdes that can be used in jointcal in order to improve its performance."
Answer: 961.0

User story: Add FGCM-application configs to obs_subaru.    The mechanism by which we "turn on" or "turn off" features in the official obs_subaru processing: RC2 reprocessing and HSC data releases is by adding the configs to obs_subaru. This helps us keep track of which config parameters were active in what eras, track why they were changed in the the commit message/Jira comments.     Only in very rare circumstances do we ask NCSA to use manual config overrides, and when we do its usually to work around a bug. They've used manual overrides for w_2020_26 and w_2020_30 and w_2020_34 to "use FGCM."     
Answer: 19870.0

User story: "The OODS was written to support one butler at a time, and sending one ingest message at a time.  A plugin interface was created so the transition from gen2 to gen3 could be a configuration file change, without having to change any code.  This has been demonstrated and is working.         There has been a request to support both gen2 and gen3 butler access for the OODS.    [https://confluence.lsstcorp.org/display/LSSTCOM/Commissioning+Activities+2020-09-08+Meeting+notes]     "
Answer: 23053.0

User story: "[~<USER> wants pywwt available in the Notebook Aspect.  See what it'll take and do it if it's easy; come up with a plan if it isn't."
Answer: 4580.0

User story: Based upon discussions in cam-ncsa-mirror slack channel.   DM-26632 has the work to make softlinks for the newest run (R4) and any new incoming Photodiode_Readings_*.txt files.  This ticket is to make the softlinks for at least the R3 run.  These older runs do not have unique filenames and as such the "backfill" script for R4 will not just work here.  [~<USER> has offered to provide instructions/pseudo-code for creating the new filenames.    After making links for R3, double check that no one needs this executed for earlier runs too (please make new ticket if even older runs need different script).
Answer: 8881.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: "Based upon discussions in cam-ncsa-mirror slack channel.  These files are currently transferred to the storage area while transferring files from SLAC.  They should be transferred as they are now and left there (no file transfer mechanism changes).  Currently these files are ignored when calling Gen2 repo ingestions.  Instead of making changes to the Gen2 butler, the request is to make softlinks in the /project/shared/BOT/_parent/raw/photodiode_data directory.  These new files should all have unique filenames, so the request is to put all of the softlinks into that single flat directory (i.e., no subdirectory structure including no date dir).    Also for previous files from *this* run manually make the softlinks for them too.  This ticket does not cover work for making the softlinks for older run(s) where the filenames aren't unique.    This change has come with a request to make it a high priority."
Answer: 8893.0

User story: "A standard CentOS 7 image for RPi4 with Docker pre-installed would be very handy to have. This ticket is for creating that image."
Answer: 11426.0

User story: "[~<USER> reported that he was ending up with filenames that were too long for the column definition in the datastore records table.    Currently the file path is 256 characters but we have lots of directories in the default template and the collection appears twice. A collection can be 64 characters so half the path can be taken up solely by the collection.    Consider using TEXT for this field rather than going to VARCHAR(512).  "
Answer: 25793.0

User story: "The version of GPhoto2 that comes with Centos 7 by default doesn't have good support for the Canon EOS 5D Mark IV camera and the latest version in GitHub does. This ticket is to make sure that the Dockerfile for the Canon camera supports that."
Answer: 4121.0

User story: "Top secret project for secret day."
Answer: 141.0

User story: "BaseCscTestCase.check_standard_state_transitions should accept settings to apply, so that it can be used to check CSCs such as the Watcher that have no useful default configuration.    Fix this and update ts_watcher to use the fixed version both on this same ticket."
Answer: 9967.0

User story: "Support a sal/kafka producer that handles OpenSplice internal DDS topics so we can get this useful diagnostic information into the EFD.    The simplest technique is probably to allow creating a SalInfo for these, so we can make Remotes that listen to them. The trick will be parsing the IDL file, since it has no revision hash codes (nor metadata comments).    We realize that when things start to go wrong we may no longer see these messages. But it's worth a try. In the long run we also want to get the standard log output into a central location, which should be more reliable when DDS has problems. We we can probably learn a lot from the data that does get into the EFD."
Answer: 20115.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 when a script fails to configure or some other failure while loading (before running), the scrip queue provides little feedback on what happened to it. The script simply disappears from the queue going from the {{salIndices}} to nowhere.     I think it would be better if those scripts also land in the {{pastSalIndices}} with some information on which stage it failed (loading? configuring?). "
Answer: 8753.0

User story: "Timespan comparisons can trigger warnings from astropy when years are out of range.    Fix the ones that are being triggered by tests."
Answer: 466.0

User story: "Add a Watcher commander to ts_watcher."
Answer: 1265.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: 14287.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: 14288.0

User story: "RFC the requirements and design developed on DM-26069 and the design sketch on DM-26259."
Answer: 40149.0

User story: "The {{butler}} command that now comes with {{daf_butler}} is intended to be extended for various repository related functions.  On task that exists in gen2, but not yet in gen3 is the utility that makes a discrete sky map from a collection of calibrated exposures: {{makeDiscreteSkyMap.py}}.  This utility is useful especially in scenarios where the visits are relatively localized on the sky.    This ticket is to implement a new subcommand using the {{click}} module.  I don't see why this couldn't be called {{make_discrete_sky_map}}.  This will involve a few steps.  1) Wrap the {{MakeDiscreteSkyMapTask}} with the necessary gen3 tooling  2) Pull the bulk of the heavy lifting out of the {{runDataRef}} method into a {{run}} method that both {{runDataRef}} and {{runQuantum}} can delegate to  3) Add a subcommand to {{butler}} that calls that task."
Answer: 37120.0