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: "participate in build hackathon on monday and wednesday"
Answer: 7206.0

User story: "As per instructions in /project/hsc/gen3repo/README, I need a postgres account. My NCSA name is emorgan2"
Answer: 26.0

User story: "Currently if a task is declared in a Pipeline task list, and the task is already declared in an inherited pipeline (with the same label), the task and its configs replace the inherited versions meaning all configs need to be declared in a pipeline, even if only one config is to be added.    This ticket will change this behavior. If a task is declared in a pipeline that inherits the same task with the same label, the new config options will be added to the existing config overrides. If a label is declared with a different task than what exists in the inherited pipeline, it will completely replace the existing definition, as the config options likely no longer apply."
Answer: 1363.0

User story: Please add Seaborn to the default Science Pipelines Conda environment. This would be a good package for the forthcoming "extras" package list (as it is unlikely Jenkins will need it), but if that "extras" functionality is a ways off, it would be good to have this sooner so people can use it. It's a small package (see the RFC for details), so should be a fairly trivial add for the jenkins environment. I could be moved over to "extras" when that becomes available.    This is the implementation ticket for RFC-707.
Answer: 9263.0

User story: In DM-21706 we discussed the general issue of filter definitions in obs_lsst.  This ticket covers the specific case of imsim.    We need the following:    # Determine every simulated filter ever used for imsim that is of interest.  # Create an LSST_IMSIM_FILTER_DEFINITIONS variable in filters.py in obs_lsst  # Give each filter a unique label (such as g_sim_20161205) and add it to LSST_IMSIM_FILTER_DEFINITIONS.  # Update imsim mapper and gen3 instrument to use these filter definitions.  # Write header fix up code in the imsim metadata translator that will replace the current "abstract" FILTER header with the correct "physical" filter name.    
Answer: 30179.0

User story: There's some concern about the scope of [www.lsst.io.|http://www.lsst.io./] This ticket is to change some of the copy in [www.lsst.io|http://www.lsst.io/] to explain that only _technical_ documentation is found on the site.    Also, explain better what content is searchable/indexed at this time. Perhaps an "about this site" type of page with a table outlining the status of different content would be food.
Answer: 10132.0

User story: "`pipetask` uses `multiprocessing` to run tasks concurrently and it appears that crash (like SEGV) in a child process is not handled in a reasonable way. Need to understand what happens when child dies unexpectedly and how to workaround that."
Answer: 33500.0

User story: "The redesign eliminates the MTArchiver, so it should be deleted from the SalSubsystems.xml in ts_xml"
Answer: 21764.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: "One of the problems we are having with running pipelines on Google is that they support pre-emption of compute nodes. At the moment what happens is that the node is shut down and depending on where the pipeline was we can end up in a weird state.  When we run tens of thousands of jobs some of those are going to be pre-empted during the writes to the datastore with no chance of rolling back any transactions. Sometimes only some of the writes have been completed, sometimes all of them have been.    Google do support pre-emption scripts which they can launch 30 seconds before the node is killed. In theory this script could send a SIGINT to any pipetask commands that are running and give them 30 seconds to clean up before being yanked.    What I'm wondering is if we could wrap the code that does all the butler puts in a try block catching  KeyboardInterrupt. Then it could know if it has done partial puts and roll those back. We probably shouldn't be in the game of trying to start a timer and seeing if we can squeeze in all the puts before the 30 seconds triggers.    I think we need to support CTRL-C anyhow and it looks like CmdLineTask tries to do so but not pipetask (I might be wrong).    Note that we absolutely do not want CTRL-C to be ignored -- the point is that this is the only way we are going to tell that a shut down is about to happen.    In a related note, pipetask really does need some way of overwriting a dataset if it has not child datasets that depend on it. We are running into many issues during development where rerunning jobs in a big workflow is something we really want to do automatically. I imagine that's a different ticket to this one though."
Answer: 58782.0

User story: "Composite disassembly is not properly tested anywhere for afw Exposures. Run ci_hsc_gen3 with disassembly turned on and see what breaks."
Answer: 10369.0

User story: "After work on DM-25488 the kafka-connect-manager Helm chart must be updated."
Answer: 12707.0

User story: "Need to be reorganized after DM-25488 to follow same standards as for example in the `kafka-aggregator`."
Answer: 13303.0

User story: "This ticket injects the fake {{flat_models.fits}} catalogue provided by the LSST:UK LSB WG into deepCoadd imaging. All processing is performed in the notebook attached below, with an example before/after plot showing the impact of fake addition for Tract 9813 Patch 3,5.     Output processing can be found in: {{/project/<USER>fakes_lsstuk/outputs/flat_models}}.   This directory is sym-linked on the LSP at this location: {{/home/<USER>fakes_lsstuk/outputs/flat_models}}.    A final combined parquet table is located here: {{/project/<USER>fakes_lsstuk/outputs/flat_models/deepCoadd-results/merged/9813/objectTable-9813.parq}}.   This can be found on the LSP at this location: {{/home/<USER>fakes_lsstuk/outputs/flat_models/deepCoadd-results/merged/9813/objectTable-9813.parq}}."
Answer: 3425.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've deployed (with Hsin-Fang's help) the Cloud Edition for Lustre software.    I remain concerned about getting the filesystem working inside a K8s container."
Answer: 5044.0

