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: The ATDome software vendor's manual needs a number of improvements. This ticket is intended to be a place to accumulate them and then fix them.    This is only for improvements to the manual, not improvements to the software.  h2. Issues   * A command may be rejected by returning "Command Error". Note that this only occurs if the command is unrecognized or has invalid parameters (according to Paul Lotz's analysis of the code). It does not occur if the command is invalid in the current state; when that happens the command is silently ignored. Here is an example:  {quote}> invalidcommad   Command Error   >  {quote}   * The list of commands is missing some that are output by HELP (these missing commands should be added to the list and also have further explanation added below the list):  {quote}t RD Set reverse direction motion delay (t=seconds,0<=t<6)   t AT Set Azimuth motion timeout (t=seconds,120<=t<600)   t RS Set Rain / Cloud activate delay (t=seconds,1<=t<10)   t DT Set Door Move Timeout (t=seconds,30<=t<=600)   AEP AZ Encoder Count Positive   AEN AZ Encoder Count Negative  {quote}   * Line 4 of status can start with {{POSN}} or {{HOME}}; the manual says {{Posn}}.   * Line 5 of status is documented to always start with {{RL}} or {{RR}} but it actually starts with {{--}} until the first rotation occurs.   * Long status is 25 lines, not 23. "Azimuth Move Timeout" and "Door Move Timeout" are missing from the manual. Here is an example:  {quote}MAIN AJAR 010   DROP SHUT 000   [OFF] 00   POSN 302.04   – 004   Emergency Stop Active: 0   SCB radio link OK: 1   Home Azimuth: 90.00   High Speed (degrees): 5.00   Coast (degrees): 0.50   Tolerance (degrees): 1.00   Encoder Counts per 360: 4018143232   Encoder Counts: 78711697570   Last Azimuth GoTo: 0.00   Azimuth Move Timeout (secs): 120 (missing from the manual)   Rain-Snow enabled: 0   Cloud Sensor enabled: 1   Watchdog Reset Time: 600   Dropout Timer: 5   Reverse Delay: 5   Main Door Encoder Closed: 731681806   Main Door Encoder Opened: 28121547241   Dropout Encoder Closed: 5669832785   Dropout Encoder Opened: 5711691005   Door Move Timeout (secs): 360 (missing from the manual)  {quote}   * Every time we connect to the controller we get the following output:  {quote}ACE Main Box   >  {quote}    h2. Requested clarifications:   * When is line 4 of status {{HOME}}? During homing, when done homing, or whenever the dome happens to be at the home position? Note that at present the home switch is not functional, so the rule is clearly not "when the home switch is depressed".   * State that one can send a new azimuth position while the dome is still moving (and the new target position supersedes the old, as you might expect).   * State that the controller always outputs ">" when it is ready for a command.   * Clarify which direction is "right" (increasing azimuth?)   * What is the output code while homing? Clearly the homing bit is set, but what about the two azimuth rotation bits (one for right, one for left)?
Answer: 126874.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "As part of Nick's visit, he discovered that the laser suffers an unknown power degregation by 10 percent that appears to correspond with one of the temperature registers starting to run hot.     The vendor has asked us to run the test with a data dump from the laser before and after the test."
Answer: 14319.0

User story: "Test take narrowband data script with Patrick down in lab.     Updated Patrick's script to write a csv file and download fits files corresponding to the appropriate data.    Help Patrick configure parameters of script."
Answer: 10088.0

User story: "Several CSC test are repeated in most packages that use ts_salobj, including:  * Check standard summary state transition commands  * Check that the bin.src script that runs the CSC works    Write these tests in ts_salobj in a way that they can be used by other packages, e.g. by providing a base class for CSC unit tests.    Also add documentation with suggestions for how to test CSCs, SAL components and Scripts.    Also convert at least one other package to make sure the new code is usable."
Answer: 403780.0

User story: "The Electrometer CSC was one of the first CSCs re-written in python, prior to standardization of the CSC format. Although currently functional, it needs to be modernized to bring it in-line with current code standards."
Answer: 131072.0

User story: "We have a test case, LVV-T768, that tries to verify that code is installable in the nublado system.  I would like a stub pip package that we control that is essentially a no op (maybe it prints some amusing message).  The name will be {{sqre-pip_install_test}}."
Answer: 10124.0

User story: "Covers all communications for the workshop including announcements on community, LSST digest, etc"
Answer: 142948.0

User story: "MultiProFit supports Gaussian mixture models, which can be fit using linear fitters (DM-18105), e.g. after initializing from a Sersic multi-Gaussian approximation. This implements an intermediate method of fitting the sizes of Gaussian mixture models by keeping the ratios of the sizes of groups of Gaussians fixed while fitting a single multiplicative scale radius, analogous to the Sersic profile's effective radius."
Answer: 57710.0

User story: "Investigate why PSF model sizes don't match measured moments for stars, and particularly whether the mismatch is consistent with noise bias."
Answer: 227643.0

User story: "Provide abstract for the AMCL meeting "
Answer: 38021.0

