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: "To make it easier for Google developers to test the butler, make utils pip installable. This should mostly be the addition of a {{setup.py}}."
Answer: 6573.0

User story: "This ticket is to create a space in the ops-controls.lsst.io documentation area for information regarding the EFD."
Answer: 59791.0

User story: "It would be helpful for Google POC developers if they could do daf_butler development using pypi dependencies. For this to work sphgeom needs to be buildable using pip."
Answer: 7015.0

User story: "<USER>called a small meeting to discuss bulk transfers, the interface to the DBB service and whether Rucio could provide any part of the bulk transfer service."
Answer: 4.0

User story: "Steve and Htut-Khine have called a meeting with K-T, Nick and I about how the catchup archiver can determine what images the DBB has or doesn't have enough replications of in order to figure out what images to resend."
Answer: 6.0

User story: "As of DM-22255, it appears the metrics defined in {{colorAnalysis.py}} are no longer being added to the verify {{job}}, so the persisted {{json}} file does not included any actual measurements (e.g. they do exist in {{datasets/hsc/repo/rerun/RC/w_2020_19/DM-24822/verify/color/tract-9813/colorAnalysis_verify_job.json}}, but are not present in {{datasets/hsc/repo/rerun/RC/w_2020_22/DM-25176/verify/color/tract-9813/colorAnalysis_verify_job.json}}).  This needs to be fixed.    Additionally, to allow tracking the metrics per-tract when dispatched to the [SQuaSH metrics dashboard|https://sqr-009.lsst.io], a tract tag needs to be added to the metric metadata."
Answer: 11683.0

User story: "Originally in www_lsst_io we tried to used styled-theming to build a design system, including a dark mode. The problem, though, is that these styles aren't getting added to the site on initial load (they do after an in-app page transition, though). I think that a safer and more compatible approach will be to take out the styled-theming integration and instead build up a design system using CSS custom properties. This will also let us support a dark mode (https://github.com/insin/gatsby-plugin-dark-mode)"
Answer: 3132.0

User story: "Update the file SALSubsystems.xml for HeaderService components for AT/CC and MT following the definitions from:  [https://ts-xml.lsst.io/salsubsystems_attributes.html]"
Answer: 1553.0

User story: "Need to fix the SALSubsystem information on the following CSCs:        * ATAOS   * ATHexapod   * ATPtg/MTPtg   * ATSpectrograph   * DIMM   * Environment   * MTM2   * Scheduler"
Answer: 1923.0

User story: "Please create PostgresSQL account for me (<USER>"
Answer: 1160.0

User story: "Time spent coordinating, creating agenda, followups, reporting and holding the weekly TMA Software Integration Meeting"
Answer: 2840.0

User story: "Add new versions of templates to the conda guide."
Answer: 33260.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Currently, we have to create rpms for forwarder manually. This creates overhead whenever we try to deploy in the production environment. This ticket explores github actions to automatically create rpms when master branch is merged with branch."
Answer: 119916.0

User story: "neophile now works to create a PR in a single repository. Add support for batch operations across multiple repositories, maintaining a tree of clones that can be updated to refresh the pull request."
Answer: 14581.0

User story: "When we send a message from the archiver to the forwarder, we expect to get back an ACK for that message.  We also set a timeout value for that ACK. If we don’t get the ACK after the timeout expires, we go into a fault state.  Note that the ack timeout is there to detect that something really bad is happening and that the system likely won’t get an ack no matter how long it waits.       What happened last week was that Michael sent a lot of requests to read BIAS information in very quick succession, with a very small delay. This causes messages to be backed up on the RabbitMQ queue since messages aren’t read until the work is ready to be started.  Since the initial message was sent, and a timeout was started, the timeout expires even before the Forwarder gets it from the message queue.       The simplest (and IMO, wrong) way to prevent this is to increase the ack timeout value in the config file. This is only a short term solution and pushes the problem off. We know this because we’ve already done this once; the ack timeout used to be 10 seconds, and now it’s 60. Increasing the ack timeout just kicks the can down the road.       There are several ways to fix this, and Htut-Khine and I went over several ideas.  Messages could be immediately retrieved in a thread, and then kept locally (or in a Redis database) after being acknowledged. One thread could keep reading and filling the queue, another (or multiple threads) reads from the work queue does the work. Note that this kind of defeats the purpose of the original ack timeout, since messages are responded to quickly, masking an error where the work wasn’t actually done.      We do have another mechanism in place to detect that the Forwarder is gone, which we also currently use, so we might be able to eliminate the timeout completely.  If that mechanism detects that the Forwarder is gone, the Archiver will go into a fault state. (The Forwarder can also detect when the Archiver is gone).      Note that we would still send ACKs back; we just wouldn’t time out, eliminating the artificial backlog response issue. We would also still keep the “aliveness” mechanism in place, so if the Forwarder crashed, we’d know and go into a fault state.      I think this means we can safely eliminate the ack timeout."
Answer: 1078.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "We wrote a couple of unit tests in DM-25832.  This ticket is to write the rest of the unit tests.  This should encompas {{PA1Task}}, {{PA2Task}}, {{PF1Task}}, {{AMxTask}}, {{AB1Test}} and {{TExTask}}.  This should also include tests of configuration for each of those tasks."
Answer: 135463.0

