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: "We noticed a significant performance degradation on the SQuaSH API after DM-16300 when posting verification jobs to InfluxDB. I suspect that the problem is flask, redis, and celery running on the same pod with increasing memory usage so that the pods get evicted.  But we need more instrumentation to understand what's going one. I have started this with the honeycomb python client. Since we are using influxdb+chronograf for the science pipelines metrics I think telegraf is a good option for the SQuaSH API monitoring. "
Answer: 4424.0

User story: "At the moment the HeaderService uses the function  \{\{read_scamp_head()}} to read in the header templates. This function does not have the ability to ignore lines with comments. The simplest and fastest solution would be to clone and modified that function and make it part of the headerservice."
Answer: 14324.0

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

User story: "Identify the most obvious error cases for the HeaderService and implement the corresponding error codes for them. The most obvious one is timing out of {{endOfImageTelemetry}} and report the appropriate code, but other need to be investigated.     For the timeout error, we'll need to major changes:   * within salpytools {{waitEvent}} function should return {{True}} if the function actually times out.   * within the HeaderService, if {{waitEvent}} for {{endofImageTelemetry}} return True, them the HeaderService should send the SAL event {{ATHeaderService_errorCode}} with appropriate number (between 3000-3999)"
Answer: 142857.0

User story: "New version of ts_sal and ts_xml have been committed to master by T&S. The new ts_xml needs to be rebuilt and the HeaderService and salpytools need to be tested against this new version."
Answer: 45968.0

User story: "Prepare list of project needs, milestones, activities, and current status as input into planning process."
Answer: 10102.0

User story: "Based on user feedback, there are some small improvements to the [stack_package template|https://github.com/lsst/templates/tree/master/project_templates/stack_package]:    * The {{.gitignore}} package should include {{.coverage}} and {{bin/}}.  * {{base}} is a necessary dependency out-of-the-box to provide {{lsstimport}}.  * {{utils}} is a necessary dependency out-of-the-box to provide unit test support.  * Include [W504 as an ignored flake8 rule|https://community.lsst.org/t/changes-to-baseline-software-versions/3366]"
Answer: 45039.0

User story: "Changes in multiband.py removed a base class that was only loosely tied to the derived classes and moved shared functionality out into free functions. At the time of merge, qa_explorer was not changed as it was not part of the main stack and so the dependency change went unnoticed.    This ticket will fix the inheritance breakage in WriteObjectTableTask and clean up some coding standards in the file it is placed in."
Answer: 1799.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "As requested in the meeting on Oct 26, check the history and notes from the past few months and compile a summary showing how the biweekly HSC-RC2 reprocessing could use software packages different from strictly the weekly tags."
Answer: 87479.0

User story: "add parser unit tests and integration tests for arithmetic operators, logical operators, bit operators, and comparison operators to verify the parser code. Make tickets to implement missing features as needed."
Answer: 66190.0

User story: "Per SODA1.0, the POS parameter for specifying the dimensions and shape of image cutouts includes: CIRCLE, RANGE, POLYGON. These are defined by their UCDs.    Imgserv will use afw as primary source of functions for these operations, with astropy as secondary or backup."
Answer: 230739.0

User story: "Register Imgserv as SODA-compliant service in VO registry, including \{sync} resource, service availability and capabilities."
Answer: 230748.0

User story: "It looks like <exposure>_wcs datasets are coming from the header (which may be an approximation) instead of the true WCS in the FITS binary tables.  Fix this, and add support for more components if it's easy to do so.    Note that using the header was once thought to be necessary to do this efficiently, but in fact there's always been a trick to get anything out of the binary tables efficiently (due originally to [~price], I think): load a 1-pixel subimage of the exposure, and pull the component out of that.    However, since DM-15500 we've had an {{ExposureFitsReader}} class that provides direct and efficient access to all of those components without that trick, and that's what we should use here."
Answer: 200262.0

User story: "The latest SODA 1.0 Recommendation from IVOA focuses on image cutout and stitching operations, in addition to the standard VO service registration.         For reference, see [SODA 1.0|http://www.ivoa.net/documents/SODA/20170604/REC-SODA-1.0.html]"
Answer: 230930.0

User story: "The scisql library (UDF extensions), designed for MySQL, is needed to support spgeom functionality.      In order for metaserv db to support queries involving spgeom terminology, as in case of supporting ADQL, it must have scisql installed.         For reference, here's the repo for scisql: https://github.com/<USER>scisql"
Answer: 137073.0

User story: "DRP accidentally let a print statement slip through to master. Remove it.    This is a first ticket Andres, and also includes familiarizing himself with our workflow.           "
Answer: 10033.0

User story: "For historical reason, the image metadata is stored in QServ db in PDAC.   But really it should be in metaserv db, as none of QServ unique capabilities are needed for the image-related searches.    So  the proposal here is to move all the image metadata to Metaserv DB, along with installing scisql, then imgserv can cut off its existing dependency on QServ."
Answer: 137076.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: "Ensure the header templates are unmodified and therefore undefined values are preserved when no data is available from SAL for a given keyword."
Answer: 6998.0

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