User story: "Coordinate with the workshop SOC to propose invited speakers covering all workshop topics"
Answer: 66719.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Currently the name associated with a Posix data store includes the path to the directory root. This is usually a full path and the name is used to indicate to the butler registry that the named datastore has a particular dataset.    If a datastore is moved to another location the name will change and the config file must be edited to reflect the new root location.  This will not update the name associated with the datasets already known to the registry.  Root can be a relative path but it is relative to the person using the butler and not relative to the butler directory.    Things sort of work by luck at the moment since butler never calls {{getDatasetLocations}}.    The posix datastore config also specifies a name for the {{records.table}} which must be unique. It is not related to the name at all and I wonder if it would be easier if it was.    For this ticket I will:    * Investigate specifying a {{name}} field in posix datastore config and using that instead of the root.  * Consider allowing root to be specified relative to butler root to allow the simple case of relocating a posix datastore with butler sqlite registry.  * Consider deriving the name of table.records from datastore name without having to specify a unique string in two places.    Opinions welcomed."
Answer: 8939.0

User story: "Shadowing can happen if you add en explicit translator method and forget to remove it from the constant or trivial mappings list. Check for this scenario and warn.  Also check that const/trivial methods are not being inherited from a parent and overriding the versions defined in the current class."
Answer: 6030.0

User story: "Manage column name aliasing in the Czar so that columns with the same name are disambiguated (N.B. the worker does not include database or table name with the column name when returning results to the Czar). This will allow the columns to coexist in the same results table. Then the results query that gets passed to the lua plugin must contain column aliases that restore the column names to what would be expected by the user (reambiguation, if you will)."
Answer: 171554.0

User story: "Modify the lua plugin so that the SELECT statement used to return results to workers is entirely generated by the Qserv C++ code."
Answer: 31792.0

User story: "Precreate the results table in qserv and populate it with results returned by workers, per design after DM-18568"
Answer: 22678.0

