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: "We're seeing a major regression in all metrics on the chronograph dashboard for the w_2020_19:  https://chronograf-demo.lsst.codes/sources/2/dashboards/58?refresh=10s&tempVars%5BFilter%5D=HSC-R&tempVars%5BTract%5D=9813&lower=2019-04-01T18%3A47%3A00.000Z&upper=2020-05-30T18%3A47%3A00.000Z    AM1, AM2 are halfway back up to pre-jointcal levels, and no longer meeting requirements.  PA1, TE1 also took a hit.     My hypothesis was that this is because of the sky sources added to processCcd:   Confirming by rerunning $COSMOS_R visits with doSkySource=False on:  {{/datasets/hsc/repo/rerun/private/<USER>RC2/w_2020_19_noSkySources}}    Fix should be explicitly filtering sky_sources in matchedVisitMetrics.     "
Answer: 8490.0

User story: "First batch of code in the re-implementation of the zogy algorithm. Main features:   * Using one PSF image for each exposure, but separate calculable values that will be re-used for the grid calculation.   * Calculation of D, F_D, Varplane(D)   * Calculation of S, Varplane(S)   * Unit test to verify DFT convention."
Answer: 97754.0

User story: Recent testing on DM-17597 has shown some small inconsistencies in the {{fgcmcal}} solutions on different platforms, particularly in the "tract" mode.  Further investigation has revealed that this is because many internal calculations are performed with 32-bit floats rather than 64-bit floats which yields floating point errors that accumulate on different platforms.    This ticket will update internal calculations in {{fgcmcal}} to use 64-bit floats where it is important, and will investigate the impact of the memory footprint.
Answer: 12612.0

User story: In some use cases we would want to make a quantum graph, store it, and run it later.  My understanding is this is already in the pipetask design; {{pipetask qgraph -q qgraph.pickle ...}} stores the graph and then {{pipetask run --qgraph qgraph.pickle ....}} executes it. It used to work last year.  But now I couldn't seem to get it right, and documentations about this seem lacking, hence this ticket.     In principle we should be able to test this with ci_hsc_gen3, by breaking  https://github.com/lsst/ci_hsc_gen3/blob/master/bin/pipeline.sh into two steps.      I guess it might look something like this but with some corrections:   {noformat}  pipetask qgraph -q ci_hsc.pickle -d "patch = 69" -b "$2"/butler.yaml \  -i calib/hsc,raw/hsc,masks/hsc,ref_cats,skymaps,shared/ci_hsc -o "$COLLECTION" \  -p "$CI_HSC_GEN3_DIR"/pipelines/CiHsc.yaml     pipetask run --qgraph ci_hsc.pickle -j "$1" -b "$2"/butler.yaml \  -i calib/hsc,raw/hsc,masks/hsc,ref_cats,skymaps,shared/ci_hsc -o "$COLLECTION" \  --register-dataset-types  {noformat}    .   It's not impossible that some code needs fixing. Or/and we might want to rethink what's better (it's fine to change interface too I think)  
Answer: 4522.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 trying to validate some changes (on DM-24858) in {{obs_lsst}} involving all detector "flavors" associated with that obs-package and requiring adaptations to tests, it was suggested that I try running {{ci_lsst}} (currently on lsst-dm github). It ran without failures for all the default cameras except {{latiss}}, which has suffered some bitrot of a sort. While we await the fully fleshed out ci integrations currently being worked on in cpp-land (e.g. DM-23302 & DM-23622), this ticket is to fix the bitrot so that at least some testing of {{obs_lsst}} changes not possible via unittests can be done.    Of note, the {{ci_lsst}} scripts are being tested and adapted here based on the data that currently resides on {{lsst-dev}} at {{/project/shared/data/test_data/testdata_lsst/raws}}.
Answer: 2933.0

User story: "This ticket updates 020 and 017 with examples of the new (proposed) config files.     "
Answer: 1.0

User story: "Make a hotfix patch to implement the recommended changes to SALSubsystems.xml in SAL"
Answer: 8831.0

User story: "Evaluate both HSC New Horizons data and DECam bulge survey data for testing AP processing in crowded fields.    * Figure out the properties of the data (sky coverage, filter coverage, number of visits, etc).  * In consultation with [~<USER>, select subset(s) of the data for further processing.    Make sure the data is available in {{/datasets}} on {{lsst-dev}} (if it's not already there), and has a [README|https://developer.lsst.io/services/datasets.html?highlight=rerun#responsibilities-on-ingest-or-maintenance] file describing its contents."
Answer: 122698.0

User story: "alert-stream-simulator has a bunch of utility code for dealing with alert packets, particularly coming from Kafka brokers. This code overlaps a lot with existing code in {{lsst/alert_packet}}. Merge the two together.  DM-25102 is a prerequisite, since {{lsst/alert_packet}} will need to be specified as a dependency of {{alert-stream-simulator}}."
Answer: 21671.0

