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: "Docs claim it supports globs; it doesn't.    {{\-\-show history=\*do\*}} gives:  {{Error: config has no field \*do\*}}  which, for {{processCcd.py}} is clearly wrong."
Answer: 4503.0

User story: "Using the work done in [DM-15098|https://jira.lsstcorp.org/browse/DM-15098], preflight should populate a region attribute when constructing a dataSetRef from a given object and registry."
Answer: 181431.0

User story: "For Firefly,     create a prototype LSST footprint overlay on image per LSST footprint data of JSON format describing the coverage by lines of segments in the image coordinate domain.     Use the prototype JSON representation from DM-15332.     "
Answer: 24598.0

User story: "Simply turning on {{doUnresolved}} does not work because there are other config parameters that need to be set."
Answer: 1422.0

User story: "use the antlr4 generated IR in qserv.    keep the old antlr parser. decide whether to generate IR all the time or ifdef it out.    we may want to dump old-antlr-generated IR to the log occasionally."
Answer: 18716.0

User story: "This ticket is concerned with merging changes to the code made to improve performance. There was a large drop in performance between KPM20 and KPM30 in the cluster at in2p3. Performance was restored to previous level for the LSST dataset, but only in the case where join queries were not included in the batches of test queries. Single join queries run quickly, but when run with a group of queries the entire system slows down significantly. This is thought to be caused by MariaDB not having sufficient resources and is still being sorted out. MariaDB optimizations should improve the situation. The number of computers in the cluster at in2p3 may simple not have enough resources to meet the KPM30 requirements.    Code was modified to add instrumentation for diagnosis and other changes were made to improve performance. Most of the changes were in qdisp (where the threading model was changed significantly between KPM20 and KPM30), wsched (as testing showed some significant problems), and memman (used by wsched and its mlock calls took significant time).    Part of the performance issue was configuration values appropriate for the PDAC were applied to the in2p3 cluster. Configuration files are part of the container. Kubernetes has tools for writing the appropriate configuration files to individual systems and they should be used as soon as practical."
Answer: 30061.0

User story: "Gather storage requirements for disaster recovery of managed databases."
Answer: 1.0

User story: "Provide preliminary plan for design."
Answer: 262034.0

User story: "Review LDM-129 and other relevant documents to design storage plan."
Answer: 2.0

User story: "With Data Backbone data transfer node in place, refine method and implementation for logging data transfer details."
Answer: 2.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: "Implementing RFC-352  prepping for the PipelineTask fka SuperTask conversion in two stages. DM-2639 changed the TaskRunner to call a Task's runDataRef method.  During code review [~<USER> points out that  {{MeasureCrosstalkTask}} would be a simple refactor. The {{run}} method is essentially the currently public-interfacing function {{extractCrosstalkRatios}}.  "
Answer: 36022.0

User story: "Implementing RFC-352  prepping for the supertask conversion in two stages. DM-2639 changed the TaskRunner to call a Task's runDataRef method.  During code review [~<USER> points out that {{ForcedPhotImageTask}} (and its children {{ForcedPhotCcdTask}} and {{ForcedPhotCoaddTask }} would be simple to refactor."
Answer: 36030.0

User story: "Implement Jupyter Notebook (ipynb) to HTML conversion for the notebook-based report system (described in https://sqr-023.lsst.io/v/DM-15003). This conversion is built on [nbconvert|https://nbconvert.readthedocs.io/en/latest/]. The main contributions of this ticket are:    # Theming of the HTML to look like an LSST document  # Integration with the [sqre-uservice-nbreport|https://github.com/lsst-sqre/sqre-uservice-nbreport] microservice (ideally this is done with a celery task queue)  # Upload the HTML and notebook to LSST the Docs."
Answer: 17744.0

User story: "The goal is to address concerns raised during the internal review and other stakeholders and prepare the final version of the document describing use cases for the batch processing service."
Answer: 58940.0

User story: "The goal is to write an initial version of use cases based on the input provided by operators and scientists (familiar with operations) and review it internally at NCSA."
Answer: 2.0

User story: "The goal is to collect input from operators regarding desired features of the offline batch processing service."
Answer: 2.0

User story: "We begin installation steps on lsst-ddb-* test machines for an xrootd installation that will support oauth2/scitokens and eventually third party copy over https.    We also test generation of scitokens for use with gfal-copy, FTS against the xrootd installation."
Answer: 7.0

User story: "Attendance and participation in Tucson for the Pathfinder Early Integration Activity involving Spectrograph integration."
Answer: 4.0

User story: "Although the HeaderService code was written to be compatible with Python2 and Python3, the migration has not been done or tested yet."
Answer: 37355.0

User story: "Write initial requirements document for the Observatory Operations Data Services, using info gathered from activity DM-15281"
Answer: 200103.0

User story: "Gather information from existing documents on the Observatory Operations Data Service, and write notes about what was found"
Answer: 3.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: "Start a document with best practices for containers and NCSA guidelines.  The intent of this is to get a document going and pass it around so that we can attach additional information and get everyone on the same page about development practices and usage of containers."
Answer: 87860.0