User story: "This is a design ticket, the outcome will be a design that has been reviewed and agreed upon by the qserv team.    We want to change qserv so that:  * the query results table is created before the query is sent to workers  * the Czar's c++ code fully specifies the SELECT statement to be used by the lua plugin to return the results from the results table  * manage column aliasing so that columns with the same name are disambiguated and can be inserted into the single results table, and are returned to workers with the expected name (and may even have 2 columns with the same name).  "
Answer: 16820.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: When folks are running against production Butler data (such as "dbb" raw and RC2 runs), their output files should be written to their own DataStore in their own directory.    (The Registry portion of this must wait for multi-registry functionality not available in the milestone.)    Recommendation from Tim:  use a ChainedDataStore where one of the datastores points to raw files and the other one points to a user directory tree.    To see whether additional work needs to be scheduled, run a Gen3 ci_hsc test with the gen2 repo containing the inputs in one directory tree and put the outputs of the Gen3 run in a completely different directory tree.   Should be able to use sqlite registry to test this.   If need Oracle registry, do [DM-18566|https://jira.lsstcorp.org/browse/DM-18566] first.     
Answer: 78143.0

User story: "I'm seeing artifacts along patch boundaries in difference images, anywhere a source falls exactly on the boundary. My guess is this is caused by the model at the edge of the patch being cut off right at the bounding box, and then shifted for DCR. The DCR shift should be applied first to a larger region with a buffer of several pixels around the edges, and only trimmed to the bounding box later. !Screen Shot 2019-03-20 at 2.17.33 PM.png!"
Answer: 53709.0

User story: "Since end users want to have documents preview at early stage, when the majority of the fields in Jira are still empty, we should avoid having mandatory fields when generating the document.    Document reviews shall then ensure that the right information has been included. Docsteady may support this highlighting some fields that are required for the approval but shall never stop the generation of the documents if some of those fields are still blanc.     "
Answer: 171747.0

User story: "Test specification should baseline the Verification elements.    Traceability should be show also the relation between verification elements and requirements."
Answer: 504170.0

User story: "When generating the test specification, docsteady shall separate in a different section the deprecated test cases.         Supporting test cases, shared by other test cases, need to be separated in a different section also."
Answer: 164736.0

User story: "sqr-018 needs some updating with current reality."
Answer: 48.0

User story: Bug:    sdss_stripe82_01.RunDeepSource has variance for 'ra' has wrong ucd: "stat.variance;pos.eq" instead of "stat.variance;pos.eq.ra"         Possible improvement:    sdss_stripe82_01.DeepCoadd and sdss_stripe82_01.Science_Ccd_Exposure - there are 5 columns with ucd="pos.eq.ra" and 5 columns with ucd="pos.eq.dec". Center ra, decl cols can be marked with extra ucd word "meta.main" if we'd like people to search on it. Then ra would have ucd="pos.eq.ra;meta.main" decl would have ucd="pos.eq.dec;meta.main".         In general, using meta.main is helpful, when there are several columns with the same ucd
Answer: 422212.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 will concentrate on adapting the visit and coadd analysis scripts to run on DC2 data. The colorAnalysis script will be addressed on a separate ticket."
Answer: 474.0

User story: "It appears that phosim assumes the eimages it produces are always oriented in focal plane coordinates when it pastes on the rough WCS.  This is true of all science detectors, but appears not to be true for the wavefront sensors, which are rotated 90 deg in each subsequent corner raft.    This leads to a rough WCS that is wrong for the WFS chips.  See the following figure.  RA and Dec labeled as inferred from the attached WCS.  Red circles are the pixel positions from the phosim {{centroid.txt}} file.  The blue circles are the RA/Dec positions from the input file to phosim.  All circles are annotated with: object identifier, RA/x, Dec/y.    As you can see the relative positions of object 0 and object 1 are flipped in RA/Dec relative to x/y.  My interpretation is that this means the translation from RA/Dec to pupil coordinates in phosim and the ray tracing step are being done correctly.  I think the issue just comes from an incorrect assumption for {{CRPIX}} and possibly the {{CD}} matrix when computing the WCS.     !labeled.png!    P.S. It's possible the bulk offset is due purely to distortions in the optics that the simple WCS does not account for. "
Answer: 1746.0

User story: "Prototype a SAL API based in the OpenSpliceDDS native python interface,  and add distribution to ts_opensplice for V6.9 community including the python  asserts pre-built"
Answer: 79939.0

User story: "Rebuild the pLAN EFD with the tables corresponding to tag 3.8.41  and prepare RPM's for switch to 3.9.0. Install OpenSplice debug tools"
Answer: 18716.0

User story: "Start development of the thermal system FPGA."
Answer: 10324.0

User story: As identified in DM-18353, there are some reading bugs with pyarrow that prevent "large" (don't know what this means exactly) parquet files from being read.  Experimentation has shown that fastparquet *can* read these files successfully.  This ticket is to implement an option to read a ParquetTable using fastparquet instead of pyarrow.
Answer: 53979.0

User story: "In DM-17429 we discuss the use of Lanczos5 kernels to improve the PSF interpolation on coadds, but we also found that Lanczos7 kernels had *worse* behaviour.    Investigate interpolation in single visit and coadds, getting to the bottom of exactly what is going on, and propose a fix.     "
Answer: 626627.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 {{deprecated}} package will probably not be available by the time I'm ready to merge DM-10156. This is unfortunate, but I don't want to delay merging that ticket, given the number of packages involved. I'm going to implement the various deprecated interfaces there, but they will only provide deprecation warnings at the C++ level, not python.    This ticket is to add deprecation warnings to the python layer for all {{getCalib}}, {{setCalib}}, {{hasCalib}} methods in afw. [~<USER> and I may have to iterate on exactly how best to do that deprecation decoration."
Answer: 35080.0

User story: "Updates needed include:    * The iDAC topology diagram to remove 'LSST' from iDAC    * Add an explanation of the iDAC topology   * Remove 'LSST' from 'LSST iDAC', we will just use the terminology 'Independent DAC'   * Add a few demonstrative science cases to the data products section   * Add content to the IDAC services section"
Answer: 1970.0

User story: "Victor has sent the JSR response template - fill in DM part"
Answer: 5701.0

User story: "Many test cases contain the common steps.  A common test case library would enable reuse of test steps between test cases and scripts, thus avoiding duplication and standardizing the test cases. "
Answer: 242467.0

User story: "The SQuaRE Events architecture for creating files and projects from Slack has https://github.com/lsst-sqre/templatebot as the core microservice for getting configuration from the user on Slack (or potentially via REST) and then rendering templates. Beyond cookiecutter template rendering, we also need LSST-specific functionality to set up projects. These are called pre or post hooks, depending on whether the hook happens before or after templatebot renders the cookiecutter project.    - Pre hooks should create the GitHub repository. For example, technotes have an automated algorithm for selecting a repository.  - Post hooks can apply a pull request to the newly created and populated GitHub repository. For example, a post hook might enable Travis CI for a repository and then submit a PR with new encrypted variables for the {{.travis.yml}} file.    These hooks shouldn't be part of the templatebot service itself since they're LSST-specific actions. We want templatebot and templatekit to be as generic as possible so that they might find use in the OSS community.    Templatebot interacts with this helper application through Kafka messages. This design is also useful because it means that potentially slow operations (like creating a repo, submitting a PR, and enabling Travis CI) happen out of band in message queues that are independent of initial Slack handler. This solves a key problem in the original {{sqre-ccutter-uservice}} where timeouts would often occur because an automation step took longer than 30 minutes.    The purpose of this ticket is to stand up the helper microservice and demonstrate basic pre- and post- hooks (create a technote's repo, set up Travis CI)."
Answer: 61698.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> points out that there is an increase in the "wired" wPerp Principal Color scatter for tract 9697 between the {{w_2018_36}} and {{w_2018_38}} HSC RC2 processing runs (and it has persisted ever since).  This is the blue "wired" curves: https://lsst-web.ncsa.illinois.edu/~<USER>RC2_w_2018_36/pipe_analysis/qaPlots/color/tract-9697/plot-t9697-griPSF-wFit-fit.png vs. https://lsst-web.ncsa.illinois.edu/~<USER>RC2_w_2018_38/pipe_analysis/qaPlots/color/tract-9697/plot-t9697-griPSF-wFit-fit.png  Investigate the cause.
Answer: 3015.0

User story: "Currently only the filter is passed through to the job metadata.  In some cases, there is additional metadata that can be passed on.  For example, some metrics are produced on a per tract basis.  A general way to do this is to create a dictionary that has just the entries that are common over the full list of data ids passed on to {{runOneFilter}} [here|https://github.com/lsst/validate_drp/blob/e350b0cd818a6640ea27be1ff037cf698d316a1b/python/lsst/validate/drp/validate.py#L293]."
Answer: 587880.0

User story: Write a initial version of the "slew telescope script". 
Answer: 65296.0

User story: "Document the Prompt Enclave software currently running on the Prompt Enclave (L1) test stand.    Document was copied from Jim's location and is now being updated here:    https://confluence.lsstcorp.org/display/DPES/L1+System+Test+Stand+Information"
Answer: 23058.0

User story: "Update LDM-153 to be auto-generated from the contents of the felis-defined YAML files, which will be stored in the cat package."
Answer: 106903.0

User story: "Please check that the v17.0.1.rc1 release candidate is good to go.    Patch release 17.0.1 will be created once this check is done."
Answer: 1518.0

User story: "Testing of the software integration between DIMM CSC and vendor provided software. "
Answer: 42388.0

User story: "We got updated information about the interface to the DIMM software. This task is to start integrating the software. "
Answer: 21554.0

User story: "Finalize ATAOS and ATPointing integration test"
Answer: 16255.0

User story: "Using the linear fitter(s) implemented in DM-18105, test linear models and/or parameter initialization on the COSMOS galaxy fitting scripts using HST/HSC data"
Answer: 45172.0

User story: "Prepare talk with Zeljko for AMCL on April 1.     "
Answer: 17171.0

User story: "Install the MySQL Cluster with Puppet on local machine in Tucson.    This is to be familiar with the baseline software setup. This task will also try to compare the MySQL Cluster and InfluxDB (NoSQL) and discuss with Andres.    The puppet script by Andres V. is here:    [https://github.com/avillalobos/lsst_devops]"
Answer: 21172.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: "Realize the OFC interface classes (in ts_ofc) to let the MTAOS to use. Chris and I discussed and defined the interface classes in the last sprint. I plan to realize them for Chris to be able to use with the real calculations instead of interface only. This is the phase 2 of task.    This task will focus on the algorithm verification (coordinate transformation) and functional units test of control interface classes."
Answer: 14055.0

User story: "Translate the LabVIEW code (ts_tcs_ofc) related to the coordination transformation from ZEMAX to subsystems to Python code (ts_ofc, I renamed the ts_tcs_ofcPython to ts_ofc to fulfill the eups package name requirement). This is to translate the OFC calculated DOF in ZEMAX coordinate to the hexapod position and actuator forces in the subsystem's coordinate system."
Answer: 14110.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: As part of the developing strategy for designing clearer interfaces into the Science Platform:    Firefly should recognize tabular data in ObsCore format and expose appropriate behavior when it is received in any form carrying sufficient metadata for it to be recognized.    The result should not be strongly dependent on whether the ObsCore data are received via a "manual" table upload via the Firefly API, the opening of a file (e.g., from a workspace) in this format, or via the normal Firefly search processor API.    This ticket covers only _recognizing the table and providing the behavior_, not the provision of any search screens or other interfaces that assist the user in finding/retrieving ObsCore-formatted data. However, it is worth noting here that implementing this ticket is a key predecessor to providing good support in Firefly for SIAv2 and ObsTAP searches, in particular.  h4. Priority 1: the most essential parts of this are:   # Recognizing the "s_ra" and "s_dec" columns (UCDs "pos.eq.ra" and "pos.eq.dec") and displaying all of the corresponding points, if not nulled, in a context image (especially a HiPS image). A "blank" context image should be supported eventually, but this is not required at first.   # Recognizing the "s_region" column in an ObsCore data table and successfully displaying it, if not nulled, as a geometrical region in a context image (especially a HiPS image). It should be API-selectable whether all regions are always displayed, with the highlighted row in the table having its region highlighted in the context image, or whether only the highlighted row has its region displayed at all.   # Recognizing the "access_url" column, displaying it as a link, and enabling the link to be used for a download of the associated data file.   # Recognizing "dataproduct_type=image" rows and loading and displaying the associated images if the "access_format" value suggests that Firefly should understand the image data format (FITS, HiPS, or a browser-displayable image such as JPEG, PNG, SVG).   # There must be API support for supplying the context image to be used. (It _may_ be useful to design the system so that a context image could be inferred from data in the table itself, e.g., the "facility_name", "instrument_name", and "obs_collection". That is not a Priority 1 requirement, though.)   # This ticket *does not mandate providing any search-form support for SIAv2 or ObsTAP*. However, if a valid URL for a method=GET synchronous search on such a service, returning valid ObsCore data, is provided to Firefly in the existing "Upload table from URL" screen it must be recognized as ObsCore and displayed appropriately. This is a key feature for testing as well as for demonstrations of the capability.         This ticket captures only the "priority one" items from DM-15783.
Answer: 59688.0

User story: "Discussions with CADC on a range of topics including TAP etc . and travel time"
Answer: 11212.0

User story: "Chair telecon March 15 – prepare - updates to doc"
Answer: 4226.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: A new organization named "LSST Commissioning" was added to Chronograf as requested by [~<USER>.    We tested Michael's verification notebook demo and showed that it works in the current deployment of the SQuaSH Sandbox instance and that data is sent correctly to the corresponding {{squash-sandbox}} database in InfluxDB.    One issue was identified related to the execution environment as described in DM-18505.    Note that the LSST Commissioning organization in Chronograf shares the same InfluxDB instance as the LSST DM org. I think that is fine for now, and we can decide later if we need a separate instance for both.     One advantage in sharing the same InfluxDB instance (and connection) is that we can combine DM and Commissioning verification results on the same dashboard.     Thus, the main reason for having a separate organization now is mainly to separate the dashboard contents and perhaps later to direct the different public to the right place.    Individuals can belong to multiple organizations, and change between organizations seamlessly in Chronograf.
Answer: 6.0

User story: When a Slack dialog is submitted with an optional field that isn't set by the user, it's value is {{null}}. The Avro schema {{com.slack.dialog_submission_v1}} doesn't yet support {{null}} values.    Here's an example payload from Slack with a null value in {{submission}}.  {code:java}    data: {   action_ts: "1552678562.412457"       callback_id: "templatebot_file_dialog_7b60fc6a-7460-4421-8e44-a005afce40a3"       channel: {…}       response_url: "https://hooks.slack.com/app/T06D204F2/578658627986/JklGOMvwAPjOrRsYQpUJ0XOe"       state: "{"template_name": "task_topic"}"       submission: {    script_name: null         task_class: "ExampleTask"         task_module: "lsst.example"        }   team: {…}       token: "Br379sIn3bY7BFimW9PcZRo1"       type: "dialog_submission"       user: {…}      }  event: "Parsed interaction request"     level: "info"     logger: "sqrbot"     method: "POST"     path: "/sqrbot-jr/interaction"     request_id: "56879f4b-4719-46a1-9925-5a07d6295af0"    }  {code}
Answer: 43.0

User story: "This task is to get the CSC overview table automatically generated by the xml. It is also to add the different tags withing the SALGenerator.xml to have the values that we want it to have to be displayed on the table."
Answer: 9925.0

User story: "This is the second half effort that will capture the work for the Java. More details to be put after completing the first half. I imagine the first half will be getting my machine able to build the tasks and learning how the binding works."
Answer: 19057.0

User story: "All LSST services are protected and require authentication to access.    Firefly_client, when running in a notebook environment, needs to obtain the authentication token and use it gain access to portal as well as other LSST services.    Token should be passed along as an http header: {{Authorization: Bearer $\{ID_TOKEN}}}     "
Answer: 31337.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Currently all the summary statistics created in DM-18318 are haphazardly listed in a single function and run as a block. This ticket will make the summary statistics run configurable, expandable, etc. by mimicking the measurement plugin system implemented for the measurement tasks within meas_base."
Answer: 261014.0

User story: "Due to a misinterpretation of RFC-550, DM-16536 left {{TimingMetricTask}} in {{ap_verify}}.    Provisionally, this involves moving {{lsst.ap.verify.measurements.profiling.TimingMetricTask}} to {{lsst.verify.commonMetrics.TimingMetricTask}}, and updating documentation and tests accordingly."
Answer: 68259.0

User story: "pyyaml 5.1 is out. Test it with the stack and use it if all tests pass. Includes some fixes that are needed for python3.7.  "
Answer: 10291.0

User story: "As all releases, also the 17.0.1 patch release shall have a corresponding document. However, having a full detailed release note like a major release, it is excessive, since we are just fixing one issue.    My suggestion is to create a subsection inside the major 17.0 release note page.     "
Answer: 11462.0

User story: "There is a need to automatically update the SAL HTML definition pages on the LSST project page, [https://project.lsst.org/ts/sal_objects/].  It would be good to have the Jenkins build publish these page, however there is an issue getting the data off the AWS hosted server.  This task covers the time it will take to investigate, propose and implement a solution."
Answer: 42349.0

User story: "Attend the DDS workshop."
Answer: 1466.0

User story: "We're going to be adding mountpoints.  Add some code to make it easier to change where volumes are mounted, or add or subtract volumes."
Answer: 489.0

User story: "This story will represent the incremental expenses charged for Power and Cooling,  The Story points on this story will be updated monthly to reflect the percentage of the budget that we have used.     "
Answer: 28.0

User story: "Test ATHexapod CSC at the summit. Tests performed were:   * Execute the CSC and see if reponds to commands   * Check possible bugs and document them   * Create next tasks to have a working version for ATHexapod CSC"
Answer: 21759.0

User story: "Test ATDome CSC at the summit, for this task I will need the ATDome CSC ready for deployment. Initially is planned for the first week of April but can change depending on [~<USER> feedback."
Answer: 41264.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 ATDome vendor interface, prior to going to the summit I will add a minimum set of test I will try at the summit.    All of these are done manually using the telnet interface, if unit testing is required can be discussed later.    Tests to perform:    * open/close shutters   ** main door *{color:#00875a}(DONE){color}*   ** dropout shutter *{color:#00875a}(DONE){color}*   ** synchronized *{color:#00875a}(DONE){color}*   * rotate to various positions{color:#00875a} *(Move just fine)*{color}   * phase wrap {color:#00875a}*(DONE)*{color}   ** (meaning go to 330 degrees, then go to 30 degrees... and it should only move 60 degrees)   * go to home position *{color:#00875a}(DONE){color}*   * open shutter then stop in the middle of the command {color:#00875a} *(DONE but not recorded as it was as expected)*{color}   * close shutter then stop in the middle of the command  *{color:#00875a}(DONE){color}*   * values out of range {color:#00875a}*(DONE)*{color}   * move commands while it is moving     *    ** dome shutter  *{color:#00875a}(DONE){color}*   ** azimuth{color:#00875a} *(DONE, it does the latest command)*{color}   * home command while it is moving {color:#00875a}*(DONE)*{color}   * emergency stop while it is moving {color:#00875a}*(DONE for shutter, same behavior as for the next test)*{color}   * emergency stop then move *{color:#00875a}(DONE for shutter){color}*   * Invalid commands *{color:#00875a}(DONE){color}*    All tests should be recorded in a text file exactly how I get responses from telnet"
Answer: 17611.0

User story: "Work with [~<USER> to deploy the MySQL Cluster + CSC to replicate some of the issues we've been experimenting:   * High memory usage"
Answer: 11782.0

User story: "Write a procedure to backup/restore all Qserv data for Qserv on GKE.  Data will be backup inside a Google storage bucket.  "
Answer: 21524.0

User story: In TAP_SCHEMA.schemas table, 'schema_index' is used to order schemas by importance.     Currently, gaiadr2 with non-existing table comes first, wise_00 comes last.    Please, set schema_index so that "sdss_stripe82_01", "wise_00", and "tap_schema" come first, followed (if they need to be kept) by non-existing or dev. datasets. 
Answer: 2848.0

User story: "```SELECT TOP 10000 * FROM sdss_stripe82_01.RunDeepSource WHERE CONTAINS(POINT('ICRS', coord_ra, coord_decl),CIRCLE('ICRS', 320.943, -0.63, 0.027777777777777776))=1```    Getting  ```SQLException:Unable to return query results:  Failure while merging result```         TOP works in other places and is mapped to LIMIT."
Answer: 194765.0

User story: "Check MySQL Cluster limitations we are currently having and document them in confluence. As this task was shorter than expected I will investigate how MariaDB High Availability MaxScale works."
Answer: 26830.0

User story: "Remotely attend the DDS workshop."
Answer: 2755.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "We do not currently specify string lengths for DatabaseDict tables. Update the constructor used from PosixDatastore to include lengths for the fields.  This is done currently in code because the tables are dynamic and each datastore gets to name the table to use."
Answer: 7429.0

User story: "We now have names with more components.  Make our menu-generation and container-spawning code happy with that."
Answer: 333.0

User story: "Draft a DMTN proposing a way to manage environment in a more flexible way."
Answer: 62327.0

User story: "Attend the DDS Workshop. The agenda is here:    [https://confluence.lsstcorp.org/pages/viewpage.action?spaceKey=LTS&title=Opensplice+Vendor+Visit]     "
Answer: 2916.0

User story: "Once the blocking ticket is completed, the heartbeat event in all subsystem XMLs need to be removed."
Answer: 331583.0

User story: "Add a new function {{set_summary_state}} to {{ts_salobj}} that allows us to put a CSC into any valid summary state.    This will primarily be used to enable or disable CSCs but it may also be handy for changing configuration (by moving it to STANDBY, then the next desired state)."
Answer: 9897.0

User story: "auxTel data from Tucson are automatically being copied back to a filesystem at NCSA.   They are also automatically ingested into a Gen2 butler.    Staff are requesting to access this data via the LSP.    This ticket requires a short term solution.   It is understood that a long term solution needs discussions to happen between various parties.    But that is outside the scope of this request.    The auxTel data and Gen2 butler repository resides on the NFS-exported filesystem /ts_data.    As far as we can tell, once the PV is created in K8's this filesystem can be mounted as whatever your normal procedure prefers.        However, the Gen2 butler repository is mostly a bunch of softlinks to avoid multiple copies of the data.   Also the root path of the Gen2 butler repository is always included on user's command line.    Having the paths match across LSST resources is ideal from the user perspective as well as keeping the softlinks working.    To that end, we are requesting that the LSP containers have a /proddata directory containing a softlink called teststand that points to wherever ts_data is mounted  (e.g., /proddata/teststand -> /mnt/ldf/ts_data)    "
Answer: 154284.0

User story: Make a "stub" ts_sal package for RPMS, something we can use eups to setup but that only includes SALPY libraries, not SAL itself.    It must include the following directories:  * lib  * python  * ups
Answer: 122900.0

User story: "Review the EFD related documents and attend the related meetings."
Answer: 8303.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: "Viewing smoothed diffims from https://jira.lsstcorp.org/browse/DM-17281 reveals background gradients near the corners of some chips which are not present in the calexps or the templates.  These areas show an excess of DIASource detections.    This ticket is to investigate this failure and potentially identify changes in configurations that provide better performance."
Answer: 263984.0

User story: "Current OpSim simulations suggest there are relatively few images per field in u & g in the first years of the LSST survey, which may make it challenging to construct usable DCR models.  This ticket is to develop an metric to characterize the relative value of a specific new image at a specific airmass and parallactic angle (given the past pointing history) in improving the DCR model and hence reducing the total number of DCR-induced false positives."
Answer: 383589.0

User story: "The dask labextension makes the logs hard to read by constantly polling on a short interval even when there is no active cluster.  See if we can make it realize it isn't getting anything back and chill out a little."
Answer: 95279.0

User story: "To tell MySQL cluster to store data on disk (when they are not PK, because PK always go to RAM), while creating tables, tablespaces need to be assigned.     First MySQL Cluster needs to have defined tablespaces, this can be done by adding        {code:java}      TABLESPACE ts_1 STORAGE DISK    ENGINE NDBCLUSTER;  {code}       at the end of the table creation, for example:       {code:java}  CREATE TABLE dt_1 (    member_id INT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY,    last_name VARCHAR(50) NOT NULL,    first_name VARCHAR(50) NOT NULL,    dob DATE NOT NULL,    joined DATE NOT NULL,    INDEX(last_name, first_name)      )      TABLESPACE ts_1 STORAGE DISK      ENGINE NDBCLUSTER;{code}       The table space needs to exist, this can be done 1 file per table or 1 file for all, this will need to be added in the sqldef scrips automatically created by SAL.         This process has been described here:    https://confluence.lsstcorp.org/display/LTS/MySQL+Internal+configuration"
Answer: 275320.0

User story: "Due to the update of ATM plugin released on March 11th, the test case search is not considering the subfolder anymore.         For example, following quiery:    [https://jira.lsstcorp.org/rest/atm/1.0/testcase/search?query=folder%20=%20%22/Data%20Management/Services/LSP%20Services%22]    is not returning any test case, when until yesterday it was returning all test cases included in the LSP Services folder"
Answer: 831510.0

User story: "Updates to LDM-554 requirements and propose a new baseline. This ticket covers only those requirements that were deemed  as simple fixes and do not imply any scope change"
Answer: 30219.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 purpose of this ticket is to implement {{templatekit.yaml}} files in the templates repository. These files customize and refine the experience of generating files and projects from Slack with tempatekit and templatebot. {{templatekit.yaml}} files are being concurrently designed in DM-18405."
Answer: 71225.0

User story: "The basic experience of generating a file or project from a Templatekit-based template (e.g. [https://github.com/lsst/templates)] is largely driven from the template's cookiecutter.json file. However, in implementing DM-18110 it's clear that the experience can be vastly improved if we can add a configuration file to individual templates that customizes how the template is presented to Slack-based users.    Some key types of configuration are:   * Customize name of template in selection menu and place it in a hierarchical context   * Configure what fields appear in the dialog (Slack limits it to 5)   * Create composite selection menus that provide presets that drive multiple boolean-type cookiecutter configurations.   * Customize labels for dialog items (can be up to 75 characters)   * Customize selection menu item labels (can be up to 75 characters)   * Customize title of dialog (can be up to 24 characters)   * Customize type of text field (a text area versus field, and also subtypes of the field).    This can be implemented with a {{templatekit.yaml}} file that appears in each template directory.    This ticket will design the schema of the templatekit.yaml file and add support for it in templatekit and templatebot."
Answer: 9042.0

User story: "Run Spectrograph system on the NCSA test stand. "
Answer: 40096.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 the work in DM-18103 document the SQuaSH InfluxDB data model."
Answer: 31551.0

User story: "The version of EUPS currently required by newinstall and lsstsw/deploy is v2.1.4.  This needs to be changed to use v2.1.5 as there are a few features that we would like to make use of (eg C++14 detection).  We should also take this opportunity to update the conda base version (edits in the same file)."
Answer: 24161.0

User story: "Work with [~<USER> to update the LSE-61 MagicDraw model for the final release of approved LCRs LCR-1425/LCR-1463/LCR-1465 and create a new version of LSE-61 PDF for upload to Docushare.     This includes checking the output from the latex docgen, adding flowdown from OSS, and adding priorities to the newly added requirements."
Answer: 2840.0

User story: The work in this ticket is to ensure that, for LSST, the "suit" application, which implements the Portal interfaces for catalog and image query UIs, be unified with the "firefly" application, and in particular, the latter's "Slate" functionality on which the recent Firefly Python API work depends.    We need a single container image that provides all these functions, and therefore provides the three end points described in DM-17973.
Answer: 173365.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 scons system builds the Test and Script libraries for almost all commands. It should only do so when running tests, and not cleaning."
Answer: 9805.0

User story: "There are a number of external dependencies that rely on existence of external repositories.  We currently build RPMs against these, and depend on them to build the L1 software.  We can't rely on GitHub repositories to continue to exist for the lifetime of the project, because if they're lost, we won't be able to rebuild the software.  We have to retain copies of these locally so that they are not lost.         These source repos include, but are not limited to:  yaml-cpp, SimpleAmqClient, rabbitmq-c.         There are also binary downloads we rely on, and these also need to be hosted locally.  This might include RabbitMQ, Redis and Boost.  (We retain a copy of Boost like this ourselves,  for the DM stack... it might be good to use that instead and stay in-sync with that version of Boost, rather than retaining two different versions).         Once we have copies of the files we're using, we'll need to readjust the RPM spec files to point to where they are housed locally.     "
Answer: 154232.0

User story: "Understand what's going on with the EFD"
Answer: 5696.0

User story: "Learn script queue. Review documentation:     https://confluence.lsstcorp.org/display/LTS/Running+the+script+queue+with+containers"
Answer: 29748.0

User story: "The QA dashboard project will require some way to look up information on source matching between visits and coadds.  As [~<USER> and [~<USER> and I discussed a few weeks ago, one simple way to do this would be to write a match table that persists this information.  This table would be per-tract, and indexed by coadd ID, contain a column for each visit, the contents of which would be the best match ID (if exists) from the corresponding visit table.    The actual matching algorithm can be improved in the future; for now, I will implement what I was doing before when I was making MatchedCatalog objects for the visit-level notebook visualization stuff I was previously working on."
Answer: 84023.0

User story: "Write a script to test the integration of ATDomeTrajectory, ATDome and ATMCS. Put it in ts_standardscripts."
Answer: 13011.0

User story: "As soon as RFC-582 is approved, I can finish the renaming project."
Answer: 13155.0

User story: "Under what conditions do we get 504s in JupyterHub?  How do we make it stop?"
Answer: 115911.0

User story: "Consult with Opensplice reps"
Answer: 11631.0

User story: "Review the Hexapod/Rotator documentation received from MOOG."
Answer: 11608.0

User story: "This task is to create stubs for all the CSC's. I will create the template pages that the relevent CSC developers need to populate. This will help get the ball rolling as to how our teams documentation needs to look like. "
Answer: 5911.0

User story: "This task will be to meet with the OpenSplice folks that will be meeting here from Tuesday to Thursday. I will attend all sessions. "
Answer: 5920.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: "Upgrade LTS-158 ICS document, to include a thermal command and a crane and rear status event"
Answer: 141931.0

User story: "Create a new registry class for Oracle, and modify the sqlRegistry to behave differently based on the registry being an instance of that class."
Answer: 14620.0

User story: "PST meeting 26-27 March 2019   * For Operations Readiness Criteria sections 4,5,7 of the [Operations Readiness Review|https://confluence.lsstcorp.org/display/LSSTCOM/Operations+Readiness+Criteria] , write introductory paragraphs describing the scope and what each one of these covers   * Prepare DM status updates   * Provide input to Commissioning, and  Pre-Operations Data Policy & Serving for the PST SciCollab talk          "
Answer: 27118.0

User story: "* Site topology network   * More detail on the data products   * Science cases & services"
Answer: 14634.0

User story: "Currently, there is no way to pre-flight merges to master for all build targets supported by the dax-matrix pipeline, because that pipeline does not support a list of refs to build.    Neither can stack-os-matrix be used for this, since it doesn't include all targets built by dax-matrix (e.g. centos7-llvm, centos7-devtoolset8).    Could we please get the dax-matrix pipeline configured to accept list of refs, as is done with stack-os-matrix?"
Answer: 1311.0

User story: "The Qserv centos7-llvm builds have been failing for a long time now, in the ANTLR4 package, on an include of standard library header {{<algorithm>}}.  Track this down and fix."
Answer: 3454.0

User story: "It's time to summarize my tests with PPDB prototype that are now spread across many Jira tickets and notebooks."
Answer: 35826.0

User story: "DAX group would like a centos7 devtoolset-8 build target to be added to the dax-matrix jenkins pipeline.  Thanks!"
Answer: 192.0

User story: I've tested this with the SQuaSH demo instance after DM-18603 and it is working fine.    The only issue was with jobs where {{ci_name='unknown'}} because of DM-18599.     For testing this and to be able to implement DM-17767, I have updated the {{ci_name}} field in the squash-demo database, as follows:    {code}  update job set env=JSON_SET(env, "$.ci_name", "validate_drp") where ci_dataset='validation_data_cfht';    update job set env=JSON_SET(env, "$.ci_name", "validate_drp") where ci_dataset='validation_data_hsc';    update job set env=JSON_SET(env, "$.ci_name", "ap_verify") where ci_dataset='CI-HiTS2015';  {code}      
Answer: 27666.0