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: "Write a hacky, zeroth order version of the pipeline so that we have some skeleton tasks and structures in place to iterate on.    This should probably be done on a user branch, but I wanted to have a ticket number for this work to save git hassles later on as this will touch more than just atmospec.    This will initially be pretty hacky in places and probably not adhere to all standards, but will be tidied up before review.         Checklist/to-do list/steps in Augustin's pipeline:       {noformat}  Prepare Image:      Load image from disk      Subtract overscan and trim & assemble    Initial ISR Step      Load the dark by filename      Scale the dark by exposure time and subtract          (you don not want to see the details of this!)    Source extraction (using SExtractor):      Find the objects and centroids    Load SExtractor catalog    Process catalog to find the primary object      return the x,y of the brightest, roundest object's centroid    Calculate the spectrum's bounding box, depending on dispersion direction and the order used      Dispersion direction is either just x or y, not arbitrary angles yet      Will need extending for arbitrary angles    Secondary ISR:      Load masks from disk if masking      removal of periodic pattern on chip      Create initial dispersion relation      Apply initial flatfielding      Find and interpolate over cosmics    Extraction (choice between three methods:)      Spectral extraction method 1:          Calculate row-wise mean and sigma of background and subtract          Row-wise, calculate:              aperture flux              PSF 1D-Gaussian flux              Moffat flux              Gauss-Moffat Flux              Voigt flux        Spectral extraction method 2:          Calculate row-wise sum for aperture flux without subtracting background)          Fit 1D Gaus for PSF flux (again, without bgSub, and without pedestal in fit function)          Same for Voigt fit (no bgSub here either)        Spectral extraction method 3 (two pass method):          1st pass: fixed aperture, no centroid, meaning that:              Per row:                  Fit 1D Gaus for PSF flux (again, without bgSub, and without pedestal in fit function)                    Between passes, fit the row-wise Gaussian's parameters with linear and quadratics functions describing the position and width of them as a function of row number i.e. position in the spectrum, respectively          2nd pass: applying a variable aperture, using the 1D centroid and 1D sigma provided, meaning that:              Per row:                  Regular aperture flux summing (still without bgSub I think)                      aperture is centered at the row's centroid, and 6 sigma around it                  fit Gaussian over a very narrow range (120-180 pixels) up spectrum    Post-extraction:    Reflatfield    Find lines in spectrum    Match to known lines    Refine the dispersion relation calculation{noformat}        "
Answer: 125472.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: "AOD from MERRA-2 is about five time below the SNF estimate (see figure).    A better measurement with MERRA could be obtained by combining 3-tables :   * The full analysis of 15 aerosol bins,   * Aerosol optical properties ([https://journals.ametsoc.org/doi/suppl/10.1175/JCLI-D-16-0609.1/suppl_file/10.1175_jcli-d-16-0609.s1.pdf)]   * and the barometric pressure profile.    the new measurement shall be tested against SNF. [^merra2_3D_AOD.py]     !Capture d’écran 2018-12-04 à 10.11.06.png! ).     "
Answer: 12043.0

User story: "Dig out LSST Europe instructions and update for AAS - ask NCSA about account sign up page."
Answer: 50094.0

User story: "Should/can we use an off-the-shelf OAuth2 proxy along with Kubernetes ingress to handle the OAuth2 OpenID Connect process for all LSP services, passing the resulting token through?  If so, how should it be configured?    Concretely, the OAuth2 proxy would listen to all LSP endpoints; detect whether an OAuth2 (OpenID Connect) authentication token is present; (reverse) proxy to the appropriate upstream service if so; and conduct the OAuth2 token acquisition process with CILogon, including providing a callback URL, if not.  The upstream connection should pass the token along so that authorization can be performed."
Answer: 60182.0

User story: "Create a mock of SAL in the https://github.com/lsst-sqre/kafka-efd-demo to generate SAL messages at arbitrary data rates with random data (though with the actual SAL schemas).    [~<USER> will work on ingesting this data into InfluxDB."
Answer: 4543.0

User story: "Create a reference quota implementation that can serve as an example and starting point for a more sophisticated quota system."
Answer: 1338.0

User story: "The direct image, forced flux columns created in imageDifferenceTask are not currently usable with slots and therefore awkward to use with calibration objects. This ticket will change the names to ip_diffim_forced_PsfFlux_[value] and the associated slot_forcedDirectFlux. The ticket will also propagate the PsfFlux plugin flag columns to the DiaSource catalog produced by ip_diffim."
Answer: 4304.0

User story: "Make a plan on what  need to be updated and how we plan to do it.     There will be follow up tickets to update the portal online help."
Answer: 769405.0

User story: "Update DMTR-102 to the latest template"
Answer: 91121.0