User story: "Continue developing the change request to incorporate the updated thinking on Solar System data products and algorithms.    The deliverables of this element include:   * Development timeline for the next 6 months, sufficient to support the next development cycle planning. ✅   * Draft long-term (4-yr) plan in form of a list of milestones and a Gantt chart. ✅   * Updates to DPDD ✅   * Updates to LSE-61   * Updates to LDM-151 ✅   * Updates to LSST Schema Document ✅   * Resolution of LSST-MPC MOU    [~<USER> and [~<USER> will be collaborating on this story (splitting the story points 50:50)."
Answer: 388045.0

User story: "Prepare change request documentation including timeline and set of milestones for MOPS development with focus on the upcoming sprint.     Deliverables: Preliminary MOPS development GANTT chart / timeline"
Answer: 49322.0

User story: "Get MOPS, sims_maf / sims_movingObjects for Solar System science running on the verification cluster at NCSA. Document the resulting setup. Work will be done jointly with [~<USER>."
Answer: 262489.0

User story: "Monthly review of LSST-MPC collaboration status, presentation of progress, review of issues."
Answer: 40429.0

User story: "Shepherd the finalization of LSST-MPC MOU text, taking into account any concerns on the LSST side. This includes the collection of feedback from LSST senior management, and incorporation of feedback into the MOU text. It also includes keeping in touch with the MPC to understand any concerns their management has raised, and respond to them if possible.    The deliverable the MOU text that the LSST is able to sign."
Answer: 49328.0

User story: "Create accounts for the Minor Planet Center staff on the epyc machine at UW, and set up a basic PostgreSQL server. The MPC staff will use this to set up a replica of the internal MPC database, running on SSDs. This will later be used to test the existing database throughputs, and whether they can scale to LSST requirements."
Answer: 49332.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 fix on DM-16392 is easiest to confirm on the {{pipe_analysis}} processing outputs of the RC2 bi-weekly reprocessing.  The issue was that the order aperture corrections were being added to the schema was not deterministic (loop was being done on a set).  As a result, when attempting to concatenate all patches of a given tract into a single catalog and using a template schema, the aperture corrections were often pointing to different key offsets, thus getting the wrong column appended into catalog.  This issue was discovered in perusal of the plots output by {{pipe_analysis}}'s *compareCoaddAnalysis.py* and *compareVisitAnalysis.py* when comparing outputs from one reprocessing to the previous one (between which no algorithmic changes had been made that could've caused this discrepancy, backed up by the identical flux measurements for the same points).  This ticket is to capture the effort that went into diagnosing the bug and ensuring the fix was successful after the {{w_2018_44}} -- assuming the fix lands on time -- is completed."
Answer: 65973.0

User story: "These somehow escaped the purge of DM-15767.  They *should* no longer be in use, and hence easy to remove."
Answer: 308.0

User story: "When he left the project in late 2017, <USER>was in the middle of a substantial refactoring of the ip_diffim codebase. Review these changes, understand what was being planned, and think about how this relates to the view of ip_diffim you developed on DM-16409.    It's unreasonable to expect you to understand all the background to this work soon after joining the project. After you have some idea of what's going on, please chat to [~<USER>, [~<USER> and [~<USER> to get their take on it.    Key tickets to take a look at in this context are:    * DM-5294  * DM-5295  * DM-3704  * DM-11654  * DM-13831    The end goal of this ticket is to decide if we want to invest further work on David's changes, or if we want to move in another direction. Ultimately, that will be a decision that we take jointly in sprint planning, but we'd like you to take this opportunity to develop your own opinions first!"
Answer: 454545.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: "[ip_diffim|https://github.com/lsst/ip_diffim] is the home of image differencing algorithms within LSST. Read through the current {{master}} branch, understand what's there and think about the structure.    Understanding the way ip_diffim is structured will (at a minimum) involve developing some familiarity with the pipe_base and meas_base frameworks. The former defines the structure of “tasks”, which form the basis of LSST pipelines; the latter, the “measurement framework” which provides a system of plugins for measuring source properties given a collection of pixels. A good target for this ticket would be to understand:    - What {{Task}}​s exist in the ip_diffim package, and what they do;  - Major {{Task}} configuration options;  - What measurement plugins exist in ip_diffim, and what they do.    Detailed understanding of how the algorithms are implemented isn't important for now, as long as you have a good mental map of what's available and the large scale structure of how the package fits together.    The following documentation may be helpful:    - https://pipelines.lsst.io/v/daily/modules/lsst.pipe.base/task-framework-overview.html  - https://pipelines.lsst.io/v/daily/modules/lsst.meas.base/intro.html    "
Answer: 157635.0

User story: "From a customer:    On our Qserv install queries using NOT LIKE return the same as those using LIKE, we’re on a fairly recent build (a week or so old). Seems like an issue but I’m not sure if LIKE is supposed to be implemented or not.         select shortName from Filter where shortName LIKE ‘Z’;    ±----------+  | shortName |  ±----------+  | Z |  ±----------+    select shortName from Filter where shortName NOT LIKE ‘Z’;  ±----------+  | shortName |  ±----------+  | Z |  ±----------+              ...we need to verify LIKE/NOT LIKE is getting handled correctly, and fix it if not.     Note, this kind of thing should not be falling through the cracks with antlr4 after DM-16218 is through review and checked in. (If the NOT in NOT LIKE is not handled then the parser code should throw a ParseException)"
Answer: 5907.0