User story: "One feature that wasn't ported over from the querymonkey was the slack alerting.  This just doesn't work the same in the mobu sense.  We need to think of a better way to report errors, and I want to gather people's feedback on how they want this info since they will be the ones investigating."
Answer: 8791.0

User story: "This will allow us to test gpfs in kubernetes on multiple worker nodes, primarily to verify file locking between multiple nodes."
Answer: 2.0

User story: "Begin testing native gpfs in kubernetes.    I'll be temporarily creating a 'k8s-gpfs' role that included the gpfs_client profile in it and applying that role to the k8s-test cluster nodes. This will allow us to test gpfs without installing all the client software on nodes that aren't ready for it yet.    I also need to add:    ```gpfs::nativemounts::mountmap:   lsst:   opts: nosuid```    to 02clusters/k8s-test in hiera."
Answer: 1.0

User story: "A lot of things in the spawned environment are currently represented by environment variables being passed in; we should, to the degree it's feasible, represent them with mounted configmaps instead."
Answer: 11567.0

User story: "Currently, {{alert_packet.schema}} provides {{retrieve_alerts}}, which builds an in-memory list of packets to return.  This fails when the input being read is large.    This ticket is to either replace this interface or provide an alternative that iterates through large files."
Answer: 4645.0

User story: "Add a function to ts_salobj that returns the OpenSplice version"
Answer: 1269.0

User story: "Perform some Rotator/CCW tests using software simulators in preparation for hardware tests at the summit. "
Answer: 34879.0

User story: "Get the TMA and Axes PXI virtual machines running. "
Answer: 33479.0

User story: "Get the hardware for [~<USER> connected. This will require that I go to the Recinto. My affadavit has been approved. I will also be bringing along a bag of cables that were in [~<USER>'s room. "
Answer: 14508.0

User story: "Convert RC2 w_2020_26 to gen3 repo"
Answer: 1783.0

User story: "This is to track the task of getting the Speedgoat machine connected to the Simulation Cluster."
Answer: 14700.0

User story: "As part of the ongoing documentation effort, it has been determined that moving the TMA technote information into a ts-tma.lsst.io site is a good idea. This will require getting files transferred over to a new repo and configured for deployment on lsst.io."
Answer: 10491.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: "https://github.com/lsst/daf_butler/blob/master/python/lsst/daf/butler/datastores/s3Datastore.py#L199-L205 checks to see if an object exists before writing it.  With AWS and likely other object stores, relaxed consistency guarantees mean that there could be a race condition here if multiple simultaneous jobs are trying to write.  Furthermore, the additional API call is pretty wasteful as it is almost always going to return false, and it may help trigger rate limiting.    We should consider whether we can live with overwriting of a dataset."
Answer: 51335.0

User story: "The MTMount CCW control loop presently sends CCW tracking commands a bit late, because it is based on the Rotator Application telemetry topic, which comes a bit late.    Extrapolate the (p,v,t) to send the commands slightly in advance."
Answer: 76147.0

User story: "The {{NotebookAuth}} class makes available a method to list all available auth keys, but it has a typo that makes it unusable [here|https://github.com/lsst-sqre/lsst-efd-client/blob/master/lsst_efd_client/auth_helper.py#L68] (endopint --> endpoint).    This should also:  1. Implement a test for this method  2. Implement class methods on the {{EfdClient}} class that delegate to {{NotebookAuth}}"
Answer: 137052.0

User story: "Need to roll mysqlproxy back to Lua 5.1 for the time-being to unblock further development on master while bug-fixes for the Lua 5.3 port are pursued on a branch. "
Answer: 698.0

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

User story: "The MTMount CSC should start up with the camera cable wrap tracking the camera rotator."
Answer: 76249.0

User story: "Computing the quartiles of the data in the aggregation window allow us to make a box plot representing the data in that window. That would be an interesting way to visualiz the {{kafka-aggregator}} results. The  Python statistics module provides the [statistics.quantiles()|https://docs.python.org/3/library/statistics.html#statistics.quantiles] method and its default behavior ({{n=4}}) is to compute the quartiles.  "
Answer: 56629.0

User story: Large loads of queries on the czar can result in an "Out of stream resources" error from xrootd SSI. This should be fixed by using XrdSsiProvider::SetSpread()  to allow more stream resources. It may also be desirable to reduce the number of streams a worker is willing to open to a particular czar (or just the czar until multi-czar is working).
Answer: 65193.0

User story: "Te-Wei mentioned that the template's questions were a little unclear. This ticket is to actually write documentation about the template and attempt to shed light on how to use it."
Answer: 4374.0