User story: "* portal deployed in NCSA environment as part of LSP (PDAC)   * portal deployed in GKE environment in cloud as part of LSP   * Firefly deployed independently as a tool (not for LSST purpose)"
Answer: 591766.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: "- UI should be 3-boxes layout. Left: selection of schema and table, bottom: columns with constraints, right: spatial/temporal/wavelength constraints if the columns with the corresponding UCDs are present.   - We need a widget for TableItemListField, (similar to but hopefully more generic than IRSA's CatalogTableListField, which would map table rows into the selectable display items. This widget will be used to display schema and table lists. (Both of them can have long descriptions with links.)   - We need to upgrade CatalogConstraintsPanel to take table model (rather than giving it processor id and parameters), so that we can pre-sort table model by column_index, if it is available, and use columns UCD information to display spatial/temporal/wavelength constraints. Also, as Loi pointed out, CatalogConstraintsPanel is buggy: tab should be moving the focus to the next input box, filters and selections should clear when different table is used. (There are some hard-to-reproduce edge cases, when they don't.)   - Should we allow user to view and modify ADQL query? As shown by the prototype implementation, keeping ADQL and ADQL-building UI on the same page is tricky, because they have to be in sync, and while UI-to-ADQL is not hard, ADQL-to-UI is non-trivial. Should we allow free-form ADQL with tree-like schema browser on the side as an alternative to the table driven UI above?    Each of the items above can be a separate ticket.    Other comments from prototype implementation [https://github.com/Caltech-IPAC/firefly/pull/713:]   - ADQL query is what get submitted, but it's not obvious that you need to click on Set ADQL from Constraints before Search.   - When new schema and table are selected, ADQL query remained the previous value. Very confusing when you've gone through the selection/inputs process then click Search to get the same previous search results.   - Having fixed boxes with spiny during loading may improve look and feel. As is, UI is resizing without feedback.   - At some point, I assume there would not be both Additional constraints and ADQL Query in this dialog.   - The native drop-down list box is not the best widget for displaying schema and table lists. We'll need one with multi-line formatting, similar to CatalogTableListField."
Answer: 235018.0

User story: "03/04/2019    Expose TAP Search and Upload dialogs as a part of portal. TAP Search should have LSST TAP service as the first in the list. (The list should be configurable.)    12/02/2018    Portal is currently use the special DAX API for data searches. When the TAP service from DAX team is available, code needs to be updated to access the new TAP service.          The UI for using TAP services is separate from the UI using the legacy DAX API. We will keep those two co-exist for a while for comparison and test purpose. "
Answer: 153804.0

User story: "Lead a discussion to propose a generic TAP search panel design."
Answer: 174237.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: Accessing TAP_Schema will allow the portal to display and search all the database and tables supported by data service. But when the list is long, it could be hard for the users to pick out the tables they are interested.          Design a configuration control of the "popular/significant tables" allow the application to give help/hint to users get a limited list of the tables. 
Answer: 154847.0

User story: "- Redeploy InlfuxDB with a persistent volume for {{/data}} in the {{influxdb-demo}} cluster.  - Use the method outlined in DM-15888 to write SQuaSH prod results to InfluxDB.  - Deploy the SQuaSH API to production after DM-16300  - Update metric definitions and specs  "
Answer: 8401.0

User story: "After reviewing the procedure and the template, it may be useful update the document, generating it from Jira using docsteady script.     "
Answer: 87868.0

User story: "A story to capture the LOE needed to support project-science related communication with Alert Production Lead, DM Subsystem Scientist, and LSST Project Scientist."
Answer: 1.0

User story: "Currently, testing is done with a single program the creates separate instances and sockets. This needs to be broken into separate pieces for testing on the cluster."
Answer: 100854.0

User story: "PR from Jim here:    [https://github.com/lsst/afw/pull/415/files]    Ticket, test, merge."
Answer: 4170.0

User story: "Add configuration files for setting IP addresses and other settings."
Answer: 57960.0

User story: [~<USER>:    {quote}  hi, I'm having trouble building a DMTN. The build (https://travis-ci.org/lsst-dm/dmtn-098/builds/461067187?utm_source=github_status) fails with  {quote}  {code}  ```Exception occurred:    File "/home/[secure]/virtualenv/python3.5.6/lib/python3.5/site-packages/sphinxcontrib/bibtex/directives.py", line 29, in <module>      logger = sphinx.util.logging.getLogger(__name__)  AttributeError: module 'sphinx.util.logging' has no attribute 'getLogger'```  {code}    I think the issue that documenteer has been allowing the sphinxcontrib-bibtex version to flow, but is proactively pinning Sphinx. A new version of sphinxcontrib-bibtex might be assuming Sphinx 1.8 APIs, which we're not using yet. The obvious solution is to pin sphinx-contrib-bibtex.
Answer: 4280.0

User story: "This implements RFC-549.  To my knowledge, PhotoCalib is currently the only part of the codebase that uses any unit for calibrated fluxes right now.  Please comment here if you know of any other code."
Answer: 39124.0

User story: "Rewrite the handling of the ap_verify Ppdb config to go through the Butler similar to DM-15901."
Answer: 15450.0

User story: "See if we can get rid of that now."
Answer: 6901.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: Please look at line 2007 in DAQForwarder.cpp on the running version. This is where the CFITSIO switches are included for endianess. Please provide a brief comment describing what these letter switches are for...I forget the use of the 'L' value, hence this ticket is yours!    : )         Pertinent lines are:                            string img_segment_name = binary_file_path + "/" + *bit                                                      + "[jL" + STRING(NAXIS1)                                                      + "," + STRING(NAXIS2) + "]";
Answer: 332063.0

