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: "In the EFD, data replication is done in one direction, copying kafka topics and schemas from a source cluster (e.g. base) to a destination cluster (e.g.  LDF) (see the multi Data Center [active-passive setup | https://docs.confluent.io/current/schema-registry/multidc.html])    The Aggregator is a component that runs on the destination cluster (e.g. LDF) and it creates new schemas for the aggregated topics.  In the active-passive setup, these schemas will exist only at the destination cluster, we don't want them replicated back to the source cluster. That means the schema IDs would no longer be globally unique if we use the same Schema Registry to register the aggregated topic schemas, there may be collisions between schema IDs for schemas created at the source and destination clusters.     For the Aggregator, we'll need *a secondary schema registry* to register the aggregated topic schemas.     In this ticket, we'll investigate this possibility further and configure the {{kafka-aggregator}} to read schemas for the source topics from the primary Schema Registry and write schemas to the secondary one.    "
Answer: 5495.0

User story: "We need an n-body propagator for ephemeris and orbit propagation; this will also improve HelioLinC."
Answer: 40308.0

User story: "When we started to allow datasets to be disassembled this resulted in a single dataset_id corresdponding to multiple disassembled files. This breaks the paradigm for getUri which assumes a single file.    On this ticket we propose to replace getUri with getURIs that will return a tuple of the URI of the primary dataset and a dict mapping component name to component URIs.    For normal disassembly the primary dataset would be None. In the future for virtual datasets this may no longer be true and the primary dataset could be defined with URIs to override components also being returned.    Predicted file will still assume no disassembly."
Answer: 13002.0

User story: "Wrapup of features for SAL V7.0"
Answer: 1164.0

User story: "Wrapup of features for SAL 6.0"
Answer: 1166.0

User story: "Wrapup of features for SAL V5.0"
Answer: 1166.0

User story: "Stack club flash crowd hit the pool limit of the TAP service, let's bump it up."
Answer: 1607.0

User story: "{{ap_verify_testdata}} is an {{ap_verify}} dataset that is used to test dataset-related functionality such as repository management and ingestion. It is essentially a port of the {{obs_test}} data to the {{ap_verify}} format, but {{obs_test}} is not intended to have Gen 3 support (see [#dm|https://lsstc.slack.com/archives/C2JPL2DGD/p1589219793199100]).    Modify {{ap_verify_testdata}} to use {{obs_lsst}}'s test data instead. Like the current dataset, the new dataset does not need to support a complete pipeline run, it just needs to conform to the format as expected by {{ap_verify}} proper."
Answer: 36175.0

User story: "Build runitme support archives (DEB/RPM) for the raspberry pi version  of OpenSplice"
Answer: 24316.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: For the <Enumeration> field, non-indexed components should be identified by the content "no" instead of an empty tag. This removes the ambiguity between it is not indexed or it was not noted down properly.
Answer: 31751.0

User story: "M1M3 SS uses boot and shutdown commands for what nowadays shall be done with enterControl and exitControl generic SAL commands. Replace boot and shutdown commands with generic enter/exitControl. Enforce their functionality (if possible) by actually stopping and restarting HW threads on exit/enter."
Answer: 104928.0

User story: "Need to mount /lsstdata/offline/teststand to NTS"
Answer: 274.0

User story: "As a component of the Environment Awareness System EAS ([https://confluence.lsstcorp.org/pages/viewpage.action?pageId=73574873),|https://confluence.lsstcorp.org/pages/viewpage.action?pageId=73574873)] it's necessary to develop a dome environment conditioning system, to control te temperature during daytime. For that purpose, a document will be generated to lead to a contract for the implementation of this system."
Answer: 21385.0