User story: "Temperature and pressure profiles are used as an input for the determination of the Rayleigh scattering from radiative transfer simulation.    The question whether or not MERRA-2 3D interpolated tables are accurate enough to be used as an input for the simulation can be answer by checking the interpolations against weather balloons soundings.    Daily launches are reported from Antofagasta Airports.    The data have been retrieved ( [https://www.ncdc.noaa.gov/data-access/weather-balloon/integrated-global-radiosonde-archive),] processed, and compared to MERRA-2.    The preliminary findings are reported in a presentation available at :    https://confluence.lsstcorp.org/display/DM/2018-08-06+Calibration+Products+Standup"
Answer: 181876.0

User story: "Code for how the magic {{config.biasCorr}} should be added so that it can be used by experts to check/recalculate this number if needed."
Answer: 62169.0

User story: "Right now {{DataUnitRegion}} and {{DataUnitJoin}} are two separate, but roughly similar objects.  Unify them, potentially also adding a base-class or mix-in for things they have in common with {{DataUnit}}."
Answer: 9879.0

User story: "I communicated with Alex Drlica-Walker about best practices for interacting with Emacs in the JupyterLab terminal emulator.  See [here|https://github.com/LSSTScienceCollaborations/DMStackClub/issues/56] for conversation.    Relatedly, I made my first attempt at using the new lspdev on-boarding procedure.  Procedure emailed to [~<USER>.    I also set up my duo account."
Answer: 1.0

User story: "Gregory and Vandana will discuss the table pop-up options need from science user point of view, make a design proposal for developers. "
Answer: 170086.0

User story: For ap_pipe and ap_verify we want symmetry between table creation and the configs of the two database interface options currently implemented.    This ticket will create a create_tables methods on AssociationL1DBProto that will call the "create schema" method in AssociationDBSqlite.  It will also add a db_name override to the AssociationL1DBProto config allowing it to behave similarly to that of AssociationDBSqlite.
Answer: 253452.0

User story: "In preparation to fully migrate the HeaderService from python2.7 to Python3.6 we'll need a stable and new docker installation/image with alll required software. These include fitsio/numpy and ts_sal"
Answer: 7154.0

User story: "Meetings bringing together networking, security, system administration, and technical staff to plan next phase of kubernetes commons design and architecture."
Answer: 2.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: We need an automated way to verify that the columns and data types returned by metaserv match the columns and types in DB, for all tables returned by metaserv.    Currently, it's not the case. Here is an example:    For _DS_wise.wise_00.allwise_p3am_cdd_, metaserv returns "double" for all types that should be "int" or "long" in db: _band_, _naxis_, _naxis1_, _naxis2_ - these are all "int" fields in DB, _cntr_ - is "long".    SUIT uses _band_ to construct WISE image URL, wrong type results in wrong URL.
Answer: 4009.0

User story: "The {{firefly_client.plot}} module includes a method for uploading and showing a table in Firefly. Add options for specifying the columns from the table that appear, as well as filters."
Answer: 134039.0

User story: When {{textangle}} is provided in a region description, Firefly does not draw the associated region. The {{afw.display.dot}} method allows specifying the textangle, but when this argument is provided, the region is not displayed.    Example of region text generated by {{afw.display.dot}} that does not display:  {noformat}text 1074 110 "Text" # color=yellow textangle=45.0  {noformat}    The format we need to support for angle is {{textangle=}} after the hash symbol.
Answer: 73293.0

User story: "Per RFC-504, scarlet will be added as a GitHub fork to the stack."
Answer: 11570.0

User story: "Add features to LTD Keeper that are needed by the notebook-based report system's API server (as developed in DM-15199):    * {{autoincrememnt}} feature for edition slugs so that LTD Keeper can create editions with monotonically increasing integer edition numbers that serve as notebook report instance IDs.  * {{manual}} tracking mode for editions so that the nbreport server can manage the updates of new editions with builds."
Answer: 13681.0

User story: A major obstacle to opening up K8 at NCSA is ensuring that network level policy is enforceable and audit-able.  To that end, security focus on separation of "backend services" from "user facing services".  Aside from proper authentication and authorization there should be network level enforcement of this logical separation.  From the K8 security meeting notes:   *  [Separation] between the users (JupyterHub) and the services (qserv, etc.)?   ** Physical network separation   *** (minus) Seems counter to the Kubernetes model (elastic computing)   *** (plus) More secure   *** (minus) More work and less automated to move hardware between networks   ** Network Policies   *** _*Don't want to blindly trust that the software implementation. How can we validate that the Network Policies are enforcing what is configured?*_   **** [<USER>https://wiki.ncsa.illinois.edu/display/~<USER> and [Matthew Long|https://wiki.ncsa.illinois.edu/display/~<USER>will run a test   * Audit network traffic to uniquely identify container and user that given network traffic originated from?   ** Still no solution. Depends on the implementation of the first goal (network isolation)
Answer: 43230.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 the /kpms API resource to feed the KPMs dashboard. It should be possible to query metrics and specification tags as well as specification query metadata stored as JSON fields in the SQuaSH database.    API changes required by DM-14751"
Answer: 65.0