User story: "Please create a PostgreSQL account for user {{svclsstdbmxk}}."
Answer: 1822.0

User story: "On -int, switch to GPFS rather than NFS by changing the mount configmap."
Answer: 1858.0

User story: "Generate template for dm_CCArchiver."
Answer: 20806.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: "Fix the transition of tracking in deciding the tracking trajectory. In the previous update (DM-25243), I made two mistakes. One is that I do not generate a smooth velocity command in the tracking (I forgot the 4000 Hz internal calculation). The other one is that I do not stop the rotator's velocity smoothly if there is no new tracking command for some time. This ticket is to fix these two bugs."
Answer: 43253.0

User story: "Update the [Sensor Characterization and ISR|https://confluence.lsstcorp.org/display/DM/Sensor+Characterization+and+ISR] page with the state of ISR in DM and a summary of the state of each detector effect listed in there, as of July 2020.      - Discuss ISR in DM at the SAWG/CVT meeting on 7/7/2020  - Discuss the state of detector effects on 7/8/2020 with <USER>
Answer: 15643.0

User story: "For some reason, when a {{Measurement}} is NaN (specifically {{numpy.nan}} the units are set to the empty string in the serialized JSON document of the {{Job}} to which the {{Measurement}} belongs.  {{astropy.Quantity}} allows a NaN to have a unit, so it does not appear to be dropped at that stage.    This is to figure out which phase is dropping the unit: adding the measurement to the {{Job}} or serialization to JSON.  Then find a way to make sure the unit is forwarded on.  This may require a special JSON serializer for {{Measurement}} objects or {{astropy.Quantity}} objects."
Answer: 19452.0