User story: "One nuisance parameter of the fit is an offset of the zeroth order impact x coordinate. The fitted value is ~10 pixels which is much larger than expected (no more than 2 pixels).    The most likely cause is quite tricky :    There possibly is an offset in the telescope throughput curve that is obtained from airmass regression in which the wavelength solution is obtained by matching special features with a gaussian at their expected positions.   The actual features are not gaussian, even more so in the red, where the dispersed beam is increasingly out of focus (which introduce a bump in the features).    As a result, the fitted gaussian ends up centered in the first dip, thus shifting the overall calibration.    The correct solution shall be to encode in the fit the actual dispersion relation, taking into account the unusual geometry of the beam on the disperser (non collimated).     "
Answer: 190549.0

User story: "Miscellaneous tests too small to enumerate separately."
Answer: 648187.0

User story: "The goal is to understand whether Pegasus job clustering can be used to group portion of workflow in smaller number of compute jobs while still meeting other Batch Production Services requirements. The concerns include:    * Can jobs inside a job cluster be executed in DAG-like manner (or are they always executed serially)?  * Can Pegasus restart a job cluster from the point of failure?  * What is the time overhead related to setting up Pegasus job?"
Answer: 648193.0

User story: The goal is to do tests which allow to address following operational concerns:    * Can hierarchical DAGs help meet dynamic workflow requirements, e.g., optional inputs/outputs?  * Can a failed subdag be restarted before "parent" DAG completion?  * How well does Pegasus handle large hierarchical DAXes (scaling)?  
Answer: 648199.0

User story: "The goal is to test in detail how file handling works in Pegasus with respect to (current draft) Batch Production Service requirements, including:  * Does it support optional inputs/outputs?  * How does it handle unexpected files?  * What does it do with files during failures/retries/restarts?    "
Answer: 648209.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: "Default relative time ranges are for quasi realtime dashboards, the current options are: 5m, 15m, 1h, 6h, 12h, 24h. That is defined in 'src/shared/data/timeRanges.ts'      Change that to fit our lower frequency time series data in SQuaSH better using instead: 15m, 1h, 12h, 24h, 7d, 30d.     Also make {{DEFAULT_TIME_RANGE}} 12h instead of 15m."
Answer: 54.0

User story: "For some reason our MySql grammar causes antlr4 to parse -1 and 2 differently than other negative integers (-3 is a constant, but -2 is a UnaryExpressionAtom). This needs to be researched & fixed.          "
Answer: 29112.0

User story: "Fix compiler warnings in meas model fit related to marking methods as overloads"
Answer: 3131.0

User story: "When the system is up and running, the list_services script displays this fact and states which state the system in in. When the system is stopped, however, the output still displays the system as running in a certain state, with the only difference being two lines at the bottom of response stating things are stopped like this:        Nov 28 06:00:21 tus-ats01.lsst.ncsa.edu bash[409035]: Data Management System is running.    Nov 28 06:00:21 tus-ats01.lsst.ncsa.edu bash[409035]: AtArchiver is currently in ENABLE state.    Nov 28 06:00:21 tus-ats01.lsst.ncsa.edu bash[409035]: Data Management System is running.    Nov 28 06:00:21 tus-ats01.lsst.ncsa.edu bash[409035]: AtArchiver is currently in ENABLE state.    Nov 28 06:00:21 tus-ats01.lsst.ncsa.edu bash[409035]: Data Management System is running.    Nov 28 06:00:21 tus-ats01.lsst.ncsa.edu bash[409035]: AtArchiver is currently in ENABLE state.    Nov 28 06:00:21 tus-ats01.lsst.ncsa.edu bash[409035]: Data Management System is running.    Nov 28 06:00:21 tus-ats01.lsst.ncsa.edu bash[409035]: AtArchiver is currently in ENABLE state.    Nov 28 06:00:22 tus-ats01.lsst.ncsa.edu systemd[1]: Stopping L1 Ctrl Check Service...    Nov 28 06:00:22 tus-ats01.lsst.ncsa.edu systemd[1]: Stopped L1 Ctrl Check Service.         This display would be much less confusing if only the two 'Stopping' and 'Stopped' lines were displayed. This could be done by checking the output for the existence of the word 'Stop' in the last two lines, and then only displaying the last two lines in the return list. This is an Awk addition to the script."
Answer: 310537.0

User story: "IngestImages/Buterization fails for some TS8 data when {{translate_detector}} fails to recognize the raft.    Please add more rafts into the [{{raftSerialData}} dict|https://github.com/lsst/obs_lsst/blob/f896a813da887ef819bccda5e32c5d83953a7a55/python/lsst/obs/lsst/ts8.py#L153]  for the TS8 data:   - LCA-11021_RTM-002_ETU1   - LCA-11021_RTM-003_ETU2   - LCA-11021_RTM-004   - LCA-11021_RTM-012   - LCA-11021_RTM-014"
Answer: 1299.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: "- Add a personalized text in the login page  - Set default page to /dashboards  - Place /dashboards as first option in the menu since it is now the default  - Remove /hosts, /logs and /config from the side navigation bar if the user role is different than admin.  - Requires Editor role for creating Alerting Rules"
Answer: 1345.0

User story: "Physical columns in Felis should be traceable to the DPDD requirements, and there should be a method for verifying requirements.    This can be done in a few ways, but investigate {{prov:wasGeneratedBy}} property in W3C-Prov, and a sparql query to find unvalidated DPDD requirements.    Add a CLI stub for executing this."
Answer: 8938.0