User story: A DatasetType in a Registry must always have the same StorageType.  A DatasetType in a Registry need not always be either a virtual or concrete composite; that is a Dataset-level distinction.  That means the DatasetType StorageClass stored in a Registry cannot be responsible for determining whether a Dataset is a virtual or concrete composite.    We currently avoid that problem by allowing the Datastore and the Registry to have a StorageClass associated with the same DatasetType.  This is at least confusing, but I think it's also fundamentally impossible with making StorageClasses global state that is initialized at module-import time, because that would take StorageClass configuration (and hence assembler configuration) out of Butler.    To address this, we need:   - A new mechanism for configuring a Butler to write concrete vs. virtual composites for a particular StorageClass.   - A new way to record whether a Dataset was written as a concrete or virtual composite to replace saving a "read StorageClass" within the Datastore.  Note that this could be (and probably should be?) Registry content, because concrete vs. virtual is *not* Datastore-private information, and that there is already a Dataset.assembler field in Registry that was intended for this purpose.  If we opt not to use it on this ticket, we should remove it instead.
Answer: 33176.0

User story: "Make sure new storage class registrations cannot modify old ones.         To make the discussion on this ticket readable for posterity, the original ticket description was:  {quote}Having all consumers of StorageClasses (which includes any code that wants to create a DatasetType) responsible for constructing a StorageClassFactory (from a config file, since they don't know if the singleton already exists) is not tenable. StorageClasses are global state, and they need to be available at module-import time.    That also means we should move them out of the configuration for Butler, which makes sense, because Butlers don't get to pick their StorageClasses    This is probably also a good time to make sure we don't have any custom StorageClasses in tests, or if we do, make sure they are run in a way that prevents them from ever polluting the real set of StorageClasses in other tests.  {quote}"
Answer: 13446.0

User story: "With support for {{asinh_q_value}} and {{gamma_value}} added to {{firefly_client.FireflyClient.set_stretch}}, make these available in the {{display_firefly}} backend as {{Q}} and {{gamma}}."
Answer: 5564.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "There are a few minor bugs to do with using {{showCamera}} to display raw and calibration frames such as biases.  Additionally the code to handle calexps was fragile, as was the handling of cameras for which {{ccd=ccd.getId()}} is an invalid dataId field.    Please fix them."
Answer: 20015.0

User story: "When a new {{MultibandExposure}} is initialized using the {{fromExposures}} method, it doesn't pass the {{psf}} from each {{Exposure}} into the new objects.  To fix this, {{afw.image.multiband.fromTriples}} should be updated to take keyword arguments that can be used to pass additional parameters to the new multiband objects."
Answer: 10517.0

User story: "daf_butler currently uses intermediate module paths (i.e. modules that should be considered implementation details, because their symbols are lifted into a parent package) when specifying formatters in config files (and possibly other things).  This currently makes the gen3-middleware stack incompatible with weekly builds w_2018_29 and later, because some of those intermediate modules changed in afw.  We should fix this by removing the source of fragility."
Answer: 14.0

User story: "Get JL environment running on PDAC cluster."
Answer: 25932.0

User story: "Update firefly_client to accept Q parameter for asinh stretch algorithm. When no value is specified, 'NaN' (case sensitive) should be passed in serialized range string to Firefly. (This would make Firefly to pick up a reasonable default based on stretch and data range.)    Update the documentation for set_stretch.  "
Answer: 1486.0

User story: "We have ~agreed on a better name for SuperTask class, {{PipelineTask}} looks like a better one for everyone. We should rename the class and move it to {{pipe_base}} in preparation to merging all gen3 stuff with master."
Answer: 11561.0

User story: Alex Drlica-Wagner has added a facility to set the colour map in {{display_matplotlib}};  this makes sense, but should be pulled up to the {{afwDisplay}} level.  Because we'd implement a dummy version of the API in {{interface.py}} there would be no immediate need for other backends to support this immediately.  The proposed API is:  {code:java} display.setImageColormap(name){code}  where {{name}} is a string;  the only one I see in common between {{ds9}} and {{matplotlib}} is {{"gray"}} and {{"viridis"}} (which {{firefly}} doesn't understand) so it is probably not worth trying to come up with a set of standard names beyond "gray".    The interpretation of "name" is backend specific;  for {{matplotlib}} I propose that we interpret it as {{pyplot.cm.name}}.  If {{name}} is invalid, we should attempt to interpret it as a colormap and use it directly (or possibly vice-versa).  For {{ds9}} I'll pass it to an {{xpa cmap}} command and trap errors. I leave it up to IPAC to make suitable choices for {{firefly}}.
Answer: 36265.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: "On the PR for DM-15098 [~<USER> noticed we are explicitly specifying {{sha1}} where we should (probably) use a more general {{hash}} in both {{schema.yaml}} and the Butler API. Fix this."
Answer: 10134.0

User story: "The {{login}} subcommand for nbreport (See https://sqr-023.lsst.io and DM-15003) will obtain a personal access token for a user from GitHub. This personal access token will then be used to authenticate the user on api.lsst.codes/nbreport (DM-15199) and authorize that user based on their organization memberships. This technique is similar to what we're already doing at https://github.com/lsst-sqre/sqre-codekit Doing so ensures that a person's actual GitHub password never passes through our servers, and instead resides locally on their machine."
Answer: 1262.0