User story: "Write a setup.py script which describes lsst/alert_stream, and put it in the root of that repository.  Write a Makefile with directives for building and uploading to PyPI.  Upload an initial release. Use version v0.1.0, handled in the same manner as {{astro_metadata_translator}} in https://github.com/lsst/astro_metadata_translator/blob/master/setup.py."
Answer: 21671.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "While trying to debug something else, I wanted to ingest a single raw file from a large bunch of files in /datasets.   Looking at butler ingest-raws --help, the only way I can see how to do this is to put the single file in its own directory and use the --dir or put the filename in a text file and use the --file option.       I expected to be able to put the filenames on the command line, even use wildcards, like one can with ingestImages.py from Gen2.   Jim said on dm-middleware channel to go ahead and make a ticket for this.    This is not a blocker because there are workarounds, and raw image ingestion by services (like DBB and OODS) will be using the API instead of CLI.          "
Answer: 138734.0

User story: "Now that we have gafaelfawr, we can guarantee that an access token will be present, which means we can simplify a bunch of things by simply submitting the access token to the /auth/analyze endpoint to determine validity and to parse uid/gids."
Answer: 47468.0

User story: "To distribute the load for the InfluxDB Sink connector we have [increased the number of replicas for Kafka Connect|https://github.com/lsst-sqre/argocd-efd/commit/4a93c47cd653ab74f79061de053cb457aeda1f8d] at the ncsa-teststand cluster and deployed Control Center temporarily to diagnose that cluster.    We have also increased the number of tasks for the influxdb-sink connector to 10.    "
Answer: 3438.0

User story: "Similar access for the k8s-nts nodes should be setup as the nodes at npcf. This includes adding    profile::allow_ssh_from_bastion::allow_groups:   - lsst_admin_ncsa   - lsst_int_kubernetes    profile::allow_ssh_from_login::allow_groups:   - lsst_admin_ncsa   - lsst_int_kubernetes    to the hiera data, and the corresponding profiles to the login node role."
Answer: 269.0

User story: "Similar to the exports for oradb nodes, please export /admin/backups/lsst-db via NFS v4 (nosuid) to the following IPs for Postgres nodes"
Answer: 7660.0

User story: "Jenkinsfile introduced in DM-24610 breaks build on branch. Partly expected, the fix (due to unclear nature of env.CHANGE_TARGET) would be to use BRANCH_NAME if CHANGE_TARGET is null"
Answer: 730.0

User story: "In order to fix the problem, build number for    - ld_impl_linux-64==2.34=h53a641e_0    - binutils_impl_linux-64==2.34=h53a641e_0  shall be changes to 2."
Answer: 97.0

User story: "Noticed when deploying bleed.  If postgres isn't ready by the time the hub comes up, the hub will throw an exception but won't quit.  It still runs forever, and never tries to reconnect, so the hub is basically stuck until the pod is deleted.  Suggest on fail to exit the process, not just throw an exception, because I guess there are other threads continuing from the reposcanner that are keeping the process alive"
Answer: 38956.0

User story: Basic monitoring/alerting may suffice. If we go to "production" with Postgres we may want (custom) service-specific checks/alerts.
Answer: 1019.0

User story: "Deploy one or more additional Postgres nodes."
Answer: 48534.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: "Once Postgres is vetted, we will want to open it up to NCSA and/or Chile. More info TBD."
Answer: 40107.0

User story: "[~kayavila] - When we discussed this in the ICI operations/planning meeting on Mon, May 18, you mentioned this should be done. Can you fill in a description please?"
Answer: 58111.0

User story: "Puppet, xCAT, physical work, DNS, etc. to deploy first Postgres node. Includes development of Postgres module (or at least profile) in Puppet."
Answer: 23055.0

User story: "hese rules are required for DDS multicast. Other nodes using this have the same rules in place.    The NTS Kubernetes nodes will need these ports open both on the kubelet NIC, as well as the multus allocated nics that will be present on the nodes when pods are created. The data for building these rules is being taken from the hiera data for ats on pup-npcf."
Answer: 1.0

User story: "...Suspect it is an issue for ALL web pages served from the new server.       When I save the HTML source of those pages from the new server, then open that in my local browser, it looks fine. It appears to be an issue somehow of when the pages are 'served' from the web server.    "
Answer: 1.0

User story: "This was mostly done over the weekend, originally intended to be a side-commit on DM-24613.  Might as well get it out for review on its own branch earlier."
Answer: 2466.0

User story: "Create a puppet profile for sal firewall in LSST-IT puppet."
Answer: 70372.0

User story: "Create profile for SAL software install in LSST-IT puppet"
Answer: 22999.0

User story: "SAL software needs mini-conda for python-3.7 support.    Research if we can re-use (directly or via fork & modify): [https://github.com/bkreider/anaconda] (developed by Anaconda)"
Answer: 2761.0

User story: "Create puppet-sal_dds in LSST-IT puppet.    Note: existing module is too broad so creating a new one. Existing module is currently in use in the NCSA Test Stand so attempting to modify it is complex and risky. Easier and cleaner to create a new module for the new design."
Answer: 23032.0

User story: "The current Dome documentation is pretty thin. Add more useful info, add version info and create a release.    Also, make sure that the flake8 line length is set to 79 characters."
Answer: 51222.0

User story: "Early on in daf_butler development we included a FITS formatter (based on afw) to simplify testing of composites. In order to implement compression (DM-13353) without copying infrastructure from obs_base, we need to move the afw formatter and associated tests into a new location. obs_base seems like the obvious place."
Answer: 4184.0