User story: "It wound up being out-of-scope in DM-14762 to exclude edges (and any other bad/flagged CCD regions) from the object/source plots I made while completing that ticket. It is possible to do now by digging into the diaSrc catalogs, but that will be slow, so we may be better off waiting for the association database to include xy pixel information for sources."
Answer: 122143.0

User story: "Add support for hue preserving rgb. Might need a variant of set_stretch function."
Answer: 47309.0

User story: "for more realistic tests I'd like to add support for running ap_proto on many hosts, maybe using MPI or some other sort of IPC (it should be a low-level data exchange so there is no critical point here)."
Answer: 38896.0

User story: "When splitting apart these two tasks, the writeMetadata method overload in the old base class was not propagated to each of the merge tasks. Add the no-op method overload to each of the merge tasks."
Answer: 1271.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: "Related to DM-16333, we want to retroactively load the {{ap_verify}} CI jobs into SQuaSH to have the [complete history of these runs|https://ci.lsst.codes/blue/organizations/jenkins/scipipe%2Fap_verify/activity].    With this ticket we'll also test a change introduced by DM-16300 into the SQuaSH API. Now {{verify}} metrics are also sent to InfluxDB and can be visualized using the [Chronograf UI|https://chronograf-demo.lsst.codes].    We'll first do this on the SQuaSH demo instance and then replicate to production in another ticket when DM-16333 is complete."
Answer: 50809.0

User story: "Do release 17.0 of science pipelines"
Answer: 182567.0

User story: "Run meetings to prepare for the SLAC bootcamp.  Prepare agenda for the bootcamp.  Iron out logistics.  Copy data to the appropriate location at the LDF."
Answer: 1.0

User story: "Prepare a demo using dask to present at the LSP workshop."
Answer: 5.0

User story: "The {{obs_lsst}} package needs to be updated to take into account the corner rafts.  This also requires some preburner code to generate gain images to use as flats and to repackage into a format closer to that expected from LSSTCam"
Answer: 7.0

User story: "Investigate dask as an option for doing distributed analysis.  Ideally this would lead to a proof of concept visualization that is only possible with this kind of system."
Answer: 10.0

User story: "Test stand data has a totally different definition for the sequence number - it's the number within a sequence (Fe55, flats, darks, etc) and there are many sequences per day, hence this number is not unique within a day like it might be elsewhere.    It therefore can't be used with the dayObs for identifying exposures, and will be totally removed, and replaced with visit numbers.    Also, apply other fixes to necessary for bootcamp to run."
Answer: 9869.0

User story: "As the shared stack at /software has been updated to w_2018_41  (https://community.lsst.org/t/shared-stack-updates/3328 ) and the DESDM stack uses it, redo the minimum necessary steps and update DM-16054 to run hsc_test_hscmini.wcl  with  w_2018_41."
Answer: 52.0

User story: "Begin preparations for support the stack tutorial and/or other needs at the American Astronomical Society meeting January 6-10: system setup, login creation, install DM tools, etc."
Answer: 71800.0

User story: "System setup, login creation, install DM tools, etc., as necessary to support LSP use for the Commissioning Camera Boot Camp November 14-15. Monitor state of the system during the event."
Answer: 28487.0

User story: "Someone (RHL) used an internal cameraGeom interface ({{camera._nameDetectorDict}}) to look up a detector from a camera.  Fix this."
Answer: 28.0

User story: "Add a few function overloads to support working with Eigen matricies in mixture models"
Answer: 6983.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: "Hook up what I've worked on so far with the CADC TAP Demo to QServ.    At least QServ looks like mysql to start, so I'm going to start there.  Hooking up a mysql server to CADC, then making it work, then pointing it at QServ and seeing if I can get it to work.    After that, then I need to be able to route queries to the appropriate backend SQL server (QServ, or postgres, or oracle, etc)."
Answer: 103980.0

User story: "The point of this ticket is to get some experience writing Kafka producers and consumers in Python, and explore Avro and message schemas. This code will go in https://github.com/lsst-sqre/kafka-efd-demo    Once this is done, a later ticket can start creating more realistic Kafka clients that mock the EFD more directly."
Answer: 12890.0

User story: "Start the container as an only semi-privileged user whose role is to provision the actual user and then sudo to it."
Answer: 1889.0

