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: "Perform a large scale (cores greater than available at NCSA) test of notebook aspect deployed on the Google Cloud. Scheduled for Thursday, 01/17/19 12pm to EOB project time."
Answer: 21557.0

User story: "Implement the adopted change of RFC-560, removing the unused CatalogStarSlectorTask"
Answer: 2727.0

User story: "Add sdss stripe 82 data to tap_schema tables so we can query it through the TAP endpoint."
Answer: 1208.0

User story: "The way that qserv_areaspec_* is written is hard for the ADQL parsing to deal with.  There's a few issues going on:   # The requirement that the qserv_areaspec functions have to be at the beginning of the query makes the SQL context dependent (because I have to put the areaspec first).  This seems unnecessary, and makes the parsing a lot harder, and is also an end user annoyance.   # qserv_areaspec_* functions actually call scisql functions under the hood, which unnaturally limit results beyond what people might expect.  It is not just a hint about the querying, but affects the results.   # If you use qserv_areaspec on a non-partitioned table, it throws an error, rather than just ignoring it and calling the scisql function.  This means the parser (and end users using qserv_areaspec functions need to know which tables are partitioned, which isn't exposed to them).   # If the ADQL parsing wants to inject multiple qserv_areaspec hints it will throw an error, even if they are put first.  This also makes the generated SQL context dependent, since I need to know how many would be put in, and if it's greater than one, then not put any in.    I propose the following:   # A new function called qserv_areahint_* that looks just like the other qserv_areaspec_ functions, but does NOT call scisql under the hood.  This means it is just a hint and not a limitation.  Having it be a different name means this shouldn't affect backward compatibility.  Only the TAP ADQL parser need know about its existence.   # If the qserv_areahint function is used on a non partitioned table, ignore it.  Since it does not call scisql under the hood, using it or not is just a performance hit, and doesn't affect the results.   # If there are multiple qserv_areahint functions in a query, qserv can either ignore them both and do a full table scan, or later on restrict the query to multiple chunks to give better performance.  By supporting multiple qserv_areahint functions, this makes the generated SQL fom ADQL queries not dependent on the context of the rest of the query."
Answer: 279555.0

User story: "prepare and attend AMCL"
Answer: 2.0

User story: "write the Management summary"
Answer: 17329.0

User story: "Evaluate whether multicast can be used in a GKE cluster for multiple firefly servers."
Answer: 196.0

User story: "add logging mechanism"
Answer: 12994.0

User story: "Last item for RFC-554 is to add new re-factored package to lsst_distrib."
Answer: 3084.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 initial integration of {{ts_sal}} with Kafka was to send text-based messages, adapted from SQL inserts, to Kafka. This is a fine starting point because it avoids the complexity of integrating Avro and the Confluent Schema Registry with {{ts_sal}}. At the same time, the InfluxDB ingest requires that messages be encoded in Avro (specifically in the Confluent Wire Format) so that the schema can be automatically discovered by the Kafka  -> InfluxDB Connector.    As an intermediate step to ultimately bringing avro to ts_sal itself, this ticket is to implement a deployable appication that consumes messages from {{ts_sal}} in text format, and produces those same messages in a Kafka format.    This work will be implemented in the kafka-efd-demo repo, but will leverage the new kafkit package (DM-17058)."
Answer: 11623.0

User story: "Both {{ap_verify_hits2015}} and {{ap_verify_ci_hits2015}} use very old coadds from HiTS 2014 data as templates for difference imaging. These should be updated with the latest and greatest (most likely CompareWarp coadds constructed from a subset of best seeing images)."
Answer: 68107.0

User story: "Debug network configuration issues involved in establishing remote access  (via reverse VPN to gateway pc) to EFD in mirror lab for test campaign"
Answer: 17131.0

User story: "Support the auto generation of Kafka capable data writers for SAL mediated data"
Answer: 100689.0

User story: "Once the software is officially delivered to LSST, it will be necessary to update the design and code to conform to SAL constraints and conventions, as defined in [https://confluence.lsstcorp.org/display/SYSENG/SAL+constraints+and+recommendations]    This includes:   * Naming conventions   * Enumeration definition   * Implementation of all standard commands and events."
Answer: 881672.0

User story: "Continue adding hw test cluster machines to optionally be no a private network,   provide mechanism for outside access (collaborate with IT N+S)"
Answer: 81047.0

User story: "Release new version"
Answer: 1997513.0