User story: "Current version of QG builder does not check whether any output Datasets that it generates are already there in the Registry. We need an option to either filter those existing Datasets from output or generate an exception."
Answer: 50663.0

User story: "This is a spin-off of DM-15189 containing (hopefully all of) the supporting work in daf_butler for that ticket, separated into this ticket to merge it sooner and avoid conflicts with other daf_butler development."
Answer: 10004.0

User story: "Make adjustments to the schema to incorporate feedback from RFC-484 and the associated review.    Should also sync the technote with the schema YAML on daf_butler master (only very minor and structural changes so far).     "
Answer: 71879.0

User story: "Define a userful {{\_\_str\_\_}} for {{Butler}} that provides minimal useful information:  So collection and root if there is a unique root, and something else (TBD) otherwise."
Answer: 38700.0

User story: "An in memory datastore was added in DM-13363. Now we need to support chaining of datastores such that the in memory datastore can be used as a cache.    This will include modifications of the configuration system to specify these relationships and the creation of at least one special datastore class for chaining.    per-datasetType Cache expiry may be included."
Answer: 20193.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 code to estimate overscan levels do not take enough care to handle low signal levels.  Once the noise level is small enough a simple median does not return an estimate of population median (think about the case that the pixels have equal probability of being either 1 or 2;  the population median is 1.5, but the median will be 1 or 2).  With enough noise this isn't much of a problem as the noise provides dithering;  even then there can be biases based on the noise's pdf.    For bias levels this is an issue; for example the bias-subtracted over-scan bias frames from auxTel (taken on 2018-07-21) have amplifier medians that differ by significant fractions of a DN – and that's enough to mess up faint light measurements as some of the effect is in overscan correction used to build the bias frames.    Using a mean instead of a median "solves" this problem, but at the expense of being sensitive to CR hits (or other outliers) in the overscan.    One simple solution to the median problem is to find the mean of sets of pixels, then estimate the median of the result (this essentially raises the noise level);  another — which we used in SDSS — is to form a histogram and estimate its median.  This should be implemented in {{afwMath.Statistics}} as a robust median;  adding a clipping option to {{afwMath.Statistics}} would also probably be fine.    The issue with a non-robust mean can be resolved by exposing the {{StatisticsCtrl}} argument and using a clipped mean.
Answer: 59841.0

User story: "In RFC-29 we allowed Python {{logging}} to be used in Python code so long as the log messages were forwarded to {{lsst.log}} whenever C++ logging is a possibility. A forwarder does exist as {{lsst.log.LogHandler}} and instructions for its use are available at https://github.com/lsst/log/blob/master/doc/mainpage.dox#L59    To enable science pipelines to forward these Python log messages we need to setup this log handler in {{pipe_base}}."
Answer: 272387.0

User story: "This ticket is intended to create a new microservice within the api.lsst.codes umbrella called {{uservice_nbreport}}. This service is envisioned in https://sqr-023.lsst.io (DM-15003). This ticket will involve creating the codebase and configuring a minimally-viable deployment. Many domain specific features like customized HTML generation may be index pages will be deferred to future tickets."
Answer: 21692.0

User story: "Following the design described in https://sqr-023.lsst.io, the nbreport tool needs to be capable of handling the git clone of a notebook repository in order to facilitate single-command production of notebook-based reports.    This ticket will add that plumbing to the https://github.com/lsst-sqre/nbreport package and integrate it with the {{nbreport test}} command (DM-15167)"
Answer: 1996.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: From https://github.com/lsst/display_matplotlib/issues/2:    {quote}  I've tried to plot source catalog objects as ellipses using the display.dot function and passing source.getShape as the first argument:    {code}  #Display the cutout and sources with afw display  image = cutout.image  #image = calexp.image    plt.figure()  afw_display = afwDisplay.Display()  afw_display.scale('asinh', 'zscale')  afw_display.mtv(image)  plt.gca().axis('off')    # We use display buffering to avoid re-drawing the image after each source is plotted  with afw_display.Buffering():      for s in sources:          afw_display.dot('+', s.getX(), s.getY(), ctype=afwDisplay.RED)          afw_display.dot('o', s.getX(), s.getY(), size=20, ctype='orange')               #ADW: This should work, but doesn't?          afw_display.dot(s.getShape(), s.getX(), s.getY(), size=35, ctype='orange')      # Our "ultra-faint galaxy" (e.g. smudge)      afw_display.dot('o', x_target, y_target, size=35, ctype='cyan')  {code}    However I get the following error:    {code}  /opt/lsst/software/stack/stack/miniconda3-4.5.4-10a4fa6/Linux64/afw/16.0-19-g2da375352/python/lsst/afw/display/interface.py in dot(self, symb, c, r, size, ctype, origin, *args, **kwargs)      526             symb = afwGeom.ellipses.Axes(symb)      527   --> 528         self._impl._dot(symb, c, r, size, ctype, **kwargs)      529       530     def line(self, points, origin=afwImage.PARENT, symbs=False, ctype=None, size=0.5):    /opt/lsst/software/stack/stack/miniconda3-4.5.4-10a4fa6/Linux64/display_matplotlib/16.0+11/python/lsst/display/matplotlib/matplotlib.py in _dot(self, symb, c, r, size, ctype, fontFamily, textAngle)      371       372             axis.add_artist(Ellipse((c + x0, r + y0), xradius=symb.getA(), yradius=symb.getB(),  --> 373                                           rot_deg=math.degrees(symb.getTheta()), color=ctype))      374         elif symb == 'o':      375             from matplotlib.patches import CirclePolygon as Circle    TypeError: __init__() missing 2 required positional arguments: 'width' and 'height'  {code}    I've confirmed that {{matplotlib.patches.Ellipse}} does expect the width and height arguments (at least in recent versions).  {quote}
Answer: 9106.0