User story: "Support the use of configuration file in rotator low-level controller. MOOG provided the middleware wrapper orginally that allows the user to update the configuration file by SAL. T&S team replaced it and used the Python CSC based on *ts_salobj* instead. This new CSC does not allow to do so. Therefore, this task will update the low-level controller code to let the user can configure the rotator by the configuration file."
Answer: 16181.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: The HTML rendering of SAL APIs is very handy, but I have a few requests for further enhancement.  * By far the biggest issue is that the generic topics are not listed. Unfortunately adding them will be some work. More on this below.  * I beg you to include a prominent link from the metadata for a given CSC (generated from SALSubsystems.xml) to the API for that CSC. Preferably also include that link in the table. That is arguably the most useful piece of information and it allows CSC docs to link to one obvious place, where a user sees the metadata and can quickly get to the API.  * Please include a link from the API back to the metadata (that may exist, but I didn't see it).  * Please consider omitting data for:  ** The Subsystem field. We *know* what subsystem this is. It's just clutter. (It's also clutter in the XML itself, but that's another issue).  ** Preferably omit the subsystem prefix as well.  ** Deprecated fields, including Version, Author and Explanation  * Also please consider omitting the following fields, though this is more of a stretch:  ** IDL_Size if it's 1. That means "no limit" (which is confusing) and is the most common case.  ** Count if it's 1. That's by far the common case.    Regarding how to handle generic topics. The obvious solution is to parse the Generics tag of SALSubsystems, though it's a bit of a nuisance. Another option is to parse the IDL files instead (salobj already has a parser for this, so just call that). This has the one really big disadvantage that it requires the IDL be built before you can generate the HTML. If you can live with that (and it's a big if) you gain some significant advantages:  * It gives you *all* the topics. The list is guaranteed to be correct because IDL files are the fundamental information used by OpenSplice (for all languages).  * It omits the garbage fields; you get the fundamentals: name, type (including if it's an array, and how many elements the array has), description and units.  * It gives you the actual data type. Several types in the XML are aliases which become the same standard DDS type in the IDL files.  * The parser already exists and it is the same one used by the sal/kafka producers.
Answer: 8332.0

User story: "Try out the new documentation format on a small package: ts_ATDome."
Answer: 26387.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 working on DM-25761 I was shocked to find in lsstts/develop-env:b101 that the file /opt/OpenSplice/V6.9.0/HDE/x86_64.linux/tools/python/src/ddsutil.py is missing a crucial fix for array data.    This can be seen by running the following in ts_salobj: {{pytest -v -k setArrays}}.    Fortunately the version in site-packages contains the fix. But the fact that it differs from the version in /opt/OpenSplice is confusing and a trap for the unwary.    If at all possible please make the code in /opt/OpenSplice match the installed code. The differences may be confined to {{/opt/OpenSplice/V6.9.0/HDE/x86_64.linux/tools/python/src}}  ; many other files in /opt/OpenSplice *are* the installed OpenSplice that we are using."
Answer: 46468.0

User story: The coadd level catalogs include a flag:  {code:python}"detect_isPrimary", type="Flag",   doc="true if source has no children and is in the inner region of a coadd patch "            "and is in the inner region of a coadd tract "            "and is not \"detected\" in a pseudo-filter (see config.pseudoFilterList)",  {code}  that is very useful for culling catalogs of duplicate (patch/tract overlap), non-deblended parent sources ({{deblend_nChild>0}}, and sky objects. No equivalent flag currently exists at the visit /single frame measurement level, so this ticket is to add such a flag. Currently, the only two conditions to be added to flag undesirable sources are:   {{deblend_nChild == 0}}   {{sky_source is False}}    A community post describing this feature may be found here: https://community.lsst.org/t/primary-source-flag-for-single-frame-processing/4425
Answer: 47863.0

User story: "Before trying to implement DM-25159, I need to check that jointcal does not have cases where the chi2 gets dramatically worse in one step but then recovers. It should be relatively simple to write a script that scans a log and generates a plot of the chi2 for that jointcal run.    I'll need access to the logs from jointcal runs on a big HSC run (RC2? Whatever the biggest one is)."
Answer: 14943.0

User story: "List ts_simactuators as a dependency of ts_ATDomeTrajectory"
Answer: 467.0

User story: "mysql-proxy seems to be having some problems after the Lua and conda upgrades.  Having debug symbols here will help us troubleshoot."
Answer: 40.0

User story: "Mobu is our stress testing monkey framework that does automated logins of jupyterhub and other services to make sure they are alive, functioning well, and can handle load.         It runs in the cluster it is monitoring but accesses it like anyone else - through the external address.  But for some reason this gives a connect timeout.    This used to work before the maintenance I believe, so this may be related to some kind of iptables or networking change?"
Answer: 1497.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Currently the EFD client ends up raising a {{JSONDecodeError}} when the InfluxDB is down.  This is essentially because a 400 is returned from the endpoint and that is not valid JSON.  The {{aioinflux}} client tries to decode the error and throws the exception.    I'm not sure whether the better thing to do is to make the {{aioinflux}} client raise a more useful error or to do a health check of the InfluxDB at construction time."
Answer: 144523.0

User story: "baseSdssShape computes the area of an ellipse from moments by converting them to major and minor axis lengths, which is unnecessary since the area is identically equal to the square root of the determinant (xx*yy - xy^2). Pair coded with [~<USER>."
Answer: 73859.0

User story: "If a pipeline definition document has the same label for two or more tasks, the last one will clobber the rest silently.  Tasks should not have the same label, but if they mistakenly do, it can lead to confusing behavior.  It would be nice if the quantum graph builder would throw an exception in the case of duplicate labels in the same pipeline definition document.    I believe it already does throw an exception for duplicate keys in separate pipeline definition documents inherited in a single one."
Answer: 2604.0

User story: "If the storage underlying Redis goes away, Redis keeps running but just rejects all writes. Determine how to make this fail health checks so that the pod can be automatically restarted."
Answer: 68558.0

User story: "Review the ESS telemetry topics and add a timestamp if there isn't already one."
Answer: 1121.0

User story: "There is a lot of documentation related to the Dome CSC and the communication with the Lower Level Components on Confluence. This ticket is to migrate the relevant documents to .rst files."
Answer: 8965.0

User story: "Compare Python performance of ADLink's official community edition of OpenSplice (with my array fix and segfault fix) against what we are using. If the performance is similar and all tests pass, I hope we will consider using it -- though it still has to be checked with the other languages."
Answer: 1737.0

User story: "Similar to how it's done for query-dataset-types    since DM-25750 is done we can do this. Per Tim at [https://lsstc.slack.com/archives/C2JPT1KB7/p1593616624232100]"
Answer: 91501.0

User story: "Deploy the docs for {{lsp-deploy}} to {{phalanx.lsst.io}} using GitHub Actions."
Answer: 279.0

User story: "A small change has been introduced in the configuration protocol: all values need to be arrays."
Answer: 7167.0

User story: "Refresh the certificate for the HTTPS service on the {{lsst-demo.ncsa.illinois.edu/firefly}} server."
Answer: 2.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: "Document in one place the specific minimal set of work that would be required to fully replace the PDAC Portal's image-search features with an IVOA-services-oriented equivalent.  This was in-progress work at the time of the DM-10 freeze, and is the minimal piece of new development that would facilitate the use of the Portal during DP0 and commissioning activities.    This amounts to writing a specification for DM-18692, and involves collecting various sketches together for concreteness."
Answer: 370.0

User story: "Spencer has been invited to present on “Ideas on using Kafka streams in DM” (specifically for alert distribution, I believe; we're already using Kafka in a bunch of other places) at the DM-SST meeting of 27 July.    He should flesh out his proposal, and do some back-of-the-envelope estimates of what it might do for bandwidth usage, number of consumers we might support, etc.    Let's meet on Wednesday or Thursday of the week before (22 or 23 July) to go through a draft/ideas for this presentation."
Answer: 112746.0

User story: "[~<USER> noted that {{registry.queryCollections}} does not work with regexes despite being documented to do so.    This patch helps a little:  {code:diff}  diff --git a/python/lsst/daf/butler/registry/wildcards.py b/python/lsst/daf/butler/registry/wildcards.py  index c416105f..52efe8f2 100644  --- a/python/lsst/daf/butler/registry/wildcards.py  +++ b/python/lsst/daf/butler/registry/wildcards.py  @@ -739,7 +739,7 @@ class CollectionQuery:           if wildcard is Ellipsis:               return cls.any           assert not wildcard.strings  -        return cls(search=CollectionSearch.fromExpression(wildcard),  +        return cls(search=CollectionSearch.fromExpression(wildcard.items),                      patterns=tuple(wildcard.patterns))          def iterPairs(  {code}    We did not notice this previously because there are no tests using regexes."
Answer: 910.0

User story: "We need to eventually generate fakes for daily tests of diaSource completeness. With this in mind this ticket will create an initial pipeline task to generate fakes in a reproducible way for both CI and image quality tests."
Answer: 102749.0

User story: "Some people want to add their own images directly rather than having them rendered by the code."
Answer: 54980.0

User story: "Previous versions of scarlet have suffered from memory issues that prevented them from running on a full HSC patch, causing us to create small 1k x 1k patches to test the stack implementation of scarlet. This ticket is just to run scarlet on a full HSC patch to verify that all of those issues have been taken care of or generate new tickets to fix any issues that come up."
Answer: 46388.0

User story: "Document the algorithm of interpolation for rotator. At this moment, the rotator Simulink model uses the extrapolation for *track* command. This task tries to define the question clearly and provides the analytical solution of interpolation. The update of Simulink model will be a separate ticket."
Answer: 10703.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Take the logic for doing the query monkey and move it into mobu to have one place to control all the testing.  This will also make it easier to report results and alert from one place. "
Answer: 8878.0

User story: Since an nginx-ingress update in LTD Keeper ([https://github.com/lsst-sqre/roundtable/pull/81)] LTD Keeper has started using http URLs in its API rather than https.    The source of this issue is [https://flask.palletsprojects.com/en/1.1.x/api/?highlight=url_for#flask.url_for]    A potential solution is either hardcoding the scheme for flask's {{url_for}} API or trying the werkzeug "ProxyFix" middleware. https://werkzeug.palletsprojects.com/en/1.0.x/middleware/proxy_fix/
Answer: 1319.0

User story: "Update *MTAOS* to adapt the latest xml version, especially for the *M2* xml update (DM-25475) and *Hexapod* xml update (DM-25856). Maybe need to check there is the update of *M1M3* or not. This task will update the CSC test as well for the [timeout issue|https://github.com/lsst-ts/ts_MTAOS/issues/27] and use the *Controller* by *ts_salobj* to help for the test (receive the subsystem correction). For the use of *Controller*, the CSC test in *ts_m2* is a good example. After this task is done, need to prepare a new docker image of *MTAOS* simulator to deploy in NCSA for the integration test."
Answer: 80889.0

User story: "Chris notes that some alert packets being generated when processing HSC data are very large, due to huge cutout images. This may be due to extremely large footprints due to saturation, bleed trails, etc. Investigate and confirm this theory. If there's an easy fix, make it on this ticket; if we need to do something complex (or to change the requirements to impose a hard maximum on the cutout size) file a new ticket and review it with science leadership."
Answer: 30670.0

User story: "Fix ts_xml doc build warnings."
Answer: 8709.0

User story: "Remy Joseph has recently added a new `StarletSource` class to scarlet to allow it to measure more complicated morphologies for larger extended sources. This ticket is for me to read his thesis and other related material to understand the basic concepts of wavelets and the undecimated isotropic wavelet transform (aka starlets) and how they have been implemented in scarlet to better understand how they are being used in this context and whether or not they will be useful for Rubin Observatory."
Answer: 601.0

User story: "cert-manager usually fails on initial deploy because it tries to deploy resources that need webhooks before the webhooks are running. I think this is due to our ClusterIssuer and the solution is to delay creating that resource until the webhooks have started. Perhaps Argo CD sync waves can do this?"
Answer: 66507.0

User story: "Okay so we've created the CILogons, and I've run the script to generate the secrets for these new environments.  Now add the values files to test it out, and let's make sure it works."
Answer: 1150.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: "Prepare for using Gafaelfawr backed by GitHub to authenticate web APIs in Roundtable by getting Gafaelfawr working in the Roundtable environment."
Answer: 131371.0

User story: "Gafaelfawr is already checking membership.  No need for hub to know about it at all, and therefore not only does allowed/forbidden not need to be a secret, it doesn't need to be present in JupyterHub at all."
Answer: 4106.0

User story: "The EFD Operations document is intend for release in the review document pack.  Review for completeness and up-to-dateness."
Answer: 2880.0

User story: To enable sorting documentation records by handle and date, these fields need to be numeric:   * "number" field needs to be numeric   * "sourceUpdateTime" field needs a version that is a unix timestamp
Answer: 4450.0

User story: "Allow the \{\{kafkaaggregator}} example to produce an indefinite number of messages. Also expose the frequency and the max_messages parameters in the configuration, that will simplify the deployment of the producer."
Answer: 239.0

User story: "Preliminary work in https://github.com/lsst-dm/jenkins-dm-jobs/pull/676"
Answer: 26499.0

User story: "For testing purposes, I'd like to have a test PostgreSQL service account which is separate from my NCSA account ({{mxk}}). Suggested name for the account: {{svclsstdbtest}}.  "
Answer: 72.0

User story: "Submit an LCR to ask for a change to the DMSR to implement the project decision on the use of nanojanskys as the standard unit of flux."
Answer: 9.0

User story: "Monthly RC2 reprocessing with w_2020_26 stack.    Jointcal is run only for astrometric calibration, photometric calibration will be done  with FGCM     "
Answer: 21980.0

User story: "HS need to be deployed at the base using version 2.3.0  "
Answer: 3503.0

User story: "Ticket DM-20070 adds code to {{cp_pipe/ptc.py}} which is based on code by <USER> This code, in turn, implements a model of the PTC that is described in equation 20 of Astier+19. This ticket should compare the gains obtained by fitting this model ({{ptcFitType = FULLCOVARIANCE}} in {{ptc.py}}) to the gains obtained by fitting the PTC to the existing {{EXPAPPROXIMATION}} (equation 16 in Astier+19) and {{POLYNOMIAL}} {{ptcFitType}} options.      Potentially useful input data for this:   * BOT data in {{project/shared/BOT}}  * auxTel data in {{project/shared/auxTel}}    "
Answer: 74542.0

User story: "See RFC-698."
Answer: 107226.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: The formal processing of the HSC-SSP data releases with the shared "stack" has long revealed the presence of extended/low surface brightness objects in the coadd catalogs that are seemingly "junk" (as identified by their location in various parameter planes where "typical" physical objects don't populate).  However, in their recent processing, the abundance of such junky objects seems to have greatly increased (from the HSC "S16" to "S19" releases).  These sources are problematic for many science cases, weak lensing analyses in particular, so it would be great if we could find a way of tracking their presence and abundance the coadd catalogs without an overwhelming overhead of processing large areas of the sky.  The HSC RC2 dataset (DM-11345), which consists of 3 tracts and is currently periodically reprocessed (DM-25402), would be a great place to start, so the aim of this ticket is to see if we uncover enough of these objects in the RC2 dataset to reliably track and characterize them (with the ultimate hope of determining a formula for preventing their contamination in catalogs – whether that be via processing tweaks preventing them from getting counted as "detections", or a reliable set of cuts to filter them out of the catalogs without also losing real sources).
Answer: 97004.0

User story: "Attempting to upgrade Vault Secrets Operator to the latest version produced the following error:    map: map[] does not contain declared merge key: name    Figure out what's wrong and redo the upgrade."
Answer: 17456.0

User story: "The salkafka producers seem to not be sending out ackcmd Kafka messages when the SAL topic messages are received."
Answer: 4115.0

User story: "Write a document in the style of greek epic poetry to our continuous deployment process and how we can both sail the ship across the sea and replace it at the same time."
Answer: 142101.0

User story: "In DM-25689 we found some problems with stray light files.  We need to add a test to obs_subaru to ingest an example file and then be able to retrieve it."
Answer: 434.0

User story: "Remove divergence in the nginx-ingress configuration between us and NCSA and between the different science platform environments. Make sure that we always redirect to https if the user uses http."
Answer: 38016.0

User story: "Add a framework for operational documentation to lsp-deploy similar to Roundtable. This will be where we document how to upgrade components."
Answer: 8447.0

User story: "Post v20 release, merge  the 20.0.x release branch to master."
Answer: 33.0

User story: "Run the Saha et. al Galactic bulge dataset identified in DM-25105 through single frame processing."
Answer: 130358.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-25447 I discovered that a read-only Filter component for Exposure can't work because the information is derived from metadata that is stripped and a Filter can not be persisted since Filter.writeFits is broken.    I propose that we write a very simple formatter that bypasses the FITS persistence system and simply writes a yaml file that includes the filter information. On read it will translate the filter name to a Filter object by looking it up in the filters singleton. This can then be set in the exposure using {{setFilter}}.    This will turn filter into a normal component and should be quick to implement."
Answer: 445.0

User story: "We now have quite a complex system of formatters and assemblers. It's time to write down how this all works. This might help clarify the situation regarding parameters for read-only components."
Answer: 110033.0

User story: "For each document series, programatically create a pre-filtered listing of documents in that series.    By default, sort by handle, but also allow sorting by revision date.    This change will allow us to keep the default listing in the advanced search page empty (requested in  DM-24956)."
Answer: 17846.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: "Others will follow instructions (still to be announced) and create their own request tickets.  But since there is a bunch we know off the top of our heads, I'm making one ticket.   Please add the following users to the PostgreSQL server.    [~<USER>: <USER>  [~<USER>: timj   [~<USER>: <USER>  [~<USER>: <USER>  [~<USER>: nate2   [~<USER>: <USER>  [~<USER>: <USER>  [~<USER>: <USER>
Answer: 28083.0

User story: "The web host changed names last week from `lsst-web.ncsa.illinois.edu` to `lsst.ncsa.illinois.edu`.  Fix this in the nagios configs."
Answer: 14.0

User story: "Update stable to the new science-platform way of doing things, like we did for int.  Should be simpler since we've hopefully found most of the issues.  Also clear out old broken stuff like abandonded namespaces."
Answer: 9707.0

User story: "Currently {{DifferenceImageTask}} does not persist the warped templates that are used in the subtraction, so we cannot provide alert cutouts that actually match what was subtracted.  This ticket is to make those warps persistable and to use them to construct appropriate cutouts for the alerts. "
Answer: 6520.0

User story: "Docker also needs to be updated to 18.09.9    This is part of our planned maintenance for June 25, 2020."
Answer: 5304.0

User story: "Part of PM"
Answer: 5322.0

User story: "There are several recent security vulnerabilities    [https://www-auth.cs.wisc.edu/lists/htcondor-world/2020/msg00005.shtml]    Please read through these and take appropriate actions as suggested."
Answer: 6.0

User story: "[kafdrop | https://github.com/obsidiandynamics/kafdrop] is an open-source web UI for kafka and can replace some of the functionalities of Control Center.  "
Answer: 149.0

User story: "Add OBSANNOT keyword needs to be implemented in the headers.    {{CCCamera_logevent_imageReadoutParameters.daqAnnotation}}    {{ATCamera_logevent_imageReadoutParameters.daqAnnotation}}      This applies to all camera flavors."
Answer: 330.0

User story: "Upgrade Confluent Platform to version 5.5 on the EFD sandbox and evaluate it before rolling this version to the other environments."
Answer: 80.0

User story: "We'll deploy the {{kafka-aggregator}} on the Sandbox EFD and evaluate its performance and scalability."
Answer: 9440.0

User story: "Ensure feedback from RFC-703 is incorporated into DMTN-155."
Answer: 121161.0

User story: "The default version of git that is supplied with RHEL/CentOS is very outdated.    On the lsst-dev servers we have replace git with 2.24.x from the [https://ius.io/] YUM repo.    This task is to create a Puppet profile or module that would replace the default git package(s) with the latest from [https://ius.io/] (which is already mirrored at [http://lsst-repos01.ncsa.illinois.edu/centos/7/x86_64/ius/]). "
Answer: 39978.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Currently the aggregation puts the method name for aggregation into the measurement name.  I think we should have a config for the aggregation task that specifies the method to use for a special summary aggregation.  Different metrics may use different methods to generate the summary aggregation we want to report.  This would mean we can refer to a special measurement called {{metricvalue_summary_\{package_name\}_\{metric\}}} in our reporting software.  This may be implemented as part of DM-25507.    The "summary" aggregation should default to either median or mean.
Answer: 23021.0

User story: "Currently the aggregations are done over the entire collection per band.  I think these should instead be done at the tract level per band.  Maybe we will find all sky metrics useful in the future, but in the short term, they do not seem to serve a concrete purpose."
Answer: 23025.0

User story: "For AP it would be useful if the same catalogue could be used to add sources to both the coadds they use for templates and the calexps they use for comparisons. To allow for this add columns to the fakes input catalogue, `coadd` or `calexp` which can be set to True or False. By default these are set to True so that all objects are added to either dataset."
Answer: 81843.0

User story: "* Ensure that a user can't create a technote using the general-purpose latex document template. Provide feedback in Slack to use the technote options.   * When there's an error, return a summary of the data the user entered so they can copy-paste it back.   * Review all Slack interactions by template bot and try to reduce the number of messages."
Answer: 8149.0

User story: "Fix the following error in the rotator Simulink model. There is the problem of physical model in plant that the rotator's position will differ from the related position command gradually until the trigger of *followingError* (the difference >= threshold) and this stops the motion of rotator. According to the observation, this happens if the rotator moves in the negative direction.    In the following figure, there are two targets: (1) position=1.2 deg and velocity=0.01 deg/sec and (2) position=1.5 deg and velocity=-0.01 deg/sec. The total simulation time is 20.1 sec. There is no big difference between the position command and position. The error of *noNewTrackCmdError* after the slew of the second target is triggered as expected.   !trackAdapNoNewTrackCmd.png|thumbnail!    However, if the second target has position=-1.5 deg and velocity=-0.01 deg/sec, the following error is triggered while the rotator turns the direction to slew to the second target:   !trackSolverAdap.png|thumbnail!"
Answer: 47468.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: [On Slack|https://lsstc.slack.com/archives/C2B6DQBAL/p1593015021219300] it was suggested that the "lsstdoc (LaTeX)" template should be renamed to "Generic LSST doc".    The Slack hint for the template should also indicate that the template isn't intended for technotes (this change should be made in conjunction with error handling in the handler).    Also, I noticed that the template for the lsstdoc template doesn't have its own README - the readme was copied over from the test_report template.
Answer: 8166.0

User story: "Handle all changes specified [here|https://confluence.lsstcorp.org/display/LTS/SALSubsystem+Attributes] and add documentation to the package."
Answer: 6804.0

User story: "Let's just rely on gafaelfawr to give us a JWT."
Answer: 2651.0

User story: "Have a look through the requirements on the notebook aspect of the science platform presented in the [DMSR|https://docushare.lsst.org/docushare/dsweb/Get/LSE-61] and the [LSP requirements|https://docushare.lsst.org/docushare/dsweb/Get/LDM-554].  The intent is to perform an audit to check for self consistence and completeness.    A special effort should be made to identify missing or incomplete requirements in order to improve our ability to verify the system."
Answer: 81932.0

User story: "Roll out the science-platform refactor to int and fix any issues that come up."
Answer: 74.0

User story: "Add statusCode and description to imageRetrievalForArchiving and image in OODS messages.   It should always use raft and sensor from the message from the forwarder, instead of trying to rely on the file name for that information."
Answer: 24030.0

User story: "Add more information such as raft, sensor into Image_retrieval message."
Answer: 21764.0

User story: "Need a no-reboot option to be able to update OS in place and reboot later."
Answer: 209.0

User story: "I'm seeing the following errors in /var/log/messages on test systems where we've upgraded to CentOS 7.8:  {noformat}  Jun 22 15:31:18 lsst-test1.ncsa.illinois.edu nrpe[5815]: Error: (use_ssl == true): Request packet version was invalid!  Jun 22 15:31:18 lsst-test1.ncsa.illinois.edu nrpe[5815]: Could not read request from client 141.142.237.31, bailing out...  Jun 22 15:31:18 lsst-test1.ncsa.illinois.edu nrpe[5815]: INFO: SSL Socket Shutdown.  {noformat}  (I'm not 100% convinced this is due to the upgrade, but I do not ever remember seeing these errors elsewhere.)"
Answer: 1.0

User story: "Create the test plan and report for the v20.0 science pipelines release acceptance test campaign."
Answer: 131001.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: Example using a window size of 1s and frequency of 1Hz:    {noformat}  [2020-06-23 09:49:45,339] [19441] [ERROR] [^---Table: kafkaaggregator-example-003-tumbling-window]: Crashed reason=StatisticsError('Error computing stdev of [0.46768980467854293].')  Traceback (most recent call last):    File "/Users/<USER>Projects/kafka-aggregator/src/kafkaaggregator/aggregator.py", line 207, in compute      aggregated_value = eval(operation)(values)    File "/usr/local/opt/python/Frameworks/Python.framework/Versions/3.7/lib/python3.7/statistics.py", line 649, in stdev      var = variance(data, xbar)    File "/usr/local/opt/python/Frameworks/Python.framework/Versions/3.7/lib/python3.7/statistics.py", line 587, in variance      raise StatisticsError('variance requires at least two data points')  statistics.StatisticsError: variance requires at least two data points  {noformat}
Answer: 1555.0

User story: "Need a nice summary of everything that exists on JIRA tickets."
Answer: 84649.0

User story: "ctrl_mpexec has a perfectly serviceable {{doc/}} directory, which builds without errors or warnings. It doesn't provide much useful information beyond automatically generated API docs yet, but it at least provides something convenient to link to. We should include it on pipelines.lsst.io."
Answer: 24014.0

User story: "Michael just noticed that the MTMount simulator is using values for Elevation and Azimuth motion that are not the same as the specification. We agreed that the best would be to use the same parameters we use for survey simulations, which are actually based on the minimum requirements.       {noformat}altitude_max = 86.5 deg  altitude_min = 20 deg  altitude_maxspeed = 3.5 deg/sec  altitude_accel    = 3.5 deg/sec**2    azimith_max = 270 deg  azimuth_min = -270 deg  azimuth_maxspeed  = 7.0 deg/sec  azimuth_accel     = 7.0 deg/sec**2{noformat}  For the camera cable wrap the (minimum) requirements are:       {noformat}position_limits = +/- 90 degrees (soft limit)  velocity = 3.5 deg/sec  acceleration = 1 deg/sec**2{noformat}  Note that there's a +/- 4 degrees of hard-limit on the CCW, probably not on the simulator though.     "
Answer: 1011.0

User story: "Write a simple authentication controller that accepts and processes requests for authentication.    This will be the foundation on which the LOVE interface for authentication will be built, so it will use the LOVE component name. The long-term plan is for LOVE to show each such request to the operators, who will accept or reject the request. In the meantime (having no telescope operators and no GUI for authentication) the simple authentication controller will simply accept each request.    For now I will put the code into a new package ts_authenticate. We may well move it when INRIA starts implementing the operator interface for approving authentication requests."
Answer: 10813.0