User story: "Release a salobj 5 that sets a random LSST_DDS_DOMAIN in {{BaseCscTestCase.check_bin_script}} by cherry-picking the change from salobj 6"
Answer: 3385.0

User story: "Task to track the work to create the Conda recipe and Jenkinsfile.conda for the Environment CSC."
Answer: 5763.0

User story: "Add the conda build files to ts_authorize. This may have to wait until ts_sal 5 is released -- at least to run it."
Answer: 6001.0

User story: "The Rotator low-level controller will output velocity information as of DM-25994. Update the Rotator CSC accordingly."
Answer: 36003.0

User story: "Rebuild container for OODS to use LSST stack weekly 30"
Answer: 3062.0

User story: "RC2 reprocessing with w_2020_30 stack."
Answer: 11277.0

User story: "Do the coverage test for rotator PXI code by *gcovr*."
Answer: 44660.0

User story: "make lsst log config conditional in ctrl_mpexec click CLI similar to DM-26088    The cmdLineFwk root logger always gets set to Info (see [https://github.com/lsst/ctrl_mpexec/blob/master/python/lsst/ctrl/mpexec/cmdLineFwk.py#L521)], the click framework should do the same.     "
Answer: 57548.0

User story: "For KPM50 we want to check the state of the existing test harness that was used for previous tests and understand its limitations and bottlenecks."
Answer: 27034.0

User story: "General reminder to add Jenkins conda build files to   * HVAC   * GenericCamera   * ESS   * MTEEC   * EAS   * Dome   * ..."
Answer: 27271.0

User story: "OpenSpliceDDS=6.9.0-8  ts_dds=v6.9.190925_7  ts_xml=6.1.0  ts_sal=4.1.4  ts_idl=1.3.0  ts_salobj=5.17.0"
Answer: 422.0

User story: "Review the trajectory document of TMA: [^TrajectoryGenerationAlgorithmForLSST.docx]."
Answer: 7131.0

User story: "Install the ESS CSC on the raspberry pi 4 running CentOS 7 and make sure that it can be started. Also update the installation guidelines with the necessary steps."
Answer: 106.0