User story: Follow the instructions in {{obs_lsstCam/policy/README}} to create obs_comCam as a "subclass" of obs_lsstCam
Answer: 836114.0

User story: "After upgrading to numpy 1.14, `lsst.ip.diffim.dipoleFitTask` raises a new error:    {code:python}  python/lsst/ip/diffim/dipoleFitTask.py:303: FutureWarning: `rcond` parameter will change to the default of machine precision times ``max(M, N)`` where M and N are the input matrix dimensions.  To use the future default and silence this warning we advise to pass `rcond=None`, to keep using the old, explicitly pass `rcond=-1`.  {code}    It was suggested by [~<USER> that we simply set `rcond=-1`."
Answer: 5366.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Write abstract interfaces and at least one concrete implementation (AuxTel) for raw data ingest into the Gen3 Butler.    I will probably actually start with attempting to ingest raw HSC data, as obs_subaru already implements the existing Gen3 customization hooks, and extend to AuxTel on the same ticket to (start to) ensure that the design doesn't "bake in" a particular camera.
Answer: 45902.0

User story: "In order to control the formatting of the test cases summary and the requirements traceability tables, a couple of functions need to be created and that tables need to be removed from the template."
Answer: 20082.0

User story: "Catch-all ticket to describe sizing model refactoring work.   * Data generation:   ** All the various data products generated (or managed) by LSST   ** All the processes creating the data products   * Data retention and management   ** All data lifecycle and management policies (copy, migrate, purge, delete)   * etc (need to copy extant documentation about the plan into this ticket)   *    *    *    * Draft of new sizing model"
Answer: 837294.0

User story: "Reprocess the HSC RC2 dataset, as defined in DM-11345, using Stack w_2018_32. Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{skyCorrection.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}}. "
Answer: 56179.0

User story: "On https://github.com/lsst/display_matplotlib/issues/1, the request is:    {quote}  Would it be possible to give the user control over the colormap used to display images? I see that this is currently set to cmap=pyplot.cm.gray.  {quote}"
Answer: 11593.0

User story: "Currently, columns ROW_IDX and ROW_NUM are sent to the client for every table request.    It's only used in a few cases.  Change it so that these columns are only sent if requested and not by default."
Answer: 27402.0

User story: "Lorena Mezini, an undergraduate working with Erin Sheldon, noticed that when scarlet fits positions, the mean position errors are ~{{0.15}} in both x and y (see attached plot). What's stranger is that one of the objects in her simulations seems to have a mean positional error of 0 in x and y while the other shows the offset.    Her dataset were generated using galsim, with very low noise and fixed bounding boxes (25 pixels) on single band images. The sources both have very small ellipticity (~.01) with random orientations, the same shear, and identical FWHM. The plot shows an example with 100k blends, each with 2 sources separated by 11 pixels.    This ticket is to investigate this behavior to understand the conditions that lead to two seemingly identical objects being deblended differently."
Answer: 7348.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: During the test of the newly deployed lsst-pdac/portal/suit, I stumbled on something that is obviously wrong. A position search on "NEOWISE-R Year 1 Single Exposure (L1b) Source Table" at  (0.014937 -0.008658) with radius 10" returned data with w1flux and w1sigflux empty while w1mpro and w1sigmpro both have data.          Upon further study, the w1flux and w1sigflux columns seem to have "char" as data type, while the meta data showed that they should be "float". We need further investigation into this.          The downloaded data is attached.          7/25/2018    Further investigation revealed that those two fields had datatype "UNKNOWN" when returned from DAX API dbserv V1. Ticket DM-15206 has been created for this.           8/28/2018    An unknown datatype's value could not be passed properly and displayed. Firefly does not need to be modified. 
Answer: 56360.0

User story: "There have been some adjustments for the permissions on the file sets for Kubernetes.  Update DMTN-084 to reflect that."
Answer: 411090.0

User story: "now that antlr4 works in qserv master, we need to merge the antlr4 integration branch {{u/<USER>antlr4}} back to master. There's a few bugs related to recent changes on master, these bugs should be fixed at the same time so that the tip of the antlr4 integration branch works in travis before merging to master."
Answer: 919.0

User story: "When actually, it was 2014. This is important for correctly assigning copyright (as well as for enabling greater pedantry, etc)."
Answer: 9644.0