User story: "Develop and support the active optics closed-loop simulation. This task will integrate the modules of ts_tcs_wep_phosim, ts_tcs_wep, and ts_tcs_ofcPython. This task will be a prototype of active optics closed-loop control (AOCLC) in the simulation mode. It is noted that in the control mode, the control system will be added/ integrated with the control systems of wavefront estimation pipeline (WEP) and optical feedback control (ofc). This task is in the phase 1 of the development."
Answer: 80563.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Fix some issues with lsst-sphinx-bootstrap-theme for single package builds:   * The copyright in the footer repeats the word "copyright." One copyright is part of the template. The other is part of the inserted string. Maybe just remove "Copyright" from the template text?   * The title of the site should be a variable. Right now it's fixed to read "LSST Science Pipelines"    While I'm in there, perhaps also reduce the font size of code samples to address some complaints.
Answer: 37784.0

User story: "Run further tests to the EFD to ensure:   * We can create almost all tables (for now with the exception of the tables with more than 512 attributes)   * We can record a big amount o data per table (this may vary among TIERS). As a result of this point, it will need to be documented how to change configuration to handle more data per table + cons of doing this.   * Create replicable tests to ensure that after any change, all keeps working as expected (this could be either manual tests or automatic tests)"
Answer: 219504.0

User story: "In order to make my AAS 233 poster, I threw a lot of things into a giant jupyter notebook which generates pretty light curves, object/source plots and histograms, and image cutouts. This code is a mess, but the core functionality will be very helpful for future analysis of ap_pipe reruns. This ticket is to preserve that work somewhere other than in a monolithic notebook on lsst-dev (perhaps a new ap_analysis package)."
Answer: 99334.0

User story: "Run jointcal with HSC-RC2 and w_2019_02"
Answer: 9998.0

User story: "* Limit write access to DM calendars to DMLT members only  * Describe the DM calendars on the Developer Guide  * Post a similar description on CLO."
Answer: 21372.0

User story: "As part of the work to make my poster for the AAS meeting, I put a fair bit of effort into code to make quiver plots of astrometric residuals. This code should be put somewhere more useful than my poster repository; {{jointcal/bin/}} seems like a good choice.    The story points here include some of the effort required to write it in the first place over the break, since it's code that is directly useful to DM."
Answer: 728667.0

User story: "Run pipe_analysis scripts   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    and validate_drp   # matchedVisitMetrics.py   # validateDrp.py   # reportPerformance.py    Upload the validate_drp metrics (json files) to SQuaSH:   # dispatch_verify.py    with the w_2019_02 RC2 outputs from DM-16110"
Answer: 11576.0

User story: "MultiProFit's python interface computes model images in one function, returns them, and then computes the model likelihood in a separate function, but this could all be done more efficiently in one (C++) function when fitting."
Answer: 60253.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: "Implement fast (C++) pixel-convolved Gaussian evaluation in MultiProFit with the covariance matrix parameterization, compare performance with existing ellipse parameterization and determine if gradients could be returned"
Answer: 60255.0

User story: "We are ready to request Letters of Intent from community brokers but need a document to do so.  This ticket is to write it and shepherd it through.    LDM-682 is the document handle."
Answer: 41918.0

User story: "At the moment SAL messaging is not working, the issue is related to IPTables definition on the puppet configuration for the SAL machines.    Audit IPtables on CSCs L1 Stand Machines to make sure SAL connection works"
Answer: 4369.0

User story: "Fix commit error on last commit: 4fc891f69ed99fa223f464564b31d495e6902a8ba"
Answer: 1521.0

User story: "Write a simulator for the ATMCS CSC in Python. I'm not positive it will have the necessary performance, but it's quick to try."
Answer: 28632.0

User story: "JupyterLab can report the wrong stack info if the cache is considered fresh but in fact you have switched images within its lifetime."
Answer: 9992.0

User story: "After DM-17235 is implemented, jenkins jobs should be converted to {{Jenkinsfile}}s and the existing free style jobs retired."
Answer: 523525.0

User story: "Investigate existing documentation left by Jim Parsons and become familiar with the system. This include meeting with <USER>to discuss the architecture of the test stand."
Answer: 69268.0

User story: "Coordinate the logistics for the Feb 11-12 DAQ 2.5 workshop at NCSA.    it includes working with Bill Click to make sure all hardware on the L1 Test Stand is ready for the installation of the new COB and make sure that all logistics are covered."
Answer: 43430.0

