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: "Support partitioning sqrbot and templatebot topics with a key.    Partitioning Kafka topics lets us have multiple consumers process message streams. For example, activity in one Slack channel won't necessarily slow down responsiveness to another Slack channel. But we want to partition smartly so that activity from a certain channel or user interaction always goes into the same partition, and thus is processed in sequence. We also want to figure out partitioning before deploying at scale because once a topic is partitioned, it's hard to reassign a key to another partition.    For sqrbot's message topics, we want to partition with a key that indicates the Slack channel. For interaction topics, we want to partition with a key that indicates the user who triggered the interaction.    We probably don't want to partition the templatebot topics because that could lead to race conditions (for example, two instances trying to claim the next github repo at the same time)."
Answer: 4583.0

User story: "Begin the documentation on the ts_sal repository. Currently there only exists PDF's outside of the repo. This is to create the SAL User Guide which will exist as a tech note. "
Answer: 76325.0

User story: "There is a rework going on with IT that will require the IP changes of many machines. [~<USER> and I have split the machines on what is most relevant to our work. The table of machines that need IP changes is here [https://confluence.lsstcorp.org/pages/viewpage.action?spaceKey=LTS&title=Auxiliary+Telescope+Temporary+Deployment]"
Answer: 25908.0

User story: "Currently, the objects {{.put()}} by the task are extremely hard to follow, let alone use. Dictionaries are nested very deep, with the final level being tuples (_i.e._ unnamed), which also don't agree with the docstrings, meaning reading the code is the only way to work out what object is actually for what.    I'm not 100% sure whether this is a place to use dataclasses, or just a normal class to hold some of this info, but I think it's got to be one of the two really."
Answer: 17321.0

User story: "MILSESTONES AND SCHEDULE    WBS/Labor/Staffing/Non-labor: change requests, dept/team goal specification, and activity/role description refresh  - following EPO example"
Answer: 139717.0

User story: "LDM-294 should be updated to include the butler work under Tim and Michelle G, with Robert G as product owner."
Answer: 97523.0

User story: "Support the hexapod Test on summit."
Answer: 29899.0

User story: "Support the rotator and CCW test on summit."
Answer: 23403.0

User story: "We have been asked to test Astropy 4 with the stack. Do some builds and see if anything breaks.    To do the install I:  * Made a fresh lsstsw deployment  * Removed astropy  * Updated pytest and pytest-* packages to get v5.3  * Followed instructions on https://github.com/astropy/astropy/wiki/v4.0-RC-testing to install astropy 4.0rc1  * Ran rebuild lsst_distrib"
Answer: 7400.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 tested a stack build with Astropy 4.0rc1 and that resulted in jointcal failing unit tests.    To do the install I:    * Made a fresh lsstsw deployment  * Removed astropy  * Updated pytest and pytest-* packages to get v5.3  * Followed instructions on https://github.com/astropy/astropy/wiki/v4.0-RC-testing to install astropy 4.0rc1  * Ran rebuild lsst_distrib    The failures in jointcal all relate to numerical changes in the final chi2 for astrometry and photometry, e.g:    {code}  AssertionError: 3292.076960636778 != 3292.08 : photometry_final_chi2  {code}    Jointcal passes with the default conda and pytest 5.3."
Answer: 7311.0

User story: "4 unit tests are failing in ts_hexapod v0.2.0. The cause is that I added jitter to the measured positions and didn't relax the comparison tolerances in the tests to accommodate."
Answer: 1252.0