User story: "[~<USER> writes:  {quote}  With w_2018_28 in {{forcedPhotCoadd}}, I got many WARNs like this:  {code}  multiBandDriver.forcedPhotCoadd.applyApCorr: Cannot aperture correct undeblended_ext_convolved_ConvolvedFlux_1_6_0 because could not find undeblended_ext_convolved_ConvolvedFlux_1_6_0_flux or undeblended_ext_convolved_ConvolvedFlux_1_6_0_fluxSigma in apCorrMap  {code}  These did not appear back in w_2018_26.  {quote}    This is from DM-15045."
Answer: 2846.0

User story: "This ticket follows on DM-15150 to create a command line interface for the {{nbreport}} client application.    The CLI is designed in https://sqr-023.lsst.io/v/DM-15003    Specifically, this ticket will create the {{nbreport test}} test CLI. This command demonstrates most of the notebook-related workflow without involving GitHub or the api.lsst.codes/nbreport service. It will    - Create a test report instance from a report repository  - Render the notebook from the template  - Execute the notebook"
Answer: 7256.0

User story: In the afw/ups/afw.table file the dependency to the "log" package is duplicated, and the dependency to "astropy"  is listed twice, the first time as setupRequired the second time as setupOptional.
Answer: 26.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 order to create the KPM dashboard we must be able to distinguish astrometry, photometry and image_quality metrics in {{validate_drp}}. This can be done by adding these tags in the metrics definition for the {{validate_drp}} package. Similarly we need to distinguish the specification thresholds minimum, design and and stretch. This is done by adding these tags in the specifications for the {{validate_drp}} package."
Answer: 26258.0

User story: "For historical reasons HSC uses a custom ISR task;  this is one of the reasons why the changed definition of the crosstalk task discussed in DM-15152 wasn't caught by our testing (as {{ci_hsc}} didn't see the change).    Following discussions with [~price] it sounds as if we could switch HSC to use the generic ISR, leaving us with one fewer pieces of code to manage specially."
Answer: 111265.0

User story: "Now that base containers have been updated to Centos7 and devtoolset6, time to try again and see if we can add ANTLR4 to the build without breaking CI..."
Answer: 451.0

User story: "A simple unit test addition that was created as part of a demo of pytest test coverage tools."
Answer: 1265.0

User story: "Refactor Fits read part of image processing:    - created a framework for processing whole FITS file (all extensions)  - improved image reading, no more 2D array  - improved mask performance  - broke up FITSRead into multiple files  - created a new package plotdata for FitsRead related processing  - improved cacheing but still needs more work  - moved header processing the the client"
Answer: 20224.0

User story: "fix case01/queries/1012_orderByClause.sql.FIXME     Requires parser work so it will be fixed in the antlr4 parser: add the ability to have a function call in ORDER BY.    Requires changes to qana to allow the function call in the ORDER BY."
Answer: 53501.0

User story: "lsst_int_lspdev should be the new group."
Answer: 30.0

User story: "Hiding symbols in the pybind11 wrapped modules (potentially) reduces the build size and enables importing modules wrapped with different pybind11 versions in the same session."
Answer: 81151.0

User story: "This ticket is to develop and test APIs for rendering a Jinja template into a Jupyter notebook. This is a key function in the notebook-based report system, described in https://sqr-023.lsst.io."
Answer: 1515.0

User story: "replace placeholder values with concrete values that will work with our test dataset.    replace unpopulated {{extendedParameter}} with {{rRadius_SG}} to determine object size."
Answer: 4207.0

User story: "Implement RFC-500 by renaming the {{invert}} method of geom {{AffineTransform}}, geom {{LinearTransform}} and afw {{GridTransform}} and the {{getInverse}} method of afw {{Transform}} and astshim {{Mapping}} to {{inverted}}.    Also rename the {{simplify}} method of astshim {{Mapping}} to {{simplifed}} for the same reason. Note that this is little used outside of astshim."
Answer: 37683.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: "MERRA-2 provides an Aerosol Optical Depth table and the question is wether it is useful for Aux.Tel. observations.         I have downloaded 2-D and 3-D tables from NASA server, I have written python scripts to extract, integrate and sum mixed components. I shall now look at :   * Integrated aerosol (AODANA) versus mixed components :    BCINC tzyx Black Carbon Mixing Ratio Analysis Increments kg kg-1  DUINC tzyx Dust Mixing Ratio Analysis Increments kg kg-1  OCINC tzyx Organic Carbon Mixing Ratio Analysis Increments kg kg-1  SSINC tzyx Sea-salt Mixing Ratio Analysis Increments kg kg-1  SUINC tzyx Sulfate Mixing Ratio Analysis Increments kg kg-1    And there associated spatial gradients.                         "
Answer: 10745.0

User story: "{{-- pragma sort result}}     needs to be added to the .sql file for case01/queries/0004_lightCurve.sql so that the output of the query (not sorted by mysql or qserv) gets sorted before being compared."
Answer: 7.0

User story: "qserv does not support subqueries; rewrite the query in a non-subquery form."
Answer: 1318.0