User story: "There seems to be a problem with propagating {{merge_footprint_XXX}} flags.         E.g. in some DESC processing an object has  {code:java} {'merge_footprint_i': False,   'merge_footprint_r': False,   'merge_footprint_z': False,   'merge_footprint_y': False,   'merge_footprint_g': False,   'merge_footprint_u': False,   'merge_footprint_sky': False,   'merge_peak_i': False,   'merge_peak_r': False,   'merge_peak_z': False,   'merge_peak_y': False,   'merge_peak_g': False,   'merge_peak_u': True,   'merge_peak_sky': False}{code}  note that there is a {{merge_peak_sky}} but no {{merge_footprint_sky}}. When [~<USER> looked into this, it seemed as if the problem was generic rather than just for sky objects."
Answer: 18815.0

User story: "Currently {{PhotoCalib.calibrateImage()}} computes the variance plane as:  {code}  fluxVar = instFlux.variance * scaleVar +  instFlux.variance * scale**2 + instFlux.image**2 * scaleVar  {code}    where {{scale}} and {{scaleVar}} are my own names for the scale factor that the photocalib applies and the measured uncertainty on that photocalib.     This equation assumes that the  scale factor variance and the image variance are independent, and this isn't obviously true.    Whether this is the correct variance equation is irrelevant, however. It is a change to how the variance plane in the zeropoint-normalized warps is currently computed, and I suspect  it is the primary source of the photometry differences we're seeing in coadds produced with jointcal.   While we are testing the effects of using {{jointcal}} vs. {{meas_mosaic}}'s calibration on coadd (DM-16596), it is important that we are able to test these two changes (jointcal's calibrations and the variance plane equation change) separately.     Implementation: This could be done with an extra argument like {{photoCalib.calibrateImage(Image, addCalibVar=False}} or with a state switch like {{Calib}}'s  {{Calib.setThrowOnNegativeFlux(False)}}.    "
Answer: 36331.0

User story: "This issue is to account for and detail investigations into the quality of the coadds that were built using the calibrations from {{jointcal}}.  They will be assessed independently and in comparison to the associated coadds that were built using {{meas_mosaic}} calibrations."
Answer: 217051.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 merging multiband coadd catalogs into a single reference catalog, "sky objects" corresponding to regions of empty sky (i.e. at positions where nothing else has been detected) are added to the catalog and get measured fluxes and shapes for whatever measurement algorithms are setup along with the "real" detected sources.  The intention of these objects is for qa purposes (ensuring the final subtracted sky level is indeed zero, in particular).  This issue is to add plots to the `pipe_analysis` scripts to make use of these "sky objects", including distributions (histograms) and metrics (mean and standard deviations) of various fluxes (namely aperture and psf fluxes) and their measurement errors.
Answer: 771883.0

User story: "The procedure to approve a Test Plan and Report, as specified in LDM-503 seems to be not corresponding with what we are doing for the first use cases we are facing:   * track the creation of a test plan (DMTR) using a DM Jira issue that follows the usual lifecycle:  To DO -> In Progress -> In Review -> Reviewed -> Done   * track the execution of the test activity and corresponding report in the DMTR using a (different) DM Jira issue.         Those Jira issues can be used to report problems to the DMTR, and therefore to trigger changes in the corresponding Test Plan, Test Cycles and Test Cases in Jira.          "
Answer: 10148.0

User story: "Create the fy19 requisition for SLAC budgets"
Answer: 8379.0

User story: "The {{.travis.yml}} configuration in https://github.com/lsst/verify is attempting to building and deploy single package documentation for the {{lsst.verify}} module — but it shouldn't be doing that anymore."
Answer: 28.0