User story: Create the M2 GUI/DDS startup procedure in Jira test manager. This is for the system engineer team to start up the system. The focus is the use of M2 control system (GUI) and SAL. For example, how to check the DDS communication, open the GUI, run the software, commend the system by SAL, etc.. The link of "LSST Verification and Validation" is [here|https://jira.lsstcorp.org/secure/Tests.jspa#/design?projectId=12800].
Answer: 21708.0

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

User story: "Check out the DIMM code from GitHub and read through it."
Answer: 11384.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: As part of bright star wings/extended PSF model (DM-23785), we will extract stamps around bright stars from calexps, apply some preprocessing, then save these (along with some metadata) to disk.    The reason this is needed is the code for DM-23785 will rely on coadding a very large number of small cut-outs around bright stars, from different calexps, together. These require some preprocessing steps, such as a normalization step, before being coadded. Since we cannot possibly store all stamps in memory at once, we cannot do this processing on the fly before coaddition, hence the choice to save them to disk.    Longer term, this choice will also enable us to change the way we build the extended PSF (aka bright star wing) models without having to redo the processing. As an example, we might (and likely will) come to realize we want a different extended PSF model for each CCD, or at least per some subregion of the full focal plane. If our initial run had all stars stacked together to build a single, constant model, we could reuse the processed stars saved at this stage to build the new models.    Regarding normalization of the stamps: while this will be carried out in the code for DM-23785, it is worth mentioning here. Since very bright stars are saturated, and otherwise contain various ghosts around their center, we cannot use usual (say, aperture) measurements of their flux. What we will do is instead integrate their flux in an annulus of constant radii around their center, far out enough that most ghosts are contained within the inner radius and do not impact this "annularFlux" measurement. These values (one per star/stamp) are one of the things stored in the dataset introduced by this ticket. These only make sense in relation to one another if the annulus definitions used are the same; the class therefore contains checks that the same annulus radii (both inner and outer) are used, every time new stamps are added to the collection.       This ticket will add the class itself, and the associated info in obs packages.  
Answer: 115382.0

User story: "I need to redeploy TSS components at NCSA with the new xml 5.1. I think we are ready to deploy them using argo cd so I'll probably coordinate with [~<USER> to get that done. "
Answer: 13437.0

User story: Some of the test messages incoming to the OODS have been badly formatted;  handle this more gracefully.    Also, there's a formatted log message in the oods that's missing the "f" in front.  Fix that too.
Answer: 54671.0

User story: "Have web service owners and other key users test the new web server for a few days before releasing it to the wild."
Answer: 55009.0

User story: "Telegraf currently throws PAM access errors when trying to sudo."
Answer: 4594.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "With CAP-468 completed, the ATAOS now tracks the different focus offsets applied to the lookup tables.     What should be in the header is the user-defined offset from the LUT.    This ticket is to update the FOCUSZ header to point to:    ATAOS_logevent_focusOffsetSummary.userApplied"
Answer: 14651.0

User story: "Tasks done:   * makeSkyMap   * singleFrameDriver   * jointcal   * skyCorrection   * coaddDriver   * multiBandDriver   * forcedPhotCcd   * visitAnalysis   * compareVisitAnalysis   * coaddAnalysis   * colorAnalysis   * compareCoaddAnalysis   * matchVisits   * dispatch_verify_colorAnalysis   * matchedVisitMetrics     * dispatch_verify_matchedVisit     * validateDrp     * writeObjectTable     * transformObjectCatalog     * consolidateObjectTable     * consolidateSourceTable"
Answer: 22211.0

User story: "The client IPs shown in Gafaelfawr logs for the {{/auth}} endpoint currently point to the NGINX ingress pod instead of the actual client IP.    The problem is that the {{/auth}} request flow is route -> internal handler -> auth route. The internal handler passes the correct remote IP to the auth route, but because it adds another proxy step, the auth route itself sees the IP of the NGINX server as the request IP and sets a new {{X-Forwarded-For}} pointing to NGINX.    We need to reconfigure the ingress to not clear {{X-Forwarded-For}} and instead append to it, which in turn means that Gafaelfawr needs to know how far back to look in the {{X-Forwarded-For}} chain to know what the first external IP is (otherwise you end up trusting random {{X-Forwarded-For}} headers sent by a client, which isn't desirable).    That will affect everything, so all services behind that ingress will get the full {{X-Forwaded-For}} header. Hopefully that won't break anything else; anything that needs to trust that header will need to be configured with the deployment IP range so that it knows what the first external IP is."
Answer: 45775.0

User story: "Add pointing offsets based on grating selection. Due to the wedge of the grating small offsets are required to ensure the WCS is correct.    Also need to verify that focus offset units are correct between ATSpectrograph and ATAOS, including in the latiss config file."
Answer: 82978.0

User story: "Now that daf_butler has started to use mypy to validate type annotations, take a quick look at datastores to see if they are some low hanging fruit."
Answer: 11759.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Build the latest MTAOS docker image to contain the update of DM-24422, DM-24423, and DM-24610 to deploy on NCSA. AOS needs the upstream packages of *lsst-distrib* and *lsst-sims*. The available version (tag) can follow [tags|https://eups.lsst.codes/stack/src/tags/]. The T&S team uses the weekly built in the most case. For the *lsst-distrib*, the latest available tag is *w_2020_18*. For the *lsst-sims*, the latest available tag is *sims_w_2020_16*. To install these two packages together, we need to make sure to use the same weekly built tag.    The T&S team releases the available development image ([develop-env|https://hub.docker.com/repository/docker/lsstts/develop-env]) regularly. The latest formal tag is *b68*, which has the *lsst-dev* *w_2020_16* installed already. It is noted that we do not use the *latest* tag usually. In this task, we will begin from this docker image to build the image of MTAOS (the latest one now is using *w_2020_15*). The followings are the steps:   # Update the [aos_sal|https://github.com/lsst-ts/ts_Dockerfiles/tree/develop/aos_sal] image to use the *lsstts/develop-env:b68* and publish as [aos_sal|https://hub.docker.com/repository/docker/lsstts/aos_sal] on Docker hub. This image installs the *lsst-sims* and other needed packages for AOS to use.   # Update the [aos_aoclc|https://github.com/lsst-ts/ts_Dockerfiles/tree/develop/aos_aoclc] image to use the latest AOS packages and publish as [aos_aoclc|https://hub.docker.com/repository/docker/lsstts/aos_aoclc] on Docker hub.   # Update the [mtaos_sim|https://github.com/lsst-ts/ts_Dockerfiles/tree/develop/mtaos_sim] image to use the latest ts_MTAOS package and publish as [mtaos_sim|https://hub.docker.com/r/lsstts/mtaos_sim] on Docker hub.   # Deliver to Tiago to deploy the image on NCSA for the test."
Answer: 5548.0

User story: "make a {{convert}} command that implements the {{the obs_base convert_gen2_to_gen3}} command.    existing tests are in {{lsst.obs.base.gen2to3.convertTests}}, and {{ci_hsc_gen2}} has a test script {{tests/test_gen2to3.py}}"
Answer: 28764.0

User story: "As part of the plan for supporting schema migrations we would like to investigate the possibility of using Alembic. [~<USER> has done a preliminary investigation and reports a positive experience. Now we need to see what is involved in modifying daf_butler to properly support this."
Answer: 50952.0

User story: "The https://confluence.lsstcorp.org/pages/viewpage.action?pageId=120786640&src=contextnavpagetreemode  proposes some changes which   will require small mods to the SAL parser"
Answer: 36071.0

User story: "Build deployable RPM and DEB assets to deploy OpenSplice to the raspberry pi"
Answer: 4371.0

User story: "For the latest LSST stack the CLOCK_TAI symbol is not defined due touse of an older glibc  version. Implement a temporary worlaround to provide the #define in this situation."
Answer: 28688.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: "This task will review the control algorithm of rotator in Simulink model and try to translate to the math equations. This is try to understand the behavior of stop command in the tracking. In the previous test on summit, we learned that the path generator has the weird behavior if stop command was issued in the tracking. We suspect the stop command results in the wrong behavior of path generator."
Answer: 25595.0

User story: "Put the hexapod PXI into the standby state after clearing the error. This task will need to update the Simulink model for the state machine transition. After this, I will need to generate the C/C++ code and put back to ts_hexapod_controller and test the new built. This task will need to learn and test and hexapod simulink model. This task will also try to understand the logic of look-up table (LUT) in code."
Answer: 10344.0

User story: "As part of gen2 deprecation we are required to store run details into the butler repository. These are expected to be per-run and so have blank dataIds.    * The config used by the pipeline.  * The pipeline definition.  * The software versions.    "
Answer: 8772.0

User story: Strings with periods apparently aren't allowed as the names of vertices or edges in graphviz unless they're quoted.  At least the pipeline-level dot files (and I assume the QG-level ones) run afoul of this when a dataset type name refers to a component, as in "{{calexp.wcs}}".
Answer: 4224.0

User story: "- -Move documentation technote onto tssw developer guide-   - -Get the current doc draft that was created at the current csc level and make a /doc/ folder so people can begin copying.-   - -Create optional title for reference document-   - -Essential the action items needed to do before next documentation meeting.-"
Answer: 44575.0

User story: "Tekniker has completed portiong of the TMA Robot framwork. This task is to have this software installed onto the Docker/virtual env environment of the TMA."
Answer: 177086.0

User story: "Update index.rst with a description of DCS."
Answer: 27279.0

User story: "The EIE lower level components express angles in radians while SAL uses degrees. Make sure that the mock controller for the lower level components use radians as well."
Answer: 7100.0

User story: In DM-24288 the component name was added to the internal posix datastore record. Unfortunately it was length 16 and sqlite did not complain -- this breaks databases that do check the length of strings. In particular "TransmissionCurve" exceeds the limit. Change the limit to 32 to fix this.    Additionally we might want to add constraints back. Constraints were added previously in DM-18438 but subsequently removed when DatabaseDict was replaced with OpaqueData.
Answer: 1349.0

User story: "Sky sources will, by default, by output on single frame processed imaging. This ticket updates the associated source table to include this flag, allowing for subsequent filtering and facilitating trivial exclusion of these sources (if not required). "
Answer: 236.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: "This ticket adds:   # configuration that tells mypy to run on just lsst.daf.butler.registry.interfaces   # fixes for the type annotations in just that package   # a non-default scons target to run mypy   # travis configuration to run mypy    As mypy isn't part of the stack's usual conda environment, users will have to take care of installing it (I used {{conda install --no-update-deps mypy}}) before trying {{scons mypy}}.    I figure we'll expand the configuration to other daf.butler subpackages as we get them to run clean under mypy.    Work for this ticket is almost entirely done in prep for a Science Pipelines team meeting on type annotations; all that remains is review."
Answer: 1298.0

User story: "One of the output formats required for the interoperability of the EFD and the LSP is Parquet. Parquet files have proven to be an efficient columnar data source for large datasets and also work with Dask distributed processing.    There are some other requirements for the Parquet Sink connector.   * We want to use Kafka Connect as for the other EFD connectors   * It must be open-source, if it is provided by Confluent it must be under the [Confluent Community Licence| https://www.confluent.io/confluent-community-license] since we are not paying for the Confluent Enterprise License.   * It must support time-based data partitioning, we want to split the EFD data by observing night.   * Must be able to read from Avro   * Should write to POSIX file system or to an object-store.     "
Answer: 5558.0

User story: "Write a security risk assessment of the Rubin Science Platform in the same style as https://sqr-037.lsst.io/"
Answer: 50812.0

User story: "Confirm in CI that the efd helper classes work with the new version of InfluxDB (1.8.0)."
Answer: 22046.0

User story: "Create a function that takes the command and its parameters and returns a yaml representation of it so all do_XXX functions in DCS can be simplified."
Answer: 18688.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: "After negotiating pricing with Confluent the conclusion was that we cannot afford their enterprise license. The license is all-inclusive and it costs 10k per node/yr.      We are currently managing a minimum of 3 nodes * 6 instances of the EFD which means 180k/yr.  Also, they consider each component of the Confluent platform running on a different node, so we cannot deploy the Schema Registry and Zookeeper in the same node to reduce costs, for example.    The decision was to replace the Replicator connector with an opensource alternative, [Mirus| https://github.com/salesforce/mirus] seems like a good option for kafka replication, it also uses Kafka connect and is superior to Mirror Maker, see [this blog post| https://engineering.salesforce.com/open-sourcing-mirus-3ec2c8a38537].    The other enterprise product we were using is the Confluent Control center, its been very useful to monitor and diagnose the Kafka clusters.  An interesting alternative for the control center is the [Lenses dashboards| https://docs.lenses.io/1.1/using-lenses/user-guide/dashboard.html]    We plan on investigating these alternatives in the next epic for the EFD.    "
Answer: 7.0

User story: After DM-18529, tract ID is added as metadata to the verification jobs and that allows us to upload metrics for multiple tracts to SQuaSH and use the {{tract}} tag in InfluxDB to create dashboards filtering the results based on the track ID.    However, currently a query like:    {noformat}  SELECT "AM1" FROM "squash-demo"."autogen"."validate_drp" WHERE  "dataset"='HSC RC2' AND "filter"='HSC-R' AND "tract"='9813'  {noformat}    returns only the last data point, because the previous data points don't have the tract information. That was expected and we need to add the InfluxDB tag {{tract=9813}} to all previous data points to fix this.
Answer: 3384.0

User story: "Upgrade InfluxDB to version 1.8.0, Chronograf to version 1.8.4 and Kapacitor to 1.5.4 in the operational EFD environments (base, ncsa-int, ncsa-teststand and sandbox).    This upgrade enables Flux 0.65 (the first production-ready version of Flux) and adds a forward-compatible API with InfluxDB 2.0 among other features and improvements, check:    [https://www.influxdata.com/blog/release-announcement-influxdb-with-long-awaited-features/]    Another reason for this upgrade is that the new InfluxDB clients for 2.0 are also compatible with 1.8.0:    [https://docs.influxdata.com/influxdb/v1.8/tools/api_client_libraries/] "
Answer: 13.0

User story: "To support writing CSCs with salobj to run in Raspberry pi we need conda packages for the dds python bindings, salobj and ts_idl. This task is to provide those packages building them on the RPi I have at home.     I'll need to setup the RPi before being able to build the packages so this may take a bit longer than expected. "
Answer: 28103.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://ci.lsst.codes/blue/organizations/jenkins/release%2Fofficial-release/detail/official-release/42/pipeline]         The problem seems to be related to stored ssh keys and known_hosts:        {noformat}+ /j/snowflake/release/lsstsw/bin/rebuild -p -r b.19.0.x -r 19.0.0 -r v19.0.0 lsst_distrib lsst_ci   Host key verification failed.  fatal: Could not read from remote repository.       Please make sure you have the correct access rights    and the repository exists.{noformat}   "
Answer: 61086.0

User story: "The DCS now accepts any reply from the lower level components without checking for errors. This ticket is for adding that error handling."
Answer: 17452.0

User story: "Document the new Ingest system at:  * [User guide for the Qserv Ingest system (API version 1)|https://confluence.lsstcorp.org/pages/viewpage.action?pageId=133333850]    The documentation should include (as minimum):  * an introduction into the design of the system  * an overview of the typical usage scenarios (users' catalog ingest workflows)  * detailed explanation of the interfaces and tools available (needed) for building the workflows  * advanced topics aiming at high-performance workflows, improving robustness of ingests, resource utilization, etc."
Answer: 53280.0

User story: "When the {{obs_lsstSim}} repository was removed from the distributed stack, it broke the repository being used by the demo Firefly notebook.  This is probably a good thing since that repository was several years old and should probably be deprecated.    This meant moving to an HSC rerun in {{/datasets}} instead.  We will need to move again when we go to gen3, but this seems like a reasonable thing for the time being."
Answer: 64.0

User story: "There no config option for this, and there really should be. Should be a very quick fix.    Just allow the \{\{afwMath.makeStatistics}} to have a configurable number of sigma."
Answer: 10128.0

User story: "Finish moving all session dbs to postgres."
Answer: 4594.0

User story: "If people go through CILogon but don't have the required groups, they get a 403 error from Gafaelfawr. Some browsers cache that error. Set the no-cache headers to try to prevent this so that retrying authentication once the user has been added to the appropriate group won't return a cached 403."
Answer: 3260.0

User story: "The Jenkinsfile for the CI job of ts_athexapod is using a fairly outdated schema.           Some notes for updates:   * instead of using {{lsstts/develop-env:sal_v4.0.0_salobj_v5.0.0_b27}} as a base image it should use {{lsstts/salobj:develop}}.   * create separate steps to checkout each individual dependency. For each individual dependency run {{/home/saluser/.checkout_repo.sh}} to update the dependency branch (or not).    * Build idl files locally to make sure it captures any xml changes.          Look at [https://github.com/lsst-ts/ts_Dome/blob/develop/Jenkinsfile] for an example.      "
Answer: 48452.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 new salobj container, which is used for some CSCs to run CI job, now ships with the configuration packs. In previous versions the Jenkins job clone/checkout/declare the package. This now creates a breakage in the test because the packages are already available.    Patrick and myself fixed most of the faulting components. This ticket is to fix [ts_atmonochromator.|https://github.com/lsst-ts/ts_atmonochromator]    This is the line that needs fixing. https://github.com/lsst-ts/ts_atmonochromator/blob/c3b0f2c4a0cd7c8383eab74b0d3171d700e1d567/Jenkinsfile#L77    It should be a trivial change, replacing the aforementioned line with something like this:                 {code:java}  docker exec -u saluser \${container_name} sh -c \"source ~/.setup.sh && cd /home/saluser/repos/ts_config_attcs && /home/saluser/.checkout_repo.sh \${work_branches}\"  {code}        
Answer: 91780.0

User story: DM-23835 upgraded us to Doxygen 1.18.8. That has deprecated a number of configuration parameters, so we now get messages like:    {code}  buildConfig(["doc/doxygen.conf"], ["doc/doxygen.conf.in"])  doxygen /home/mfl/lsst/pipe_drivers/doc/doxygen.conf  warning: Tag 'TCL_SUBST' at line 238 of file 'base.inc' has become obsolete.           To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u"  warning: Tag 'PERL_PATH' at line 2108 of file 'base.inc' has become obsolete.           To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u"  warning: Tag 'MSCGEN_PATH' at line 2130 of file 'base.inc' has become obsolete.           To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u"  {code}    Please make them go away.
Answer: 6.0

User story: "Currently the EFD helper classes prefer to find credentials in a file in a known location.  We will keep that mechanism, but will also provide a service that can serve low risk (read only) credentials.  This will allow us to transparently update the credentials without the utilities that depend on them update a file on disk at a know location.  The service will run on roundtable and will serve the credentials from a k8s secret provided by Vault Secrets Operator."
Answer: 38777.0

User story: "lsst_sims needs to be updated for the conda-forge third parties.    This involves updating the table files and possible fixing any build/linking issues."
Answer: 23010.0

User story: "Currently, the {{Job}} object writes using `json.dump` with no keyword arguments.  This means there are no carriage returns and that the file is hard to read without reformatting.  Adding a little formatting makes it much more readable at relatively small cost to overall file size."
Answer: 241.0

User story: "In ts_xml 5.1 there was a change in ATCamera takeImages command. Update latiss command to support these changes.         groupId, imageType, and testType"
Answer: 10291.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: "DM-24664 should have provided everything we need in terms of a starting data repository, but since we last ran on RC2 we've switched to YAML pipeline definitions, and neither the generic DRP one in pipe_tasks nor the custom one in ci_hsc_gen3 seem quite right.  Ideally we'll be able either make the pipe_tasks one viable with just instrument overrides or define a generic HSC+DRP pipeline in RC2, but if necessary we can put one in the Gen3+RC2 script repo.  After that, time and profile QG generation on RC2 and create tickets to optimize as needed."
Answer: 34553.0

User story: "Mock up the overall task, then make variants for the various assemble coadd flavours. Establish what the minimum set of test data is to make a meaningful test case. This is the base test framework, upon which specific tests can be developed in separate tickets. Use this framework to provide tests for artefact rejection (to detect the problem seen in DM-22825)."
Answer: 100878.0

User story: "In early May 2020, we saw significant changes to our ap_verify runs tracked in Chronograf — the total number of DIAObjects per CCD, and the ratio of DIASources to direct image sources both jumped significantly. This is expected to be due to the decorrelation afterburner updates which happened around this time (DM-24371). Dig in to the data and see if you can confirm that."
Answer: 5501.0

User story: "We should run `flake8` using the config described in the dev guide."
Answer: 14067.0

User story: "Currently we have to remember to manually upgrade most GKE clusters. Put them into release channels so that GKE will do this automatically and we can stop thinking about it."
Answer: 227.0

User story: "See [https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/]"
Answer: 175610.0

User story: "Due to the multus interface usage, we need a way to override the OSPL configuration in all of the CSC containers (including Kafka producers). This needs to be done in a way that doesnt' create a maintenance headache. Create new charts to handle this and reduce the number of namespaces to handle."
Answer: 5752.0

User story: As pointed out in https://github.com/lsst-dm/alert-stream-simulator/pull/3#issuecomment-623492975, alert-stream-simulator's license headers call the project "rubin-alert-stream." This should be corrected.
Answer: 417.0

User story: "In DM-20573 we removed obs_lsstSim from lsst_obs such that lsst_distrib no longer depends on obs_lsstSim. We missed lsst_ci though so Jenkins is still building the package.    Remove the obs package from lsst_ci table file and replace with lsst_obs (Which should be a no-op since we already depend on lsst_distrib)."
Answer: 2856.0

User story: "C/C++ controller lacks interface to HealthAndStatus FPGA data. This needs to be implemented, so controller and other apps can receive e.g. transmitted and received bytes on modbus ports. The Tx/RX statistics is vital for understanding where is problem in connection to ILC/Simulator. Similar statictic shall be collected and displayed simulator."
Answer: 6478.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: "Canceled due to serious slurm problem and moved to w_2020_19.    Related ticket: DM-24746"
Answer: 9970.0

User story: "The Rubin Observatory LSST-VTS Blending Task Force has attempted to run scarlet on the globular cluster NGC 6569 to test it's effectiveness on crowded fields. The attached image shows that things did not go so well at all, but possibly because of very poor object detection and/or a poorly modeled PSF. This ticket is to investigate the source of the error and at least ensure that scarlet works as well on this field as can be expected on a first pass without detections on the residuals, which is left for a future scarlet ticket."
Answer: 1863.0

User story: "With the new conda-forge environment we updated to matplotlib 3.2. Unfortunately the matplotlib bug described in DM-22818 is still present in that version of matplotlib which means that fgcmcal will not build on macOS catalina.    I can fix the environment myself by doing:  {code}  % conda uninstall matplotlib matplotlib-base  % conda install matplotlib=3.0 scikit-image  {code}    but that results in removal of healpy that we also need for fgcmcal. Installing healpy from conda-forge unfortunately brings matplotlib-base 3.2 back into the environment (which breaks fgcmcal again).    This should be a blocker for the 20.0 release."
Answer: 13067.0

User story: "Based on the contents and discussion of RFC-620, and DMTN-087, help to prepare the LCR and also with the LCR adoption process."
Answer: 82630.0

User story: "LCR-620 requires changes to a number of documents managed at the system level. This issues is to track the submission and approval of an LCR to make those changes."
Answer: 201418.0

User story: "Develop M1M3 command line tool, so testing of communication to a single actuators can be reasonably commanded. This is just engineering tool, with purpose similar to unit tests (which are missing in M1M3 support as well)."
Answer: 14498.0

User story: "Many of the {{afwGeom}} aliases (e.g. [Sphere]Point, Extent, angular units) are now deprecated in favor of those defined in {{geom}}.  Please replace all instances in the \{\{pipe_analysis}} scripts."
Answer: 2859.0

User story: "Assist Jenkins CI testers in speeding up  / parallelizing / streamlining the test runs"
Answer: 4577.0

User story: "This will update the deployment scripts for the OODS to release 2.2.0 of ctrl_oods, and relabel containers as lsstts"
Answer: 14640.0

User story: "See https://lsstc.slack.com/archives/C2JPT1KB7/p1588310584058000"
Answer: 115.0

User story: "Update ts_hexrotcomm to be forward-compatible with the pending ts_xml 5.2 release and to make it compatible with explicitly listing the generic topics used.    The issue is that BaseCsc implements several generic commands that it does not actually support (by raising an exception if they are called). The fix is to remove that code. Then those commands can be removed from the XML without affecting ts_hexrotcomm, ts_hexapod or ts_rotator."
Answer: 25.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 schemas for diaSources/Objects/ForcedSources in Avro alerts contain some columns that are a combination of multiple values/types. For instance, the various covariances of various quantities. These could be flattened and given names to match those in the Apdb schemas for ease of translation between the alerts and data loaded from the Apdb."
Answer: 61598.0

User story: "The producer list in the default values YAML file don't seem to be removable when using null from ArgoCD. Just remove them from the chart as we have defaults set up in the ArgoCD config."
Answer: 84.0

User story: "Update the mock controller code in ts_hexrotcomm to transition from FAULT to STANDBY instead of OFFLINE, in order to match improvements that [~<USER> has made to the rotator low level controller, and will make to the hexapod."
Answer: 74.0

User story: "If the OODS catches an ingest failure from the Butler, and the original file is not located where the OODS expects it to be, an exception occurs which causes the OODS to fail to send out a failed ingest status message.  The ingest message needs to go out in any case."
Answer: 1033.0

User story: "Scylla is a drop-in replacement for Cassandra re-implemented in C++. We want to try it hoping that its performance will be better and it does not have GC issues of Java.    ScyllaDB page: https://www.scylladb.com/open-source/"
Answer: 35892.0

User story: "Calculation of flux with apertures that are not circular top-hats are not calculated with sinc interpolation. For Gaussian Aperture and Photometry (GAaP), we need to compute accurate fluxes with (elliptical) Gaussian apertures"
Answer: 37244.0

User story: Current use of saz::sudo doesn't make necessary changes to access.conf.    Make a separate profile that wraps saz::sudo and also makes the accss.conf changes.    This profile will get "include"d by authnz
Answer: 17365.0

User story: "This ticket is to update the ATAOS to include automatic focus corrections based on what filter/dispersers are put in the beam by LATISS         This is to fulfil CAP-468. "
Answer: 14546.0

User story: "We need another instance of the EFD at the base to record data from ComCam while the Summit is shutdown.     An EFD at the base was in the plans anyway and will serve as an intermediate step in replicating data from the Summit to LDF, and as a natural backup of the Summit EFD.     SQR-034 needs to be updated to reflect retention policies for the Base EFD, replication configuration, etc."
Answer: 2127.0

User story: "Install Raspbian Buster on a raspberry pi 3 and then install salobj in it."
Answer: 6185.0

User story: "Include the remote IP address and the address being authenticated in the Gafaelfawr logs. Document the logging in the manual, and enable Safir production logging. Add structure to the logging where possible."
Answer: 10935.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: "Prefixing alert messages with a magic byte and schema ID will let us interoperate with the Confluent Schema Registry in the future, if we should choose to use it. I've heard good things about the CSR from teams using Kafka in similar ways; it would help manage schema updates much more easily.    "
Answer: 21278.0

User story: "Currently ts_salobj's CI buyilds the salpy unit tests because it uses the ts_idl conda package which by design does not provide the salpy libraries. I need to determine a way to handle skipping and un-skipping of the tests. Which means that I also need to determine a way to build the correct salpy libraries given a version of SAL and the XML."
Answer: 19961.0

User story: "We want to have an automated process that starts with an interface change (XML update) and runs all the jobs necessary to create libraries and run the application builds.  These application builds will run through the unit tests and ensure the interface change hasn't broken anything.  Currently, we have these jobs working individually, but we want them to run in series and automatically.  So the first job, when successfully complete, will trigger the next and so on.  Having one giant pipeline job seems unwieldy, so we need a way for a Jenkins pipeline job to trigger another pipeline or freestyle job, passing necessary parameters."
Answer: 33283.0

User story: "The [SalObj Conda Jenkins job|https://tssw-ci.lsst.org/job/SalObj%20Conda%20package/] will create an item when new tags appear, but no jobs runs automatically.  The job can obviously be started manually, but it would be nice to have it trigger automatically.  Determine a way to do this."
Answer: 11369.0

User story: "The ATSpectrograph Conda package job should use the DeployEnv docker image and the necessary RPMs/IDLs, all from Nexus3.  It should create a conda package and then run the unit tests.  Must-have unit tests include instantiating the topics and running through the state-machine workflow.  The goal here is to catch unsupported interface changes before a release occurs."
Answer: 53188.0

User story: "The ATDome Conda package job should use the DeployEnv docker image and the necessary RPMs/IDLs, all from Nexus3.  It should create a conda package and then run the unit tests.  Must-have unit tests include instantiating the topics and running through the state-machine workflow.  The goal here is to catch unsupported interface changes before a release occurs."
Answer: 113999.0

User story: "The ATHexapod Conda package job should use the DeployEnv docker image and the necessary RPMs/IDLs, all from Nexus3.  It should create a conda package and then run the unit tests.  Must-have unit tests include instantiating the topics and running through the state-machine workflow.  The goal here is to catch unsupported interface changes before a release occurs."
Answer: 57610.0

User story: "We want these plots to be per-tract instead of 3 points per time stamp.  I'll try to do this, but might need help from the squash pros. "
Answer: 67585.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: "Add postgres to our charts for int, and move the user database over."
Answer: 7285.0

User story: "Figure out if the new Python MTMount CSC could keep up with telemetry from the low level controller: read the data, parse it and output it as SAL while tracking.    Test at the current rate of 20Hz tracking updates and 20Hz telemetry output per topic.  If that works, try speeding things up the telemetry and tracking rates until the system fails, to get a sense of how close to the edge we will be.."
Answer: 11571.0

User story: "There are hard-coded strings in the forwarder code base that need to be moved into the config file.          This work is done by Sam Cappon."
Answer: 48343.0

User story: "I'm almost certain the Gen3 RC2 bootstrap was broken by the changes to collection handling on DM-21849.  Fixes should be easy, but testing them will be slow."
Answer: 3690.0

User story: "Set up the technical foundations of the design system for [www.lsst.io|http://www.lsst.io/] and implement it via styled components. The design system needs to         * Detect prefers-dark-mode with JavaScript and listener for changes: [https://medium.com/@jonas_duri/enable-dark-mode-with-css-variables-and-javascript-today-66cedd3d7845]   * Big article about dark mode: [https://web.dev/prefers-color-scheme/]   * Your dark mode toggle is broken: [https://kilianvalkhof.com/2020/design/your-dark-mode-toggle-is-broken/?utm_campaign=CSS%2BLayout%2BNews&utm_medium=email&utm_source=CSS_Layout_News_248]   * Creating a dark mode with styled components: [https://bluegg.co.uk/blog/creating-a-dark-mode-with-styled-components]   * Implementing dark Mode in React Apps using styled-components: [https://www.smashingmagazine.com/2020/04/dark-mode-react-apps-styled-components/]   * Design System Utils (use with theming?) [https://github.com/mrmartineau/design-system-utils]   * Styled Components: theming: [https://styled-components.com/docs/advanced#theming]   * What are design tokens? [https://css-tricks.com/what-are-design-tokens/]   * Design tokens 101: [https://kilianvalkhof.com/2020/design/design-tokens-101/]"
Answer: 22018.0

User story: "It looks like we can force the CILogon IdP to be NCSA via the selected_idp parameter to the authorize URL per https://www.cilogon.org/oidc. This can be done via the login_params configuration parameter, which we should plumb through from values.yaml instead of hard-coding."
Answer: 24285.0

User story: "When tagging the v19.0.1.rc1 the job    [https://ci.lsst.codes/blue/organizations/jenkins/release%2Fofficial-release/detail/official-release/39/pipeline]    failed on dax_ppdb     "
Answer: 2392.0

User story: "Before the ATAOS can be upgraded to include focus corrections for filters/gratings/wavelengths, it will need to be able to get that information from the atspectrograph CSC.    This ticket changes the configuration schema for the spectrograph to add these values. During the XML updates DM-22614 will also be addressed"
Answer: 18683.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 parquet files at  {{/datasets/hsc/repo/rerun/RC/w_2020_14/\*/deepCoadd-results/merged/\*/\*parq}}   as inputs, go through the workflow and ingest into Qserv."
Answer: 73719.0

User story: "Per LSST dev guide, everything in sight should get a GPL header. Stick that header everywhere and write a test to make sure we don't forget that in the future."
Answer: 4352.0

User story: "Make a script which is pip-installable which can send data to the alert stream simulator broker. The script should just take a file and write it into the broker."
Answer: 4275.0

User story: "Continue update of software interface documentation, to make consistent with the new partition of development of control software by Rubin Observatory and EIE contractor, as we continue to settle on details."
Answer: 18439.0

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

User story: "Add an integration test, triggered with Github Actions, which tests that the alert stream simulator is installable and works with the basic tools we are providing."
Answer: 23002.0

User story: "Write enough docs that a software engineer could install, use, and make sense of the alert stream in a box."
Answer: 64991.0

User story: "Provide a consumer application which simply counts the number of alerts it has received and prints the count to stdout every second. This is intended to be scaffolding code for users to work with."
Answer: 64991.0

User story: "Package up the alert stream simulator to make it straightforward to install on a Linux host. Some code duplication with (for example) sample-avro-alert is acceptable."
Answer: 23006.0

User story: As laid out in DMTN-149, implement a looping infinite-mode pacer for injecting alerts from disk into a Kafka broker which attempts to simulate a "realtistic rate." Make it configurable as described in DMTN-149, too.
Answer: 69282.0

User story: "As laid out in [DMTN-149|https://dmtn-149.lsst.io/#injector-and-data-rates], implement a single-pass pacer for injecting alerts from disk into a Kafka broker using the timestamps in the files themselves."
Answer: 20507.0

User story: "Update Opensplice 6.9 RPM to include master priority change to ospl.xml"
Answer: 14206.0

User story: New "raft" and "sensor" elements are in the process of being added to ts_xml for the Archivers and the OODS messages.   This ticket is for modifying the code in those so that information will be transmitted.
Answer: 4140.0

User story: "CscCommander presently waits for each command to finish before allowing another command. That is unnecessarily restrictive and really annoying if a task hangs. Modify the commander to run commands asynchronously."
Answer: 10671.0

User story: "Someone with the appropriate privileges should delete the entire contents of {{/datasets/comCam}} and {{/datasets/auxTel}} now that RFC-691 has passed.    "
Answer: 4511.0