User story: "lsst.log allows its config to be set via a configuration file at the LSST_LOG_CONFIG environment variable. However currently this feature cannot be used with the PipelineTask framework, because it resets the logging properties.      It'd be convenient if this reset can be skipped while a configuration file is provided.   "
Answer: 1467.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 recent run on RC2 (DM-25714) resulted in a systematic offset between the calibrated stars and the reference stars using fgcmcal (e.g. [https://lsst.ncsa.illinois.edu/~<USER>w_2020_26_qaPlots/HSC-I/tract-9615/plot-t9615-HSC-I-matches_CircApRad12pix_mag-psfMagHist.png] ). However, internally, the fgcmcal calibrated stars did not show any such problem.    A deep dive revealed the source of this offset. First (and much less importantly) a couple terms of the fit were not quite converged. I am going to slightly restructure the logic to ensure that consistent answers are output even in the case when the fit is not 100% converged. These effects are at the few mmag level, and is not the majority of the problem.    Second, and more importantly, the update to fgcmcal that by default subtracted off the local background (DM-23036) results in a tighter, more robust fit, but I unfortunately had not noticed that the background is typically so wrong that _even for the brightest stars_ subtracting off the local background yields an offset of 1-2%. For example, here are all the stars in an arbitrary i-band visit, the x-axis is uncalibrated magnitude, and the y axis is the difference when the magnitude when estimated with and without the local background estimation:   !delta_vs_mag.png|thumbnail!    This varies from visit to visit (and ccd to ccd) and may vary systematically with time/location, which is a problem.    I am going to add a term to the output zeropoints to account for this offset on a -per-ccd- per-ccd or per-visit basis when local background correction is turned on."
Answer: 29918.0

User story: "In DM-12030, the persistence to parquet tables of the compiled per-tract(visit) catalogs assembled when running the {{pipe_analysis}} scripts was added to facilitate QA efforts external to {{pipe_analysis}} (these were originally intended for use with the interactive QA dashboard under development -- see, e.g. DM-25395 -- but, e.g., they were also used in the analysis of DM-25709 as a quicker full-tract input than the now-persisted per-patch {{obj_}} parquet files).  The (denormalized) catalogs created by matching the detected sources to an external reference catalog would also be of use for external QA analyses and validations, so they will be added as (optional) outputs on this ticket."
Answer: 69255.0

User story: "All of the current deployment charts need to be changed in order to support the new shared memory model."
Answer: 102535.0

User story: "Since we're giving users interactive shell inside the Kubernetes cluster, add a layer of protection to Gafaelfawr's Redis and require password authentication. This isn't strictly necessary because all the storage is encrypted, but it reduces the attack surface."
Answer: 36475.0

User story: "Complete the phishing and driving exams, send the certificate to Giovani to be able to drive up the summit. "
Answer: 11732.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: "Determine how to integrate authentication for Chronograf and InfluxDB with Gafaelfawr to standardize our authentication platform."
Answer: 51809.0

User story: "After discussion with [~<USER> about approaching implementation of the new Filter design, we wanted to write down a list of requirements for the new system. RFC-541 was more focused on technical requirements, but some of the comments there can be built on to help with use case requirements. RFC-624 provides a design, but discussion since that has led to some questions about how exactly that design maps to how this system would be used.    For this ticket, I will write up (probably not a DMTN?) a list of use cases and requirements for Filters in the stack, based on the above RFCs, my own experiences with the {{Instrument}} {{FilterDefinitions}}, and expectations for how filter names are used for photometry."
Answer: 82036.0

User story: "Ingest some or all of the Object tables from [S20 HSC PDR2 Reprocessing|https://confluence.lsstcorp.org/display/DM/S20+HSC+PDR2+Reprocessing] , as generated in DM-23856, into a Qserv instance.  "
Answer: 10112.0

User story: "Use setuptools_scm to properly calculate the scarlet version, and create a scarlet 1.0 tag."
Answer: 64.0

User story: "Take the object table parquet files at  {noformat}  /datasets/hsc/repo/rerun/RC/v20_0_0_rc1/DM-25349/deepCoadd-results/merged/9615/objectTable-9615.parq  /datasets/hsc/repo/rerun/RC/v20_0_0_rc1/DM-25349/deepCoadd-results/merged/9697/objectTable-9697.parq  /datasets/hsc/repo/rerun/RC/v20_0_0_rc1/DM-25349/deepCoadd-results/merged/9813/objectTable-9813.parq  {noformat}  as inputs, go through the workflow and ingest into Qserv.    "
Answer: 1.0

User story: "Tests currently fail because they specifically ask for v2.1 of the alert schema, but that was deleted recently. They should use the latest schema."
Answer: 71.0

User story: "This ticket is to follow the steps at https://developer.lsst.io/stack/add-a-package-to-pipelines-lsst-io.html to list {{alert_packet}} on pipelines.lsst.io"
Answer: 3013.0

User story: "As pointed out by @<USER> there's a missing method from the internal Kafka client."
Answer: 159.0

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

User story: "Go to the recinto and coordinate the completion of the Raspberry pi connectivity to the server room."
Answer: 183.0

User story: "Go to the Recinto and coordinate with Te-Wei and Julio to get the M2 and Hexapod servers online so that IT can access them to create backups. "
Answer: 26.0

User story: "Now that the raspberry pi 3 with the Canon all-sky camera is up and running at the Recinto, it is time to install the CSC on it and get it working with the camera."
Answer: 13245.0

User story: "Current forwarder tests use redis and rabbitMQ from production with different vhost and database. Those tests can be run inside containers to create isolated environment."
Answer: 2202.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 discussing with [~<USER> and Chris Stephens at NCSA, I have an empty APDB-like PostgreSQL I can connect to hosted at lsst-pg-devel1. Eventually we will probably want to use one of these instead of sqlite for all/most AP reprocessing, especially the larger multi-filter HSC "medium" dataset I used for DM-24252. For now, this ticket is just to rerun ap_pipe with this new flavor of database to see if I can get it to work. The results should be nearly identical to the official July 2020 reprocessing (DM-25910).    Fun facts   * Credentials are an issue, as every time I connect to this DB I presently have to type my NCSA password   * I don't currently have the ability to run e.g. make_apdb.py and get a fresh empty PostgreSQL proto-APDB on this host, instead I have to ask Chris S to make me one, and there's just one for me to play with for starters   * I need to read up on psycopg2 (python package for interfacing with PostgreSQL databases so I can load APDB data into python/pandas)   * The host for this test database is, as Chris S described, the wild west, and we will need to do something to make sure this and future APDBs are accessible in the future
Answer: 54523.0

User story: "The hexapod simulator needed for running the AT Hexapod separate from hardware needs some extra configuration to make it work within the k8s environment."
Answer: 93666.0

User story: "Get newer version on -int"
Answer: 20.0

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

User story: "DM-25883 implemented re-loading of previous save results; this ticket extends that functionality to re-load previous fits to deblended sources and use them to do a simultaneous (linear) fit for an entire blend (i.e., deblending)."
Answer: 70329.0

User story: Need to update {{gen3-hsc-rc2/bootstrap.py}}   {noformat}  gen3-hsc-rc2/bootstrap.py", line 209, in makeTask      return ConvertRepoTask(config=config, butler3=butler)  TypeError: __init__() missing 1 required keyword-only argument: 'instrument'  {noformat}  
Answer: 30530.0

User story: "Freshen TexLive"
Answer: 1320.0

User story: "Currently defineVisits reads the WCS directly from each raw file, via datastore, and uses camera geometry to work out the bounds of the observation.  For S3 storage this is going to require a download of each raw (or at least a part of it). Since the WCS is defined solely from the ICRS tracking ra/dec and the boresight rotation angle, if we stored those values in registry the bounding box could be calculated solely using registry."
Answer: 102474.0

User story: "Tiago says this works to get conda unstuck:    conda list --explicit > spec_file.txt && \      conda create -n $LSST_CONDA_ENV_NAME -y python=3.7.6 && \      conda install -y --file spec_file.txt"
Answer: 39.0

User story: "New obs_lsst template in DM-25470 means BOT data needs reingesting please."
Answer: 34110.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: "Write a documentation for setting up the Replication/Ingest system for the _mono_-node setups of the Replication/Ingest system. Include an example of ingesting a small catalog via the new system. Eventually, this recipe should be used in extending the Qserv integration tests to also include the new Replication/Ingest system.    The initial version of the document to be placed at: https://confluence.lsstcorp.org/pages/viewpage.action?pageId=140281270    *NOTE*: the catalog ingest example of this document should be be based on the comprehensive User guide for the Qserv Ingest system: https://confluence.lsstcorp.org/pages/viewpage.action?pageId=133333850  "
Answer: 157.0

User story: "Work with IT Chile to automate (puppet) the setup of a dedicated DDS debug node on the base cluster"
Answer: 95229.0

User story: "Install debug tools on the NCSA test stand and use to monitor DDS during timeouts fetching history, and other communication problems"
Answer: 11303.0

User story: "Tasks capturing Mike's work on the Rotator Plant Model for the last couple of weeks.  Mike has entered 24 hours into his time sheets, so 3 SP will used for this task."
Answer: 1.0

User story: "The explicitly-pinned packages in {{scipipe_conda_env}} at 1a1d771 are now incompatible with upstream conda-forge and appear to prevent any conda-forge packages from being installed on top.    Re-pin the dependencies, for now with minimal changes to avoid any possible downstream effects on the Science Pipelines."
Answer: 2603.0

User story: "Find out whether JL 2.x is moderate or large effort."
Answer: 13186.0

User story: Gen3 middlleware implemented a YAML description of a pipeline.  ctrl_bps previously defined its own pipeline YAML description.  To enable using pipeline YAML files prior to having "merge" with pipetask discussions, modify BPS to take a pipeline YAML file similar to how it can take a pre-existing QuantumGraph file.  Where easily possible, minimize bps config when being given pipeline YAML or QuantumGraph file.      
Answer: 22099.0

User story: "if a connection's (or task's) dimensions is specified without a comma and there is only one dimension a weird error is generated as the system attempts to iterate over the string. This ticket will add validation to catch this case"
Answer: 143.0

User story: "This page    [https://confluence.lsstcorp.org/display/LTS/SALSubsystem+Attributes]    describes the attributes of all subsystems in SAL. Check the attributes for the following projects and correct them if necessary:   * Dome   * EAS   * ESS   * HVAC"
Answer: 2887.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Since I merged DM-25923 we've been getting some intermittent failures in obs_lsst tests that seem to be related to the camera caching returning the wrong object.  This only seems to happen in some environments with many cores. The TS3 ingest test fails because it ends up registering a camera that looks like LSSTCam and not TS3.  There is also a failure in writeCuratedCalibrations that is related where the detector in the data package does not exist in the camera despite the correct data package being used.  "
Answer: 1328.0

User story: "Now that [~<USER> has removed our usage of namespace packages, we can simplify our mypy configuration by running it in a more standard manner - from the root directory, on a directory, instead of from the python subdirectory, on a package.    At least in my (VSCode) case, this will also make in-editor configuration vastly better."
Answer: 138.0

User story: "Add to the neophile documentation instructions for how to set up a repository with Dependabot, Renovate, and neophile according to our best practices."
Answer: 5301.0

User story: "pex_config serializes to pickle by converting to text. This should be easy to also do as a yaml representer.  Doing this will give us the option of switching quantum graphs over to yaml."
Answer: 50591.0

User story: "ATDome tests are failing with the new build script. Figure out what's going on"
Answer: 37318.0

User story: "create config file for adamSensors in ts_eas_config"
Answer: 40052.0

User story: "Currently {{pipetask qgraph --show workflow}} figures out the dependencies in its own method, but the {{QuantumGraph}} class can provide such information already.  I don't know why I didn't use it but I'll clean it up here.  For this ticket the output format would stay the same, just improving the implementations. "
Answer: 216.0

User story: "Some maintenance chores now that we've launched www_lsst_io:   * Upgrade the node version we're using locally and in GitHub Actions, and thus update more packages (locally this means adopting the node version manager).   * Cleaning up the components, namely moving components into the basics/ and algolia/ directories.   * More consistent documentation of components"
Answer: 15602.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 current search UI includes a "Clear refinements" button, but the refinements UI isn't complete yet. Let's try to finish it:   * Include breadcrumbs for individually active refinements ([currentRefinements|[https://www.algolia.com/doc/api-reference/widgets/current-refinements/react/]] widget)   * Hide the "Clear refinements" button if there aren't any refinements    Feedback from Gregory:  {quote}It’s not clear what a “refinement” is until you actually play with the system for a while - then it becomes clear that it’s only an action on the content types or author checkboxes, but not, say, adding an additional search term.  The lack of an “active” vs “greyed-out” state on the “Clear all refinements” button makes it hard to tell what it’s going to do.  If it started out grey and only went “live” when a checkbox was checked, it would be easier to become confident about the behavior.  {quote}
Answer: 28898.0

User story: "{quote}The cursor doesn’t become the pointing-finger over the blue buttons, and the buttons don’t display any transient “I’m being pressed” feedback.  Combined with the other things below it creates some uncertainty about whether the buttons are “live” or not.  {quote}"
Answer: 30026.0

User story: "The XML attributes are defined here:    [https://confluence.lsstcorp.org/display/LTS/SALSubsystem+Attributes]    Add this task to this page:    [https://confluence.lsstcorp.org/display/LTS/SALSubsystems+Attributes+Work+Tracking]     "
Answer: 3853.0

User story: "Add the funding notice to [www.lsst.io,|http://www.lsst.io,/] based on https://project.lsst.org/documents/name-use-guide"
Answer: 59.0

User story: "M1M3 states aren't described in the code and there seems to be lack of any documentation. Purpose of this task is to review the state, document them and propose changes to align with the current SAL implementation."
Answer: 14115.0

User story: "Publish the velocity or needed telemetry to DDS for rotator."
Answer: 15993.0

User story: "At launch, [www.lsst.io|http://www.lsst.io/] doesn't cover documents in DocuShare that don't have counterpart versions on LSST the Docs, which we're currently scraping. This ticket is to temporarily add notices to the site to clear this confusion up."
Answer: 298.0

User story: "I spent significant time in June and early July preparing for and attending SATCON1. I gave a talk which highlighted my contributions to the paper about how low earth orbit satellites will affect Rubin Observatory by measuring Starlink brightnesses in DECam data. My slides are available at [https://zenodo.org/record/3937869|https://zenodo.org/record/3937869.] and the paper led by Tony and Zeljko is on arXiv [https://arxiv.org/abs/2006.12417] (should appear soon in AJ)."
Answer: 6747.0

User story: "Next step in supporting schema migration for registry, need to determine and implement how we are going to define schema versions in the registry code and mechanism to store versions in the butler_attributes table."
Answer: 26035.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: "Changes somewhere mean that this sadly needs a reingest. Something like {{ingestImages.py /project/shared/comCam-CCS /lsstdata/offline/teststand/comcam/CCS/storage/...}} should do it.    Sorry for such a brief ticket, just let me know if there's any other info you need."
Answer: 1069.0

User story: "Run SQR-044 past the CILogon team and see how many of those requirements will be met by COmanage. Also reach out to the identity management community and see what else we should be looking at."
Answer: 107731.0

User story: See [this report on Slack|https://lsstc.slack.com/archives/C2JPMCF5X/p1594855003499800] from [~kadrlica]:  {code}  ingestReferenceCatalog.py repo reference_catalog_v479028-i.txt --configfile ImageProcessingPipelines/config/DC2_run22_ingestRefConfig.py   LsstCamMapper WARN: Unable to find valid calib root directory  CameraMapper INFO: Loading exposure registry from /global/u2/k/kadrlica/projects/sims_ci_pipe/repo/registry.sqlite3  root INFO: Running: /cvmfs/sw.lsst.eu/linux-x86_64/lsst_distrib/w_2020_24/stack/miniconda3-4.7.12-1a1d771/Linux64/pipe_tasks/19.0.0-63-gd25ffe2a/bin/ingestReferenceCatalog.py repo reference_catalog_v479028-i.txt --configfile ImageProcessingPipelines/config/DC2_run22_ingestRefConfig.py  Traceback (most recent call last):    File "/cvmfs/sw.lsst.eu/linux-x86_64/lsst_distrib/w_2020_24/stack/miniconda3-4.7.12-1a1d771/Linux64/pipe_tasks/19.0.0-63-gd25ffe2a/bin/ingestReferenceCatalog.py", line 3, in <module>      IngestIndexedReferenceTask.parseAndRun()    File "/cvmfs/sw.lsst.eu/linux-x86_64/lsst_distrib/w_2020_24/stack/miniconda3-4.7.12-1a1d771/Linux64/pipe_base/19.0.0-24-g878c510+9/python/lsst/pipe/base/cmdLineTask.py", line 610, in parseAndRun      resultList = taskRunner.run(parsedCmd)    File "/cvmfs/sw.lsst.eu/linux-x86_64/lsst_distrib/w_2020_24/stack/miniconda3-4.7.12-1a1d771/Linux64/meas_algorithms/19.0.0-21-gf63060fa+1/python/lsst/meas/algorithms/ingestIndexReferenceTask.py", line 88, in run      task.createIndexedCatalog(files)    File "/cvmfs/sw.lsst.eu/linux-x86_64/lsst_distrib/w_2020_24/stack/miniconda3-4.7.12-1a1d771/Linux64/meas_algorithms/19.0.0-21-gf63060fa+1/python/lsst/meas/algorithms/ingestIndexReferenceTask.py", line 354, in createIndexedCatalog      self.log)    File "/cvmfs/sw.lsst.eu/linux-x86_64/lsst_distrib/w_2020_24/stack/miniconda3-4.7.12-1a1d771/Linux64/meas_algorithms/19.0.0-21-gf63060fa+1/python/lsst/meas/algorithms/ingestIndexManager.py", line 84, in __init__      self.coord_err_unit = u.Unit(self.config.coord_err_unit)    File "/cvmfs/sw.lsst.eu/linux-x86_64/lsst_distrib/w_2020_24/conda/miniconda3-4.7.12/envs/lsst-scipipe-1a1d771/lib/python3.7/site-packages/astropy/units/core.py", line 1886, in __call__      raise TypeError("None is not a valid Unit")  TypeError: None is not a valid Unit  {code}
Answer: 1176.0

User story: "{{Measurement}} objects can contain a dictionary of {{astropy.Quantity}} objects.  This is to test the round tripping of those extras."
Answer: 20694.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Fix up logging, get rid of unauthenticated access and get the deployment and pushing working after the nonsense."
Answer: 30295.0

User story: "Add the GitHub action that runs Helm lint on each changed chart."
Answer: 8913.0

User story: "Nublado presentation Thursday July 16 2020."
Answer: 2789.0

User story: "Use [gatsby-plugin-canonical-urls|https://www.gatsbyjs.org/packages/gatsby-plugin-canonical-urls/] to ensure that Google only indexes the [www.lsst.io|http://www.lsst.io/] site, and without query strings."
Answer: 1568.0

User story: "Create OpenSplice RPM for 6.9.0-8 with MASTER_PRIORITY mod, package source for KT to build on el6/conda    Create OpenSplice RPM for 6.10.4 Commercial edition"
Answer: 3085.0

User story: "Update HeaderService version to 2.3.1"
Answer: 65.0

User story: "In early days SQuaSH had a web frontend, a REST API and Bokeh apps in three separate repos. The deployment was managed by a fourth repo called {{squash-deployment}}.    From that only the {{squash-deployment}} and the SQuaSH API survived. The frontend and the the Bokeh apps where removed when we introduced Chronograf, InfluxDB and Kapacitor.    The goal of this ticket is to manage the deployment of SQuaSH using Argo CD to have configuration management.     We decided that the lsp-deploy repo would be a good home for the SQuaSH deployment.    The SQuaSH API has a Helm chart now DM-26455.    I plan on testing the InfluxData Helm charts for Chronograf, InfluxDB and Kapacitor.    I'll look at the let's encrypt certificate as a replacement for the wild certificate currently used in the SQuaSH deployment.    I plan on testing Gafaelfawr to authenticate Chronograf and in InfluxDB as another goal for this ticket.     I'll start with the {{squash-sandbox}} Argo CD app to test things out, in a separate ticket I plan on creating  {{squash}} production deployment.         "
Answer: 92192.0

User story: "postgresql has a number of client utilities that would be very useful to developers on the project.    please install the client programs and libraries from [https://download.postgresql.org/pub/repos/yum/reporpms/EL-7-x86_64/pgdg-redhat-repo-latest.noarch.rpm] on all lsst-dev nodes. If possible, please do the same on HTCondor and slurm nodes as well.    we would like to have this available for long-term use by users of these systems."
Answer: 11095.0

User story: "Build TSS component for xml 6.1 using the new cycle build procedure.    I will also allocate some time to document the procedure. "
Answer: 24238.0

User story: "There are two places in daf_butler where we use numpy without needing to. Both of them involve random numbers that can be replaced with calls to {{Random}} instead. There is one usage in a test which is protected and then one other test that requires a numpy integer.    Remove the unnecessary usage and protect the remaining one.    numpy is going to be pulled in by sphgeom but that's not reason to use numpy in butler when it doesn't give us anything."
Answer: 530.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Presentation will involve a few overview slides and a lot of Q&A.     "
Answer: 4371.0

User story: <USER>provided comments and feedback on the "Sensor Characterization and ISR" confluence page: https://confluence.lsstcorp.org/display/DM/Sensor+Characterization+and+ISR#/    This ticket is to follow-up on those comments, and file new tickets for some of them if needed. 
Answer: 29470.0

User story: "*NOTE*: this effort requires https://jira.lsstcorp.org/browse/IHS-3977. It also depends on https://jira.lsstcorp.org/browse/IHS-1270.    Deploy and test the Docker-based instance of Qserv on the k8s prod cluster. The cluster has the following nodes:  * 2 _masters_: {{lsst-qserv-db03}}, {{lsst-qserv-db04}}  * 6 _workers_: {{lsst-qserv-db31}} - {{lsst-qserv-db36}}    Requirements:  * In the initial deployment, there will be one Qserv {{czar}} installed at {{lsst-qserv-db03}}.  * Data directories of Qserv will be at folder {{/qserv/qserv-prod}} on each node of the cluster.  * Qserv management tools to be installed at: {{/home/qserv/management/qserv}}.    Other actions:  * Test and report (as comments to this ticket) the performance of the data filesystems used by Qserv.  * Document all deployment steps in this ticket.  * Work with the rest of the team on installing the logs collection services.  * Work with the NCSA LSF team on opening ports of the Qserv Ingest system to the verification cluster's nodes. The ports will be needed for ingesting catalogs into Qserv. Create an IHS ticket to request the port opening.  * put management scripts and configurations into Git package: https://github.com/lsst-dm/qserv-ncsa"
Answer: 52867.0

User story: "Create an exploratory notebook to associate DIAObjects found in HiTS data with known SSOs from the Minor Planet Center."
Answer: 49.0

User story: "Prepared two presentation for the LSST SSSC sprint, one describing the current state of Solar System Processing, the other one discussing the new synthetic solar system observation database.    https://lsst-sssc.github.io/Sprint2020/"
Answer: 66.0

User story: "Construction of a full density simulation of observations of Solar System Objects during year one of LSST. This constitutes substantial update to the only full density sample available before (Vereš & Chesley, 2017) featuring a recent opsim run ([https://community.lsst.org/t/fbs-1-5-release-may-update-bonus-fbs-1-5-release/4139]) as well as false detection modeling. The Synthetic Solar System Model (S3M, Grav et al. 2011) was used as input population.    Work involved:   * DM-25332   * [https://github.com/dirac-institute/survey_simulator]"
Answer: 70.0

User story: "Forwarder currently utilizes days to query DAQ catalog for missed images. That should be updated to use minutes and hours to accomodate new CatchupArchiver requirement."
Answer: 1352.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: "Data products graphic needs to be updated, Replace LSST with Rubin. Once available replace in slide [https://docs.google.com/presentation/d/1MkTtcNq0teInE-C9Dowetp7FyO2Uv-FcA-Kdvm0XyOA/edit#slide=id.g53030eed7b_0_473]"
Answer: 1299.0

User story: "There is currently a bug that prevents some models from saving correctly due to an integer that is wrapped by autograd. This ticket is to fix that bug."
Answer: 87.0

User story: "Limit the size of the alert cutouts to 2 times the size of the largest side of the DiaSource detection footprint. Also re-run the ap_verify_hits2015 dataset."
Answer: 5724.0

User story: "Initial release of kafka-aggregator with the following features:    * Use Faust windowing feature to aggregate a stream of messages.  * Use Faust-avro to add Avro serialization and Schema Registry support to Faust.  * Support to an internal Schema Registry to store schemas for the aggreated topics (optional).  * Create aggregation topic schemas from the source topic schemas and from the list of summary statistics to be computed.  * Ability to create Faust records dynamically from aggregation topic schemas.  * Ability to auto-generate code for the Faust agents (stream processors).  * Compute summary statistics for numeric fields: {{min()}}, {{mean()}}, {{median()}}, {{stdev()}}, {{max()}}.  * Add example module to initialize a number of source topics in kafka, control the number of fields in each topic, and produce messages for those topics at a given frequency.  * Use Kafdrop to inspect messages from source and aggregated topics.  * Add kafka-aggregator documentation site.  "
Answer: 175.0

User story: "Despite existing safeguards, loosing the connection with the database still makes components of of the DBB endpoint buffer manager terminate their execution. The goal is to add new and/or alter existing ones to make sure that all components will continue to operate even when the database is not responding."
Answer: 2597.0

User story: "Instantiating a yaml camera takes a long time (10 seconds for imsim on my Mac). This can cause significant slow downs if there are repeat calls to yamlCamera.makeCamera with the same yaml file.  This is particularly noticeable in tests.  Since the camera returned by makeCamera should be immutable, it makes sense to add an lru_cache decorator around that call.   This should also allow the local caching to be removed from obs_lsst."
Answer: 1780.0

User story: "[~<USER> has written lots of great CTI correction code, and there was talk with [~<USER> in March about getting some of this DM-ified.    Ticket is to get this conversation restarted, and put somewhere more appropriate than in private messages."
Answer: 91950.0

User story: "Support activities to develop a dome environment conditioning contract, to control the temperature during daytime. The activities include reviewing proposals, provide technical information to potential contractors, meetings with Rubin Observatory reviewers and contractors."
Answer: 14352.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: [www.lsst.io|http://www.lsst.io/] includes documents in the Algolia search index, but we haven't created ingest pipelines for user guides yet.    In the meantime, lets manually add links to these user guides from the homepage so that our documentation is more discoverable.    The guides can probably be maintained in a JSON file with Title, link, description fields, category, and "featured" fields. This data can be ingested via Gatsby data layer. On the homepage, we'll display these links in cards/grid.
Answer: 31911.0

User story: These documents are examples of technotes not being correctly ingested:   * [https://dmtn-153.lsst.io|https://dmtn-153.lsst.io/] (LaTeX technote has no content, only an abstract)   * [https://dmtn-152.lsst.io|https://dmtn-153.lsst.io/] (LaTeX technote has no content, only an abstract)   * [https://dmtn-150.lsst.io|https://dmtn-150.lsst.io/] (reStructuredText technote)   * [https://dmtn-146.lsst.io|https://dmtn-146.lsst.io/] (LaTeX technote has no content, only an abstract)   * [https://dmtn-139.lsst.io|https://dmtn-139.lsst.io/] (no sectioning)   * [https://dmtn-138.lsst.io (no sectioning)|https://dmtn-138.lsst.io/]   * [https://dmtn-134.lsst.io (no abstract— intentionally)|https://dmtn-134.lsst.io/]   * [https://dmtn-107.lsst.io -> actually fine|https://dmtn-107.lsst.io/]   * [https://dmtn-106.lsst.io|https://dmtn-106.lsst.io/]   * [https://dmtn-105.lsst.io|https://dmtn-105.lsst.io/]   * [https://dmtn-096.lsst.io -> no abstract, but has content.|https://dmtn-096.lsst.io/]   * [https://dmtn-078.lsst.io|https://dmtn-078.lsst.io/]   * [https://dmtn-076.lsst.io|https://dmtn-076.lsst.io/]   * [https://dmtn-075.lsst.io|https://dmtn-075.lsst.io/]   * [https://dmtn-074.lsst.io|https://dmtn-074.lsst.io/]   * [https://dmtn-072.lsst.io (LaTeX technote with no abstract?)|https://dmtn-072.lsst.io/]   * [https://dmtn-065.lsst.io|https://dmtn-065.lsst.io/]   * [https://dmtn-056.lsst.io|https://dmtn-056.lsst.io/]   * [https://dmtn-054.lsst.io|https://dmtn-054.lsst.io/]   * [https://dmtn-052.lsst.io|https://dmtn-052.lsst.io/]   * [https://dmtn-042.lsst.io|https://dmtn-042.lsst.io/]   * [https://dmtn-034.lsst.io|https://dmtn-034.lsst.io/]         In this ticket we'll analyze these ingests, and devise fixes to ensure that these documents appear in the Algolia index. A large part of this work may be to create new diagnostic tools for the ook ingest pipeline.    While working on the ingest code, let's also see if its possible to "bin" LaTeX paragraphs together to result in fewer records.
Answer: 6087.0

User story: "DC2.2i reprocessing with w_2020_28 stack"
Answer: 4328.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: LDM-148 needs updates to flow down changes including:   * LCR-1923 removal of crosstalk correction in Camera Data System   * LCR-2233 image simplification   * LCR-2376 Solar System processing (anticipated)   * DM-18030 LDM-148/LDM-151 consistency   * Operations adopting the term "US Data Facility" and associated FOA   * OCPS naming (DMTN-133)   * Obsolescence of the Calibration Database concept   * Replacement of JupyterLab Aspect with Notebook Aspect (LDM-542)
Answer: 3692.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_07}}. "
Answer: 35987.0

User story: "Some topics in the pointing are publishing values only in sexagesimal notation, which makes them hard to analyze with chronograph. I will update the topics to either replace those informations with float data or publish both together. "
Answer: 54480.0

User story: "The following updates are needed to the DMSR to reflect what DRP will actually provide for coadds:    * Update DMS-REQ-0334 to remove remove the mention of “best-seeing” coadds; per-band deep coadds only will be archived.  * Update DMS-REQ-0281, -0330 to state that DM will deliver software to produce these on-demand and not archive them.    An RFC proposing the changes needed will be submitted"
Answer: 40053.0

User story: "Now that we have the MTCS and ComCam classes in the ts_observatory_control package, we can start writing some basic enable/standby and operations Script for the main telescope.          I will write an initial batch of simple scripts that will allow us to exercise the system."
Answer: 54530.0

User story: Sort out ambiguity between the "slot name" which is the butler-queired detectorName, _i.e._ just S12, and the fully qualified name reported by {{detector.getName()}}.
Answer: 126.0

User story: This ticket is to create a new subcategory, "Statistics Q&A", in the "Science" category on Community.lsst.org, and link it to the LSSTC Slack #issc-ask-the-issc (new topics only). This new subcategory is desired by the Informatics and Statistics Science Collaboration (ISCC) and the details are described in this topic in the "Meta" category:     [https://community.lsst.org/t/proposed-new-category-in-science-statistics-q-a/4227]
Answer: 73.0

User story: "The Speedgoat hardware does not have a rack mount. It is possible for the hardware to sit on a shelf but this is not a permanent solution as we are in an earthquake prone city. This task is cordinating the procurement of the racking hardware for the Speedgoat.     The associated ticket for IT is https://jira.lsstcorp.org/browse/IT-2387"
Answer: 28855.0

User story: "Small portions of the developer guide are out of date - updating the guide to match current reality. "
Answer: 50448.0

User story: "Update to:    dm_CCArchiver 2.2.0    dm_ATArchiver 1.2.0    dm_csc_base 2.2.0    dm_config_cc 1.0.0"
Answer: 4717.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 unit tests of GenericCamera still make use of the old Harness infrastructure. This is not needed anymore. This ticket aims to replace that with a more modern CSC test approach."
Answer: 5659.0

User story: Discussion on slack led to the realization that "it would be completely trivial to patch the old gen2 mapper to make it report the gen3 instrument class".  This would help people bootstrap gen3 repos from gen2 repos.
Answer: 4982.0

User story: "When starting to use the Gen3 repo from the scripts from DM-24300, it became apparent that some things were missing, including (a) the transmission curves (which are now calibrations), and (b) definitions of runs to contain the {{calexp}}, {{src}}, and {{sourceTable_visit}} files.  These should be solvable with a configuration file specifically for the {{testdata_jointcal}} HSC repo."
Answer: 137736.0

User story: "Logging broke on int and stable, and we believe this may be because of the upgrade to the opendisto-es chart (since that also broke logging on Roundtable). Publish the old version of the chart from the SQuaRE charts repo again so that it can be pinned to the previous version and see if that fixes logging."
Answer: 13.0

User story: "Roll out mobu to stable now that -int looks good.  Let's make a version, turn on mobu for the science platform, and pin the version for stable."
Answer: 1250.0

User story: "MultiProFit writes fit results to catalogs but lacks functionality to read them back in, e.g. for plotting. This is a prerequisite for linear deblending."
Answer: 41510.0

User story: "During some test processing on Google we are running into an odd situation where a file exists in S3 that should not exist and an attempt is made to overwrite it. To help debug this add more debug logging messages into s3datastore."
Answer: 1538.0

User story: "Write the user document of MTAOS. The target reader is the operator or scientist. The [ts_athexapod|https://github.com/lsst-ts/ts_athexapod] can be used as an example."
Answer: 30528.0

User story: "Based on ME 20-05 data."
Answer: 108234.0

User story: "Update CCArchiver, ATArchiver, CCOODS and ATOODS         Requirements listed here:         [salsubsystems_attributes.html|https://ts-xml.lsst.io/salsubsystems_attributes.html]"
Answer: 192.0

User story: "In DM-25867 it was noted that the approach to building sphgeom is quite outdated and inefficient in that it creates seperate importable modules for each sphgeom class. A pre-existing test branch from [~<USER> does exist that combines everything into a single import. Resurrect that and see if it works."
Answer: 230.0

User story: "Write the SAL User guide as an RST document."
Answer: 32237.0

User story: "The tables in the Dome CSC documentation are marked up with list-table directives but it is clearer with csv-tables. This ticket is to replace all list-table markup with csv-table."
Answer: 137.0