User story: "I'm finding that ever since upgrading to macOS Mojave I'm not getting EUPS binaries for newinstall installations of {{lsst_distrib}}.    I'm always doing a clean newinstall installation. I'm using recent tags like {{d_2018_10_30}}.    Here are some environment variables:    {code}  LSST_CONDA_ENV_NAME=lsst-scipipe-fcd27eb  CONDA_SHLVL=1  CONDA_DEFAULT_ENV=lsst-scipipe-fcd27eb  CONDA_EXE=/Users/<USER>lsst/pipelines_lsst_io_stack/stacks/d_2018_10_30/python/miniconda3-4.5.4/bin/conda  CONDA_PREFIX=/Users/<USER>lsst/pipelines_lsst_io_stack/stacks/d_2018_10_30/python/miniconda3-4.5.4/envs/lsst-scipipe-fcd27eb  CONDA_PROMPT_MODIFIER=(lsst-scipipe-fcd27eb)  CONDA_PYTHON_EXE=/Users/<USER>lsst/pipelines_lsst_io_stack/stacks/d_2018_10_30/python/miniconda3-4.5.4/bin/python  EUPS_SHELL=sh  EUPS_DIR=/Users/<USER>lsst/pipelines_lsst_io_stack/stacks/d_2018_10_30/eups/2.1.4  EUPS_PATH=/Users/<USER>lsst/pipelines_lsst_io_stack/stacks/d_2018_10_30/stack/miniconda3-4.5.4-fcd27eb  SETUP_EUPS=eups LOCAL:/Users/<USER>lsst/pipelines_lsst_io_stack/stacks/d_2018_10_30/eups/2.1.4 -f (none) -Z (none)  PYTHONPATH=/Users/<USER>lsst/pipelines_lsst_io_stack/stacks/d_2018_10_30/eups/2.1.4/python  EUPS_PKGROOT=https://eups.lsst.codes/stack/src  {code}     Let me know what other system stats I can provide to help debug why my machine isn't matching up with binaries."
Answer: 668598.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "[~<USER> reports that he's found a reference catalog with fluxSigma errors that can no longer be read by our code in w_2018_39 and later.    How to reproduce:       {code:java}  import lsst.meas.algorithms    keys = lsst.meas.algorithms.getRefFluxKeys(ref.schema, 'lsst_u_smeared')    assert keys[1] is not None     {code}  I suspect new backwards-compatibility code for flux to instFlux broke older backwards-compatiblity code for Sigma to Err."
Answer: 3010.0

User story: "Dont have TN series in TSS ..  but this should be  a tech note."
Answer: 17866.0

User story: "The obs_lsst package should be included in the upcoming v17 pipelines release.    Note that this can only be done after:    * It has been renamed from obs_lsstCam to obs_lsst;  * The package has appropriate tests;  * The package has been appropriately reviewed;  * An RFC has been passed.    This ticket exists to cover the process of shepherding it through that process."
Answer: 139040.0

User story: "To support VO standards for querying a database,  it's crucial to know  ADQL and SQL-92 of which it's based upon, with some key modifications, particularly in specification of reserved keywords in astromath, as well as limiting SQL to read-only access via SELECT.... and the addition of TOP n as set limiter.    One way to examine or quantify the differences is to compare the BNFs (readily available) of the two variants. To facilitate this, the BNFs been converted to JSON (see attached files) format.    The main purpose of this ticket is to answer the following questions: just how compatible is ADQL with SQL-92, and furthermore with MySQL (or QServ)?  How best to support handling of ADQL (coming from external VO tools) queries in Qserv? "
Answer: 4132.0

User story: "Disk/optics were ordered in lieu of the entire system and parts were used from NCSA for this demo "
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: coaddAnalysis with HSC-RC2 tract=9615 filter=HSC-R data gave the following error:  {noformat}  Traceback (most recent call last):    File "/software/lsstsw/stack_20181012/stack/miniconda3-4.5.4-fcd27eb/Linux64/pipe_base/16.0-13-gb122224+8/python/lsst/pipe/base/cmdLineTask.py", line 388, in __call__      result = self.runTask(task, dataRef, kwargs)    File "/software/lsstsw/stack_20181012/stack/miniconda3-4.5.4-fcd27eb/Linux64/pipe_base/16.0-13-gb122224+8/python/lsst/pipe/base/cmdLineTask.py", line 447, in runTask      return task.runDataRef(dataRef, **kwargs)    File "/home/<USER>stack/pipe_analysis/python/lsst/pipe/analysis/coaddAnalysis.py", line 334, in runDataRef      postFix="_unforced")    File "/home/<USER>stack/pipe_analysis/python/lsst/pipe/analysis/coaddAnalysis.py", line 577, in plotSizes      labeller=StarGalaxyLabeller(), flagsCat=flagsCat,    File "/home/<USER>stack/pipe_analysis/python/lsst/pipe/analysis/analysis.py", line 104, in __init__      self.good = np.isfinite(self.quantity) & np.isfinite(self.mag) if self.quantity is not None else None  ValueError: operands could not be broadcast together with shapes (23872,) (23873,)  {noformat}    Other tracts/filters in HSC-RC2 finish without errors. A command to reproduce is   {noformat}  coaddAnalysis.py /datasets/hsc/repo/ --calib /datasets/hsc/repo/CALIB  --rerun RC/w_2018_42/DM-16095:private/user/name/coaddAnalysis  --id tract=9615 filter=HSC-R   {noformat}    This used to finish fine in early September with {{w_2018_36}} (before the DM-15869 issue). 
Answer: 41726.0

User story: "The purpose of this ticket is to demonstrate a basic Kafka cluster deployment in GKE. This cluster will be a testbed for Kafka applications during the DM EFD development.    A good starting point is the Confluent Helm chart: [https://github.com/confluentinc/cp-helm-charts]    Or the incubator chart in the main helm repo: https://github.com/helm/charts/tree/master/incubator/kafka"
Answer: 1419.0

User story: "[~<USER> found memory usage problems with MatchPessimisticB in extremely dense reference fields. This is due to larger data structures that the code makes to the searching steps as fast as possible. The complexity and size of these could be reduced enabling quicker task creation and lower memory overhead at the cost of slightly slower matching. This ticket will implement this reduction in complexity and compare to previous run times."
Answer: 132669.0