User story: "selectDimensions currently produces DatasetRefs that do not include components where appropriate, and this is partially worked around in pipe_base's {{GraphBuilder}} by calling {{Registry.getDataset}} _when a dataset_id is present_.  That has the disadvantage of replacing the {{DataId}} as well, destroying any metadata (such as regions) that we've included in {{selectDimensions}}.  An extra workaround is being added to pipe_base on a working branch by [~<USER> to re-expand at this point, but the right fix is to include the components  in {{selectDimensions}} itself and remove the pipe_base workaround.    We should also think about the {{Registry.getDataset}} API and how it should handle data ID metadata."
Answer: 191896.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. Plazas, M. Fisher-Levine (DRP), P. Astier, P. Antilogus, A. Nomerotski (SAWG) will have a Zoom telecon on 01/16/19 regarding the status and priority of known sensor effects (e.g., [https://confluence.slac.stanford.edu/pages/viewpage.action?spaceKey=LSSTDESC&title=Known+Sensor+Effects+and+Anomalies]). Some questions to guide the discussion:    - What are the effects that we know or suspect will have an impact on LSST science (taking into account the science goals and requirements)?   - For those effects, are there any algorithms to correct for them to acceptable levels or is this still a topic of investigation?   - If there are, should they be implemented as part of the DM pipelines? What inputs would be needed?          "
Answer: 3028.0

User story: "Once DM-16554 is merged there will be two metadata translators in obs_lsst. This ticket will replace the translation logic in the butler gen2 translator with astro_metadata_translator logic. It looks like I can subclass ParseTask and insert an ObservationInfo constructor. Then most of the translators can be replaced with a trivial data type conversion rather than duplicated camera logic."
Answer: 13061.0

User story: "Update ATMCS interface according to discussion with Patrick, Rolando and Russell    Changes:  - Add M3 motor encoder data to existing telemetry topics.  - Remove ATMountState enumeration values that overlap summary state.  - Remove M3State enumeration values that overlap summary state.  - Reorder fields in the {{mountEncoders}} telemetry topic to the standard order used everywhere else.  - Rename command topic fields that are ignored to {{ignored}}.  - Rename brake fields from {{engage}} to {{engaged}}.  - Remove {{m3RotatorDetentLimitSwitch}} to {{m3RotatorDetentSwitches}} and remove {{Detent}} from the field names.  - Remove redundant {{State}} suffix from {{ATMountState_}} and {{M3State_}} events, e.g. change {{M3State_DisabledState}} to {{M3State_Disabled}}.  - Add documentation for all topics (and fix existing incorrect documentation).  "
Answer: 41912.0

User story: "1. Milestone for Science Platfiorm       Depends on DAX services for ADQL and Imgacutout        decide if it test uses the new CAOM model            2. DAQ milestone - nominally April as thats when Huffer the new DAQ (full) would be delivered. "
Answer: 78864.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: 02/28/2019   # Implemented support for preserving selections in client tables.   # Enabled sorting and filtering of the constraints table itself.   # Sorting and filtering does not change checkbox states.   # Principal columns are pre-selected.   # No switch between All/Principal, removed by [~<USER> request.   # Removed additional constraints. (They can be added in ADQL tab.)    Bug fixes:   # Now supporting table ids with . character. (UI state was not stored correctly for such tables.)   # Enum filter was not shown (hidden behind) when the table is in the dropdown.   # It was not possible to request to show filters without showing filter button.   # Filter was not working for multi-line values.    01/14/2019    (The "constraints table" is the "table of columns" that exposes the schema for a single table and allows a form-based interface for applying per-column constraints to the search being constructed. In the current Gator, IRSA Viewer, and Firefly TAP Search layouts, the "constraints table" is found in the lower half of the screen.)    The details of what to do need some work.    Bugs:   # The constraints currently don't seem to work / don't appear in the generated ADQL.   # The "additional constraints" box at the bottom has a label that mentions "SQL" - should be "ADQL".    Features:   # If the {{principal}} column is present in the {{TAP_SCHEMA.columns}} data for the table, *AND* if any row (representing a column in the table being described) has a non-zero value for {{principal}}, offer a choice at the top of the displayed table of checkbox-selecting only the "principal non-zero" rows, or all of them. This should offer equivalent functionality to the comparable feature in the IRSA Viewer interface.   # Enable sorting and filtering of the constraints table itself.   # Ensure that sorting and filtering _does not change checkbox states_. (Understood that this may need to be handled later.)   # Allow the "additional constraints" text to begin with {{WHERE}} (or not) as a convenience to the user.    (review of the current prototype is still ongoing)
Answer: 64931.0

User story: "Do the following:   * Write advance query panel part of the TAP search   * work with [~<USER> and [~<USER> to determine what should be in it."
Answer: 29994.0

User story: "To the following:   * Write top top right box on the TAP search panel - Spatial and time selection   * Work with [~<USER> and [~<USER> to determine what should be in it.   * Add analysis of tap schema to control what is displayed"
Answer: 14187.0

User story: "Do the following:   * Write the top left side of the panel of the TAP panel   * Change the select tables on be one similar to IRSA viewer/firefly catalog   * Write this component   * Add button to be a placeholder for a advanced table select popup   * Anything else to complete this panel"
Answer: 31406.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: "Do the following:   * Update layout to all for a blank spacial/time search panel   * Update layout to allow to a tab area with advance tap search panel - move existing dialog box.  Possibly  add a button to populate and switch tabs.   * Add area to select TAP search service.   * Any other clean up to allow for concurrent work on the TAP search panel"
Answer: 12983.0

User story: "Go through the teams Confluence page. Reorganize so that finding documentation becomes easier. Have had multiple conversations with team members and <USER>before making the actual changes as well as a tech talk where team members can give input. "
Answer: 5824.0

User story: "Get the tests for ts_sal running on a Jenkins program. Tei wei has a method for doing this user docker containers. The python\ environment will be downloading either using lsstsw or the newinstall script. "
Answer: 272879.0

User story: "We setup a configuration of running rsync file transfers/syncs over an stunnel  as a strawman installation for data transfer for AuxTel.   "
Answer: 40267.0

User story: "Move all the SAL unit tests into a single file so that when running under an automated test environment it is much faster to finish testing.     It is faster because unlike how it currently is, you need to start SAL services for every single topic. By having all the tests in a single file the SAL services only needs to start once."
Answer: 11557.0

User story: "Running {{pipeTask}} with the same output collection and different quanta tries to write init outputs (schemas) multiple times, failing.  Provide (ideally) ways to run any combination of   - Preflight   - Initialization I/O   - Execution    or if that's too hard, at least make it possible to run Execution without Initialization I/O."
Answer: 204.0

User story: "I delivered to N. Mondrick Ozone level during our Gemini observations.          This is following ticket    # DM-14337    PWV and AOD ongoing.     "
Answer: 232996.0

User story: "The stack_package template is currently based on the assumption that the documentation will be part of [https://pipelines.lsst.io.|https://pipelines.lsst.io./] However, some packages will be part of other stacks, or even stand alone (and have an independent documentation site). This ticket will make the stack_package template more flexible for these cases.    This should make the stack_package template usable for Telescope & Site projects as well."
Answer: 5391.0

User story: "Document the wavefront estimation pipeline (WEP) with new update to adapt the new scientific pipeline feature (tag: sims_w_2018_47). The obs_lsst replaces the obs_lsstSim. The phosim_utils is used to repackage the PhoSim amplifier outputs. "
Answer: 15377.0

User story: "Teach David (PhD student in Stanford University) the background knowledge of active optics and the use of AOS codes (contains ts_tcs_wep, ts_tcs_wep_phosim, and ts_tcs_ofc). Discuss the AOS closed-loop simulation with PhoSim."
Answer: 9572.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "In this ticket, now that I've supported the qserv and scisql functions, I'm going to start rewriting the ADQL queries into SQL queries that qserv can understand.  This is at least a first attempt, although I'm sure it will change over time."
Answer: 86038.0

User story: "Need to run on multiple nodes.    Can use a shared repo on the shared file system and a shared sqlite3 file, without the  subsetting/transferring/merge features.   May or may not use {{QuantumGraph}} & {{Quantum}}"
Answer: 17305.0

User story: "Create a YAML file for default OODS values, add optional config override to command line, and integrate configuration information into the code."
Answer: 7224.0

User story: "Write tests for the latest functionality that has been added, specifically the cache cleaning code."
Answer: 20168.0

User story: "The default configuration doesn't give enough memory to MySQL cluster to allocate all the tables for the EFD. Need to be reviewed why and how to solve it."
Answer: 14510.0

User story: "Try to use table spaces to allocate tables in different disks for TIER purposes. This seems to be a better solution than having multiple instances (one for each TIER).    This test will be performed in a virtualized environment."
Answer: 21714.0

User story: "Meet with Orlando Castro from DatControl to test and review communication protocol between our software and their HVAC system. It seems that is can be done using a SQL data base to send commands to their system.    Also need to check if this also give us the telemetry of the system, so we can publish it through SAL later.    This task is to keep things moving forward while German is on vacation."
Answer: 21799.0

User story: "To have this task done, the CSC should:   * read configurations from configuration files   * publish settingsApplied for configurations used    * publish settingsAppliedMatchStart when applies   * publish settingVersions when first running the CSC   * publish detailedState    * Publish telemetry positionStatus with current position   * accept and execute commands: moveToPosition, applyPositionLimits, applyPositionOffset, stopAllAxes, pivot   * Publish detailedState when the state change   * Publish settings Applied for: settingsAppliedPositionLimits, settingsAppliedPivot, settingsAppliedTcp   * Publish positionUpdate when position command change try to move "
Answer: 139121.0

User story: "Develop GUI and Unittest for ATHexapod.    This task should deliver:   * set of unittests to test the behavior of the CSC   ** values out of range   ** state transitions   ** try position limits   ** move command    ** offset command   ** stop command   ** settingsApplied events   ** appliedSettingsMatchStart   ** settingsVersions   * A very *basic* GUI to control the CSC"
Answer: 139105.0

User story: "Add error check to ATHexapod code. This also includes command rejection."
Answer: 24870.0

User story: "Write a first draft of the MTTCS for the Big Bang"
Answer: 65035.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: "Move schema definitions out of YAML and into Python, and particular into overridable methods so it's easier to customize for different DBs.  These will probably be on a separate class to be overridden along with Registry instead of on Registry itself so we don't pollute Registry with tons of {{_createTableX}} methods.    I'd also like to cook up some approach to make it easier to have different DB implementations generate compatible schemas (or at least make it difficult have them define incompatible schemas) from the perspective of still having the common code for running at least most SELECT queries across databases.  That may involve keeping some of the YAML around and using it either for validation or to extract something to pass to the Python methods.    An alternative would be waiting for [~<USER>'s Felis to become an alternative, but I both don't think we can wait *and* I don't think we can reasonably expect that to handle the case where one DB decides to use a view to one or more private tables where another just uses a single public table.  Its role will probably be in providing a schema that we can validate per-DB Python-defined schemas against instead."
Answer: 393508.0

User story: "The pipeline task mode of MergeDetection task is only writing out it's detection schema, but should also be writing out its peak schema, add this behavior."
Answer: 57.0

User story: "If the activator is being used to run or list, it will not find, or hide results for modules for which there was an import error, and report to the user that that module does not exists. This should at least produce a warning that there was a problem importing a module by python so the user can track down why there was a problem importing."
Answer: 35487.0

User story: "At some point daf_butler became more strict and there was no testing to catch that all instances of Exposure should be ExposureF. Fix this in DetectCoaddSourcesConfig"
Answer: 83.0

User story: "The MERRA pressure table is given by 1 file per date delivering 8 timestamps  (0h : 3h : 6h : 9h : 12h : 15h :18h : 21h).   Each timestamps record the lat-lon pressure and altitude of the 72 z-layers.    First estimation assumed that altitude is independent of time,   thus using the 3-D map determined from first hour of first day.    —>It is not, it varies both from one timestamp to the next as well as from one file to another.    see the impact on the attached .pdf"
Answer: 128367.0

User story: "- Update qserv and qserv_deploy container images an validate using CI  - Put all openstack script in `obsolete/` directories, final goal is not to have kubernetes provisioning script inside qserv_deploy, but to delegate it to underlying infrastructure  - update GKE procedure for creating k8s cluster"
Answer: 20568.0

User story: "This milestone is completed by successful execution of test plan LVV-P15."
Answer: 132407.0

User story: "This makes it easy to see which milestones are being pushed out by other subsystems, etc."
Answer: 918458.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "In the same way as we already have tickets for the creation of test plans.    We can then monitor the execution of milestones as part of the regular DMLT discussions."
Answer: 203.0

User story: "Since the base detector type is {{SCIENCE}} the Corner rafts are inheriting the same type.  I need to add some detector types that implement the other enumerations."
Answer: 28832.0

User story: - Save the table in VO format.      Firefly will have more meta data about table supplied by VOTable, and keeping them in the saved file would be desirable.     - fix the following table save' related issues as commented in DM-16048 https://jira.lsstcorp.org/browse/DM-16048     Comment 2:  . In the "Save table" dialog, the second line "Save as"  is changed to "File name".    Comment 3.   The default filename for a cone search has a dash, underscore, parenthesis, colon, space, and double quotes.     Fixing methods:        remove all of the special characters except for dashes and underscores.        Replace left parentheses with dashes.        Remove the trailing right parentheses, or replace the right parentheses with dashss.        Replace double-quotes with 'asec'.        Remove spaces.        Replace decimal points with 'p' for 'point'.          ex: for cone search,        WISE-allwise_p3as_psd (Cone:100'').csv => WISE-allwise_p3as_psd-Cone_100asec.csv       for elliptical, box, polygon, multiple-object and all sky search, form the filenames        respectively to be like:       WISE-allwise_p3as_psd-Ellipse60_0_0p26asec.csv        WISE-allwise_p3as_psd-Box_100asec.csv      WISE-allwise_p3as_psd-Polygon.csv      WISE-allwise_p3as_psd-MultiObject.csv      IRAS-irasgal-AllSky.csv    Comment 4,   For elliptical searches, the filename comes out with the string 'Eliptical'.     Fixing method:     Change it to be 'Ellipse', and the filename contains information on position angle and axial ratio as well as the semi-major axis.     Comment 5     When you upload a table for Multi-Object search,  there is no string to indicate what type of search was done.    Fixing method:   'MultiObject' is appended to the filename to indicate the type of search.    Comment 7,   For the "Load Catalog Dialog", the chosen filename is severely truncated in the display.   I see "Custom catalog in IPAC table format" in that dialog, even though I seem to be able to load csv and tsv files.    Fixing methods:   More space is shown to contain the chosen filename.   Fix the hint sentence that custom catalog in IPAC, CSV, TSV, VOTABLE and FITS table format are able to be loaded.    Other fixings:  Fixes the help link for 'table save' dialog and 'Load Catalog' panel.         
Answer: 104188.0

User story: "[~<USER> points out that {{SkyMeasurementTask.measureScale}} uses {{zip}} to iterate over x and y limits, so it's only iterating over the diagonal of the image. He sent [a patch|https://github.com/michitaro/pipe_drivers/commit/f7763978b803a464cb3974fe1f80747465410e78] which I'll clean up and shepherd through."
Answer: 10309.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: "Also, populate the December monthly report with milestone data, and send a summary of upcoming milestones to the {{dm-cams}} list."
Answer: 35.0

User story: "The butler tests in obs_lsst take a very long time (12 minutes on my laptop just for imsim). It seems that this is almost entirely down to a butler being setup for every single test. Investigate whether the butler can be set up once per test class instead (there might be an issue with the global variable when tests run in parallel)."
Answer: 289.0

User story: "investigate Mike's question in [https://community.lsst.org/t/qserv-group-by-question/3540] and propose a solution (or implement if trivial)"
Answer: 37691.0

User story: "The query class code is very hard to work on:   * the formatting is bad (there are no spaces between functions)   * there is code that is not copy/pasted but duplicates behaviors (of a function written to perform that behavior in some cases, perhaps at a later date?)   * raw pointers are extracted from shared_ptr   * factory classes add complexity but not value    this is a time-boxed story to go through the query classes to improve & clean the code."
Answer: 13074.0

User story: "e.g. allow {{=1}} in {{select objectId from Object where qserv_areaspec_box(...) = 1}}    the {{=1}} will be thrown away.    this unblocks [~<USER>, who is blocked because her framework won't pass the qserv areaspec restrictor to the where clause without being part of an expression.     "
Answer: 10.0

User story: "Remove any use of Antlr 2 and related code (refactor or remove as appropriate) from qserv."
Answer: 89309.0

User story: "Providing support for the emerging Gen3 Butler and SuperTask frameworks in March 2019."
Answer: 118010.0

User story: "Providing support for the emerging Gen3 Butler and SuperTask frameworks in January 2019."
Answer: 73533.0

User story: "Providing support for the emerging Gen3 Butler and SuperTask frameworks in January 2019."
Answer: 33263.0

User story: "For some subset of the data (may be all) that was produced before rsync service deployment, manually initiate transfer process for the early data."
Answer: 101996.0

User story: "Provide support for the transferring of the AuxTel teststand images as well as accessing the files in the Gen2 repo for around a week after deployment."
Answer: 293887.0

User story: "Implement the software/scripts needed on the NCSA end that finds the newly transferred AuxTel files (may be by searching transfer log files) and ingests the images into a Gen2 repo (call ingestImages.py)."
Answer: 102011.0

User story: "Software/scripts to be run on the AuxTel machine initiating the transfers to NCSA."
Answer: 102016.0

User story: "Per minrk's suggestion the proxy should be in its own container."
Answer: 37441.0

User story: "Lower some of the new logger INFO messages to DEBUG"
Answer: 75.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: "Under DM-17059, [~<USER> has re-established the legacy DAX services under Kubernetes control on {{lsst-lsp-int}}.    We now should re-establish the legacy PDAC portal at that address, using Kubernetes for deployment, and in a way which derives the DAX services' URLs from the base URL for the deployment in a relocatable way."
Answer: 28237.0

User story: Narrowly, this ticket requests that in a case where an API-driven request for a plot refers to one or more non-existent table columns, a more informative message is presented to the user through the UI.  The current message is of the form “Failed to fetch trace 0", which provides virtually no guidance to a user on how to correct the error.    Something like "Cannot display requested data: can't find column(s) 'x', 'y' in table 'z'." would be helpful.  Only if there are multiple traces should traces be mentioned, e.g., "Cannot display requested data for trace 1: can't find column(s) 'x', 'y' in table 'z'."         [https://jira.ipac.caltech.edu/browse/FIREFLY-114] has been created to address this above issue specifically.     The general issue described below will not be address in this ticket.     More generally (a) we need to think through all the failures that may occur and how to route useful messages through the various layers, and (b) whether the same / a similar message should be returned to the Python client as well.  I fear that may be (very?) hard because of the asynchronous messaging that (I think) is used in the API.    See [https://lsstc.slack.com/archives/C8EEUGDSA/p1546973044297700] and ff. for an instance where this arose and people had to spend time guessing at what the problem was.
Answer: 304443.0

User story: "We took nbdime out because it was breaking with JupyterLab; looks like that's fixed now, so try putting it back."
Answer: 75.0

User story: "DM-17060 implements parsing of the value of the option {{--dataset-name-substitution}} inside PipelineBuilder class. I think it would be better and more generic for PipelineBuilder to accept a dict and parsing should happen in a cmdLineParser."
Answer: 10017.0

User story: "This ticket implements a set of tooling in documenteer that allows us to rendering installation documentation in pipelines.lsst.io that is exactly appropriate for the EUPS tag of the stack being documented. Some examples of functionality are:   * Include the right EUPS tag in the {{eups distrib install}} documentation line.   * Reference the right Python/Conda dependency files for the EUPS tag   * Populate the version labels throughout the documentation.    Inside the stack documentation build container we can use the {{EUPS_TAG}} environment variable. ([https://github.com/lsst-sqre/jenkins-dm-jobs/blob/master/pipelines/lib/util.groovy#L1155)]    An alternative would be to use the EUPS APIs to figure out what tag is currently installed (this might be useful for local builds by developers, but in that case perhaps it would be better have some sort of default fallback)."
Answer: 48906.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: Calling it "jupyterlabdemo" seems a bit shortsighted now.
Answer: 80665.0

User story: "Some work did not get properly merged in pipe_supertasks on ticket-16797 before much of that content was refactored into different packages. This ticket will add that missing code to the right places."
Answer: 1296.0

User story: "Fritz has mentioned that Gregory has asked for the legacy DAX services to be deployed under the new hostname to have something for the portal to call.    Most of this seems trivial, at least for my part.  But this means that all the NCSA plumbing has to be ready, which I will check on in the process of doing this."
Answer: 259.0

User story: "Create a Confluent Registry-enabled Avro serializer plugin for aiokafka. This will be similar to how the producers and consumers in the confluent-kafka Python library work:   * Producers include a byte header that includes the ID of the schema in the schema registry. See [Wire Format|https://docs.confluent.io/current/schema-registry/docs/serializer-formatter.html#wire-format] documentation.   * Consumers look at that byte header and obtain the schema (from a local cache if possible).    For SQuaRE Events we want to use the aiokafka library instead of confluent-kafka so that we can use asyncio in our apps.    This functionality will be implement in a Kafka helper library that can be used by both SQuaRE Events and the DM EFD projects. The sqrbot-jr project will be the first consumer of this API."
Answer: 33343.0

User story: "Some of the columns names in dax_ppdb still has several columns that were not converted by myself from Sigma to Err. This ticket will convert the column names to the expected Err name."
Answer: 17176.0

User story: "This ticket follows on DM-17024 and adds the ability to encode and produce Avro+Kafka messages for Slack Events API messages:   * message events (message.im, message.channel, message.mpim, message.group varieties)   * app mentions (app_mention event)    There should likely be two Kafka topics:   * sqrbot.message (all message.* events)   * sqrbot.sqrbot_mention (all app_mention and message.im events)    Thus an app that works by responding to messages direct to it can just subscribe to the {{sqrbot.sqrbot_mention}} topic. Apps that monitor all Slack traffic (that the bot is a privy to) can monitor the {{sqrbot.message}} topic.    This is still an MVP effort. The Kafka topics can be manually created and the schemas can be manually uploaded."
Answer: 60352.0

User story: "Test Kafka -> InfluxDB connector producing messages for ~1000 SAL topics at different frequencies and find the breaking point in the current deployment at GKE.    See https://github.com/lsst-sqre/kafka-efd-demo  "
Answer: 19171.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 was trying to add to the SQuaSH dashboards a single stat showing the time of the last validate_drp measurement - it turns out that stats visualization does not display timestamps, only numbers, and it is not possible to do math on timestamps in InfluxQL to get say "number of days without measurements"     https://github.com/influxdata/docs.influxdata.com/blob/master/content/influxdb/v0.13/troubleshooting/frequently_encountered_issues.md#doing-math-on-timestamps     So I think it is a good idea to add the timestamp of the measurement as a new field, as we did for the EFD topics, there that information was useful to report on things like latency for instance. 
Answer: 370752.0

User story: "We've been accidentally ignoring ref_cat because we didn't have its StorageClass (SimpleCatalog) in Gen3 yet; adding that yields a sequence of (minor) additional problems."
Answer: 21524.0

User story: "Learn the basic of Pegasus hierarchical workflow and make up a simple demonstrative example for dynamic workflow.    A recent version of Pegasus is installed at   {{/project/production/pegasus/4.9.0/ }}    "
Answer: 94734.0

User story: "Convert AssembleCoaddTasks to PipelineTask, using as much of existing code as possible with the shims that make gen3 quack like a gen2. Inputs are declared, so this is fine. They just don't fit into memory at once.     Will require DM-13504, so I'm putting that change on this ticket.     In the future, we'll refactor to split out the background-matching/mask-gen step from the stacking step. Now now. "
Answer: 32074.0

User story: "The process of importing all modules in lsst.pipe.tasks to search for PipelineTask is slow enough that it's not always a convenience; while it's very nice to have for the list subcommand, it'd be nice to disable it if the user provides fully-qualified names for the Tasks to be run.    Another option might be to cache the results of the search to a temporary file so it's only slow the first time the activator command-line tool is invoked in (e.g.) a terminal session, but it seems to me that it'd be difficult to know when to invalidate that cache."
Answer: 7589.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 *objectSizeStarSelector* Task allows for source selection based on flux limits. A selection on signal-to-noise (S/N), i.e. flux/fluxErr, is often preferred, so should be added as an option for this source selector.    Additionally, there is currently no unittest for *objectSizeStarSelector*, so a minimal one should be added (following the *test_astrometrySourceSelector.py* and *test_matcherSourceSelector.py* examples).    For this ticket, the option will simply be added in the same manner as the flux selection is done, but all current defaults will be left as is. Looking towards the future, I anticipate submitting an RFC to make S/N selection the default (instead of a flux-based selection, but, in principle, both could be activated simultaneously) as well as adapting all the *SourceSelectorTask* to make use of the configuration-based selection classes in *BaseSourceSelector*-derived Tasks (e.g. *objectSizeStarSelectorTask*, *AstrometrySourceSelectorTask*, *MatcherSourceSelectorTask*, *FlaggedSourceSelectorConfig*) [https://github.com/lsst/meas_algorithms/blob/master/python/lsst/meas/algorithms/sourceSelector.py#L153])."
Answer: 13150.0

User story: "Options like {{-c label.option=True}} don't seem to work.  If needed, I think [~<USER> has a more complete how-to-reproduce."
Answer: 8583.0

User story: "stac/pipetask currently require the user to create a label explicitly in order to provide config overrides.  We should make the default label to the Task class name (i.e. the same name that was just passed to {{-t}}).  While it's possible to to have multiple instances of the same Task, that's currently quite rare and we should make the common case simpler and more intuitive.    After a bit of discussion, [~<USER>, [~<USER>, and I agreed it'd be better to use the Task class name rather than {{Task._defaultName}} because the former is what's also typically present on the same command line."
Answer: 7640.0

User story: "This is the second of of implementation of RFC-554. pipe_supertask has been split into two packages now, things in pipe_base should be mostly OK, but modules in ctrl_mpexec need serious re-factoring to make them more reusable for other potential clients."
Answer: 27079.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "In the process of trying to plumb through the UDFs for scisql and qserv, I've noticed that the lack of a return type of qserv_areaspec functions is really, really painful.  It should return something, even if that is only a 1, or bit, or whatever.    In the various sql parsers, if you have a function, it is expected to return something.  Without a return to compare against something else, it will fail.    For example, the JSQLParser (which CADC uses) allows you to specify UDFs with a name, and you say the return type.  This is how I've been able to pass through the scisql_angSep function, since it returns a double.    I have tried to do the same for the qserv_areaspec functions, but the parsing always fails because we aren't comparing it against something in the WHERE part of the clause.  If I tell it that qserv_areaspec_ returns an int (and just compare it against 1) it seems to work.  But then qserv won't accept that query.    TOPCAT also has query hints that will pop up a warning flag (although it still allows you to submit), since it also tries to parse the ADQL.  It's fine without having to tell it what the function names are, but it says that it was expecting an =, not equal, in, not, between, etc.  Since a lot of astronomers will be using this, it seems better to allow TOPCAT to help us with its ADQL parsing hints.  If you make it = 1 at the end, all is well in the world of TOPCAT.    I have tried to test passing the scisql_angSep function down to qserv with a query, but I think the lack of qserv_areaspec has made the query get denied:    MariaDB [(none)]> SELECT o1.id AS id1, o2.id AS id2, scisql_angSep(o1.ra1, o1.dec1, o2.ra1, o2.dec1) as distance FROM wise_00.allsky_2band_p1bm_frm WHERE scisql_angSep(o1.ra1, o1.dec1, o2.ra1, o2.dec1) < 0.02 AND o1.id <> o2.id;  ERROR 4120 (Proxy): Unable to return query results:  -- WARN multiple errors    Unfortunately, I think with the moving of the qserv containers around, I don't seem to be able to find the proxy logs to help give me the errors, and the mysql command line client doesn't tell me what they are, so it might just be my bad query writing that is at fault here."
Answer: 20014.0

User story: "I used the sql scripts located here ([https://github.com/lsst-dm/db_pdac_wise]) for creating a mock-qserv.  This is a single container mysql deployment with the tables set up correctly but no data.  This is to help test things outside of NCSA without having to connect right to qserv.    For allsky_2band_p1bm_frm, it looks like it is missing the qs_fact column.  This is included in the wise_00 data generated by the felis tool, which I'm guessing was generated by looking at what is in qserv.  So it seems like there is a mismatch between what is contained in this repo, and what is in qserv.    Other missing columns are:    allsky_3band_p1bm_frm.icaldir    allsky_4band_p1bm_frm.icaldir    allsky_2band_p1bm_frm.qs_fact    The allwise_* tables seem to be fine.    This is just to track what might be missing."
Answer: 76347.0