User story: "It is happening with more frequency now and might be the cause for the alert notifications flapping we are seeing in #dm-squash-alerts"
Answer: 34507.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 a component of the Environment Awareness System EAS ([https://confluence.lsstcorp.org/pages/viewpage.action?pageId=73574873),|https://confluence.lsstcorp.org/pages/viewpage.action?pageId=73574873)] it's necessary to develop a dome environment conditioning system, to control the temperature during daytime. This is a continuation of DM-24835 to compose the technical support documents for the implementation contract."
Answer: 16033.0

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

User story: "Reformat ts_MTAOS Python repository by black."
Answer: 4477.0

User story: "Reformat ts_phosim Python repository by black."
Answer: 4479.0

User story: "Tests for PID code inside M1M3 SS. C++ code to verify PID functionality, look for possible runaways scenarios."
Answer: 12315.0

User story: "Reformat ts_ofc Python repository by black."
Answer: 4481.0

User story: "Reformat ts_wep Python repository by black."
Answer: 4484.0

User story: "In order to prevent regressions due to multiple developers outside of DM on scarlet, we're looking at creating a way to identify a few dozen test datasets that will be run each time a PR is created/updated in scarlet. This will allow us to identify when a change has negatively (or positively!) impacted the performance of scarlet before the changes hit master.    So this ticket includes both identifying the test datasets and setting up a framework to run the tests, most likely in Travis, and possibly using the SQuaRE backend to track the metrics over time."
Answer: 134079.0

User story: "The code in ts_sal v4.1.2 that generates the has code for DDS topics seems to have a flaw. When I switched the Script SAL component to explicitly list the generic topics it uses (ts_xml tickets/DM-22109), the hash code for {{logevent_checkpoints}} changed (compared to ts_xml develop 133d378) even though {{logevent_checkpoints}} is not a generic topic and did not change at all. I see the same issue in ts_sal v4.1.1    This is quite worrisome for using the new ability to list generic topics as it means the new IDL will not be compatible with the old IDL even though the schemas have not changed.    I have attached the two IDL files.  "
Answer: 20232.0

User story: "Enable OPSTN production with sqrbot-jr:   * Edit templates   * Add sqrbot GitHub user to rubin-observatory GitHub organization"
Answer: 2931.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 is probably the last test that I want to do with Cassandra on PDAC cluster and before we move to something more scalable.    The only test with three replicas that was done with Cassandra was made with docker which is totally inadequate. I want to repeat this without docker but with just three nodes as it was done with Scylla.    Need to remove Scylla now, reinstall Cassandra and restore the same config that was used for previous tests. Also I think it's better for Cassandra to split storage into individual disks as before, the issue is that storage on master02 is limited so it needs some care in assigning it."
Answer: 71822.0

User story: "Install Centos 7 on a raspberry pi 4 and then install all sal components: OpenSplice, ts_xml, ts_sal, ts_idl and ts_salobj."
Answer: 4031.0

User story: "Reformat the AOS packages to black with the same coding style. There are four packages: ts_wep, ts_ofc, ts_phosim, and ts_MTAOS. The task is a place holder for DM-25062, DM-25063, DM-25065, and DM-25066 to calculate the story point."
Answer: 18593.0

User story: "Replace the cython by pybind11 in cwfs module of ts_wep to follow the DM convention."
Answer: 15774.0

User story: "This task will review the rotator Simulink model and try to reproduce the error we had on the summit test that the demand rotator position can be -2000 peak. Another error we have is the peak between tracking targets. We will also investigate the stop profile in model. This is the phase 2 of DM-24799."
Answer: 24020.0

User story: "We have a proof of concept for a verification pipeline in the works on DM-25007.  It looks very promising.  Adding AMX and TEX will get it almost to the place where validate_drp is."
Answer: 5765.0

User story: "Invited talk on LSST Year 1 Operations and Alert Generation  at the LSST Solar System Readiness (Virtual) Sprint 3 "
Answer: 37080.0

User story: " LSSTC Board requested an update on DM status at their 4 June board meeting"
Answer: 20352.0

User story: "replace the ci_hsc_gen2 validate script with a butler subcommand"
Answer: 15847.0

User story: "replace installExternalData from ci_hsc_gen2 with a butler subcommand"
Answer: 15845.0

User story: "The following keyword comments need to be fixed to refer to MainTel systems in the ComCam/MainCam headers:     This should reference MTCS  TRACKSYS=                      / Tracking coordinate system from ATMCS       For MainTel, this is from the Camera Hexapod  FOCUSZ  =                   0. / Focus Z position from ATAOS/ATHexapod (mm)"
Answer: 37248.0

User story: "The following keywords are specific to AuxTel and should be removed for ComCam/MainCam   *   INSTPORT   *   ATM3PORT   *   GRATING   *   GRATPOS"
Answer: 37251.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: "replaces ingestExternalData from ci_hsc_gen3 with a butler subcommand; it should be a straightforward wrapper around {{Butler.import_}}    define the command in daf_butler    it should be able to read whatever the butler export generates  and we will consider (later) whether butler export | butler import works (with associated parameters)"
Answer: 12546.0

User story: "replace defineVisits from ci_hsc_gen3 with a butler subcommand."
Answer: 12549.0

User story: change the {{butler create}} option {{--config-file}} to {{--seed-config}}. Keep the existing help text "Path to an existing YAML config file to apply (on top of defaults)."    Change the shared {{--config-file}} option's default help text to be more specific: "Path to a pex config override to be included after the Instrument config overrides are applied."    TODO verify the new config-file help text.
Answer: 16018.0

User story: "While taking images, forwarder uses a notification system from daq. What if images were taken while Archiver is away, forwarder will not know what image it is currently being told to stream and will say this image is not correct. "
Answer: 29847.0

User story: "Work with Tiago to create a workflow where the daily RPM job will trigger the SalObj Conda job, which, in turn, will trigger the DevEnv job.  The artifacts from the DevEnv job can be junked; we only want feedback on the status and stability of the dependencies of the DevEnv."
Answer: 21570.0

User story: "Contribute to a memo on  the scientific impact of delays in the release of pixel-level   full focal-plane data on different science cases for the agencies with PST"
Answer: 401.0

User story: "This ticket exists for the upgrade to python 3.8.    pybind11 issues likely need to be addressed before this upgrade, and a boost upgrade is also desirable."
Answer: 161392.0

User story: "In the current {{Sources.yaml}} which defines the conversion of {{src}} catalogs to {{sourceTable_visit}} parquet tables, the {{base_LocalBackground_instFlux}} is converted to {{sky}}.  However, as pointed out in DM-25019, the {{sky}} value should be the overall background value, and not the residual.  Therefore, {{base_LocalBackground_instFlux}} should be recorded non-transformed, while {{sky}} should have a temporary placeholder that is flagged with a DM-25019 TODO."
Answer: 236.0

User story: "Do a standard reprocessing of HiTS2015 with ap_pipe with the latest weekly. The results will land on lsst-dev in {{/project/<USER>hits2015/rerun/cw_2020_05}}. "
Answer: 29014.0

User story: "add     {{REF=}}     right after after rebuild line 77"
Answer: 8097.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 {color:#e01e5a}@pipeBase.timeMethod{color} decorator is widely used, but when tasks using this are set to DEBUG level, they also get the DEBUG output from the timer, which is chatty and usually not desired, especially when mixed into the desired output due to multiple calls to the timed method in the calling task.    https://github.com/lsst/pipe_base/blob/master/python/lsst/pipe/base/timer.py#L112         KT recommended making a sub logger so that this can be independently configured.    This is low priority but if someone's bored sometime..."
Answer: 1131.0

User story: "Compute summary statistics like {{count}}, {{min}}, {{mean}}, {{stddev}}, {{median}}, and {{max}} for the source fields in a list of incoming messages.    These stats are fixed in the code, for now. I think it won't be difficult to define these operations in the configuration but that is left to the future.    Evaluate if we use the Python statistics module, Numpy, or Pandas for that.        "
Answer: 18928.0

User story: "Need a document for planning znd defining DPO"
Answer: 99288.0

User story: "Create a configurable setting in diaPipe to optionally enable or disable seralizing alert packets."
Answer: 18522.0

User story: "DC2.2i run with w_2020_20 stack.    Tasks ran:   * singleFrameDriver   * makeSkyMap   * coaddDriver   * multiBandDriver"
Answer: 19896.0

User story: "Specify all = [ ... ] in all modules to limit what symbols are public (more or less), especially those that have “from .foo import *” in an __ init __ .py file. Otherwise this will introduce pollution of the namespace with unwanted symbols, which can cause interesting bugs."
Answer: 29947.0

User story: "In putting together a prototype metric pipeline, we re-implemented some of the same things implemented in {{MetricTask}}.  We will just switch over to subclassing that."
Answer: 8869.0

User story: "Currently the efd client looks for a special file, but now we need to query the segwarides service first."
Answer: 17229.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 EUI dockerization is completed along with instructions on how to create the docker container youself. This can be found in a README in ts_Dockerfiles/mtmount.     This task is to create the windows portion of the container, I also already see some faults in how I have organized the installation files and may need to do more cleaning... lamesauce. Anyways, for this task to work I will need to add more files to the shared disk drive. This is because (just like the EUI) there is proporietary software. I am now adopting to using the Shared disk drive to host all required software files. This makes creating your Docker file easy, you just need to copy into your root directory and that's it. The ugly part is that some software needs to be pulled, checked out a certain branch, then saved into the drive. This means I must maintain the software until it can be hosted somewhere other than Teknikers Gitlab that is a barrier to most Rubin Observatory software developers. I do not want to create documentation expecting our members to have access to Teknikers gitlab. Because if they don't they simply won't have access to the files that they need.  "
Answer: 27365.0

User story: "This is to update to conda 4.8 (likely 4.8.3)"
Answer: 88798.0

User story: "I have a [pipeline task|https://github.com/lsst-dmsst/metric-pipeline-tasks/blob/master/tasks/MatchedCatalogs.py] that worked with w_2020_17 with {{ci_hsc_gen3}}.    With w_2020_19, it now returns {{UserWarning: QuantumGraph is empty}} whether I ask for `calexp.photoCalib` or `calexp.wcs`.  If I switch to using a stand alone dataset, `jointcal_photoCalib` the quantum graph looks as I expect and it allows my pipeline to run to completion."
Answer: 4040.0

User story: "Run ci_hsc_gen3 using a weekly stack against PostgreSQL"
Answer: 28401.0

User story: "The commissioning and T&S people would like to use organizations to handle their dashboards.  It makes sense to provide that by making organizations with an admin per organization.  I will also hook up github orgs with each organization so people can self serve membership."
Answer: 40268.0

User story: "When reading fits files, case change log messages should be logged to debug instead of warn."
Answer: 84.0

User story: "To transition our PDF documentation deployments form Travis CI to Github Actions, we need support for the GitHub Actions environment in Lander. Support is already in place with LTD Conveyor."
Answer: 21757.0

User story: "DMTN-112 recommends subsystem and team even for k8s_operator.  This is kind of pointless since it's all under the same read secret.    Therefore, adjust the technote to point out that if you're doing K8s_operator, just encode your secrets under an :application: key.    Also maybe fix up lsstvaultutils docs."
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: "in DM-24923 `IngestTestBase.file` was changed from a member variable to a class property. Some subclasses use their `testdata` package to define the value of `file`. These tests are skipped when the testdata package is not set up, but class properties are loaded import time and this fails when performing e.g. `os.path.join`. These class properties must be property functions with the @property decorator to prevent this error.     "
Answer: 146.0

User story: "Update the HeaderService to define the names of the header templates from the Camera configuration event {{focalPlaneSummaryInfo}}"
Answer: 180248.0

User story: "Add/Replace LFO event with the proper S3 object and URL."
Answer: 151291.0

User story: "in [https://github.com/lsst/daf_butler/blob/master/python/lsst/daf/butler/cli/opt/config_file.py#L27]         the 'help' input argument should be stored as a member var and passed to click.option in __call__"
Answer: 3806.0

User story: "Segwarides needs to be deployed on roundtable serving at least read only credentials for all the known EFD InfluxDBs."
Answer: 19732.0

User story: "Google Cloud Storage (GCS) provides S3-compatible access via Boto.  For authentication, GCS provides the [HMAC keys|https://cloud.google.com/storage/docs/authentication/hmackeys]  which can be the drop-in replacement for AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY.     In this ticket I have a few minor changes to use a GCS bucket as the datastore:    - it needs the GCS endpoint URL   - {{client.upload_file}} doesn't work for files >8MB. In the default bucket setup it would try to use multi-part unload. S3 has a particular brand of multipart upload that GCS doesn't support yet.  A workaround is to switch to {{put_object}}.  - For a non-empty bucket, {{bucket.objects.all().delete()}} works on AWS but not on GCS. I only see it used in {{daf_butler/tests/test_s3utils.py}}.  As the tests use moto it doesn't really matter. But I feel it would be more consistent to use the low-level client in both setUp and tearDown so I rewrote it too. "
Answer: 12949.0

User story: "Need the package otherwise failure occurs."
Answer: 29758.0

User story: "There are too many science platform directories, and we should clean this up to have less boilerplate per environment.  Less boilerplate is more better."
Answer: 14533.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: "Using {{conda env export}} is susceptible to not being resolvable if a package is marked as broken. We should switch to using {{conda list --explicit}} to avoid this issue.     This triggers a few different modifications:  1. newinstall/lsstsw need to be modified to install using conda install. This is a different workflow than the existing workflow.   2. newinstall/lsstsw should probably be backwards compatible with previous methods  3. pip packages should be moved into conda-forge (pytest-subtests, peigen) as conda list --explicit does not seem to spit out packages installed by pip  4. Some additional work with the conda-forge team is necessary to ensure broken packages are NOT removed for the CDN the way the currently are, but are removed from the metadata. This ensure broken packages are still installable    "
Answer: 25817.0

User story: "The currrent and previous conda environments are not solvable after the metadata for the conda-forge repodata.json was modified to remove the re2 package we were using.    We need to regenerate the conda environment to something which is solvable.    A further ticket will address avoiding this issue in the future."
Answer: 317.0

User story: "The new flake8 update has caused some minor whinging in alert-stream-simulator's lint job. We should fix this."
Answer: 2.0

User story: "The current code tries to {{raise}} confluent_kafka.KafkaError values. This is not quite right. The raisable one is a {{confluent_kafka.KafkaException}}. We should wrap errors in the Exception class before raising them."
Answer: 51.0

User story: "One of our security risks is not updating third-party software regularly. Explore dependabot as a way to address one part of that problem, namely updating dependencies of software packages on GitHub."
Answer: 35865.0

User story: "GitHub usernames are case-insensitive but case-preserving. For Nublado purposes, we must have the lowercase form of the username. When accepting authentication from GitHub, coerce the username to lowercase."
Answer: 6032.0

User story: "INRIA Chile would like to change the temporary observing log application to store entries in the postgres at the base cluster.  The name can be LOVELOG and the users are:   * Sebastian Fehlandt <<EMAIL>>   * Jose Galaz <<EMAIL>>   * <USER><<EMAIL>   * Grazia Prato <<EMAIL>>    And I know [~<USER> asked me to add namespace/key for a DB password, but I have no knowledge of this information.  It would probably be best to contact INRIA Chile for those details.    This will probably take some coordination between INRIA Chile & [~<USER> first, to make sure whatever gets set up, works for everyone."
Answer: 28865.0

User story: "See RFC-688 for more information."
Answer: 220686.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 the Kustomize deployment and actually deploy Ook to Roundtable.    When doing this, we should plan to separate the deployment replica set that's responsible for getting events from LTD events or the HTTP handlers from the nodes that are responsible for performing the actual ingest. This will keep the queuing nodes responsive from the nodes that actually perform the ingest."
Answer: 48834.0

User story: "MultiProFit currently only implements priors that are attached to individual parameters, which are inflexible and impractical. This ticket is to implement some more useful priors aplied to arbitrary transformations of one or more parameters, including:  - a conditional size prior (e.g. on PSF magnitude);  - a shape prior;  - a background level prior."
Answer: 104985.0

User story: "Currently, searching with an empty search condition produces a result set of several SQRE tech notes.  I'm not sure exactly how that list is populated, but I would expect it to either provide an empty result set or redirect back to the same page."
Answer: 78874.0

User story: "It is really nice that the search fills in the URL so it can be copied and shared, but using the URL results in a redirect loop.  This can be triggered by either:  1 doing a search and hitting the reload button in the browser  2 clicking on [this link|https://search-demo.lsst.io/search?query=test]"
Answer: 55979.0

User story: "update ts_idl jenkinsfile to include versions of ts_sal, ts_idl, ts_xml, and spend some time learning how things fit together"
Answer: 19907.0

User story: "The develop-env Dockerfiles and Jenkins files need to undergo a bit of maintenance and upgrades. This task will the to perform this tasks. The following is a list of things that need to be done:         1 - Rename packages;   * ts_standardscripts -> ts_scripts   * ts_externalscripts ->  ts_scripts_dev    2 - Explicitly add parameters to Jenkinsfile.    3 - Make sure new packages are properly versioned. Some configurations are not being passed from Jenkinsfile to Dockerfile.    4 - Verify if build works with newer stack images, try to make them work if no.     5 - misc.          "
Answer: 35587.0

User story: "Update MOTD puppet class to match what look and functionality that is currently used by dev nodes. New features:   * more condensed output   * custom messages via hiera   * improvements to PM notices"
Answer: 100.0

User story: "Add new profile::gpfs_quota_reporting (or similar) to NPCF & NCSA puppet to be used by login (and other future interactive roles)."
Answer: 59082.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: "When inserting fake sources using {{insertFakes}}, it is necessary to subsequently run {{multiBandDriver}} with {{doDetection=True}}. Currently, the detection options for {{detectCoaddSources}} are not propagated through to {{multiBandDriver}}, resulting in different configuration setups relative to a standard image processing run. Specifically, the {{detectCoaddSources.detection}} config options {{reEstimateBackground}}, {{background.binSize}} and {{tempWideBackground.binSize}} are not set. This ticket updates obs_subaru to successfully propagate these configuration parameters."
Answer: 8966.0

User story: "Attempts to submit jobs from one of the HTCondor submit nodes (tested on {{lsst-condordac-sub01}}, {{lsst-condortest-sub0[12]}} end with error.    (_can_ submit a job from {{lsst-login}} node though.)"
Answer: 1.0

User story: "Take a bunch of the data from ap_verify_hits2015 and compile it into a single .avro data file which covers multiple CCD visits. Publish it through lsst-dev web directory, and add a Make directive for downloading it."
Answer: 18715.0

User story: An early attempt to do some of DM-24938 on DM-24734 ran afoul of messiness involving regular dictionaries with dimension element names vs. NamedKeyDict objects holding real DimensionElement instances.  This is exactly the sort of stuff mypy is designed to fix, but the type annotations for NamedKeyDict and NamedValueSet are tricky and in some cases incorrect, and need to be fixed first.    We're also regularly using these containers in downstream packages because they're the natural way to pass around and group by DatasetTypes, and that means we should be exporting them at "lsst.daf.butler" level, instead of requiring imports from "lsst.daf.butler.core.utils", because the last two entries in that path should be considered internal daf_butler details.
Answer: 8799.0

User story: DM-24734 revealed that repeated lookups for the same dimension records make up a significant fraction of both Gen3 RC2 bootstrap (~47% in Oracle) and QuantumGraph generation (17% in SQLite).  This could be at least mostly addressed by caching more of those lookups, but we need to define interfaces that allow user code to make it clear when caches can be expired, and it would be even better to be able to do bulk fetches of these records to populate those caches up-front.    At the same time, discussions with [~<USER> about DM-21904 have revealed a very similar use case for pre-fetching and then making simple relationship queries (e.g. "give me the tracts related to this visit") against an in-memory data structure.    I have an idea for how to deal with both of these together, and I think I just need to work out the interfaces in more detail with Nate to ensure it will meet his needs.
Answer: 141330.0

User story: "the butler command functions config_dump and config_validate need to be refactored so that their implementations are in the scripts folder, similar to the other command functions."
Answer: 6368.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 of DM-24062, HSC calexp sources (at least) can be consolidated into visit level {{sourceTable_visit}} parquet tables.  While reading this in is extremely fast relative to reading in the individual source catalogs (especially when not reading the full width) [about 95-98% faster in some testing], these full catalogs are {{DataFrame}} objects and cannot be used with our source selectors.    It should be relatively easy to add {{DataFrame}} support to {{ScienceSourceSelectorTask}} and {{ReferenceSourceSelectorTask}} which I believe are the most common down-stream source selectors used for science analysis (and, for example, in {{fgcmcal}} which will be one of the first consumers of {{sourceTable_visit}}, DM-24319."
Answer: 1780.0

User story: "Make sure that it is clear what CW/CCW/UP/DOWN in the Dome commands XML in SAL mean and make sure that it is stated in the description of the crawl commands. Also make sure that negative velocities are rejected?"
Answer: 27412.0

User story: "Clean up some minor things that have come up with Gafaelfawr    - Add a request context so that the auth method can be added to the logs  - Remove unnecessary debug logging by making info-level logging more useful  - Change the lsp-deploy configuration to use info logging  - Improve test coverage for the session store and token verifier  - Format /auth/analyze output  - Add pytest-sugar  - Support configuration overrides via create_app  - Move XForwardedFiltered to its own file  - Separate logging tests  - Expose IP address of client in auth headers  - Refresh dependencies  - Better error message when unable to reach the auth provider  - Figure out why logs don't have timestamps"
Answer: 27631.0

User story: "The mock controller contains a timed loop that updates the statuses of the LLCs every 0.1 s (hard coded). Replace this loop with a function that takes a time argument so the new status can be computed w.r.t. that time. This will speed up unit testing considerably while now losing any functionality."
Answer: 22966.0

User story: The Dpdd specifies that the size of a the cutout in the alerts is set by the detection footprint wot a maximum of 30x30 pixels. Currenty the 30x30 is the default and used for all cutouts. This ticket will implement using the footprint or equivalent detection "size" to be discussed with [~<USER>.
Answer: 28648.0

User story: "There are two Jenkinsfiles for SAL/XML builds; one for releases and one for daily builds.  They are heavily duplicated, but build different branches and set variables differently.  In theory, with some smart conditionals, these two files can be merged into one.  This task covers the time needed to attempt this consolidation."
Answer: 158125.0

User story: "obs_lsst should be able to allow the Simonyi Survey Telescope as a valid telescope name in order to read files for ComCam and LSSTCam."
Answer: 1628.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: "address [~<USER>'s comments from the code review of DM-24584:   * I don't like how test subclasses are now required to specify duplicate information. Subclasses should specify the Instrument class or instrument class name and the name of the instrument itself can come directly from that.     "
Answer: 5802.0

User story: "This is the last environment using older authentication methods, so once this is done, clean up all the authnz support Helm charts and secrets."
Answer: 3164.0

User story: "GPDF has completed his initial review. Revise the document based on his feedback.    - Clarify that this is not a risk assessment  - Document account creation hold for non-US affiliations (and maybe non-affiliate IdPs)  - Be more explicit about requiring TLS  - Document how we determine affiliation for initial account creation  - Discuss scoping for limited-use tokens  - Add authentication of API calls from the Portal Aspect as a use case  - Identities are also linked to quotas (probably should be in the dashboard)  - Portal also talks to WebDAV  - WebDAV is also important for the 3-Aspect model    Also discuss the federated auth use case and document the limitation of browser auth to the same domain"
Answer: 23364.0

User story: "address [~<USER>'s comments from the code review of DM-24584:   * I prefer YAML to using eval for checking output.   * Maybe DAF_BUTLER_MOCK should be called CLI_BUTLER_MOCK_ENV or something since it's an override environment for doing click mock testing.    I may have thought of a better way using unittest.mock, will investigate."
Answer: 2061.0

User story: "Keep sal-sciplat-lab updated, per Tiago's instructions."
Answer: 32035.0

User story: "Write rst generator for sal-interfaces xml for documentation."
Answer: 11695.0

User story: "Testing in scarlet started failing on Travis CI yesterday, meaning that the docs are no longer being built. Tests pass locally, and the first test to fail is the current master: https://travis-ci.org/github/<USER>scarlet/builds/686233127 . Executing the previous master commit, which was previously passing, is now failing as well: https://travis-ci.org/github/<USER>scarlet/builds/686224195 .    This indicates thats something on Travis changed, but it is not clear what this could have been. I checked all of the dependencies and they use the same versions now as they did before:    numpy 1.18.1  scipy 1.4.1  astropy 4.0.1  nbsphinx 0.7.0  matplotlib 3.2.1  numpydoc 0.9.2  jupyter 1.0.0  pybind11 2.4.3  proxmin 0.6.10 (loaded from github, has not been updated)  peigen 0.0.9  prompt_toolkit 3.0.4  sep (loaded from github but has not had a new commit since November)  autograd 1.3"
Answer: 327.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: [~<USER> has discovered that the column type for the _max fields in the instrument table is not large enough for the values we use in obs_lsst - apparently we're not using a 64-bit type, and we never noticed because <sigh> SQLite doesn't care about types.    We should do full audit of all of our integer fields and make sure we chose appropriate sizes for all of them.  This may involve switching from just "int" in the dimension configs to more precise types.  
Answer: 39379.0

User story: "Update the google docs version of LTS-159 to reflect the changes we want from Tekniker.    https://docs.google.com/document/d/1o8xpBU5kkm_G6MjWjnkKkghKt1XeapFpqLGZrvDTDrY/edit?usp=sharing    This work will be done in collaboration with [~<USER> and others. This ticket is to track my contribution."
Answer: 14194.0

User story: "The base container contains upgrades in dm_csc_base that includes raft and sensor information for OODS ingestion messages.    Update containers to use LABEL to show which versions of the component software packages are in use.    Update versions of the T&S software."
Answer: 19900.0

User story: "We need a CI build so that we can merge ourselves."
Answer: 8521.0

User story: Saga of the dataset templates for calexp and friends for obs_lsst ImSim.     * obs_lsst templates changed all instances of "visit" to "expId"  {code}  sqlite> .schema raw  CREATE TABLE raw (id integer primary key autoincrement, run text,visit int,filter text,date text,dateObs text,expTime double,raftName text,detectorName text,detector int,snap int,object text,imageType text,testType text,lsstSerial text,wavelength int,controller text,obsid text,expGroup text,expId int, unique(expId,detector,visit));  {code}     * We reingested all the DC2 repos on DM-23441    * templates increase number of digits in an expId, breaking data access to these reingested repos.   * ImSim get's its own policy override file so that we're not sensitive to changes necessary for comcam latiss etc.  * Today [~<USER> notices that downstream code depends on visit being the dataId key.     Copied and pasted from Slack:   We need something for gen 2, because we’ll be using it for a while. Downstream code depends on “visit” as Eli has noticed. We will have a 1-1 mapping between expId and visit for as long as gen 2 is in use (maybe forever, but I don’t want to get into that here)  placeholder snapCombine was going to take place in ISR.  => ISR is supposed to accept ids per expId and write out dataIds per visits.    => we can keep @hsinfang’s reingested repos (see https://jira.lsstcorp.org/browse/DM-23312)  Write a special imsim specific ISR snapCombine placeholder that’s just a “visit = expId”  Change all our templates back to visit (except for raw of course)  and be on our merry way    The registry knows that expId=visit because they're both columns in the table. Whether or now we want to query the butler and assert that it is the only expId/ccd combo for its associated visit/ccd combo is up to the implementer.     
Answer: 3910.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "I have just noticed that psutil is not in our new conda env. The python_psutil dependency was removed from the utils table file but nothing replaced it.  This means that the file leak testing has been disabled and we didn't notice.    Please add it back to the env."
Answer: 12699.0

User story: "Currently, Travis just runs a {{pip install flake8}} when it lints our code. That means it pulls the latest version of flake8, which may not match that in scipipe_conda_env. Let's pin the version of flake8 being used by Travis to match the version we specify in scipipe_conda_env."
Answer: 1215.0

User story: "With multiple puppet masters per data center, need to backup CA cert for each node (as well as puppet agent cert).    Update xcat-tools and install new xcat-tools on xcat master nodes."
Answer: 86.0

User story: "* Felipe needs two test nodes in NTS for puppet development work on Headerservice profile     ** lsst-nts-test12 (puppetmaster)   ** lsst-nts-test13 (puppet agent)"
Answer: 20214.0

User story: "Increase the connection pool limit to allow more users at stackk club to run queries at the same time.  Right now it's probably far too low."
Answer: 1.0

User story: "Found a bug in argocd with the login command not respecting port forwarding, and I need that to work for what I'm doing in DM-24367"
Answer: 8771.0

User story: "RepoWalker raises when initialized when there is nothing for it to look for.  This is useful information that should be propagated up to avoid unnecessary filesystem scanning, but it shouldn't be allowed to propagate _all_ the way up and kill conversion, as this isn't all of the work that might need to be done."
Answer: 417.0

User story: "During the first attempt to add fakes to the bi-weekly reprocessing it crashed due to not adding the sky_source column. Update the processCcdWithFakes code to add the sky_source column in the same way that calibrate.py does."
Answer: 24610.0

User story: "The API for scarlet changed slightly, with some improvements in performance and in memory usage. So this ticket is to update {{meas_extensions_scarlet}} to properly wrap and propagate those changes and run on the fake patches to measure the gains in performance from the previously tested version."
Answer: 23038.0

User story: "Task to track time spent coordinating meetings, creating agendas, fact finding TMA related information, opening communication between TMA experts and RO team, reporting to Shawn/Andy."
Answer: 20246.0

User story: "The lint job has a typo, instructing flake8 to run on a non-existent file. This was secretly broken; flake8 v3.8.0 (released today) now errors on non-existent files, so we are seeing it for the first time."
Answer: 823.0

User story: "processCcdWithFakesDriver is running for people who aren't me. I think the problem is that I forgot to add it to bin.src."
Answer: 5233.0