User story: Using {{w_2018_28}} and {{pipe_analysis}} at commit {{ebd48cf}}, {{coaddAnalysis.py}} failed in the COSMOS tract=9813 filters HSC-G, HSC-R, HSC-Z, and HSC-Y:     {code:java}  Traceback (most recent call last):    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_base/16.0-2-g852da13+6/python/lsst/pipe/base/cmdLineTask.py", line 392, in __call__      result = task.run(dataRef, **kwargs)    File "/home/<USER>stack/pipe_analysis/python/lsst/pipe/analysis/coaddAnalysis.py", line 348, in run      hscRun=repoInfo.hscRun, wcs=repoInfo.wcs)    File "/home/<USER>stack/pipe_analysis/python/lsst/pipe/analysis/coaddAnalysis.py", line 450, in readSrcMatches      if not hasattr(matches[0].first, "schema"):  IndexError: list index out of range  {code}    The command I ran was   {{coaddAnalysis.py /datasets/hsc/repo/ --calib /datasets/hsc/repo/CALIB  --rerun RC/w_2018_28/DM-14988  --id tract=9813 filter=HSC-G -c doWriteParquetTables=True}}   (and 3 other filters)
Answer: 2445.0

User story: "Update LDM-639 from Jira after removing Req ID from Test Case name"
Answer: 90.0

User story: From Bill Wisher at Princeton: "The new tiger has two login nodes.  #1 is tigergpu, an Intel Broadwell server.  And #2, tigercpu, an Intel Skylake server."  So I believe they will each need their own builds, please add them.
Answer: 63801.0

User story: "* In the LDF environment we won't display code changes, the monitor app should be flexible enough to suppress the corresponding column in the table if theres no data do display   * Also, the table should report RUN_ID instead of CI_ID and link correctly to the corresponding URL."
Answer: 352597.0

User story: "Create {{nbreport}}, the Python client-side app for the notebook-based report system.    This ticket will set up the package and its CI infrastructure so that features can be added in following tickets."
Answer: 1343.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: "*  clone the demo notebook [repository|https://github.com/lsst-sqre/notebook-demo].  * check out the {{prod}} branch  * branch the {{prod}} branch to a personal branch: e.g. {{u/<USER>DM-15123}}  * make  and commit a change.  * push personal branch back to github."
Answer: 2829.0

User story: "Browse through notebooks in the {{prod}} branch and improve content: e.g. language, plot labels.  The repository is [here|https://github.com/lsst-sqre/notebook-demo/tree/prod]."
Answer: 34517.0

User story: I came across the following log record from processCcd-ing HSC data {{--id visit=38950 ccd=64}}     {code:java}  processCcd.charImage.measurePsf.makePsfCandidates WARN: Failed to make a psfCandidate from star 33458070113746946:    File "src/image/Image.cc", line 84, in static lsst::afw::image::ImageBase<PixelT>::_view_t lsst::afw::image::ImageBase<PixelT>::_makeSubView(const Extent2I&, const Extent2I&, const _view_t&) [with PixelT = float; lsst::afw::image::ImageBase<PixelT>::_view_t = boost::gil::image_view<boost::gil::memory_based_2d_locator<boost::gil::memory_based_step_iterator<boost::gil::pixel<float, boost::gil::layout<boost::mpl::vector1<boost::gil::gray_color_t> > >*> > >; lsst::geom::Extent2I = lsst::geom::Extent<int, 2>]      Box2I(Point2I(470,-1),lsst::geom::Extent2I(21,21)) doesn't fit in image 2048x4176 {0}    File "src/PsfCandidate.cc", line 182, in std::shared_ptr<lsst::afw::image::MaskedImage<ImagePixelT1, int, float> > lsst::meas::algorithms::PsfCandidate<PixelT>::extractImage(unsigned int, unsigned int) const [with PixelT = float]      Extracting image of PSF candidate {1}  lsst::pex::exceptions::LengthError: 'Box2I(Point2I(470,-1),lsst::geom::Extent2I(21,21)) doesn't fit in image 2048x4176 {0}; Extracting image of PSF candidate {1}'  {code}    Then the processing carries on and finished processCcd just fine.  This "LengthError" didn't appear by using {{w_2018_17}} but appeared using {{w_2018_18}}.   It still appears with the most recent weekly of {{w_2018_28}}.    
Answer: 383299.0

User story: "Reprocess the HSC RC2 dataset, as defined in DM-11345, using Stack w_2018_30. Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{skyCorrection.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}}. "
Answer: 54862.0

User story: "Run pipe_analysis scripts   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    and validate_drp   # matchedVisitMetrics.py   # validateDrp.py   # reportPerformance.py   # dispatch_verify.py    with the w_2018_28 RC2 outputs from DM-14988"
Answer: 1570.0