User story: "Understand the distribution of and peak densities of reference catalogs possible in Gaia."
Answer: 125593.0

User story: "Setup LDAP Groups to Support Generic JupyterHub Users    Update sssd.conf to show all_lsst Master Group    New LDAP Group for LSST2018 LSPdev Demos    Create a LSST Staff LDAP Group"
Answer: 115217.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: "Per LPM-121, LSE-279, all LSST systems should be using KRB for authentication and LDAP for authorization. Currently using LDAP for both (proxies to KRB). The longer this remains undone, the greater the deviation from LSE-279. Machines need to support LSST' s Unified IAM project."
Answer: 48292.0

User story: "to be used by keytab-host-key-auto-generation script"
Answer: 3.0

User story: "I refactorized the methods to extract the 3-D tables :    - It now determines in each cell the correct altitude and interpolate in z in between the 2 adjacent bin. The algorithm has been tested against the barometric pressure which is thought to be correctly reported by the SNF model. SNF and MERRA agree at 2 mBar, which is 3/1000. This is a good consistency check. However the ~10-20 mBar variability are not well correlated between MERRA and SNF, the amplitude in MERRA being about twice as small, and SNF having a set of unexplained default values at 618mB.  - the method has been further developed to integrate in each cell from top-of-the atmosphere down to a constant altitude.  - This has been used to measure PWV. A first control will be to estimate if it reduce the residuals between MERRA and SNF with respect to the previous integration down to a constant binding."
Answer: 8927.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: Bug encountered while trying to test the new astro metadata package that fixes obs_decam observatory longitude:    {code:}  dcrAssembleCoadd FATAL: Failed on dataId=DataId(initialdata={'filter': 'g', 'patch': '0,0', 'tract': 0}, tag=set()): ValueError: operands could not be broadcast together with shapes (2003,2003) (2000,2000) (2003,2003)   Traceback (most recent call last):    File "/Users/<USER>LSST/code/eups_distrib/stack/miniconda3-4.5.4-fcd27eb/DarwinX86/pipe_base/16.0-13-gb122224+4/python/lsst/pipe/base/cmdLineTask.py", line 388, in __call__      result = self.runTask(task, dataRef, kwargs)    File "/Users/<USER>LSST/code/eups_distrib/stack/miniconda3-4.5.4-fcd27eb/DarwinX86/pipe_base/16.0-13-gb122224+4/python/lsst/pipe/base/cmdLineTask.py", line 447, in runTask      return task.runDataRef(dataRef, **kwargs)    File "/Users/<USER>LSST/code/eups_distrib/stack/miniconda3-4.5.4-fcd27eb/DarwinX86/pipe_base/16.0-13-gb122224+4/python/lsst/pipe/base/timer.py", line 149, in wrapper      res = func(self, *args, **keyArgs)    File "/Users/<USER>LSST/code/eups_distrib/build/pipe_tasks/python/lsst/pipe/tasks/dcrAssembleCoadd.py", line 217, in runDataRef      results = AssembleCoaddTask.runDataRef(self, dataRef, selectDataList=selectDataList)    File "/Users/<USER>LSST/code/eups_distrib/stack/miniconda3-4.5.4-fcd27eb/DarwinX86/pipe_base/16.0-13-gb122224+4/python/lsst/pipe/base/timer.py", line 149, in wrapper      res = func(self, *args, **keyArgs)    File "/Users/<USER>LSST/code/eups_distrib/build/pipe_tasks/python/lsst/pipe/tasks/assembleCoadd.py", line 361, in runDataRef      inputData.weightList, supplementaryData=supplementaryData)    File "/Users/<USER>LSST/code/eups_distrib/build/pipe_tasks/python/lsst/pipe/tasks/dcrAssembleCoadd.py", line 378, in run      modelWeights)    File "/Users/<USER>LSST/code/eups_distrib/build/pipe_tasks/python/lsst/pipe/tasks/dcrAssembleCoadd.py", line 521, in dcrAssembleSubregion      maskedImage.image.array *= modelWeights  ValueError: operands could not be broadcast together with shapes (2003,2003) (2000,2000) (2003,2003)   {code}
Answer: 15935.0