User story: [~<USER> has requested that a "Configurable" column in the Subsystem xml for the ts_xml page.  Please query him for further details.
Answer: 2.0

User story: "A new Configuration attribute should be added to the SALSubsystems.xml file. The values of the attribute should be a single character of Y if a CSC is configurable and N if not."
Answer: 31393.0

User story: "The check version script in the eups package of astropy does not understand release candidate version numbers. Fix it so that  trailing characters are ignored."
Answer: 8830.0

User story: "Ticket to check in against to roll out Nublado and TAP to stable.         For Nublado, this means taking it under helm for the first time.    For TAP, this means running an updated chart that uses vaultsecrets with the same versions."
Answer: 261.0

User story: "We need to put annotations into the Hub, so that we can propagate the Argo tags down to spawned pods/namespaces/etc, so they end up as managed objects."
Answer: 40595.0

User story: "Astroquery is now capable of retrieving Solar System Object data directly via the NASA JPL API. The new interface is tested and an example added to https://github.com/lsst-dm/pysbdb"
Answer: 55203.0

User story: "The error message for {{lsst.pipe.base.connections.ScalarError}} is missing a required {{f}} to properly format the output. I ran into this error, so I'm fixing it."
Answer: 1069.0

User story: "Now that DM-16234 is merged, add writeObjectTable.py transformObjectCatalog.py, and maybe consolidateObjectTable.py  to ci_hsc_gen2 so they get covered."
Answer: 14352.0

User story: "Add tests for the new tag in SALSubsystems.xml to allow specification of which languages we need to build support libraries and tests for.   e.g.    <RuntimeLanguages>cpp,java,python,pydds,labview</RuntimeLanguages>"
Answer: 31476.0

User story: "run the new post-processing tasks with the most recent HSC-RC2 rerun outputs to generate the Object tables in Parquet format"
Answer: 33092.0

User story: "If a task uses a deferredDatasetHandle, it should have the ability to fetch a component of the dataset if the handle wraps a composite object. Add that ability."
Answer: 101956.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: "Misc stuff for whitelight. Since the last ticket included an XML change, we will need to wait for the next XML release to test this CSC on the control network. IN the mean time...   * alarms from the chiller should include a descriptive error message   * when we go to fault, we shouldn't be allowed to leave fault until relevant cooldowns have happened, even if we've lost/regained connection to some devices.   * chiller should run during bulb cooldown   * migrate to salobj 5, which will include some changes to the way simulation mode and connecting to components happen   * general cleanup of debugging code, print statements   * (possibly on this ticket, possibly not) fix automatic chiller reconnect     "
Answer: 137060.0

User story: "Continue problematic process of copying large datasets over multiple  gateway machines to get them to a) NCSA and b) Live as EFD in tucson  "
Answer: 2826.0

User story: "Includes LabVIEW SAL 4.0 upgrade on CCW code."
Answer: 22993.0

User story: "This task is to capture the work done in preparation for the TMA integration on December 2. "
Answer: 1319.0

User story: The following changes are needed in the {{lsst/suit}} code, probably all in {{SUIT.js}}:    # Obtain the {{appIcon}} property in a way which does not leave the loading of the icon relative to the *page URL* (which in the JL extension is generally something like https://lsst-lsp-int.ncsa.illinois.edu/nb/user/<USER>.  # Add to the {{findCorrectLSSTTapService}} function logic this reasoning: first look for "/portal", then, if that is not found, look for "/nb" (and then regardless of which one was found, use the URL up to that point as the base onto which to append the TAP_PATH.  # Display the base URL from which that reasoning was performed, i.e., the value of window.location.href, in the error message dialog.  Text like "Could not infer the location of the TAP service for this LSP instance from the page URL (window.location.href)" would be reasonable.  # Check over the SUIT code for anything else that looks like it might break if loaded in the nested context of the JL Firefly extension.  (I wonder about some of the {{import}} statements at the beginning of the file.)    Note that the issues addressed here affected the behavior of the Firefly JupyterLab extension, which is based on the {{slate}} endpoint,  _even though the TAP search screen is not even referenced at that endpoint_.
Answer: 20166.0

User story: "Now that we have a working nublado helm chart, we can tie it into argocd's application framework.  Tracking that work on this ticket."
Answer: 110.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: "Test data packages with dependencies on code packages lead to the test data package being installed every time a dependency of the code package changes. This can lead to massive bloat of an installed stack for validation packages that can contain gigabytes of data. On my laptop I have 100GB of installed copies of validation_data_decam.    I propose we remove code dependencies from validation_data and afwdata and testdata packages (most testdata packages don't have them but ap_pipe_testdata does). Code packages that use the testdata must themselves have the associated code dependency rather than relying on the obs package to be pulled in with the data package.    It also looks like lsst_ci is installing 1GB of test data each time it is built.  [~<USER> do we need that data to be installed or is it an artifact of the testing performed by that package? Is the idea that you want to examine the output data once installed?"
Answer: 4366.0

User story: "We had to redeploy the EFD on Kubes at the Summit after that {{139.229.162.114}} started showing problems (see IT-1379)"
Answer: 1.0

User story: "While working on DM-21688, it was discovered that certainly plugins in diaCalculationPlugins could be sped up by a factor of ~ 100 by using some of the pandas build in functions.    This ticket will implement these simple changes and compare the speed of using these plugins that of the current stack. The plug insto change are:   * NumDiaSourcesDiaPlugin   * SimpleSourceFlagDiaPlugin   * SigmaDiaPsFlux   * MinMaxDiaPsFlux   * ErrMeanDiaPsFlux   * SigmaDiaTotFlux    This is around 30% of the plugins current implemented. One would naively expect a roughly a 30% decrease in the speed of the diaCalculation step. Functions for skew and percentiles are implemented in Pandas GroupBy/Dataframe processing but don't seem to be highly optimized like the above calculations are."
Answer: 15993.0

User story: "Right now we have a nublado helm chart that works for GKE, and GitHub, but hasn't been tried on -int.  So we need to try it out and make whatever changes to get that ready."
Answer: 6907.0

User story: "In testing, there was an error in the Exception message that was emitted. This will fix that."
Answer: 1447.0

User story: "Have BaseCsc create a topic reader for summaryState and wait for the final Offline when shutting down. That is more robust than the current system which uses a delay.    That said, we still want a delay in order for any final log messages to be output."
Answer: 243737.0

User story: "This is a child of DM-22178, providing a quick fix to remove replicated records from the output of queryDatasets"
Answer: 345795.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: "{{meas_mosaic}} is not required to be setup for the {{pipe_analysis}} scripts. At present, one can still explicitly ask for {{meas_mosaic}} calibrations to be applied with the config {{useMeasMosaic=True}} (default is {{False}}), but should give you a helpful error message if you do ask for it and it’s not setup (i.e. {{import}} is in a {{try:}}).  The {{ups}} table needs to be updated to reflect this."
Answer: 129.0

User story: "The creation of the release candidate 1 for 19.0.0 failed:    [https://ci.lsst.codes/blue/organizations/jenkins/release%2Fofficial-release/detail/official-release/28/pipeline/228]     "
Answer: 18407.0

User story: "Remove all components deprecated in DM-17566 before release 21.0.0."
Answer: 73198.0

User story: "DM-21801 implemented single Gaussian (without PSF convolution) model fitting in MultiProFitTask. This ticket is to implement an option to fit every source in blends with a single Gaussian in MultiProFitTask and test how it performs."
Answer: 181497.0

User story: "Recalculate the percentage of  the WFD survey that will be covered by templates given the reduction in SV commissioning surveys, as well as for all other commissioning data and provide an updated estimate of how much of the sky could be covered with templates from the new commissioning data. Update DMTN-107 with new estimates.     "
Answer: 266327.0

User story: "Platforms covered by this validation:   * MacOS (Mojave)   * Linux RedHat-Centos 6.9   * Linux RedHat-Centos 7.6   * Linux Debian-Ubuntu 18.04   * Linux Debian-Ubuntu 16.04    This list may change is new platform releases are available."
Answer: 24542.0

User story: "The term MOPS has been deprecated in favour of Solar System Processing (SSP). The glossary should be updated to reflect this. "
Answer: 30712.0

User story: "Add the environment variable IIP_CREDENTIAL_DIR which, if it exists, will be used instead of the $HOME/.lsst"
Answer: 877.0

User story: "It is November? Time to reprocess the full HiTS dataset with ap_pipe. Stick with the higher-res templates until DM-21330 is complete."
Answer: 23211.0

User story: "PyArrow is in our shared stack on lsst-dev and LSP. However, the version in the stack depends on a newer boost than our eups boost.  In order to unblock DM-16234, we are skipping the unittests that require pyarrow, unless pyarrow can be imported. This way it still gets test coverage on the linux Jenkins nodes.     Remove these {{skipUnless}}'s when we can import pyarrow on a macos build stack. "
Answer: 216205.0

User story: "To convert pipe_analysis to gen 3 the butler calls need to be taken out of the lower level functions. As a first step move all the plotting related IO into runDataRef."
Answer: 278334.0

User story: "Refer to LIT-292 for the substance."
Answer: 44316.0

User story: "As an initial setup towards Gen3-ification of the {{pipe_analysis}} scripts, audit all usage of {{butler.get()}} to get a feeling for how easy it will be to convert them to Gen3-land."
Answer: 3107.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: "Previously, ACK_ID was not sent from the ATArchiver to the Forwarder in its association message.  It will be as part of DM-22239, so the Forwarder should add this to to the build_associated_ack method as part of the message.         This has to be done with the work I'm doing in conjunction with DM-22239"
Answer: 8876.0

User story: "There exists a race condition where a flag for an acknowledgment can get reset after it's been cleared if messages come in too quickly."
Answer: 4042.0

User story: "The schedule for releasing DPs as presented at PCW2019 should be integrated into   * LSO-011  * https://confluence.lsstcorp.org/display/LSSTCOM/Commissioning+Data+Delivery+Dates?focusedCommentId=120784827#comment-120784827"
Answer: 12420.0

User story: "Connect the Kiloarc lamp to ADAM    read the status lights on the KiloArc, which will be published as telemetry    verify that hitting the e-stop button results in an error status signal from Kiloarc, and this sends the CSC to fault state."
Answer: 24106.0

User story: "A couple of our packages are importing Mapping or Iterable from collections rather than collections.abc. Fix these."
Answer: 4243.0

User story: "There are some packages in lsst_distrib that still use python future to support python 2.7. In some cases these are residual table file mentions or a handful of imports of past.builtins. Clean these up."
Answer: 9856.0

User story: "astrometry_net_data is an optional dependency of pipe_tasks. The relevant methods from pipe_tasks ({{setConfigFromEups}} are currently used in {{lsst_ci}} and {{testdata_jointcal}}.    The testdata_jointcal usage is purely from a config file created from a dump which includes imports of every lsst package that was loaded when the config was written. This is trivial to fix.  The lsst_ci usage includes code to set processCcd configurations that I believe are no longer relevant since we are not use astrometry_net any more.  "
Answer: 248860.0

User story: "With the move to InfluxDB, the column number and byte size limitations imposed by MySQL are removed.  This means the current suite of tests to very topics don't exceed those limitation are no longer necessary.  Additionally, InfluxDB introduces a new set of Reserved Words, see DM-22216.    This ticket tracks the work needed to remove the topic size tests, update the Reserved Words tests, as well as acts as documentation for this change.         The SAL Constraints documentation will also need to be updated:    [https://ts-xml.lsst.io/v/tickets-dm-20234/sal_constraints_and_recommendations.html#sal-topic-sizes]"
Answer: 50331.0

User story: "Testing the XML files as well-formatted and against a schema file requires an additional python tool, probably lxml.  This task covers the work necessary to update the docker image to install this tool and write the tests and test generator scripts, as well as implement those tests in the build."
Answer: 51891.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: "There was a recent build failure caused by a Telemetry topic containing a duplicate attribute.  Add tests to check for that condition."
Answer: 35876.0

User story: Andrés reports that he can't run measurePhotonTransferCurve.py, with the failure reporting:  {quote}  RuntimeError: Unable to retrieve bias for DataId(initialdata={'detector': 96, 'filter': 'SDSSi+ND_OD0.01', 'visit': 2019101200239}, tag=set()): no such column: raftName.  {quote}    The problem's deep down in Butler Gen2, and the simplest "fix" is to lookup the {{raftName}} (and {{detectorName}}) before trying to run the ISR.  This hack should not be needed in Gen3;  it's equivalent to the calls to {{CalibTask.addMissingKeys()}}.
Answer: 5607.0

User story: "In preparation for the official rerun for week 46 of RC2, we will like to do a test the run of RC2 using week 42 in order to debug scripts."
Answer: 12981.0

User story: "Reprocess the HSC RC2 dataset, as defined in DM-11345, using Stack w_2019_46.    pipe_drivers / pipe_tasks   # makeSkyMap.py   # singleFrameDriver.py   # jointcal   # skyCorrection.py   # coaddDriver.py   # multiBandDriver.py    pipe_analysis   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    qa_explorer   # matchVisits.py    validate_drp   # matchedVisitMetrics.py   # validateDrp.py   # reportPerformance.py    Upload the validate_drp metrics (json files) to SQuaSH:   # dispatch_verify.py    Also upload the json file generated by colorAnalysis to SQuaSH:   # dispatch_verify.py      Also added missing tasks:    * writeObjectTable.py  * transformObjectCatalog.py  * consolidateObjectTable.py"
Answer: 49144.0

User story: "There is a new pipeline for processCcd and the goal is to add defaults to the configs"
Answer: 27595.0

User story: "Like the title says.  Hopefully in time for bootcamp."
Answer: 42822.0

User story: "Reprocess the HSC RC2 dataset, as defined in DM-11345, using Stack w_2019_42.     pipe_drivers / pipe_tasks  # makeSkyMap.py  # singleFrameDriver.py  # jointcal  # skyCorrection.py  # coaddDriver.py    # multiBandDriver.py    pipe_analysis   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    qa_explorer  # matchVisits.py     validate_drp   # matchedVisitMetrics.py   # validateDrp.py   # reportPerformance.py    Upload the validate_drp metrics (json files) to SQuaSH:   # dispatch_verify.py    Also upload the json file generated by colorAnalysis to SQuaSH:  # dispatch_verify.py  "
Answer: 1173.0

User story: "To use the k8s vault secrets operator we will need to restructure the secret paths.  Document the style to use with k8s vault secrets operator."
Answer: 15.0

User story: "It would be useful to bundle all of the call to *.sl files per task into a single bash files that executes them."
Answer: 39920.0

User story: "See [https://lsstc.slack.com/archives/C2JPL2DGD/p1573657708086900]    More pair-coding between [~<USER> and [~<USER>."
Answer: 34878.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: "INRIArequests a new Watcher command to show all rules. This is a great idea as it allows the user interface to come up to speed when it connects, without relying on trying to read historical data."
Answer: 2.0

User story: "INRIA has requested that the ConfiguredSeverities rule loop forever.    Probably that should be the only choice, but look into alternatives, such as providing the number of iterations.    Updating the code for the rule is simple. Updating the unit test may take a bit more work."
Answer: 4.0

User story: "create conda recipes for dm_ATArchiver and dm_csc_base"
Answer: 8451.0

User story: "We often iterate over multiple values in tests. We have been writing this iteration explicitly, which is annoying (for classes, this involves subclassing; for methods, this means the values that caused a failure aren't clear unless special efforts are made). Some decorators will help!"
Answer: 8863.0

User story: "The MQTT based generated list of HVAC parameters, will be verified for completeness by comparing with the Windows server list and, then proceed with the final generation of XML telemetry, alarms and commands files."
Answer: 18491.0

User story: "DM-21997 has plots comparing fit parameters for nominally isolated sources in COSMOS. Some of the most discrepant values come from seemingly isolated and reasonably bright galaxies that somehow get tiny sizes and faint fluxes in HST. I suspect that the initialization is awry; hopefully it's as simple as the centroid being off."
Answer: 123966.0

User story: "Following the LOY1 alerts meeting, DMTN should be updated to include:   * references to the official pre-operation data previews  * a clear statement that we will use templates from the DPs will be used to generated LOY1 alerts. "
Answer: 222386.0

User story: "Will be deprecated on DM-22070, which will probably make it into 19.0, so we'll assume for now that this can be removed after 19.0 and must be removed before 20.0."
Answer: 246766.0

User story: "I think that DM-18610 changed the default value for {{amplifier.getSuspectLevel()}} from Nan to zero, and this means that isr now masks out all amps built from yaml cameras.    This could be fixed many ways - getting all yaml cameras to specify it, getting the yaml camera builder to default it to nan in obs_base, having a failsafe in isr, because zero is never a legit value (if all values above zero are suspect you've got some serious problems that we can't help with, after all).    Some of these are more sensible than others, and yet more probably exist. I'm about to go on vacation so can't sort this out right now, but it seems quite urgent to me."
Answer: 430.0

User story: "Take a visit that we have, and which Jérémy has analysed, and perform end-to-end extraction, getting roughly comparable results, _i.e._ something which looks like a legit extracted spectrum.    It doesn't have to be perfect (or even very good) yet, but something that isn't garbage-in, garbage-out, showing that the interface is working properly."
Answer: 442517.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: "File tickets and annotate the Object.yaml file per discussion with [~<USER>, [~<USER>, and [~<USER>.     Need branch number to update Object.yaml."
Answer: 429584.0

User story: "Check that the weekly build chosen as the starting point for the 19.0.0 release is valid.    This is in order to avoid to start the release process and then discover that the weekly has regressions that are not acceptable in the release."
Answer: 11377.0

User story: "Sometimes it is useful to be able to control the plot limits for comparison purposes. Add this functionality to the fakes plots."
Answer: 4133.0

User story: "Try to get the landing page and the TAP service to be deployed by argo cd, including getting the secrets figured out, and be able to be triggered by commit."
Answer: 15866.0

User story: "Task covering work needed to learn how to test Rotator software with Andy.    This task will also cover Eric's time spent on the summit helping with assembly and test."
Answer: 19740.0

User story: Running a query like    {code}  list(butler.registry.queryDatasets("calexp", collections=["shared/ci_hsc_output"],                                     skymap="discrete/ci_hsc", tract=0, patch=70))  {code}    produces many duplicate records for unclear reasons (they're not from having multiple collections, so {{deduplicate}} doesn't help).  Try to fix this, or at least document when duplicate results must be expected.
Answer: 358977.0

User story: "We don't have a good way for the Hub to signal it needs an auth refresh."
Answer: 115.0

User story: "Attend the DM boot camp 2019. The agenda is [here|https://community.lsst.org/t/dm-boot-camp-2019/3887].    I am interested in:    1. System Architecture (2:30 EST, 12:30 PM in Tucson) at 11/12    2. All courses at 11/13 (begin from 2:00 EST, 12:00 PM in Tucson)    The meeting room will be in the Workroom (229) for this meeting.         Lectures will be remotely streamed: [https://princeton.zoom.us/j/5752451825]"
Answer: 11930.0

User story: "I don't actually know how to pass a datetime into a query expression, or if that's possible.  [~<USER>, could you add support if it's missing, or document it if it's present?         We may want to make support for this explicit (via built-in datetime or astropy time calls), to insulate us from changes to the database type used for datetimes (e.g. DM-15890)."
Answer: 203859.0

User story: "Add documentation support to repo. Fix docstrings to comply with numpydoc format."
Answer: 116916.0

User story: "Add Jenkinsfile."
Answer: 116916.0

User story: "Finish implementing CSC. Add mock controller and add unit tests."
Answer: 116917.0

User story: "- Update the milestones repository with data extracted from PMCS (/)   - Update LDM-503, LDM-564, images repository (/)   - Update milestone dates loaded into Jira (/)   - Update skeleton November 2019 monthly report (/)   - Audit and update https://confluence.lsstcorp.org/display/DM/DM+PMCS+Update+Requests"
Answer: 50789.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: "PipelineTask execution should automatically write a metadata dataset for each Quantum.  We want that to appear in the QuantumGraph as well, so downstream PipelineTasks can use these as inputs.     "
Answer: 45802.0

User story: "DM-21801 implemented a single Gaussian, no-PSF fit mode for MultiProFitTask. This ticket will validate single-band measurements against the various already-implemented (e.g. SDSS) moment measurements in HSC UDeep (COSMOS)."
Answer: 215774.0

User story: "This task covers the time needed to complete the XML test conversion.  See DM-22032."
Answer: 44500.0

User story: "After updating the XML tests, it was found that the MTVMS_Telemetry.xml file defines three topics that do not conform to naming standards as defined in    [SAL_Recommendations|https://ts-xml.lsst.io/sal_constraints_and_recommendations.html] page.    The topics MTVMS_M1M3, MTVMS_TMA and MTVMS_M2 should be renamed to MTVMS_m1m3, MTVMS_tma (or MTVMS_mtmount) and MTVMS_m2, respectively."
Answer: 44657.0

User story: "After updating the XML tests, it was found that the EFD_Telemetry.xml file defines a topic that does not conform to naming standards as defined in    [SAL_Recommendations|https://ts-xml.lsst.io/sal_constraints_and_recommendations.html] page.    The topics EFD_Summary should be renamed to EFD_summary, with a lowercase s."
Answer: 20072.0

User story: "After updating the XML tests, it was found that the Dome_Telemetry.xml file defines several topics that do not conform to naming standards as defined in    [SAL_Recommendations|https://ts-xml.lsst.io/sal_constraints_and_recommendations.html] page.    The topics are Dome_DomeADB_status, Dome_DomeAPS_status, Dome_DomeLouvers_status, Dome_DomeLWS_status, Dome_DomeMONCS_status and Dome_DomeTHCS_status.    Suggested fix is to name them    Dome_domeADB_status, Dome_domeAPS_status, Dome_domeLouvers_status, Dome_domeLWS_status, Dome_domeMONCS_status and Dome_domeTHCS_statu, instead."
Answer: 186942.0

User story: "Draft the hexapod test plan in SAL level.    The followings are suggested by [~<USER>:       Informally I would say that the same tests we proposed as for the rotator would be relevant here:  * Check that the state transition commands work as we think they were coded to (not exactly as per our standards). In particular I think clearError will send the CSC to OFFLINE/PUBLISH_ONLY, though I would love to be wrong about that.  * Check that the motion commands work as expected — to within a tolerance we can reasonably measure. I think trying to measure with high accuracy will be beneficial at some point (to understand what the hexapod is truly capable of), but I think our initial focus should be on sanity checking motion rather than trying to measure precision of motion."
Answer: 14446.0

User story: "The {{T_AG}} header (from which we set the {{autoguider}} field in the registry) isn't always set, which leads to ingest breaking."
Answer: 76.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: "At the current moment the {{PixelAreaBoundedField}} (and the {{PixelScaleBoundedField}} that it is replacing, see RFC-644) are too slow (by a couple orders of magnitude) to use in coaddition via a {{PhotoCalib}}.  [~<USER> says that this is a non-trivial fix (DM-22071).    However, for many purposes, it is possible to use a {{ChebyshevBoundedField}} to approximate a {{PixelAreaBoundedField}} (or other {{BoundedField}}).  Provided the field to approximate is smooth, preliminary tests show that (e.g.) a typical HSC WCS can be approximated at the 1e-7 level with plenty of speed, which is sufficient for use in a {{PhotoCalib}}.      This ticket is to add a python-only {{approxBoundedField}} method to {{ChebyshevBoundedField}}.  Tests will be written by approximating {{PixelAreaBoundedField}} (the primary use case) so this requires DM-22070 to be completed first."
Answer: 38977.0

User story: "This task will test the new CSC codes by Russell to see why the rotator cRIO in SLAC can not receive the command. This is a follow-up task of DM-21951, DM-22104, DM-22066, and DM-22067."
Answer: 44498.0

User story: "This is a continued task of phase 1: DM-22144."
Answer: 20244.0

User story: "This task begins to update the M2 control system to the latest SAL version. The original SAL version is 3.5.1. On the summit, only the telemetry and event can work for M2 control system. It can not be commanded by the SAL commands. This task will try to fix this bug as well."
Answer: 14411.0

User story: "Backup the data from the M1M3 test campaigns and copy to NCSA and   make available access to the  live M1M3 EFD instance (mysql) from Tucson"
Answer: 46967.0

User story: "Add a tag to the SALSubsystems.xml to allow specification of which languages we need to build support libraries and tests for.  e.g.     <Languages>cpp,java,python,pydds,labview</Languages>  "
Answer: 25440.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 developed a branch of scarlet that implements a proximal ADAM algorithm to calculate gradients without specifying a step size. This algorithm offers significantly improved performance on the test cases run so far, so this ticket is to get a branch of {{meas_extensions_scarlet}} to work with the ADAM implementation so that it can be included with the other tests being run by [~<USER> and myself."
Answer: 102274.0

User story: "Following on DM-21493, create a Roundtable deployment for the Strimzi Schema Registry operator (built in DM-21493) that is managed by Argo CD.    * Argo CD deployment  * Ensure the client ACLs are correct given https://www.confluent.io/blog/securing-confluent-schema-registry-apache-kafka/"
Answer: 155.0

User story: "Write the Dockerfile for the ATArchiver based on the deployment container from T&S."
Answer: 38975.0

User story: "Prepare and deliver a tutorial on how to find documentation and how to write documentation for the November 2019 DM Bootcamp."
Answer: 8773.0

User story: "As we go to a wider variety of platforms and k8s versions, we're finding some issues.  Tracking fixing them here."
Answer: 5981.0

User story: "The transition to ts_salobj has been fully vetted and therefore there is no need to continue carrying salpytools and its dependencies into the HeaderService. Therefore all  salpytools dependencies need to be removed from the HeaderService."
Answer: 10353.0

User story: "new versions:   {code}ts_sal 4.0.0 ,  ts_xml 4.4.1 ,  ts_salobj 5.0.0  ts_idl 1.0.0{code}  have been released. These new version rpms/repo and the accompanying new meta-data need to be tested at the NCSA Test Stand. The test should include {{ATCamera}}, {{ATArchiver}} and {{ATHeaderService}}.    "
Answer: 16260.0

User story: "Deploy versions:       {code}   ts_sal 4.0.0 ,    ts_xml 4.4.1 ,    ts_salobj 5.0.0    ts_idl 1.0.0  {code}      on the NCSA Test Stand and create docker images for ATHeaderService"
Answer: 12.0

User story: "There's a memory leak in pyarrow 0.13.1 when reading/writing Pandas to parquet.    https://github.com/apache/arrow/issues/2624    This is fixed in 0.15.1.    I'd like to suggest upgrading the required pyarrow in the stack to at least 0.15.1.    [~<USER> What do you think?"
Answer: 147209.0

User story: "This is the branch where I'll update my personal notebooks in ts_notebooks based on the observing run on 2019-11-06 and for 2019-12-07"
Answer: 50836.0

User story: The INRIA group requested a command that will show all currently active alarms (those not in the nominal state). This will allow the Watcher user interface to "catch up" when it starts.    They also requested that the ConfiguredSeverities cycle forever.
Answer: 23152.0

User story: "Current forwarder is installed using rpm. This ticket explores steps necessary to dockerize dm_forwarder."
Answer: 22983.0

User story: "In DM-21797 we implemented TAB WCS but there are some places in the code that duplicate the table and column names. Replace these with a single source of truth."
Answer: 154.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: "Fitsfile generated by Forwarder has differing segment orders to fitsfile generated by Tony. The readout order is determined by LCA-13501 and this ticket addresses fix for forwarder."
Answer: 1088.0

User story: "The default method I implemented to compute non-adaptive moments to initialize Gaussian in MultiProFit worked reasonably well for HSC but not so much for large HST images, or in general on noise-dominated images, where the moments are skewed by outliers at large radii. This ticket will tweak the existing options to make non-adaptive moments more robust by adding options for (essentially) sigma-clipping and/or selecting only contiguous above-threshold pixels."
Answer: 40050.0

User story: "SAL_VERSION=4.0.0  SALOBJ_VERSION=5.0.0  XML_VERSION=4.4.1  IDL_VERSION=1.0.0        "
Answer: 51384.0

User story: "Revamp athexapod CSC for Salobj 4/5 and ConfigurableCSC support."
Answer: 29072.0

User story: "The nightly from last night failed because we updated newinstall.sh without also bumping the miniconda version in the tarball builds.  I believe it is as simple as adding {{4.7.10}} as the left most choice in [this line|https://github.com/lsst-dm/jenkins-dm-jobs/blob/master/jobs/tarball.groovy#L26]."
Answer: 121.0

User story: "Any assembly/testing needed at the summit for the Camera Hex/Rot to be ready for the individual functional testing as well as the Camera Rot/CCW/Camera Cart integration testing.  Will be working in tandem with IT (IT-1145) in regards to this process.    Will probably need switches and/or UPS from IT to complete this task."
Answer: 28726.0

User story: "DM-21738 showed that the correct way to write a copyright statement for AURA is:    {code}  Association of Universities for Research in Astronomy, Inc. (AURA)  {code}    DM-21738 is updating the Developer Guide; this ticket updates copyright statement templates in https://github.com/lsst/templates"
Answer: 289.0

User story: "Following on DM-22099, the templatebot and templatebot-aide Kafka clients need to be adapted to work with the Kakfa cluster on Roundtable:    # Add TLS configuration to work with the TLS-secured Kafka.  # Adapt schema naming following DM-22099's work.  # Do not create topics within the client; rather use topics pre-created and configured with Strimzi."
Answer: 35513.0

User story: "Roundtable has a Kafka cluster, so we can now move the sqrbot-jr Slack bot deployment to this cluster. However, there are some adjustments we need to make first:    # Add TLS authentication to the Kafka client since the Events Kafka cluster in Roundtable requires all clients to authenticate over TLS.  # Make the topic names configurations and do not create topics on startup; in Roundtable topics are pre-created.  # Adapt the Schema names to be compatible with Kafka connect."
Answer: 35516.0

User story: "Present the LSP to the TVS Science Platform Task Force in a Telecon on  5 Nov 2019 09:00 AM Pacific Time"
Answer: 42659.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 sizing model is conservative with regard to scaling compute and storage by input data (approximately proportional to ForcedSources) and sky area (approximately proportional to Objects).  Compare with previous numbers for HSC and attempt to generate a more accurate model."
Answer: 9996.0

User story: "In this ticket, we'll deploy Argo CD to a new GKE cluster following the [Getting Started |https://argoproj.github.io/argo-cd/getting_started/] documentation. We'll play around with the Argo CD application concept and define the structure for the Kubernetes deployment configuration to accommodate the different EFD environments (dev, lab, summit, ldf)."
Answer: 11602.0

User story: "SAL 4.0.0 release"
Answer: 11471.0

User story: "Deploy the new landing-page with the helm chart, and fix anything that crops up."
Answer: 73.0

User story: "As discussed at DMLT F2F 2019-10-28, LDM-503 needs to be updated to reflect policy around which requirements can be verified within the DM subsystem, based on available data. "
Answer: 334495.0

User story: "Incorporate comments / updates following discussions at [DMLT F2F 2-19-10-28|https://confluence.lsstcorp.org/display/DM/DM+Leadership+Team+Face-to-Face+Meeting%2C+2019-10-28+to+30]"
Answer: 284011.0

User story: "It would be useful if some of the fakes plotting code was refactored to make the actual plotting bit more easily usable."
Answer: 12759.0

User story: "The 2014 Decam HiTS data we are currently using for ap_pipe and to evaluate the performance of the DCR model has worse seeing and not as even distribution of airmasses as the 2015 data. As a result, using the 2015 data as a template to run ap_pipe on the 2014 may work much better than using the 2014 data as a template for 2015, as we are currently doing. This ticket is to process the 2015 data through to generate DCR models, and run ap_pipe on the 2014 data twice, once using standard coadd templates and once using the DCR templates."
Answer: 144372.0

User story: "Attended the joint TVS + SMWLV meeting and hack days, Oct 14-18. Presented a talk on crowded field processing plans, and solicited input and ideas for improvements on that plan."
Answer: 11441.0

User story: "An oversight in DM-18610 prevents linearity type and coefficients from being read correctly from FITS.  Fix is trivial."
Answer: 1558.0

User story: "Setup the Linux laptop that will be used on the summit for the test."
Answer: 5761.0

User story: "Ensure that Templatebot checks if the templates repo is updated (a new commit to a branch, for example), before starting any processing request."
Answer: 1283.0

User story: "Port Gen2's write-only support for writing matplotlib Figures to (at least) PNG to Gen3."
Answer: 20747.0

User story: "The current situation including encryption for north america is covered   in DMTN-108 ([https://dmtn-108.lsst.io/]) - this should be updated to    cover Europe to keep this all in one place."
Answer: 174057.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: "PixelScaleBoundedField is a bit inconvenient to use in full-focal-plane contexts (the only contexts in which we expect to use it) because it normalizes by the area of the origin pixel in order to yield a unitless quantity, and that origin pixel is a per-CCD quantity, resulting in a discontinuous combined field over the focal plane.    Duplicate and adjust it to define a new PixelAreaBoundedField class; I'll RFC deprecating and removing the original in a separate RFC to avoid worrying about code duplication in the interim.  Also make sure the new class is persistable (the original is not).     "
Answer: 16267.0

User story: "[~<USER> would like a BoundedField implementation that simply multiplies two other BoundedFields, and I've long said I'll add it as soon as it becomes a pressing need - that kind of composition is something I've always had in mind for BoundedField but hadn't prioritized.     "
Answer: 3971.0

User story: "In order to support butler I/O for HSC's bespoke stray-light correction files, we should:   * Add an abstract base class for camera-generic stray light correction information to ip_isr, and make the implementation in obs_subaru inherit from it.   * Add a StorageClass to daf_butler for the abstract base class.   * Add a formatter to obs_subaru for the concrete HSC class.   * Add code and possibly a script to ingest the stray light data into a Gen3 repository."
Answer: 3723.0

User story: "In rotator testing at SLAC DM-21951 we discovered that commands from the Python CSC were being ignored.    This ticket is to diagnose the problem. I propose to make use the fake cRIO controller in the ts_rotator package to talk to the real vendor's CSC, monitor the data in the commands sent by that CSC, and compare it to the data in the commands sent by the Python CSC."
Answer: 15649.0

User story: "In SLAC rotator testing today we discovered several issues that need fixing:    * The {{counter}} field was the wrong type for Command and Header (should be uint, not ushort).  * The rotator and hexapod CSCs have no heartbeat output. This strongly suggests we should have a base class for both CSCs.  * The rotator commander outputs too much noise because of encoder jitter (not a surprise). This is likely an issue for the hexapod commander as well.    Note that we still were not able to command the rotator: the commands were ignored. Fixing that is a different ticket.    I have attached a file that shows some binary telemetry data we read from the rotator, and how the Python code parses it."
Answer: 15709.0

User story: "DM-19843 implemented using an analytic Jacobian for least squares fits of Gaussian mixture models in MultiProFit. I made a regrettable choice to re-use the output argument in the C++ code, so that if you compute the Jacobian, the code cannot write out the model that it computes. This ticket is to allow for outputting both if desired."
Answer: 48830.0

User story: "Port formatters for Parquet files to Gen3, including support for lazy loading of columns."
Answer: 28526.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "This task is to remove the developers that are no longer on the team from the ts_xml salsusbsystems table.     I imagine it will take a few iterations before completing the table, therefore it makes more sense to update the table now having no information rather than misinformation.    Along with removing old developers, I will focus on updating these rows."
Answer: 60138.0

User story: "Just realized that ATMonochromator needs to be upgraded to salobj 4 and to become a configurable CSC."
Answer: 96437.0

User story: "implement the last few white light features, including reading warning/alarm settings from config file and applying  them, going to fault in case of a lost connection to chiller, telemetry publishing"
Answer: 36020.0

User story: "The main goal of the effort is to improve the deployment & management scripts to support the new Ingest system at {{lsp-int}} (former {{PDAC}})  "
Answer: 66.0

User story: "When files were rebased and merged, these variables were left as re-declared."
Answer: 31718.0

User story: "Implements RFC-642"
Answer: 29023.0

User story: "Implement RFC-641."
Answer: 2281.0

User story: "The RobotFramework tests of the XML are essentially being used as XML unit tests.  But this implementation is all wrong for unit tests; unit tests should coexist with the source code (be in the same repo).  These tests are maintained along with the source code.  Therefore, it makes sense to convert the RF tests into a format that can be put into the ts_xml repo along with the XML files themselves.  Additionally, the format should be broadly acceptable to all XML maintainers.          While I think RF is a great tool, the effort to bring everyone up to speed is greater than the effort to put them into python.  I will convert the tests into pure python unit tests, and then transfer maintenance responsibility to ALL XML users."
Answer: 18745.0

User story: "Add the dependencies for the QA dashboard to the shared stack.  These are listed in this environment file here: https://github.com/Quansight/lsst_dashboard/blob/master/environment.yml    Packages in that file for documentation (e.g., sphinx, nbsite, recommonmark, and sphinx_rtd_theme) are not required, and the only specific version requirement we are aware of is panel >= 0.6.3."
Answer: 169686.0

User story: "Test run just to know how things work."
Answer: 11733.0

User story: "Update ctrl_bps to work with newer version of networkx    Example error when trying to use version 2.4 instead of 2.3:  AttributeError: 'DiGraph' object has no attribute 'node'"
Answer: 1721.0

User story: "Present the strategy outlined in LSE-459 to the science collaborations at a PST talk 20 Nov.   LSE-459 should be reviewed and agreed by the DM-SST/PST/SAC prior to giving this talk"
Answer: 51815.0