User story: "In https://github.com/lsst-dm/dmtn-101, there are commands like {{\inputData{CBP}}}. These are being detected by lsst-projectmeta-kit as {{\input}} commands."
Answer: 14684.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: ...or just similar field names, I suppose. Viz:    {code:python}  In [1]: import lsst.pex.config as pexConfig    In [2]: class SuperConfig(pexConfig.Config):     ...:     foo = pexConfig.Field(doc="test", dtype=str)     ...:     In [3]: class SubConfig(SuperConfig):     ...:     bar = pexConfig.Field(doc="test", dtype=str)     ...:     In [4]: super_c, sub_c = SuperConfig(), SubConfig()    In [5]: pexConfig.compareConfigs("", super_c, sub_c)  Out[5]: True    In [6]: pexConfig.compareConfigs("", sub_c, super_c)  ---------------------------------------------------------------------------  AttributeError                            Traceback (most recent call last)  <ipython-input-7-e502e8e334d3> in <module>()  ----> 1 pexConfig.compareConfigs("", sub_c, super_c)    /software/lsstsw/stack_20181012/stack/miniconda3-4.5.4-fcd27eb/Linux64/pex_config/16.0-7-g9645df7+1/python/lsst/pex/config/comparison.py in compareConfigs(name, c1, c2, shortcut, rtol, atol, output)      101     equal = True      102     for field in c1._fields.values():  --> 103         result = field._compare(c1, c2, shortcut=shortcut, rtol=rtol, atol=atol, output=output)      104         if not result and shortcut:      105             return False    /software/lsstsw/stack_20181012/stack/miniconda3-4.5.4-fcd27eb/Linux64/pex_config/16.0-7-g9645df7+1/python/lsst/pex/config/config.py in _compare(self, instance1, instance2, shortcut, rtol, atol, output)      356         """      357         v1 = getattr(instance1, self.name)  --> 358         v2 = getattr(instance2, self.name)      359         name = getComparisonName(      360             _joinNamePath(instance1._name, self.name),    AttributeError: 'SuperConfig' object has no attribute 'bar'  {code}    *Both* of these comparisons are mistakes: the configs aren't equal, so shouldn't return as if they are (in the first case), and the comparison should certainly not raise.
Answer: 1149.0

User story: "Support the {{Mask}} when displaying {{Exposure}} and {{MaskedImage}} objects using {{Display.mtv()}}.  "
Answer: 337303.0

User story: "A.T. observations will be analyzed using a forward modeling approach :    An end-to-end pipeline has been implemented by S. Dagoret-Campagne and J. Neveu and tested on the CTIO 0.9-m campaigns.    Here, I analyze the result with respect to the most challenging atmospheric parameter : The AOD determination.     As I currently do with SNF data, I shall compare it with global MERRA-2 data.    [^jeremy_model.pdf]"
Answer: 19582.0

User story: "DM-15588 removed the placeholder database APIs from ap_association, pipe, and verify. In doing this, a convenience function was created to compute a summary metric on the PPDB for use in ap_verify. This ticket will move that function and it's unittest into the Ppdb class and modifies ap_verify's usage of the function."
Answer: 384514.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: "Add translators for cameras in obs_lsst.  This is needed in order for LSST data files to be used with Gen 3 butler and also to allow a simple way for NCSA to extract metadata when ingesting test files into the data backbone."
Answer: 84779.0

User story: "Develop a summary on Confluence of the various sensor effects which DM team should be aware of. Collate as much information as possible on:    - A description of the effect;  - What strategies the Camera Team have developed to mitigate it;  - What strategies DM have developed to mitigate it;  - Identify where those strategies diverge;  - What requirements there are for handling this effect.    Note that, in some cases, the strategies developed to date may be “none”!    Record this information on Confluence at: https://confluence.lsstcorp.org/display/DM/Sensor+Characterization+and+ISR    The aim is to use this page as a central “knowledge base” for future work, and to keep it updated as we learn about new effects or refine our approach to addressing them."
Answer: 99435.0

User story: "The YAML storage tests in daf_persistence create a temporary directory but do not use it. This leads to test failures when the tests are run in parallel.  Also fix the pickle test so that it no longer uses the root directory."
Answer: 8814.0

User story: "Chronograf supports using [GitHub OAuth 2.0 authentication|https://docs.influxdata.com/chronograf/v1.7/administration/managing-security/#configuring-github-authentication]"
Answer: 168.0

User story: "The atmospheric parameters for Mauna Kea between 2006 and 2016, as well as the atmospheric transmission obtained from the SNFactory observations and the MERRA-2 3-D tables are being compared.    This is the first time that I know of where 10 years of a local atmospheric monitoring is being compared to a determination based on global satellite data only.  [^snfVSmerra2_3.pdf]     "
Answer: 23600.0

User story: "The Telegraf InfluxDB Input Plugin populates the `influxdb_*` measurements with several metrics that can be used to monitor the InfluxDB load. In this ticket we deploy Telegraf with proper configuration and create a dashboard for InfluxDB."
Answer: 1116.0

User story: "As identified in DM-13081, the DM-14762 reprocessing of HiTS shows a sharp increase in the number of DIASources along the chip edges.  While these are appropriately flagged as EDGE we wish to investigate the origin of the increased detections."
Answer: 337662.0

User story: "The completed work can be seen at [<USER>fault_injection_tests|https://github.com/lsst/ctrl_iip/tree/<USER>fault_injection_tests]."
Answer: 1.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 use case for creating calibration products requires making creation of the Dataset distinct from (and prior to) the identification of its validity range.  That suggests we should replace the ExposureRange DataUnit with something like a "CalibIdentifier" (currently imagines as a string provided explicitly when running calib-creation PipelineTasks).  CalibIdentifier would also serve as the primary key of a new table with validity range fields, which would be used to define a view for a traditional DataUnitJoin between CalibIdentifier and Exposure.  That should remove the need for some special-casing of ExposureRange in preflight added on DM-16482, and make it easier to refactor DataUnit code later.
Answer: 155686.0

User story: "Add PSTN series to www.lsst.io and include refresh date on page."
Answer: 27249.0

User story: "The Git repository at https://github.com/lsst-dm/diffimTests contains a bunch of scripts, notebooks and other artefacts relating to tests carried out on image differencing in the LSST context. Take an inventory of this repository, experiment with the contents, and find out if there is material there that we can learn from in the short term and/or should preserve for posterity as important results.    When both this ticket and DM-16409 are complete, you should be able to give us a concise overview of what image differencing functionality is available within the LSST codebase and what tests have been performed on it, together with a summary of any key results."
Answer: 27426.0

User story: "Modify Confluent's helm charts to set up LoadBalancers, or alternatively modify https://github.com/Yolean/kubernetes-kafka to do everything the Confluent stuff does."
Answer: 25920.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 think I've found a parsing bug in the ANTLR part of the czar, when parsing out the incoming SQL statement:  {code}mysql> SELECT source_id, designation, ra, decl, w1mpro, w1sigmpro FROM `wise_00`.`allwise_p3as_psd` WHERE source_id = '2813m031_ac51-041856';   ERROR 4110 (Proxy): Query processing error: QI=?: Failed to instantiate query: NoSuchTable:Table '`wise_00`.`allwise_p3as_psd`' does not exist.   mysql> SELECT source_id, designation, ra, decl, w1mpro, w1sigmpro FROM wise_00.allwise_p3as_psd WHERE source_id = '2813m031_ac51-041856';   +-----------------------+--------------------++-------------------------++-------------------+  |source_id|designation|ra|decl|w1mpro|w1sigmpro|    +-----------------------+--------------------++-------------------------++-------------------+  |2813m031_ac51-041856|J184558.41-023707.0|281.4933836|-2.6186303|4.269|0.269|    +-----------------------+--------------------++-------------------------++-------------------+   1 row in set (0.10 sec)  {code}  If you escape the schema or the table name with quotes, it doesn't run, although it should. Probably just need to escape out somewhere in the parsing before we do whatever checking we're doing (edited)   I can also make a jira thing if someone wants me to for this    <USER>[12:15 PM]   I'd be surprised if quoting was that broken. It could also be case-sensitivity issue, can you try all-cap quoted names?    <USER>[12:17 PM]  {code}   mysql> SELECT source_id, designation, ra, decl, w1mpro, w1sigmpro FROM `wise_00`.`ALLWISE_P3AS_PSD` WHERE source_id = '2813m031_ac51-041856';   ERROR 4110 (Proxy): Query processing error: QI=?: Failed to instantiate query: NoSuchTable:Table '`wise_00`.`ALLWISE_P3AS_PSD`' does not exist.   mysql> SELECT source_id, designation, ra, decl, w1mpro, w1sigmpro FROM `WISE_00`.`ALLWISE_P3AS_PSD` WHERE source_id = '2813m031_ac51-041856';   ERROR 4110 (Proxy): Query processing error: QI=?: Failed to instantiate query: NoSuchTable:Table '`WISE_00`.`ALLWISE_P3AS_PSD`' does not exist.  {code}  <USER>[12:17 PM]   And maybe `SHOW DATABASES` and `SHOW TABLES` to figure out correct table name case.    <USER>[12:17 PM]   it looks all lowercase in mysql client   also, the quoting works like a charm for column names   just not for schema / table names    <USER>[12:19 PM]   OK, then it is probably parser or qserv bug, JIRA is probably the best next step."
Answer: 14575.0

User story: "Due to changes to ts_sal and ts_xml and underlaying names and function, the salpytools module  needs to be updated,"
Answer: 34503.0

User story: "Basic idea: create a namespace per user at spawn time, set quotas on that namespace."
Answer: 17720.0

User story: "Add Additional explanation of how jobs and nodes are labeled."
Answer: 69.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 implementation of the footprints viewer in DM-15823 uses a VOTableFile to include the variable-length spans and peaks. The table is serialized as {{tabledata}} format. Prototyping has shown that that the table can be made 3 times smaller by outputting as {{binary2}} format. This ticket is to implement {{binary2}} format in a manner that works with Firefly's current libraries and that also passes STILTS {{votlint}}.     Some Markdown items in the example notebook will also be improved."
Answer: 20111.0

User story: "Perform final tweaks, enter into JIRA, submit final plan to the project control specialist. "
Answer: 99472.0

User story: "Work with draft and final plans, staff availability, and existing status to produce fully scheduled, resource-loaded cycle plan."
Answer: 99474.0

User story: "Iterate on preliminary task plan with team leads and staff to arrive at a draft final plan."
Answer: 70404.0

User story: "Create proposed list of tasks/epics by area/WBS."
Answer: 46364.0

User story: "Meet with area leads and relevant staff to discuss current status and next steps."
Answer: 41613.0

User story: "Running Kafka in k8s isn't too hard.  Piping messages into it from the outside world is tricky."
Answer: 1.0

User story: "Learn enough about SAL et al to make a thing that ingests SAL events and emits Kafka inserts."
Answer: 20225.0

User story: "Support {{dataId}} s of the form {{dict(visit=666, detectorName='S11')}}    The problem is that {{_extractDetectorName}} hard codes using {{detector}}     "
Answer: 1207.0

User story: "Build/Install and test new ts_sal and ts_xml for the HeaderService in preparation for the Reverification of the Auxtel CSC funcionality.    https://confluence.lsstcorp.org/display/SYSENG/Reverification+of+AuxTel+CSC+Functionality"
Answer: 33174.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: [DMTN-098|https://dmtn-098.lsst.io/] speculates that it may be possible to write an adapter that allows the same {{MetricTask}} to be used with both Butler 2 and Butler 3 workflows. However, the details depend substantially on how the new Butler works and how much custom information the adapter needs (in particular, it's not clear how to create a {{DatasetTypeDescriptor}},  one of the classes the {{PipelineTask}} API must return). While we can't _implement_ such an adapter until Butler output of measurements is supported, knowing whether or not an adapter is possible affects the best way to implement {{MetricTask}} and its subclasses.    This issue is to spend some time investigating how Butler 3 and {{PipelineTask}} interact, and what is "missing" from the Butler 2 equivalents.    Note that the middleware development team is also working on something that will allow {{CmdLineTasks}} to be used as {{PipelineTasks}}. Their solution may or may not satisfy our requirements, for the following reasons:  * it may only work on {{CmdLineTask}}, which the metrics support framework does not use  * even in the Butler 2 context, {{MetricTask}} reports the dataset(s) it needs as input. An adapter that can translate this information to a Butler 3 representation may be simpler than one that needs to get the same information from an external source  * it is not actually clear whether the middleware team's solution is an adapter in the OOD sense, or whether it only maps {{PipelineTask.run}} to {{Task.runDataRef}} while leaving other {{PipelineTask}} capabilities (i.e., dataset management) unsupported    This potential conflict/redundancy can be addressed once we have a clearer picture of our own requirements.
Answer: 8738.0

User story: "Fake sources have been added to calexps and then processed. To go further through the process they need to be propagated into skyCorrection and coaddDriver."
Answer: 294588.0

User story: "The purpose of this ticket is to understand how message consumption latency is affected by load in the messaging system. Specifically, by frequency of messages in a single topic, and by the overall number of topics.    https://github.com/lsst-sqre/kafka-efd-demo is the testbed for this experiment. The producers and consumers will all be run inside the same GKE cluster."
Answer: 27589.0

User story: "Add the configuration necessary to turn on flake8 linting and travis CI to daf_persistence. This will require fixing any linting errors."
Answer: 154.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "The Kafka Confluent Platform deployment in [efd-kafka-demo|https://github.com/lsst-sqre/kafka-efd-demo] includes a {{confluent-kafka-cp-kafka-connect}} pod but no connectors are configured.    The idea is to use the Kafka Connect REST API to create and configure the [InfluxDB Sink Connector|https://docs.confluent.io/current/connect/kafka-connect-influxdb/influx-db-sink-connector/index.html] which will let us to consume specific kafka topics and save them  InfluxDB.    This ticket includes a new deployment of  [efd-kafka-demo|https://github.com/lsst-sqre/kafka-efd-demo] and  [ick-deployment|https://github.com/lsst-sqre/ick-deployment] in the same cluster.       "
Answer: 4439.0

User story: "Add the configuration necessary to turn on flake8 linting and travis CI to `ctrl_platform_lsstvc`. This will require fixing any linting errors."
Answer: 288.0

User story: "Currently, fgcmcal uses some home-brew math to convert from camera geometry in the focal plane to delta RA and delta Dec on the sky.  With DM-14932 it should be possible to remove this math and use makeSkyWcs to build a wcs from the camera geometry described in [https://community.lsst.org/t/constructing-a-wcs-from-camera-geometry/3039] .  "
Answer: 435584.0

User story: The job to create in the test environment a 16.2 release failed for the following reasons:        # The repo url for an eups product to be cloned and built as a final sanity check of the binary tarball build(s) is hardcoded and isn't configurable via a yaml key. The repo used needs to be changed when eups tarball packages are being built in an end-to-end test env.   # The eups tag, which is derived from the git tag, should always start with {{v}} and isn't being prefixed with the git tag does not start with {{v}} – as in the cause of a "final" release git tag
Answer: 20323.0

User story: "Chronograf latest release was just announced and bring some interesting features, like pre canned dashboards for various Telegraf input plugins, e.g., for monitoring kubernetes pods.    https://www.influxdata.com/blog/release-announcement-influxdb-1-7-0-and-chronograf-1-7-0/"
Answer: 39.0

User story: "This feature will allow xrootd container to lock  memory at GKE.     See Robinson message in Slack:  {code}  Hey @fjammes , how's everything... re: docker configuration for memlock, I found a way, but it will need some modifications on the statefulset  https://github.com/kubernetes/kubernetes/issues/3595  thockin  #3595 rlimit support  moby/moby#4717 (comment)    Now that this is in, we should define how we want to use it.  Labels  area/isolation, kind/feature, priority/backlog, sig/node  Comments  90  kubernetes/kubernetesJan 18th, 2015Added by GitHub    basically we need an entry point that sets the required `ulimit` values, and add SYS_RESOURCE to the SecurityContext section of the YAML file  {code}"
Answer: 82040.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: "DM-16467 cannot be completed until we have ExposureRange some support in pre-flight. Minimum support that we need for that is to be able to specify ExposureRange in DatasetTypes, support in user filter query can be implemented later."
Answer: 7230.0

User story: "DM-15082 has changed the boost files to yaml. Update the butler template used by DESDM to be consistent. "
Answer: 27374.0

User story: "Demonstrate the conversion of SAL's XML schemas (in https://github.com/lsst-ts/ts_xml) to Avro schemas. This is a first step towards demonstrating a Kafka writer for SAL messages.    This will be done in the https://github.com/lsst-sqre/kafka-efd-demo testbed repository."
Answer: 25984.0

User story: Revamp table watching sagas or watcher so there is one "Master Table Watcher" which will:   # Analyze the table for type. Right now we have three- catalogs, image meta data, footprints but there will be more.   # Start the appropriate watcher for just that table id.  This watcher will live as long as the table is loaded.   # The "Master Table Watcher" has configuration to determine which watcher are supported. i.e. it would not load a LSST footprint watcher in the IRSA case.   # A watcher would have two functions.  One to determine if it is a supported table and the other that would be the watcher.
Answer: 128395.0

User story: "Recognize ObsCore, Recognize UCD, do normal catalog overlay.    The ticket is just 1.1 of DM-15783 but lays the foundation for more.  Using upload, when a table is sent to the client. If it is a VO like table,  determine if it is ObsCore or if there is ra/dec information based on UCD and do the normal catalog overlay.    The source of the table does not have to be a VO table we just want to be able to recognize VO type meta-data."
Answer: 46341.0

User story: "The problem is a typo in the yaml file for {{raw_hdu}}; {{python: lsst.daf.base.propertyList}} not {{python: lsst.daf.base.PropertyList}}"
Answer: 290.0

User story: "Support BNL ts8 data and add raft data to the serial number dictionary"
Answer: 81.0

User story: "As discussed in #dm-lsstcam, config/lsstCam.py is being replaced with config/isr.py.  All references to config/lsstCam.py need to be updated and the file removed from the repo."
Answer: 138392.0

User story: "for the query {{SELECT objectId,ra_PS FROM Object WHERE objectId BETWEEN 417857368235490 AND 420949744686724;}}    the integration test fails, the {{qserv}} and {{qserv_async}} results are much shorter than the {{mysql}} results.     "
Answer: 57551.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: "With larger numbers of DCR subfilters (e.g. 5) the dcrModel solution can sometimes oscillate between iterations of forward modeling. This results in premature termination of the modeling loop, because the convergence may improve by a large amount in one iteration, and by a very small amount in the next, triggering the convergence end condition. One solution is to set a small enough gain on the new model solutions so that modeling converges smoothly, but then more iterations are required to reach the same level of convergence. Instead, the gain should adapt to how well the model is improving compared to predictions."
Answer: 21646.0

User story: "Under the config/ dir, will be a 'configurables' directory. A user-defined configuration file can be dropped in this directory, and any time the DM L1 system is moved into standby state, the files in this directory will be read and inserted into a redis database instance. When DM offers a list of possible configs for the operator to choose from, the primary keys  (config file name) that define each separate config file will be presented to the operator as a comma delimited list. When the operator chooses a particular name, the key/value pairs for that configuration is presented.    Note: A formal enumeration of keys in a user configurable file will be provided. It is expected that the list of configurable options will grow as the system approaches completion. Users will be able to select values for the list of some or all of the keys, and name this configuration with a unique name.         A default configuration will be present and used if a unique config is not selected.    If a config file only sets values for two out of say, 50 possible keys in the formal enumeration, the other 48 keys will be set to default values.    One of the many uses these files will be used for is to describe which CCDs in the FPA are to be read. This data will be able to be specified as *_inclusive_* or _*exclusive.*_         The configurables dir will have a README and a couple of example files."
Answer: 15984.0

User story: "SSIA"
Answer: 25778.0

User story: "SSIA"
Answer: 25782.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 L1 image ingest optional values reside in a yaml file called L1SysCfg.yaml. This file resides in ~/src/git/ctrl_iip/python/lsst/iip. It was initiated and has resided here since early prototype days.    This file contains the user names and passwords for the message broker consumer accounts. Every consumer or publisher needs credentials in order to send and receive messages on a per vhost basis.    It is also used to allocate a pool of Forwarders to different jobs such as AT  Archive Forwarders, MT Archive Forwarders, Prompt Processing and Alert Forwarders, and Forwarders to be used with the Catchup Archiver. The CSC reads this section of the file to discover which Forwarders will be working with each CSC, their hostnames, their message consume queues, their proper names, and their login account names,     Finally it is a place where general config settings can be located, both for operational as well as testing uses, such as whether checksum validation of transferred files is to be used, the name of the target directories in the Archive, the user name of the user that owns the Archive, a list of which CCDs in which Rafts are to be excluded from this sessions work, etc.         This ticket is the overarching ticket for a number of other tickets that each describe a part of the work necessary to refactor the config section of L1 into a config system that:   # splits sections of the initial cfg file into pieces - avoiding the need for each component to read the entire config file.   # Introduces the ability for user defined config files to be added to the system, and then selected for use at start-up time   # A means by which any specific config settings for a telescope session can be closely identified with the session for the history of the survey(s) and beyond."
Answer: 26214.0

User story: "Although LDM-538 contains a test specification covering this test  we should now have a test plan which is a subset of that for the 503-8 test .. or do we already have a test report for this ?  (I think we do)  then it may be a matter of getting that input to the Jira system,"
Answer: 149400.0

User story: "The SQuaSH API pod fails to initialize sometimes. The api container which runs the flask web app must keep trying the connection with the database if the cloudsql-proxy container has not started yet."
Answer: 960503.0

User story: "This notebook shows how to use the LSST verification framework to create a new metric and track metric values in SQuaSH."
Answer: 393359.0

User story: "Create an example dashboard for ap_verify metrics in Chronograf."
Answer: 123845.0