User story: "While writing the paper with Erin on shear measurements on coadds, a number of one off questions arose that needed investigation. "
Answer: 17.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: To reproduce, run:  {code:java}  processCcd.py /datasets/hsc/repo/  --rerun private/user/name --id visit=36234 ccd=24  {code}    It finished successfully using {{w_2018_26}}, but failed using {{w_2018_27}} or {{w_2018_28}} with the following:  {code:java}  processCcd FATAL: Failed on dataId={'visit': 36234, 'ccd': 24, 'field': 'SSP_WIDE', 'dateObs': '2015-07-21', 'pointing': 1297, 'filter': 'HSC-I', 'taiObs': '2015-07-21', 'expTime': 200.0}: RuntimeError: Unable to measure aperture correction for required algorithm 'modelfit_CModel_exp': only 1 sources, but require at least 2.  Traceback (most recent call last):    File "/ssd/lsstsw/stack3_20171021/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_base/16.0-2-g852da13+6/python/lsst/pipe/base/cmdLineTask.py", line 392, in __call__      result = task.run(dataRef, **kwargs)    File "/ssd/lsstsw/stack3_20171021/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_base/16.0-2-g852da13+6/python/lsst/pipe/base/timer.py", line 150, in wrapper      res = func(self, *args, **keyArgs)    File "/ssd/lsstsw/stack3_20171021/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_tasks/16.0-4-g08dccf71+3/python/lsst/pipe/tasks/processCcd.py", line 188, in run      doUnpersist=False,    File "/ssd/lsstsw/stack3_20171021/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_base/16.0-2-g852da13+6/python/lsst/pipe/base/timer.py", line 150, in wrapper      res = func(self, *args, **keyArgs)    File "/ssd/lsstsw/stack3_20171021/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_tasks/16.0-4-g08dccf71+3/python/lsst/pipe/tasks/characterizeImage.py", line 349, in run      background=background,    File "/ssd/lsstsw/stack3_20171021/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_base/16.0-2-g852da13+6/python/lsst/pipe/base/timer.py", line 150, in wrapper      res = func(self, *args, **keyArgs)    File "/ssd/lsstsw/stack3_20171021/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_tasks/16.0-4-g08dccf71+3/python/lsst/pipe/tasks/characterizeImage.py", line 428, in characterize      apCorrMap = self.measureApCorr.run(exposure=dmeRes.exposure, catalog=dmeRes.sourceCat).apCorrMap    File "/ssd/lsstsw/stack3_20171021/stack/miniconda3-4.3.21-10a4fa6/Linux64/meas_algorithms/16.0-6-g2dd73041+3/python/lsst/meas/algorithms/measureApCorr.py", line 245, in run      (name, len(subset2), self.config.minDegreesOfFreedom+1))  RuntimeError: Unable to measure aperture correction for required algorithm 'modelfit_CModel_exp': only 1 sources, but require at least 2.  {code}
Answer: 71288.0

User story: "Investigate options to run three single-repo pipe_analysis pipelines (visitAnalysis, coaddAnalysis, colorAnalysis, as-is) at larger scales on Verification Cluster. Use existing tools if possible. This is for the short term only. "
Answer: 554837.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: "Update the VPN documentation at https://nb.lsst.io/getting-started/logging-in.html#step-1-use-the-ncsa-vpn-with-cisco-anyconnect according to new standards:    {quote}FYI.  July 27th new VPN is required, and old VPN will be turned off.   Check the status page for details.   It's highly to switch to new VPN now and don't wait for 7/27 to switch.   New VPN does require DUO (2 factor).   Status page has details and how to get it all working.{quote}    https://lsstc.slack.com/archives/C2K6D7R61/p1531343203000173    - Status page: https://confluence.lsstcorp.org/display/DM/LSST+Service+Status+page  - Duo docs: https://wiki.ncsa.illinois.edu/display/cybersec/Duo+at+NCSA"
Answer: 21223.0

User story: "Make some small improvements to the {{stack_package}} template that reflect current practices:    - Add {{pyList}} argument to {{tests/Sconscript}}  - Delete ups/*.build  - Fixup {{setup.cfg}} according to best practices"
Answer: 4055.0

User story: "Adapt the {{pipe_analysis}} scripts to be compatible with the changes coming out of RFC-498.  Also make accommodations for it to be backwards compatible with catalogs run on older, pre-RFC-498, processed catalogs."
Answer: 69038.0

User story: "Create a jupyter notebook to demonstrate how to use scarlet and the new LSST deblender on multi-band images."
Answer: 47788.0

User story: "The multi-band deblender needs to be updated to use the new multi-band classes and fit in the same task structure as the current deblender."
Answer: 20517.0

User story: "obs_subaru has many bare {{except}} usages. Fix these and make the codebase pass flake8."
Answer: 8648.0

User story: "Currently the deblender is run as part of the {{MeasureCoaddSources}} task. In order to make it easier to swap out the current and future deblenders , {{SourceDeblendTask}} should be pulled out and placed in a new {{DeblendCoaddSourcesTask}}, along with an option to run {{MultibandDeblendTask}} instead. The current version of SCARLET also needs to be added to the stack as a 3rd party package."
Answer: 40464.0

User story: "When running this query  {code:java}  SELECT offset, mjdRef, drift  FROM LeapSeconds   WHERE whenUtc = (  SELECT MAX(whenUtc)   FROM LeapSeconds   WHERE whenUtc <= NAME_CONST('nsecs_',39900600000000000000000000)  )  {code}  qserv fails with the error    {{ERROR 1146 (42S02): Table 'qservResult.result_4492' doesn't exist}}"
Answer: 151.0

User story: "Write a presentation about the current status of the deblender for the Science Collaboration Chairs (to be presented on Tuesday, July 17, 2018)."
Answer: 4220.0

User story: "Update LDM-533 with latest test cases added in jira.         This will update the entire document to use the new approach.  There will be some differences ion the layout but there should not be any difference in the content derived from the existing issue of the test specification.     "
Answer: 4714.0