User story: Based on a [Slack|https://lsstc.slack.com/archives/C2B6DQBAL/p1539799040000300] conversation, there are questions about how to build the pipelines.lsst.io site. This can be improved by doing two things:    # Link to the Developer guide pages on how to build the {{pipelines_lsst_io}} repo (locally and via Jenkins)  # Add a screenshot and review language on how to language on the "ltd slug" field of the Documenteer Jenkins job.
Answer: 1172.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "This ticket covers work to update the Discourse instance at community.lsst.org:    - Upgrade droplet to a 60GB disk 3GB RAM. We were running out of disk space on the 40 GB droplet and couldn't upgrade.  - Activate monitoring on the new droplet  - Upgrade to Discourse v2.2.0  - Switch to Lets Encrypt for TLS rather than purchasing a wild cart cert for *.lsst.org.    Notes on the Lets Encrypt upgrade: https://meta.discourse.org/t/setting-up-https-support-with-lets-encrypt/40709?u=<USER>
Answer: 1.0

User story: "The various camFlux fields in the existing reference catalogs are unused and their purpose is unclear (especially now that we have color term maps). We should remove them entirely from meas_algorithms."
Answer: 145251.0

User story: "Adding fluxErr to {{LoadReferenceObjectsTask.makeMinimalSchema()}} helps with some of the problem posed in RFC-535, while being uncontroversial. This will ensure that future reference catalogs have this field by default."
Answer: 73062.0

User story: "Following DM-16286, the shared stack build on Princeton systems is broken. We'll need to bootstrap a new shared stack to revive it."
Answer: 1125.0

User story: In this ticket we test several features of Chronograf for creating dashboards and as a result  we implement a "proof of concept dashboard" for validate_drp   - Display multiple time series plot  - Use the query builder to define the time series we want to display  - Combine more than one time series in a single plot (e.g. querying different databases)  - Use template variables to select a given property and make an interactive plot e.g. the dataset.  - Use static legend when grouping results by filter_name  - Test the export to (import from) JSON functionality  - Test the share functionality  - Use annotations on time series  - Use annotations on cells (available in Chronograf 1.7)  - Test Markdown/HTML content in cells (available in Chronograf 1.7)  - Keep a copy of the Dashboard on GitHub for version control
Answer: 59024.0

User story: "For any single points of failure found, identify and test mitigations, for production implementation as deemed necessary."
Answer: 76362.0

User story: "Define and determine what uptime is needed for Oracle RAC, and using current configuration, identify any single points of failure which put those uptime needs at risk."
Answer: 58952.0

User story: "List hardware and software specs for Oracle RAC as it currently exists, in preparation for identifying points of failure."
Answer: 8824.0

User story: "In TSEIA-83 we noted that Astropy has been generating time strings in a non-standard format.  Fix Astropy."
Answer: 1772.0

User story: "Tiago would like TSS added to the types of tickets sqrbot knows about."
Answer: 110.0

User story: "When reviewing DM-16295 [~<USER> asked me to file a ticket for checking the use of the {{datetime}} package in {{obs_lsst}}, so here it is.    Jim, if you want to add your thoughts/comments/motivations, feel free :)"
Answer: 139492.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: "Scarlet needs to have MACOSX_DEPLOYMENT_TARGET set to at least 10.9 to compile on Mojave."
Answer: 3.0

User story: "Treecoor needs the same fix of MACOSX_DEPLOYMENT_TARGET as needed by packages such as coord (DM-16025)."
Answer: 2.0

User story: "Change the qserv unit tests that are using ANTLR2 to use ANTLR4.     Add a test to check for expected parse failures."
Answer: 42.0

User story: "Once the budget has been sent to AURA and the requisition has been approved at AURA, NCSA will receive a contract that will need to be signed and returned to the project "
Answer: 142699.0

User story: "We have received the contract from AURA, we need to do some work to finalize FFY18 spending and submit the finalized contract to the project"
Answer: 142700.0

User story: "Submit final acquisition plan to project for review - includes finalizing acquisition plan and budget. Does not include the actual approval of the plan, just up to the plans submission"
Answer: 8724.0

User story: "I have been asked to take a look at obs_lsstCam to do a mini review."
Answer: 37450.0

User story: "DM-15537 renamed couple of things in gen3 registry, those names should also be changed in pipe_supertask."
Answer: 258.0

User story: "We should add centralized code that maps the strings identifying these things to instances, and use it in all high-level APIs that accept them.  Right now we are inconsistent about whether APIs expect e.g. a full DatasetType instance or just its name, and in many places we should support either.     "
Answer: 505996.0

User story: "Per [discussion on Slack of 2018-10-25|https://lsstc.slack.com/archives/C2B6DQBAL/p1540481139000100], there's a certain amount of ambiguity in our developer documentation about formatting docstrings. Please propose some text to make this clearer."
Answer: 163556.0

User story: "Participate in the Data Management System Science Team group meetings, and pursue emergent activities."
Answer: 8931.0

User story: "I implemented a stop-gap solution to DM-16235 (using the original calibration for the mean calibration so that mean calibrations are never negative). This ticket is to finish the integration code that was started there, so that we can compare the jointcal means with the original processCcd calibration means.    [~<USER> suggests using the Chebyshev1dBasis in {{lsst.geom.polynomials}} to help implement the integration code."
Answer: 68752.0

User story: "Update Gaia performance in overview paper - include new references."
Answer: 27404.0

User story: "need to set agenda for a few telecons and organise committee"
Answer: 1418.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 SQuaSH API already has the capability of executing Celery tasks, e.g. we have a task to upload verification jobs to S3.    It makes sense to implement another task to send the time series data (metric values, tags, and timestamps) to InfluxDB.    The transformation of  a SQuaSH job to InfluxDB line maps each verification package to an InfluxDB measurement, job metadata to InfluxDB tags and metric names and values to fields.  "
Answer: 18782.0

User story: "The new API of ap_association in DM-15588 assumes that all SourceCatalogs fed into are calibrated data products with column names close to that of the DPDD and Ppdb schema.    This ticket creates a task to convert outputs from ip_diffim into a usable format for ap_association to be use in association and set to the PPDB to be written."
Answer: 13131.0

User story: "I anticipate this involving some changes to the Instrument base class, and hence changes to our only existing implementation of it in obs_subaru as well.     "
Answer: 475763.0

User story: "A new version of flake8 came out last night.  This is breaking pull requests because the flake8 used by Travis is not pinned.  On this ticket I will add new versions of pycodestyle and flake8 and determine how big the issue is, fixing things if that is feasible. If this is a large issue then the alternative is to consider editing every setup.cfg file to pin the flake8 version."
Answer: 8772.0

User story: "There will be several changes necessary, don't know what they are till we try and they pop up.    Put them all on this ticket."
Answer: 1779.0

User story: "obs_lsst has some unnecessary overrides of obs_base datasets and some datasets that probably shouldn't exist at all.  For the latter we should try to track down where they were cargo-culted from as well."
Answer: 1758.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 {{getCurrent()}} method in salpytools should have the ability to return None (or False) when no telemetry is present for the topic requested. At the moment, when no SAL information can be retrieved, it is returning an uninitialized SAL data object (i.e. myData) which by default contains zeros for floats and integers and empty '' for strings. This behavior is not desired, as it doesn't keep undefined values as defined in the header templates.   "
Answer: 21338.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: "Check test.cilogon.org for regressions."
Answer: 1.0

User story: "In DM-14011 the lsstsw conda packages were updated.  This technically did not change the baseline for minimum supported package versions but after some debate (RFC-537) it is deemed desirable that Jenkins should always track our minimum version baseline.  If we say it's a minimum we should be testing that minimum.    This ticket will update the EUPS stub packages for astropy, numpy, matplotlib, and scipy to match those set in DM-14011."
Answer: 3131.0

User story: "At least one telecon and trying to sort out the invitee list"
Answer: 3963.0

User story: "Before starting with 17.0 release activities it is recommended to do a 16.1 release, in order to ensure that the scripts and the jobs are ready.         In this way, the process to get to the 17.0 will be smoother and quicker, and will increase the chances to have it ready by the end of November.          No announcements will be done for the 16.1, nor release note information will be collected.     Also I will not verify that the 16.1 release will work on all (usual) platforms, unless there is the time to do so (best effort).         In order to ensure that the process has been concluded successfully:    - tags will be present in the github repos    - packages will be available in the eups filesystem    - docker images should be available for download         Additionally, in order to make this meaningful, no changes should be made in the CI scripts related to the release process, from the cut of 16.1-rc1 until the completeness of the 17.0 release, unless they are clearly affecting the release process (this should be obvious)."
Answer: 51610.0

User story: "Create the first release candidate for 17.0 release"
Answer: 164188.0

User story: "Some of the fields in {{sample-avro-alert}} no longer appear in the DPDD. This ticket is to update the schemas accordingly and produce an average size estimate relevant to https://jira.lsstcorp.org/browse/RFC-538"
Answer: 82222.0

User story: Add a datatype to exposures.yaml for calexps with fake sources added. Currently this is called "calexp_fakes", open to suggestions if anyone hates this.
Answer: 156988.0

User story: "Worker level data exists in the cloud, but deploying it in a new cluster requires regenerating CSS metadata, schema, secondary index and chunks lists."
Answer: 194501.0

User story: "Move data from bucket storage to qserv-ready persistent disks on the k8's cluster for both WISE and KPM30"
Answer: 275551.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: It looks like PipelineTask.runQuantum (at least) uses iteration through the Config instance to find all of the input and output DatasetTypes.  This at least partially ignores the get*DatasetType methods, which should be permitted to add and modify the set of DatasetTypes processed.    Fixing this may involving changing the signatures of the get*DatasetType methods a bit - there is at least some information (e.g. "scalar") that is currently only available from the configs, and that probably needs to be forwarded through the get*DatasetType methods so they can be considered the final source of truth by PipelineTask and all activators.     
Answer: 5932.0

User story: "There seems to have been a merge conflict on the notebook in    [https://github.com/<USER>watch]         I got Jeff to check out an old one which is fine for now,    There is also some code in the notebook which should just be in a python file."
Answer: 398.0

User story: "There are several SearchProcessors that insist on saving the results as IPAC table before passing it on.   This may cause lost of meta information because IPAC table does not have the facility to store them.  Identify and fix these processors."
Answer: 14424.0

User story: "The existing slack plugin is deprecated.     !image-2018-10-22-13-07-25-177.png|thumbnail! "
Answer: 862762.0

User story: "Sync SQuaSH prod database with InfluxDB.    "
Answer: 1735.0

User story: "When ATS system development began, the overarching desire by all was to get the ATS system running only. After implementing the ATS Forwarder, it became clear that some areas would need to be modified in order to work correctly for the general archiver (as well as prompt processing and catchup archiving) while keeping the Forwarder a generic component that will work for all CSCs.    These things include:    1) Making separate intermediate data containers for amp segment data so that data is not overwritten(the ATS only needs one area per image_id, but the full telescope will need multiple instances of these data structures.    2) Making certain that data for a particular raft image can remain resident in memory without being overwritten, even if two image exposures begin to overlap.    3) Proper cleanup of intermediate, temporal data.    This set of changes addresses these issues."
Answer: 9.0

User story: Download, ingest and play with atmospec dev data.    "Play with" means create a master bias using some of the data, use it to debias the input frames to that master to check for consistency, use it to debias the spectrum frames, and debias other bias frames, and see how it goes.
Answer: 6.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 old meas_extensions_ngmix tried to wrap ngmix functionality within the constraints of DM's existing SingleFrameMeasurement framework, which immediately rules out a lot of what ngmix does well (fitting multiple bands or epochs together).  It also never really got off the ground.    Blow away the SFM plugins that currently exist, and replace them with (to start) a CmdLineTask that processes all bands in a patch at once, and loops over optionally-deblended objects without trying to package that up in some kind of plugin framework.  This task will depend on all current pipe_tasks multiband outputs (or at least deepCoadd_ref).    Once we've gained some experience with the actual APIs of measurements like this have, we can consider factoring that out into a new measurement framework in e.g. obs_base."
Answer: 192115.0

User story: "KevinR has started a  management plan including org chart roles etc."
Answer: 335897.0

User story: "Look at obs_lsst with [~<USER> - perhaps after [~<USER> adds some tests ...    1 point enough ??"
Answer: 33236.0

User story: "Look at the java code in TSS"
Answer: 7257.0

User story: "Added PST and PSTN to the texmf"
Answer: 5.0

User story: "Implement a method the atHeaderService to read and load the meta-data present in the configuration of atCamera."
Answer: 853941.0

User story: "Move the [pyprofit|https://github.com/lsst-dm/pyprofit] code into a new [multiprofit|https://github.com/lsst-dm/multiprofit] repository"
Answer: 140896.0

User story: "Once DM-15914 merges switch the VisitInfo translators in obs_decam and obs_cfht to use the astro_metadata_translator infrastructure."
Answer: 18779.0

User story: "Identify still missing or undefined sources of meta-data for the atHeaderService and make requests to individual CSC to identify how to publish these as part of SAL Events/Telemetry."
Answer: 2.0

User story: "The following packages:         ctrl_prepdc3b - data challenge 3b prep scripts    ctrl_prepdc3a - data challenge 3a prep scripts    ctrl_dc3pipe - configuration for data challenge 3    ctrl_dc2pipe - configuration for data challenge 2    ctrl_pipevis - Alert production visualization    ctrl_sched - job blackboard scheduler    ctrl_evmon - Complex event processing system use for pipeline monitoring         Are no longer in use and should be moved to lsst-dm/legacy status."
Answer: 819.0

User story: "The CSC being used for the ATS system is a simplified version of the general Archiver CSC. There have been a few changes in the ATS device that need to be present in the Archiver device. While most if not all of these changes have been merged into the Archive device, it must be tested and the unit test for the Archiver CSC updated if necessary."
Answer: 350557.0

User story: "The code to allow this properly has been integrated with the ATS branch, and works for the ATS, but has not yet been tested at raft scale.    This ticket is a dependency on the successful conclusion of ticket number DM-16171."
Answer: 350567.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: "Now that successful image transfer to the archive can be tracked in the EFD as a telemetry event, we can begin prototyping the software that compares the DAQ image list with the list of images that have been successfully processed, and develop a backlog work list. This capability will be integrated with the DM base CSC shell."
Answer: 711721.0

User story: "Using the ts_xml eupspkg.cfg.sh as a basis, create a CMakeLists.txt that will enable simplified building of CSC interfaces based on their XML descriptions."
Answer: 21372.0

User story: "This contributes to build & deploy of all CSCs, including DMs."
Answer: 19800.0

User story: "attend LSP workshop at NCSA"
Answer: 31592.0

User story: "Attend the LSP workshop at NCSA. "
Answer: 31942.0

User story: "The wavefront sensing chips do not run through {{runIsr.py}} with master of {{obs_lsst}} (housed in the {{obs_lsstCam}} repository.  Suggest changes to make that happen."
Answer: 18416.0

User story: "{code}  import lsst.daf.persistence as dafPersist  tract = 9813  visit = 23692  ccd = 62  root = '/datasets/hsc/repo/rerun/RC/w_2018_41/DM-16011-jointcal'  butler = dafPersist.Butler(root)  photoCalib = butler.get('jointcal_photoCalib', visit=visit, ccd=ccd, tract=tract)  {code}  {code}  >>> photoCalib.getInstFluxMag0()  -278609934862735.6  >>> butler.get('jointcal_photoCalib_filename', visit=visit, ccd=ccd, tract=tract.getId())  ['/datasets/hsc/repo/rerun/RC/w_2018_41/DM-16011-jointcal/jointcal-results/HSC-R/9813/jointcal_photoCalib-0023692-062.fits']  >>> str(photoCalib)  'TransformBoundedField on Box2I(Point2I(0, 0), Extent2I(2048, 4176)) with mean: -3.59376e-15 err: 2.98536e-17'  >>> photoCalib.instFluxToMaggies(100)  -3.589247456278528e-13  >>> photoCalib.instFluxToMaggies(100, lsst.geom.Point2D(0,0))  3.9565953264617065e-12  {code}"
Answer: 12988.0

User story: "Get up to standards and move https://github.com/lsst-dm/qa_explorer/blob/master/python/lsst/qa/explorer/writeObjectTable.py and  https://github.com/lsst-dm/qa_explorer/blob/c284960e91d337a746300378fe7a9f4f2c70fca5/python/lsst/qa/explorer/postprocess.py    into the stack under pipe_tasks."
Answer: 573538.0

User story: "Ingest files into a Gen2 butler."
Answer: 360587.0

User story: "Transfer raw image files from the CCOB to NCSA."
Answer: 223022.0